Upgrading to Bullseye (troubleshooting Armbian 21.08.1)


ebin-dev
 Share

11 11

Recommended Posts

Armbian is a community driven open source project. Do you like to contribute your code?

Hi everyone! Thank you for all the updates on this. I have now fully upgraded my Helios64 with a ZFS pool from Armbian 21.08.2 Buster to Armbian 21.08.2 Bullseye (full Debian and Armbian repos). All good, no issues. As currently I'm just using the emmc to boot with system installed on sata1, the emmc speed impact is negligble in my case - but hopefully this will be sorted in the near future.

Link to post
Share on other sites

Did anyone try 21.08.2? Is it worth upgrading already?
I made an upgrade buster -> bullseye yesterday on Pine64 . It just works .

Upgrade needed only if you need some updated software from Bullseye . As for me trigger was mpd (my Pine64 board used mostly as audio player / receiver ) .

Sent from my M2007J20CG using Tapatalk

Link to post
Share on other sites

Hello everyone,

 

I am currently trying to repair my Helios64.


I exposed my problem in this topic

A member ( @IcerJo ) said that this problem could be related to this topic. So I read the posts of this topic looking for a solution.

 

I removed the hard drives from my NAS (to avoid a false manipulation) and I opened it (to be able to force the boot from the microSD with the jumper cab P10). Then I followed the instructions of the @TDCroPower message (here

 

Unfortunately, it didn't work. My NAS refuses to boot from the eMMC (fail at step 10 of the @TDCroPower message). Note that I tried 2 times these instructions: first with the Armbian_21.08.2_Helios64_buster_current_5.10.63 image. Then with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image. My current version is: Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64 and my NAS can only boot from the MicroSD card. Moreover, I can only communicate with it through the usb−usb-c cable, via picocom. SSH doesn’t work (I have an error message " WARNING: remote host identification has changed! "...).

 

Concerning the boot from the eMMC, I understood that it was maybe necessary to refresh the bootloader on eMMC. I didn’t understand very well the procedure to follow to make such thing. I went to armbian-config > System > Install > 5 - Install/Update the bootloader on SD/eMMC, then I rebooted... but nothing. Here is what picocom returns when I try to boot from the eMMC

 

Spoiler

picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 1500000
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready
DDR Version 1.24 20191016
In
channel 0
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 254
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
mmc0:cmd8,20
mmc0:cmd5,20
mmc0:cmd55,20
mmc0:cmd1,20
SdmmcInit=0 1
StorageInit ok = 67971
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5af4
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
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 2020.10-armbian (Feb 03 2021 - 22:43:46 +0100)

SoC: Rockchip rk3399
Reset cause: POR
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
166 bytes read in 13 ms (11.7 KiB/s)
15701569 bytes read in 1507 ms (9.9 MiB/s)
28580352 bytes read in 2727 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15701505 Bytes = 15 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 f4ff6000, end f5eef601 ... OK
   Loading Device Tree to 00000000f4f79000, end 00000000f4ff5fff ... OK

Starting kernel ...

 

I'm a little bit lost. I don't understand much about it. Does anyone have a clue for me? Whether the NAS runs on eMMC or MicroSD doesn't really matter to me. I just want to be able to get a working NAS and recover the data from my hard drives (previously configured with OpenMediaVault). 

 

Thank you very much, everyone.

Link to post
Share on other sites

14 hours ago, Cariboux said:

I removed the hard drives from my NAS (to avoid a false manipulation) and I opened it (to be able to force the boot from the microSD with the jumper cab P10). Then I followed the instructions of the @TDCroPower message (here :

 

Unfortunately, it didn't work. My NAS refuses to boot from the eMMC (fail at step 10 of the @TDCroPower message). Note that I tried 2 times these instructions: first with the Armbian_21.08.2_Helios64_buster_current_5.10.63 image. Then with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image. My current version is: Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64 and my NAS can only boot from the MicroSD card. Moreover, I can only communicate with it through the usb−usb-c cable, via picocom. SSH doesn’t work (I have an error message " WARNING: remote host identification has changed! "...).

 

 

 

If you boot from sdcard while your previous system was on eMMC the ssh identification is different. If you want to connect to the sd card rescue system:

ssh -o "UserKnownHostsFile /dev/null" -o StrictHostKeyChecking=no -o  "PasswordAuthentication yes" root@helios64

I mean if your system is on eMMC and you boot from a sd card rescue system you have to tell ssh to ignore the host (and force password auth because the sd card system will not have public kay auth set up).

 

about the failure at step 10 ... you should remove the sd card before boot (and your jumper mod) to boot from eMMC and all should be fine.

Mind the process you followed did not tell to set the jumper 10 because it tells to switch boot media via u-boot prompt a command "run bootcmd_mmc1" for sd and "run bootcmd_mmc0" for eMMC. Doing both jumper 10 and u-boot bootcmd_mmc1 is undefined. Simply do one or the other not both.

 

Cheers

Link to post
Share on other sites

22 hours ago, prahal said:

about the failure at step 10 ... you should remove the sd card before boot (and your jumper mod) to boot from eMMC and all should be fine.

Mind the process you followed did not tell to set the jumper 10 because it tells to switch boot media via u-boot prompt a command "run bootcmd_mmc1" for sd and "run bootcmd_mmc0" for eMMC. Doing both jumper 10 and u-boot bootcmd_mmc1 is undefined. Simply do one or the other not both.

 

Cheers

 

Hi @prahal, thank you for helping me !

 

So, I have remove the jumper cap and the MicroSD card, but the boot from eMMC doesn’t work. 

This is what I have when I try to start from eMMC : 

Spoiler

DDR Version 1.24 20191016
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 323
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 79411
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5ba8
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
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 2020.10-armbian (Sep 08 2021 - 10:55:50 +0000)

SoC: Rockchip rk3399
Reset cause: RST
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
=>                                                 
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
166 bytes read in 12 ms (12.7 KiB/s)
15701569 bytes read in 1508 ms (9.9 MiB/s)
28580352 bytes read in 2726 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15701505 Bytes = 15 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 f4ff6000, end f5eef601 ... OK
   Loading Device Tree to 00000000f4f79000, end 00000000f4ff5fff ... OK

Starting kernel ...
 

 

... and the kernel never start. (The System activity LED of the Front Panel is blue still. It’s not blinking.)

 

When I boot from the MicroSD card (with the command « run bootcmd_mmc1 »), it’s working. 

 

 When I boot from the MicroSD card, at the step 5 of the @TDCroPower’s message (https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=128305 ), I see this (I don’t know if it’s normal, especialy what is in red)

Spoiler

Welcome to Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64

 

No end-user support: work in progress

 

System load:   7%               Up time:       0 min    
Memory usage:  3% of 3.77G      IP:           192.168.2.155
CPU temp:      51°C               Usage of /:    5% of 29G        
RX today:      16 KiB      
 

root@helios64:~# mkdir -p /mnt/system
root@helios64:~# mount /dev/mmcblk2p1 /mnt/system
root@helios64:~# cd /mnt/system/
root@helios64:/mnt/system# ll
total 102792
lrwxrwxrwx   1 root root        7 Feb  4  2021 bin -> usr/bin
drwxr-xr-x   3 root root     4096 Oct 13 17:47 boot
drwxr-xr-x   2 root root     4096 Oct 13 17:46 dev
drwxr-xr-x 112 root root    12288 Sep 16 16:13 etc
drwxr-xr-x   2 root root     4096 Jan 12  2021 export
drwxr-xr-x   3 root root     4096 Feb 18  2021 home
lrwxrwxrwx   1 root root        7 Feb  4  2021 lib -> usr/lib
-rw-r--r--   1 root root   314356 Jul  8 19:32 linux-dtb-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root   316512 Sep  8 13:19 linux-dtb-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 11533048 Jul  8 19:32 linux-headers-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 11466188 Sep  8 13:19 linux-headers-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 40272020 Jul  8 19:33 linux-image-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 41246520 Sep  8 13:19 linux-image-current-rockchip64_21.08.2_arm64.deb
drwx------   2 root root    16384 Feb  4  2021 lost+found
drwxr-xr-x   2 root root     4096 Feb  4  2021 media
drwxr-xr-x   2 root root     4096 Feb  4  2021 mnt
drwxr-xr-x   2 root root     4096 Feb  4  2021 opt
drwxr-xr-x   2 root root     4096 Nov 22  2020 proc
drwx------   7 root root     4096 Mar 16  2021 root
drwxr-xr-x   2 root root     4096 Oct 13 16:32 run
lrwxrwxrwx   1 root root        8 Feb  4  2021 sbin -> usr/sbin
drwxrwxr-x   2 root root     4096 Feb  4  2021 selinux
drwxr-xr-x   7 root root     4096 Feb 28  2021 srv
drwxr-xr-x   2 root root     4096 Nov 22  2020 sys
lrwxrwxrwx   1 root root       42 Sep 16 16:13 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0
drwxrwxrwt   2 root root     4096 Oct 13 17:47 tmp
drwxr-xr-x  10 root root     4096 Feb  4  2021 usr
drwxr-xr-x  14 root root     4096 Feb 18  2021 var
 

 

( Maybe I have made a mistake because when I have do the step 6 of @TDCroPower’s message, I only « wget » 3 packages of this link : http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.63-rockchip64/ : linux-dtb-current-rockchip64_21.08.2_arm64.deblinux-headers-current-rockchip64_21.08.2_arm64.deb and linux-image-current-rockchip64_21.08.2_arm64.deb. I didn’t « wget » the 3 packages « 21.05.9 ».

(But, when i have try the downgrading with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image on my MicroSD, i have « wget » all the three packages of http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.35-rockchip64/ . But it was not working neither....) )

 

Link to post
Share on other sites

On 10/15/2021 at 3:20 PM, Cariboux said:

This is what I have when I try to start from eMMC : 

  Hide contents

DDR Version 1.24 20191016
In
soft reset
SRX
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 416MHz 0,1
Channel 0: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,416MHz
Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
256B stride
channel 0
CS = 0
MR0=0x18
MR4=0x1
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x18
MR4=0x2
MR5=0x1
MR8=0x10
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
change freq to 856MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x40
ch 1 ddrconfig = 0x101, ddrsize = 0x40
pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD
ddr_set_rate to 328MHZ
ddr_set_rate to 666MHZ
ddr_set_rate to 928MHZ
channel 0, cs 0, advanced training done
channel 1, cs 0, advanced training done
ddr_set_rate to 416MHZ, ctl_index 0
ddr_set_rate to 856MHZ, ctl_index 1
support 416 856 328 666 928 MHz, current 856MHz
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 323
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=14910MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 79411
SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit read PBA: 0x1404
SecureInit read PBA: 0x1804
SecureInit read PBA: 0x1c04
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3380ec0 signature is wrong
recovery gpt...
GPT 0x3380ec0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xe5ba8
RunBL31 0x40000
NOTICE:  BL31: v1.3(debug):42583b6
NOTICE:  BL31: Built : 07:55:13, Oct 15 2019
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1190): pd status 3e
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 2020.10-armbian (Sep 08 2021 - 10:55:50 +0000)

SoC: Rockchip rk3399
Reset cause: RST
DRAM:  3.9 GiB
PMIC:  RK808 
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
MMC:   mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Helios64
Revision: 1.2 - 4GB non ECC
Net:   eth0: ethernet@fe300000
scanning bus for devices...
starting USB...
Bus usb@fe380000: USB EHCI 1.00
Bus dwc3: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fe380000 for devices... 1 USB Device(s) found
scanning bus dwc3 for devices... cannot reset port 4!?
4 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
=>                                                 
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
166 bytes read in 12 ms (12.7 KiB/s)
15701569 bytes read in 1508 ms (9.9 MiB/s)
28580352 bytes read in 2726 ms (10 MiB/s)
81924 bytes read in 42 ms (1.9 MiB/s)
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15701505 Bytes = 15 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 f4ff6000, end f5eef601 ... OK
   Loading Device Tree to 00000000f4f79000, end 00000000f4ff5fff ... OK

Starting kernel ...
 

 

... and the kernel never start. (The System activity LED of the Front Panel is blue still. It’s not blinking.)

 

check that eMMC boot/armbianEnv.txt contains:
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371
rootfstype=ext4
overlays=dwc3-0-host
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x0bc2:0x231a:u

 

Note rootdev=UUID= will be different. You can check your by running

sudo blkid

from the sdcard os.

 

I believe yours is fine so you could also:

fsck /dev/mmcblk2p1

when booting from sdcard (booting kernel that has the emmc fix only ! your log shows 5.10.63 armbian 22.08.2 so your are fine. But double check before fscking).

Fscking will tell you if the filesystem is fine (readable/mountable by for one u-boot itself to start the kernel).

 

My mmcblk2p1 boot/armbianEnv.txt content was wrong as I ran fsck when my emmc was unstable (this was a bad idea). Thus u-boot was unable to start the system. Restoring armbianENv.txt fixed my boot.

 

On 10/15/2021 at 3:20 PM, Cariboux said:

When I boot from the MicroSD card (with the command « run bootcmd_mmc1 »), it’s working. 

 

 When I boot from the MicroSD card, at the step 5 of the @TDCroPower’s message (https://forum.armbian.com/topic/18855-upgrading-to-bullseye-troubleshooting-armbian-21081/?do=findComment&comment=128305 ), I see this (I don’t know if it’s normal, especialy what is in red)

  Hide contents

Welcome to Armbian 21.08.3 Buster with Linux 5.10.63-rockchip64

 

No end-user support: work in progress

 

System load:   7%               Up time:       0 min    
Memory usage:  3% of 3.77G      IP:           192.168.2.155
CPU temp:      51°C               Usage of /:    5% of 29G        
RX today:      16 KiB      
 

root@helios64:~# mkdir -p /mnt/system
root@helios64:~# mount /dev/mmcblk2p1 /mnt/system
root@helios64:~# cd /mnt/system/
root@helios64:/mnt/system# ll
total 102792
lrwxrwxrwx   1 root root        7 Feb  4  2021 bin -> usr/bin
drwxr-xr-x   3 root root     4096 Oct 13 17:47 boot
drwxr-xr-x   2 root root     4096 Oct 13 17:46 dev
drwxr-xr-x 112 root root    12288 Sep 16 16:13 etc
drwxr-xr-x   2 root root     4096 Jan 12  2021 export
drwxr-xr-x   3 root root     4096 Feb 18  2021 home
lrwxrwxrwx   1 root root        7 Feb  4  2021 lib -> usr/lib
-rw-r--r--   1 root root   314356 Jul  8 19:32 linux-dtb-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root   316512 Sep  8 13:19 linux-dtb-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 11533048 Jul  8 19:32 linux-headers-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 11466188 Sep  8 13:19 linux-headers-current-rockchip64_21.08.2_arm64.deb
-rw-r--r--   1 root root 40272020 Jul  8 19:33 linux-image-current-rockchip64_21.05.1_arm64.deb
-rw-r--r--   1 root root 41246520 Sep  8 13:19 linux-image-current-rockchip64_21.08.2_arm64.deb
drwx------   2 root root    16384 Feb  4  2021 lost+found
drwxr-xr-x   2 root root     4096 Feb  4  2021 media
drwxr-xr-x   2 root root     4096 Feb  4  2021 mnt
drwxr-xr-x   2 root root     4096 Feb  4  2021 opt
drwxr-xr-x   2 root root     4096 Nov 22  2020 proc
drwx------   7 root root     4096 Mar 16  2021 root
drwxr-xr-x   2 root root     4096 Oct 13 16:32 run
lrwxrwxrwx   1 root root        8 Feb  4  2021 sbin -> usr/sbin
drwxrwxr-x   2 root root     4096 Feb  4  2021 selinux
drwxr-xr-x   7 root root     4096 Feb 28  2021 srv
drwxr-xr-x   2 root root     4096 Nov 22  2020 sys
lrwxrwxrwx   1 root root       42 Sep 16 16:13 thermal_zone0 -> /sys/devices/virtual/thermal/thermal_zone0
drwxrwxrwt   2 root root     4096 Oct 13 17:47 tmp
drwxr-xr-x  10 root root     4096 Feb  4  2021 usr
drwxr-xr-x  14 root root     4096 Feb 18  2021 var
 

 

The red is fine it is color for deb file type.

 

 

 

On 10/15/2021 at 3:20 PM, Cariboux said:

( Maybe I have made a mistake because when I have do the step 6 of @TDCroPower’s message, I only « wget » 3 packages of this link : http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.63-rockchip64/ : linux-dtb-current-rockchip64_21.08.2_arm64.deblinux-headers-current-rockchip64_21.08.2_arm64.deb and linux-image-current-rockchip64_21.08.2_arm64.deb. I didn’t « wget » the 3 packages « 21.05.9 ».

(But, when i have try the downgrading with the Armbian_21.05.1_Helios64_buster_current_5.10.35 image on my MicroSD, i have « wget » all the three packages of http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.35-rockchip64/ . But it was not working neither....) )

 

 

just  a note. The steps were to download from :

root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-dtb-current-rockchip64_21.05.4_arm64.deb
root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-headers-current-rockchip64_21.05.4_arm64.deb
root@helios64:/mnt/system# wget http://armbian.hosthatch.com/apt/pool/main/l/linux-5.10.43-rockchip64/linux-image-current-rockchip64_21.05.4_arm64.deb

not 5.10.63 ... but 5.10.63 will be fine too per

 ie 21.08.2 has the emmc fix.

Link to post
Share on other sites

 Share

11 11