• Content Count

  • Joined

  • Last visited

About kjn260

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi All, So after some learning and playing, there are three options that worked for me: 1) use nanopi-air config, use armbian build to patch device tree for uboot, and patch device tree for kernel to add sun8i emac device. Patch air defconfig to include CONFIG_SUN8i_EMAC = Y. 2) use nanopi-neo config, use armbian build to patch device tree for uboot , and patch device tree for kernel to add mmc device(s). Use Igor's patch above to patch the neo defconfig. 3) write custom board configuration, defconfig, and device trees (uboot and kernel) for a "
  2. Ok, so the problem seems to be the same as ethernet to air image as emmc to neo image? Is it as simple as patchinng the u--boot nanopi_neo_defconfig : CONFIG_MMC_SUNXI_SLOT_EXTRA=2? or does the device tree also need updating to initialise the eMMC device?? ## u-boot/arch/arm/dts/sun8i-h3-nanopi-neo-air.dts ## &mmc0 { pinctrl-names = "default"; pinctrl-0 = <&mmc0_pins_a>, <&mmc0_cd_pin>; vmmc-supply = <&reg_vcc3v3>; bus-width = <4>; cd-gpios = <&pio 5 6 GPIO_ACTIVE_HIGH>; /* PF6 */ cd-inverted; status
  3. Both, but this is only based on my observations of the function in the nano pi neo. Does ethernet have to be enabled in u-boot to properly initialize the device for the kernel driver?
  4. Hello Igor, Forgive my ignorance of the armbian build environment - I think I have already done what you asked: 1) Create file nanopi_neo_air_defconfig_2 to include line "CONFIG_SUN8I_EMAC=y" 2) diff -Naur nanopi_neo_air_defcong nanopi_neo_air_defconfig_2 > nanopi_core_emac.patch (contents quoted above) 3) copy nanopi_core_emac.patch to /userpatches/u-boot/u-boot-sunxi 4) run build environment "sudo ./compile.sh" 5) option for full image 6) note application of patches (from: output/debug/patching.log): ... Processing file /home/armbian/
  5. There are obvious differences here too: https://github.com/RobertCNelson/u-boot/blob/master/arch/arm/dts/sun8i-h3-nanopi-neo-air.dts v https://github.com/RobertCNelson/u-boot/blob/master/arch/arm/dts/sun8i-h3-nanopi-neo.dts Do I need to patch the air dts file also during build? does the armbian build environment recompile dts > dtb at build time?
  6. Hi, Please see my comments in the other thread: Essentially when booting a Neo Core using the current air/core mainline image, the onboard fast ethernet is not being initialised. At a guess its because this is not included in the device tree (dtb/dts) for the nano pi air image or in uBoot config - however, if the image is to serve both boards it almost needs to - or they need to be separated. Both are probably reasonable options. Right now i'm trying to understand where the board defs for ethernet are collected during the image build using the armbian buil
  7. So I went hunting through all the board defs - I only found one difference between the air and core: https://github.com/u-boot/u-boot/blob/master/configs/nanopi_neo_air_defconfig v https://github.com/u-boot/u-boot/blob/master/configs/nanopi_neo_air_defconfig Line 16 - which seems like it could be related. However, I tried modifying the build patch to include but it was unsuccessful - I guess I will have to keep looking.
  8. So I flashed the latest nano pi (non-core) image: root@nanopineo:~# dmesg | grep eth [ 0.000000] psci: probing for conduit method from DT. [ 4.313531] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 4.313606] dwmac-sun8i 1c30000.ethernet: No regulator found [ 4.313782] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000) [ 4.313809] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 4.313821] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 4.313832] dwmac-sun8i 1c30000.ethernet: Normal descriptors [
  9. root@nanopiair:~# dmesg | grep eth [ 0.000000] psci: probing for conduit method from DT. root@nanopiair:~# and root@nanopiair:~# ifconfig eth0 eth0: error fetching interface information: Device not found root@nanopiair:~# so no driver is loaded. FYI: Armbian_5.38_Nanopiair_Ubuntu_xenial_next_4.14.15 so out of curiosity I plugged in a USB<>Ethernet Cable I had lying around: root@nanopiair:~# dmesg | grep eth [ 0.000000] psci: probing for conduit method from DT. [ 10.724772] asix 2-1:1.0 eth0: register 'asix'
  10. So I just tried to bring up a NanoPi Neo Core w/ minishield using the core/air image 5.37. To board boots but seems to leave ethernet disabled - it doesn't activate the port at all. I tried again with the friendly arm image and this worked fine - connected, picked up an address and I could ssh into the device. Is there a chance that the fast ethernet controller on the core is disabled on the mainline air image? is this controlled somewhere in the dts? Any help, please?
  11. Hi Guys, I have recently been contracted to a new project where I have moved out of my comfort zone (embedded 8-bit/32-bit uC) and have started my work on a H3 based device (currently NanoPi Neo) with Armbian. Over the course of my work I have managed to get up to speed with the basics; configuration, scripting, hardware and interfaces and device trees to a point where I can now work on the device as a proof of concept. The work that has been contributed so-far to the armbian project is impressive as is the active and knowledgeable forum - to which I hope I can contribute