June 10, 20233 yr Armbian Jammy (Minimal CLI) boots/works fine from an SD Card. (Armbian_23.5.2_Nanopi-r1_jammy_current_6.1.30_minimal.img.xz) apt update && apt upgrade -y && apt autoremove apt install armbian-config -y armbian-install I choose option #2 - Boot from eMMC - System on eMMC Accept the warning. I choose option #1 - ext4 The install appears to move along smoothly. I choose the "Power Off" option. Pull the power, remove the SD Card. Reconnect the power. I never see the "heartbeat" on the "System"(red) LED. The NanoPi never boot or obtains an IP address. Edited June 10, 20233 yr by ScottV
June 11, 20233 yr Author @Werner, Unfortunately, I do not have the necessary hardware to set up a serial console connection.
June 13, 20233 yr I have observed the same problem. My NanoPi-R1 - which interestingly identifies at a NEO on the boot UART console...... I do have a serial UART console. So have captured my findings. Albeit limited as verbosity isnt set high and the console log when booting the SD armbian image Armbian_23.5.2_Nanopi-r1_bookworm_current_6.1.30_minimal.img.xz SHA: ea10d9a0940a516be9f627f4a943caf39f3c2f3d1e80afafc95f78c65e4d2d10 Written to a 8G Sandisk SD. Put into the SD slot and powered the unit on. Console output gets to Starting Kernel ... and then the red LED light just blinks and blinks for a long time with no change. Unit has DHCPd and I am able to ssh into it with the root defaults. Establish my new root passwd and setup a user account and locale details etc. I then run the nand-sata-install Select the emmc and it takes about 2 minutes to copy over after all the warnings etc. Armbian for NanoPi R1 install script, https://www.armbian.com qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq lqqqqqqqqqqqqqqqqqqqqqqqqqqqeMMC installqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x x x All done. Power off x x x tqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqu x <Power off> < Exit > x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj root@nanopi-r1:~# Then the unit reboots and the console comes alive and displays. U-Boot SPL 2022.07-armbian (Jun 06 2023 - 04:52:59 +0000) DRAM: 1024 MiB Trying to boot from MMC2 MMC Device 1 not found spl: could not find mmc device 1. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### https://paste.armbian.com/ivopizatot Edited June 13, 20233 yr by Gul-Dukat
August 28, 20233 yr I have the same problem, the debug console output is as follows: U-Boot SPL 2022.07-armbian (Jun 06 2023 - 04:52:59 +0000) DRAM: 1024 MiB Trying to boot from MMC2 MMC Device 1 not found spl: could not find mmc device 1. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### This looks like a problem that has occurred in the past, the cause may be related to the eMMC driver in u-boot, I found some links: https://community.ipfire.org/t/friendlyarm-nanopi-r1-flash-image-to-emmc/594/5 https://wiki.ipfire.org/hardware/arm/friendlyelec/nanopi-r1 Quote The default bootloader in the image boots from mmc0 (SD-Card), however the eMMC (Flash-ROM) is connected to mmc2. To boot from the eMMC you need a special u-boot that switches mmc0 to mmc2.
August 28, 20233 yr 1 hour ago, Le Mka said: I have the same problem Try latest images from CI automated build section - should be fixed by now. Stable images rebuild = soon. https://www.armbian.com/download/
August 28, 20233 yr 34 minutes ago, Igor said: Try latest images from CI automated build section - should be fixed by now. Thanks for your reply, I just tried the latest ci build: Armbian_23.8.0-trunk.294, but it still doesn't work. U-Boot SPL 2023.07.02-armbian (Aug 26 2023 - 11:57:38 +0000) DRAM: 1024 MiB Trying to boot from MMC2 MMC Device 1 not found spl: could not find mmc device 1. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### Should i wait for the next build?
August 28, 20233 yr 10 minutes ago, Le Mka said: Should i wait for the next build? Debugging and fixing is not automatic. You will need to fix it first. When your fix will be merged, then new build will provide fixed results ... It could be this.
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.