Search the Community

Hi, For long (long) time I did not update my nano pi duo image, recently I changed microSD card and wanted start fresh with latest image. I have tried latest debian image and also tried building image for the BOARD target as `nanopiduo`, but in in both cases my board is stuck at ... U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000) DRAM: 128 MiB Trying to boot from MMC1 ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi DUO DRAM: 128 MiB Core: 57 devices, 16 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial,usbkbd Out: serial Err: serial Net: No ethernet found. starting USB... No working controllers found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 5475 bytes read in 6 ms (890.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD 182 bytes read in 6 ms (29.3 KiB/s) Load fdt: /boot/dtb/sun8i-h2-plus-nanopi-duo.dtb 8431400 bytes read in 357 ms (22.5 MiB/s) 11476944 bytes read in 484 ms (22.6 MiB/s) Found mainline kernel configuration 36294 bytes read in 20 ms (1.7 MiB/s) Working FDT set to 43000000 504 bytes read in 17 ms (28.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 17 ms (28.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 4185 bytes read in 17 ms (240.2 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0xaf1fd0 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8431336 Bytes = 8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Working FDT set to 43000000 Loading Ramdisk to 497f5000, end 49fff6e8 ... OK Loading Device Tree to 42ee4000, end 42f55fff ... OK Working FDT set to 42ee4000 Starting kernel ... [ 2.314576] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 2.322869] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.43-current-sunxi #1 [ 2.330722] Hardware name: Allwinner sun8i Family [ 2.335438] Call trace: [ 2.335467] unwind_backtrace from show_stack+0x11/0x14 [ 2.343286] show_stack from dump_stack_lvl+0x37/0x42 [ 2.348377] dump_stack_lvl from panic+0xc9/0x278 [ 2.353116] panic from mount_root_generic+0x171/0x1f4 [ 2.358299] mount_root_generic from prepare_namespace+0x161/0x1ae [ 2.364527] prepare_namespace from kernel_init_freeable+0x1f9/0x20a [ 2.370928] kernel_init_freeable from kernel_init+0x21/0x100 [ 2.376720] kernel_init from ret_from_fork+0x11/0x1c [ 2.381808] Exception stack(0xc8821fb0 to 0xc8821ff8) [ 2.386881] 1fa0: 00000000 00000000 00000000 00000000 [ 2.395074] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 2.403265] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 2.410060] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- In older images, CPU was detected as `Allwinner H2+`, however now it's detecting as H3. I have tried couple other SD cards, with same error. What config I can try to get my `nanopi duo` working? offtopic: I tried images available from friendlyelec drive, which are getting stuck at "Starting kernel".

Image Armbian_23.5.2_Nanopiduo2_bookworm_current_6.1.30.img uname -a Linux nanopiduo2 6.1.30-sunxi #1 SMP Wed May 24 16:32:53 UTC 2023 armv7l GNU/Linux It turns out the dtb has some missing pieces: ethernet@1c30000 { compatible = "allwinner,sun8i-h3-emac"; syscon = <0x1e>; reg = <0x1c30000 0x10000>; interrupts = <0x00 0x52 0x04>; interrupt-names = "macirq"; resets = <0x03 0x0c>; reset-names = "stmmaceth"; clocks = <0x03 0x1b>; clock-names = "stmmaceth"; status = "okay"; phy-handle = <0x69>; // differs from NEO phy-mode = "mii"; allwinner,leds-active-low; after adding phy-handle, phy-mode and allwinner.. wired ethernet works. Of course NetworkManager config /etc/network interfaces must be configured properly. In my case # Network is managed by Network manager auto lo iface lo inet loopback # network interface not managed by Network Manager allow-hotplug eth0 iface eth0 inet static address 192.168.179.222 netmask 255.255.255.0 gateway 192.168.179.1 dns-nameservers 192.168.179.1 Possibly the leds* are not required. Maybe these can be tweaked for other IO's then 🙂 btw. would be nice to thave a separate Nanopi duo2 section here. T.

Just tried Armbian 23.5 Bookworm, cli & minimal. Both report the same in the console. Board works just fine with official img from www.friendlyelec.com Here is the terminal output.

Hello, I am using a NanoPi Duo2 with Armbian 22.11 and Kernel 5,15,80. This device uses an AP6216 wireless interface, which I have noticed are pretty common on sunxi based boards. I ran some bandwidth tests and had pretty poor results: [ ID] Interval Transfer Bandwidth [ 3] 0.0000-1.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 1.0000-2.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 2.0000-3.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 3.0000-4.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 4.0000-5.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 5.0000-6.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 6.0000-7.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 7.0000-8.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 8.0000-9.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 9.0000-10.0000 sec 129 KBytes 1.05 Mbits/sec Not sure if the issue was the driver, hardware, or otherwise I connected a USB wifi dongle and disabled the AP6216. I've tested with the same results again: [ ID] Interval Transfer Bandwidth [ 3] 0.0000-1.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 1.0000-2.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 2.0000-3.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 3.0000-4.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 4.0000-5.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 5.0000-6.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 6.0000-7.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 7.0000-8.0000 sec 127 KBytes 1.04 Mbits/sec [ 3] 8.0000-9.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 9.0000-10.0000 sec 129 KBytes 1.05 Mbits/sec [ 3] 0.0000-10.0191 sec 1.25 MBytes 1.05 Mbits/sec It's my suspicion that the issue is now elsewhere - but where? I have no idea. Thanks for any ideas.