RockPro64 updates automatically on 1st boot, reboots on his own, does not start anymore
echo $G_DISTRO_NAME or cat /etc/debian_versionuname -ausable system
does not boot, black screen
I did not touch any dietpi.txt config, just flashed and booted.
I have a 2nd RockPro64 with the exact same setup and hardware, can reproduce there too.
@1uc4
Thanks for your report.
I hope Fourdee finds some time to replicate, since it don't have a RockPro64 here.
@1uc4
Many thanks for the report 馃憤
I suspect APT package kernel/uboot update causing this, will verify with local testing.
Notes:
Unable to replicate on my board with EMMC or SD. Regardless, will update the image based on Ayufan's latest:
Thanks for looking into it.
I will try plugging in the serial console tonight (will be my 1st time) to see if I can grab some additional output and attach it to this thread.
Some additional info:
@1uc4
Serial debug would be ideal.
In the mean time, i've updated our image based on Ayufan 0.7.11:
https://dietpi.com/downloads/images/DietPi_RockPro64-ARMv8-Stretch.7z
Please let us know if this resolves the issue.
It does. :clap:
I repeated the exact same steps, now on 1st boot it upgrades from v6.18 --> v6.19.7.
On reboot it does not come up, no white led turns up. Power button and Reset button don't help. An unplug-plug of the power connector with a pause of about 15-20sec in-between does the trick.
I will perform the procedure again on my second board and then try to see if I can capture serial debug on a soft reboot, which is failing.
Thanks again! :+1:
Here is my dmesg output post-upgrade boot:
dmesg.txt
@Fourdee : Does a soft reboot work on your setup? Or can you also reproduce this behavior?
Here's the serial console output after issuing a reboot command, which fails to boot:
DDR Version 1.13 20180801
In
soft reset
SRX
Channel 0: LPDDR4,50MHz
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,50MHz
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x98
MR4=0x81
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x81
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x98
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x1
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
OUT
U-Boot SPL board init
U-Boot SPL 2017.09-rockchip-ayufan-1033-gdf02018479 (Aug 06 2018 - 22:29:15)
booted from SD
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
@1uc4
mmc_load_image_raw_sector: mmc block read error
SPL: failed to boot from all boot devices
Thanks for the serial debug 馃憤
Yep, appears filesystem issue. Could be kernel related (latest image may resolve mmc/sd instability).
I also have a v2.1 rev board, was unable to replicate the issue you experienced. Very strange. I suspect kernel/stability issue during filesystem resize.
As the updated image resolved the issue, i'll mark this as closed. However, please reopen if required.