Nano Pi neo3 not booting after restart, how to debug?

[Claudio Saavedra]

Hi,

I have a neo3 that has been running without any issues for about a year. Today after I had to restart it and the device wouldn't boot anymore. I checked the systemd logs by mounting the sd card in my laptop and I can see that it didn't get to boot at all (as there are no systemd logs after the shutdown). I checked the card for filesystem issues, and it seems to be OK. But I have no idea how to fix this. I really don't want to flash again an image and start from zero as I have a good amount of software installed that would take a lot of time to setup again. If this is a problem with the bootloader, how can I troubleshoot it? I don't have a serial interface so I am a bit in the dark here (as the neo3 doesn't have a video output, only USB and ethernet).

 

There was another topic saying that after an upgrade, rk3328-nanopi-neo3-rev02.dtb had gone missing. I also checked that, and the file is in its place and armbianEnv.txt is pointing to it, so I don't think that is the problem.

 

Anyway, pointers in how to debug this would be appreciated!

[Werner]

https://debug.armbian.de

[Gugolple]

Hello, I updated recently my nanopi neo3 and I am unable to get it to boot. The log from uart is attached below. Is there any idea/log I could report to fix the issue?

 

Thank you and kind regards,

 

Juan.

 

```

Welcome to minicom 2.8

OPTIONS: I18n                                                                
Port /dev/ttyUSB0, 00:10:32                                                  
                                                                             
Press CTRL-A Z for help on special keys                                      
                                                                             
DDR version 1.16 20190528                                                    
ID:0x805 N                                                                   
In                                                                           
DDR4                                                                         
333MHz                                                                       
Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
ddrconfig:14                                                                 
OUT                                                                          
Boot1 Release Time: May 13 2019 17:34:36, version: 2.50                      
ChipType = 0x11, 248                                                         
mmc2:cmd1,20                                                                 
emmc reinit                                                                  
mmc2:cmd1,20                                                                 
emmc reinit
mmc2:cmd1,20
SdmmcInit=2 1
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=60906MB
FwPartOffset=2000 , 0
StorageInit ok = 32496
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x337a9f0 signature is wrong
recovery gpt...
GPT 0x337a9f0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
hdr 000000000337a3b0 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,

Load OK, addr=0x200000, size=0xaea08
RunBL31 0x40000
INFO:    Preloader serial: 2
NOTICE:  BL31: v1.3(debug):403e0b816
NOTICE:  BL31: Built : 14:13:08, Aug 11 2020
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
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 2022.04-armbian (May 27 2023 - 19:32:11 +0000)

Model: FriendlyElec NanoPi R2S
DRAM:  2 GiB
PMIC:  RK8050 (on=0x40, off=0x00)
Core:  223 devices, 20 uclasses, devicetree: separate
MMC:   mmc@ff500000: 1
Loading Environment from MMC... MMC Device 0 not found
*** Warning - No MMC card found, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: FriendlyElec NanoPi R2S
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3252 bytes read in 5 ms (634.8 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
227 bytes read in 3 ms (73.2 KiB/s)
16255321 bytes read in 709 ms (21.9 MiB/s)
30030336 bytes read in 1305 ms (21.9 MiB/s)
65884 bytes read in 15 ms (4.2 MiB/s)
2825 bytes read in 8 ms (344.7 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Unknown command 'kaslrseed' - try 'help'
Moving Image from 0x2080000 to 0x2200000, end=3f40000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    16255257 Bytes = 15.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to 7cfa7000, end 7df27919 ... OK
   Loading Device Tree to 000000007cf2e000, end 000000007cfa6fff ... OK

Starting kernel ...

Loading, please wait...
Starting systemd-udevd version 252.26-1~deb12u2

Timed out for waiting the udev queue being empty.

```

Edited July 19 by Gugolple
Added new line to the log, "Timed out for waiting the udev queue being empty."