Nanopi R6S - Boot Issues

[Simon Thomas]

Hi Team,

 

I hope you're all keeping well.

 

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?

[jam123]

Hi,

 

i got similar results, rk3588-eflasher-debian-bookworm-core-6.1-arm64-20240522.img works without issues but Armbian_community_24.5.0-trunk.667_Nanopi-r6s_bookworm_edge_6.8.10_minimal.img doesnt.

Red light is the only one on. I got this result from the serial console - it shows an error about OPTEE:

 

DDR 9fffbe1e78 cym 24/02/04-10:09:20,fwver: v1.16
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x1
CH0 RX Vref:27.1%, TX Vref:19.8%,20.8%
CH1 RX Vref:27.9%, TX Vref:19.8%,20.8%
CH2 RX Vref:26.7%, TX Vref:21.8%,21.8%
CH3 RX Vref:27.1%, TX Vref:20.8%,19.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g1b1171b7c71-220418 #fa (Apr 18 2024 - 11:12:44)
unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(7efcd01a0f...) + OK
## Checking uboot 0x00200000 ... sha256(b76f2f6c2a...) + OK
## Checking fdt 0x0031ec90 ... sha256(c5d44f02b4...) + OK
## Checking atf-2 0x000f0000 ... sha256(da90adf3a4...) + OK
## Checking atf-3 0xff100000 ... sha256(1163474a5b...) + OK
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 402.313/555.636 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-589-g3389cfdda:derrick.huang
NOTICE:  BL31: Built : 10:14:29, May  9 2023
INFO:    spec: 0x13
INFO:    ext 32k is valid
INFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO:    system boots from cpu-hwid-0
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
ERROR:   dfs get fsp_params[0] error, 0xfead0004 != 0xfead0003
ERROR:   dfs get fsp_params[1] error, 0x1111 != 0xfead0003
ERROR:   dfs get fsp_params[2] error, 0x0 != 0xfead0003
ERROR:   dfs get fsp_params[3] error, 0x60241520 != 0xfead0003
ERROR:   loader&trust unmatch!!! Please update trust if need enable dmc
INFO:    BL31: Initialising Exception Handling Framework
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-armbian (May 21 2024 - 16:20:03 +0000)

Model: NanoPi R6S
MPIDR: 0x81000000
PreSerial: 2, raw, 0xfeb50000
DRAM:  8 GiB
Sysmem: init
Relocation Offset: eda3f000
Relocation fdt: eb9f9960 - eb9fecd0
CR: M/C/I
Using default environment

optee check api revision fail: -1.0
optee api revision is too low
### ERROR ### Please RESET the board ###

 

I have no idea (yet) what that means or how to fix it.

 

Any hints are apreciated :),

 

thanks, J.

[erik_123]

Similar results for me.  I have the R6C.  rk3588-sd-debian-bullseye-minimal-6.1-arm64-20240117.img installs OK.  I try to install Armbian_community_24.8.0-trunk.139_Nanopi-r6s_bookworm_vendor_6.1.43_minimal.img.  As instructed in the documentation, I edit /boot/armbianEnv.txt and change R6S to R6C.  I flash to the SD card, insert the SD card into the device, and power up.  I get only the red light.  The output on the debug console is almost identical to that posted above:

 

