gounthar Posted January 31, 2023 Share Posted January 31, 2023 (edited) Hi there 👋 I've tried the CSC edge images Armbian_23.02.0-trunk_Nanopiduo2_lunar_edge_6.1.8.img and Armbian_23.02.0-trunk_Nanopiduo2_sid_edge_6.1.8.img and the machine does not want to boot. Is there a more stable image somewhere? FriendlyCore boots on this board. Thanks. U-Boot SPL 2022.07-armbian (Jan 30 2023 - 06:49:28 +0000) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Jan 30 2023 - 06:49:28 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi NEO DRAM: 512 MiB Core: 60 devices, 17 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: phy interface1 eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) 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 4077 bytes read in 2 ms (1.9 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 234 bytes read in 2 ms (114.3 KiB/s) 18804544 bytes read in 780 ms (23 MiB/s) 8706400 bytes read in 363 ms (22.9 MiB/s) Found mainline kernel configuration Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-duo2.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 504 bytes read in 8 ms (61.5 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Error applying DT overlays, restoring original DT Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-duo2.dtb' Kernel image @ 0x42000000 [ 0x000000 - 0x84d960 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 18804480 Bytes = 17.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device sun8i_emac_eth_start: Timeout missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-81-e1-0b-9c-e0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/000 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/00 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/0 sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm-sunxi sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default-arm sun8i_emac_eth_start: Timeout Retrieving file: pxelinux.cfg/default sun8i_emac_eth_start: Timeout Config file not found sun8i_emac_eth_start: Timeout sun8i_emac_eth_start: Timeout Edited January 31, 2023 by gounthar 0 Quote Link to comment Share on other sites More sharing options...
Benben Posted April 16, 2023 Share Posted April 16, 2023 Hi, Got same issue, looks like allwinner subdir is expected but not there. From a linux laptop, mounting the SD, I create a symlink dir named allwinner linked to /boot/dtb : root@nanopiduo2:/boot/dtb# ls -l allwinner lrwxrwxrwx 1 root root 1 Apr 16 15:15 allwinner -> . 1 Quote Link to comment Share on other sites More sharing options...
gounthar Posted April 24, 2023 Author Share Posted April 24, 2023 Thank you, I should try that. 0 Quote Link to comment Share on other sites More sharing options...
Jimmay Posted June 6, 2023 Share Posted June 6, 2023 (edited) I ran into this issue with the Armbian 23.5.1 Jammy image (`Armbian_23.5.1_Nanopiduo2_jammy_current_6.1.30.img.xz`) yesterday. Tried it twice, different SD cards, cleared them with "SD Card Formatter", burned and verified with BalenaEtcher, checked all SHA256 values, everything good. This seems to be the part of the process where things start to go awry: Found U-Boot script /boot/boot.scr 4121 bytes read in 3 ms (1.3 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 234 bytes read in 2 ms (114.3 KiB/s) 16661873 bytes read in 694 ms (22.9 MiB/s) 8477464 bytes read in 354 ms (22.8 MiB/s) Found mainline kernel configuration Failed to load '/boot/dtb/allwinner/sun8i-h3-nanopi-duo2.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! So it looks like the exact same issue as gounthar and Benben. I didn't test out Benben's fix, but decided to build an image file directly using Armbian's Github `./compile` tool, and that worked fine as of 6 June 2023. The options I used were: `./compile.sh build BOARD=nanopiduo2 BRANCH=current BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy` I'm not sure how repeatable builds from the compile system are, but SHA hash of mine is attached in case this helps anyone. N.B. I just noticed that the version on the board page is now `Armbian_23.5.2_Nanopiduo2_jammy_current_6.1.30.img.xz` so perhaps this has been fixed there in the point release? I will try to test later. Armbian_23.08.0-trunk_Nanopiduo2_jammy_current_6.1.30.img.sha Edited June 6, 2023 by Jimmay Format text 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted June 7, 2023 Share Posted June 7, 2023 7 hours ago, Jimmay said: so perhaps this has been fixed there in the point release? We hope so. Allwinner32 in general had boot issues. https://armbian.atlassian.net/browse/AR-1765?focusedCommentId=11868 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted June 7, 2023 Share Posted June 7, 2023 Duo2 was tested with 23.5.2 image that was uploaded yesterday. 1 Quote Link to comment Share on other sites More sharing options...
schunckt Posted June 22, 2023 Share Posted June 22, 2023 Armbian_23.5.2_Nanopiduo2_bookworm_current_6.1.30.img works, had to fix wired ethernet. See other topic if interested in https://forum.armbian.com/topic/28911-nanopi-duo2-wired-ethernet-fix-bookworm-6130-tested/ also it seems armbian-config doesn't work properly. I had to enable spi and i2c overlays manually (not really a problem IMHO) . T. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.