Page 1 of 1

Boot issue with Nanopi R6S

Posted: Tue Nov 12, 2024 6:44 am
by magdalenadet
​Hello,
I'm into my first foray into armbian, and I'm having trouble just getting it to boot on my Nanopi R6S. Feeling a bit thick, like I'm missing something obvious.

I can get FriendlyELEC's rk3588-sd-debian-bookworm-core-6.1-arm64-20240511 to boot without any trouble, but not armbian images.

My procedure:

- Format microSD card with the SD Card Formatter from the SD Association
-Burn image to SD card with balena etcher
- Eject microSD reader from my PC
- Pop microSD into the device and apply power
 
When it boots into the FriendlyELEC image:

- the SYS light shines solid red for about 3 seconds
- then the SYS light starts blinking
- After a short while, the WAN light comes on for about 2 seconds then goes off.
- The SYS light continues blinking.

When I try an armbian image: the SYS light just shines solid red ad infinitum. It also does the same with no SD card at all.

Things I've tried:

- Two separate microSD cards, both will happily boot the FriendlyELEC images
- Three type-C power supplies (two Lenovo OEM 65W supplies that I use with my laptop + a Belkin 100W PD unit that gets used for everything)
- Waiting a long time for anything to happen on screen or with the LEDs
- I have also tried win32diskimager to burn the images to the microSD cards to ensure it's not a problem with balena
Cleared any bootloader on the eMMC while booted into the FriendlyELEC image (per the FriendlyELEC wiki)
dd if=/dev/zero of=/dev/mmcblk2 bs=8M count=1

Armbian images I've tried:

- My own built Armbian images - very impressed with armbian-build!
- Armbian_community_24.5.0-trunk.563_Nanopi-r6s_bookworm_edge_6.8.9_minimal.img.xz from Armbian website (verified SHA of a5e6da3593d221813cc874415b3c1f7f509aca9a09ff008a5bca7eb73313e2e7)
- Armbian_community_24.5.0-trunk.563_Nanopi-r6s_jammy_edge_6.8.9_gnome_desktop.img.xz from Armbian website (verified SHA of cf2dd5f25f1dae97ea3750e00cf335c1b68dc861b4d5d98b0fc0420050227a88)
 
Am I doing something obviously wrong?