DDR 9fffbe1e78 cym 24/02/04-10:09:20,fwver: v1.16
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x1
CH0 RX Vref:27.9%, TX Vref:22.8%,21.8%
CH1 RX Vref:25.8%, TX Vref:19.8%,20.8%
CH2 RX Vref:26.7%, TX Vref:20.8%,19.8%
CH3 RX Vref:27.5%, TX Vref:20.8%,20.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g1b1171b7c71-220418 #fa (Apr 18 2024 - 11:12:44)
unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(a7d1d8d191...) + OK
## Checking uboot 0x00200000 ... sha256(5292f1b184...) + OK
## Checking fdt 0x0031f058 ... sha256(a4fd4b8eff...) + OK
## Checking atf-2 0xff100000 ... sha256(4b2065349b...) + OK
## Checking atf-3 0x000f0000 ... sha256(aa71013e72...) + OK
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 443.155/593.829 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-682-g4ca8a8422:derrick.huang, fwver: v1.45
NOTICE:  BL31: Built : 10:11:21, Dec 27 2023
INFO:    spec: 0x13
INFO:    code: 0x88
INFO:    ext 32k is valid
INFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO:    l3 cache partition cfg-0
INFO:    system boots from cpu-hwid-0
INFO:    disable memory repair
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO:    BL31: Initialising Exception Handling Framework
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-armbian (Jun 11 2024 - 18:28:00 +0000)

Model: NanoPi R6S
MPIDR: 0x81000000
PreSerial: 2, raw, 0xfeb50000
DRAM:  8 GiB
Sysmem: init
Relocation Offset: eda3e000
Relocation fdt: eb9f9d20 - eb9fecc8
CR: M/C/I
Using default environment

optee check api revision fail: -1.0
optee api revision is too low
### ERROR ### Please RESET the board ###

 

Edited June 14 by erik_123

[ColorfulRhino]

If you can, try to build your own image on the latest version: https://github.com/armbian/build?tab=readme-ov-file#getting-started

 

For NanoPi R6S:
./compile.sh BOARD=nanopi-r6s BRANCH=edge

For NanoPi R6C:
./compile.sh BOARD=nanopi-r6c BRANCH=edge

(replace BRANCH=edge with BRANCH=vendor if you prefer the vendor kernel from Rockchip or BRANCH=current if you prefer a stable mainline linux experience)

 

At least for NanoPi R6C there should not be a problem since I recently added support for the latest bootloader version.

[erik_123]

Thanks for getting back to us.  I ran the script.  During the setup, I am pretty sure that I asked it for a window manager (xfce).  Then I fired up the image, I get no output on the HDMI connected monitor.  Then I connected it to the serial port and rebooted and this time it asked me to specify a root password, and a username and password.  So it seems to have started up successfully.

 

nanopi-r6c login: erik
Password:
 _   _ ____  _   ____   __    ____
| \ | |  _ \(_) |  _ \ / /_  / ___|
|  \| | |_) | | | |_) | '_ \| |    
| |\  |  __/| | |  _ <| (_) | |___
|_| \_|_|   |_| |_| \_\\___/ \____|
                                   
Welcome to Armbian-unofficial 24.8.0-trunk Bookworm with bleeding edge Linux 6.10.0-rc4-edge-rockchip-rk3588

No end-user support: built from trunk

System load:   17%               Up time:       0 min    
Memory usage:  9% of 7.75G      IP:           192.168.1.60
CPU temp:      34°C               Usage of /:    5% of 116G       
RX today:      83.9 KiB      


Configured profile sync daemon with overlayfs.
erik@nanopi-r6c:~$

 

But the window manager does not start, and still nothing on the monitor.  Is this the expected behavior?  Sorry if I'm being dumb, I have never used armbian before.

[erik_123]

P.S. Below is the initial output that I got on the serial port, before it asked me to reset the root password:

 

$ sudo bt -b 1500000
No port specified, using ttyUSB0 (last registered). Use -l to list ports.
Trying port ttyUSB0... Connected to ttyUSB0 at 1500000 bps.
Escape character is 'Ctrl-]'. Use escape followed by '?' for help.
DDR 9fffbe1e78 cym 24/02/04-10:09:20,fwver: v1.16
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x1
CH0 RX Vref:28.3%, TX Vref:22.8%,21.8%
CH1 RX Vref:26.3%, TX Vref:19.8%,19.8%
CH2 RX Vref:26.7%, TX Vref:19.8%,19.8%
CH3 RX Vref:27.5%, TX Vref:20.8%,20.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g1b1171b7c71-220418 #fa (Apr 18 2024 - 11:12:44)
unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
No misc partition
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(a7d1d8d191...) + OK
## Checking u-boot 0x00a00000 ... sha256(235390ebc4...) + OK
## Checking fdt-1 0x00aa7e10 ... sha256(d25019e2ea...) + OK
## Checking atf-2 0x000f0000 ... sha256(aa71013e72...) + OK
## Checking atf-3 0xff100000 ... sha256(4b2065349b...) + OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 368.979/520.85 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-682-g4ca8a8422:derrick.huang, fwver: v1.45
NOTICE:  BL31: Built : 10:11:21, Dec 27 2023
INFO:    spec: 0x13
INFO:    code: 0x88
INFO:    ext 32k is valid
INFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO:    l3 cache partition cfg-0
INFO:    system boots from cpu-hwid-0
INFO:    disable memory repair
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO:    BL31: Initialising Exception Handling Framework
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0xa00000
INFO:    SPSR = 0x3c9


U-Boot 2024.07-rc4-armbian (Jun 17 2024 - 14:10:22 +0000)

Model: Generic RK3588S/RK3588
DRAM:  8 GiB
Core:  291 devices, 25 uclasses, devicetree: separate
MMC:   mmc@fe2c0000: 1, mmc@fe2e0000: 0
Loading Environment from nowhere... OK
In:    serial@feb50000
Out:   serial@feb50000
Err:   serial@feb50000
Model: Generic RK3588S/RK3588
Hit any key to stop autoboot:  0 
Scanning for bootflows in all bootdevs
Seq  Method       State   Uclass    Part  Name                      Filename
---  -----------  ------  --------  ----  ------------------------  ----------------
Scanning global bootmeth 'efi_mgr':
No EFI system partition
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
  0  efi_mgr      ready   (none)       0  <NULL>                    
** Booting bootflow '<NULL>' with efi_mgr
Loading Boot0000 'mmc 1' failed
Loading Boot0001 'mmc 0' failed
EFI boot manager: Cannot load any image
Boot failed (err=-14)
Scanning bootdev 'mmc@fe2c0000.bootdev':
  1  script       ready   mmc          1  mmc@fe2c0000.bootdev.part /boot/boot.scr
** Booting bootflow 'mmc@fe2c0000.bootdev.part_1' with script
Boot script loaded from mmc 1:1
225 bytes read in 4 ms (54.7 KiB/s)
28236660 bytes read in 2365 ms (11.4 MiB/s)
32883200 bytes read in 2752 ms (11.4 MiB/s)
148215 bytes read in 22 ms (6.4 MiB/s)
Working FDT set to 12000000
Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards.
Unknown command 'kaslrseed' - try 'help'
## Loading init Ramdisk from Legacy Image at 12180000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    28236596 Bytes = 26.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 12000000
   Booting using the fdt blob at 0x12000000
Working FDT set to 12000000
   Loading Ramdisk to eb3d9000, end ecec6b34 ... OK
   Loading Device Tree to 00000000eb34c000, end 00000000eb3d8fff ... OK
Working FDT set to eb34c000

Starting kernel ...

Loading, please wait...
Starting systemd-udevd version 252.22-1~deb12u1
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... [FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server.
[FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server.
[FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server.
[FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server.
[FAILED] Failed to start ssh.servic…[0m - OpenBSD Secure Shell server.

Armbian-unofficial 24.8.0-trunk Bookworm ttyS2 

nanopi-r6c login: 

 

[Werner]

6.10 is, as the name implies, bleeding edge, so do not expect stuff to work. Mainline support for rk3588 is still in development.

In theory though HDMI should work already, however might not have been tested on this device yet and there are caveats.

Anyway if you prefer a working system, get an image with vendor 6.1.y kernel.

 

Regarding the ssh stuff I think @Alessandro Lannocca did some work on SSH, either you grabbed an image where fixes were ongoing or you found another bug that needs attention.