Jump to content

Firfly-rk3399 have not been booting up reasent images from Armbian


denni_isl

Recommended Posts

Have been struggling to install Armbian on Firefly rk3399 - did try many images from armbian.com/firefly-rk3399 with no luck at all.   Then I did stumble on a Arbmian image on a USB stick from 5 of January  this year  Armbian_19.11.7_Firefly-rk3399_bionic_legacy_4.4.208_desktop.img  which did work to my

surprise.   Thought it had something to do with u-boot and partitions.    I did always stop on starting kernel ... with some prior errors.    

 

Will try to install newer images for the sake of curiosity :-)

 

Btw. have donated to the Armbian project twice - not so much, but some amount - as people should do.    

 

This is the serial output from the successful starting of Armbian_19.11.17 image.   Firefly seems to be completely focused on android and the android partition method. 

 

Spoiler

Press CTRL-A Z for help on special keys

DDR Version 1.24 20191016
In
Channel 0: DDR3, 800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: DDR3, 800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA17AA1, stride = 0xD
OUT
20492296 bytes read in 1290 ms (15.1 MiB/s)
101178 bytes read in 14 ms (6.9 MiB/s)
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd                                                        
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)                  
   Data Size:    8626159 Bytes = 8.2 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 f56e7000, end f5f20fef ... OK                             
ERROR: reserving fdt memory region failed (addr=0 size=0)                       
   Loading Device Tree to 00000000f5665000, end 00000000f56e6fff ... OK         
                                                                                
Starting kernel ...                      

 

Link to comment
Share on other sites

1 hour ago, denni_isl said:

Have been struggling to install Armbian on Firefly rk3399 - did try many images from armbian.com/firefly-rk3399 with no luck at all.

Did you also try the nightly images?
You can also check in the archive for the latest working image. I don't know/think anyone has a board to test the images.
https://archive.armbian.com/firefly-rk3399/archive/

Link to comment
Share on other sites

14 minutes ago, NicoD said:

Did you also try the nightly images?
You can also check in the archive for the latest working image. I don't know/think anyone has a board to test the images.
https://archive.armbian.com/firefly-rk3399/archive/

 

Actually i did not try the nightly images.   Just the those marked stable.    They did all stop in the the - starting kernel process.... with some prior errors.     My guess is that it is some issues with the connection between u-boot and the /boot directory in Armbian.  

Link to comment
Share on other sites

7 hours ago, piter75 said:

Can you post the serial console output from the failed boot rather than the successful one? ;-)

 

The testing image is Armbian_20.08.1_Firefly-rk3399_focal_current_5.8.6_desktop.img.xz

 

Some error messages;

*  Loading Environment from MMC... *** Warning - bad CRC, using default environment    

 

* WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destineK
ERROR:   Error initializing runtime service opteed_fast

 

*  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   

 

This is the messages from u-boot

 

 

Spoiler

DDR Version 1.24 20191016
In
Channel 0: DDR3, 800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: DDR3, 800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA17AA1, stride = 0xD
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 243
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=119276MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=61056MB
FwPartOffset=2000 , 0
StorageInit ok = 250209                                                                                   
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=0xb1cb0                                                                      
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 destineK
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.07-armbian (Sep 03 2020 - 19:56:25 +0200)                                                     
                                                                                                          
SoC: Rockchip rk3399                                                                                      
Reset cause: POR                                                                                          
Model: Firefly-RK3399 Board                                                                               
DRAM:  3.9 GiB                                                                                            
PMIC:  RK808                                                                                              
Cannot find regulator pwm init_voltage                                                                    
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0                                                
Loading Environment from MMC... *** Warning - bad CRC, using default environment                          
                                                                                                          
In:    serial@ff1a0000                                                                                    
Out:   serial@ff1a0000                                                                                    
Err:   serial@ff1a0000                                                                                    
Model: Firefly-RK3399 Board                                                                               
Net:   eth0: ethernet@fe300000                                                                            
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                                                                        
3185 bytes read in 5 ms (622.1 KiB/s)                                                                     
## Executing script at 00500000                                                                           
Boot script loaded from mmc 1                                                                             
116 bytes read in 5 ms (22.5 KiB/s)                                                                       
15587897 bytes read in 664 ms (22.4 MiB/s)                                                                
27275776 bytes read in 1156 ms (22.5 MiB/s)                                                               
75813 bytes read in 11 ms (6.6 MiB/s)                                                                     
2698 bytes read in 9 ms (292 KiB/s)                                                                       
Applying kernel provided DT fixup script (rockchip-fixup.scr)                                             
## Executing script at 09000000                                                                           
## Loading init Ramdisk from Legacy Image at 06000000 ...                                                 
   Image Name:   uInitrd                                                                                  
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)                                            
   Data Size:    15587833 Bytes = 14.9 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 f5038000, end f5f159f9 ... OK                                                       
   Loading Device Tree to 00000000f4fbd000, end 00000000f5037fff ... OK                                   
                                                                                                          
Starting kernel ...       

 

Link to comment
Share on other sites

This might be the actual case - a missing bl30.bin and bl32.bin - Think it is almost first in the boot process.

 

* GPT 0x3380ec0 signature is wrong                                                                          
recovery gpt fail!                                                                                        
LoadTrust Addr:0x4000                                                                                     
* No find bl30.bin                                                                                          
No find bl32.bin                 

Link to comment
Share on other sites

3 часа назад, denni_isl сказал:

This is the messages from u-boot

Judging by the log, u-boot works fine and passes control to the kernel. The DTB setting may be incorrect.

Try before writing the Armbian image to the SD card, perform a full SD card cleanup. Most likely, you have previously written a system with GPT to the SD card and its "remnants" (a backup copy at the end of the Sd card) prevent it from starting.

 

https://www.stationpc.com/forum.php?mod=viewthread&tid=97&extra=page%3D1%26filter%3Dauthor%26orderby%3Ddateline

Link to comment
Share on other sites

Still struggling to get a newer version of Armbian.   Did try wipefs, blockthiscard, gui tools, dos partiotions, no partiotions, dd if=/dev/zero of=/dev/mmcblk1 (and the card) - just about everything to get the cards clean.   Now there is just one warning "Warning: Bad CRC, using default environment".   Did stop u-boot and >  saveenv - reset with image  Armbian_20.05.2_Firefly-rk3399_buster_current_5.4.43_desktop.img.xz -

 

The image from January this year works - kernel 4.4.

 

So this is interesting -

 

Spoiler

U-Boot 2020.04-armbian (Jun 03 2020 - 10:01:42 +0200)                           
                                                                                
SoC: Rockchip rk3399                                                            
Reset cause: RST                                                                
Model: Firefly-RK3399 Board                                                     
DRAM:  3.9 GiB                                                                  
PMIC:  RK808                                                                    
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0                                     
Loading Environment from MMC... OK                                              
In:    serial@ff1a0000                                                          
Out:   serial@ff1a0000                                                          
Err:   serial@ff1a0000                                                          
Model: Firefly-RK3399 Board                                                     
Net:   eth0: ethernet@fe300000                                                  
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                                              
2940 bytes read in 6 ms (478.5 KiB/s)                                           
## Executing script at 00500000                                                 
Boot script loaded from mmc 1                                                   
102 bytes read in 4 ms (24.4 KiB/s)                                             
12177392 bytes read in 520 ms (22.3 MiB/s)                                      
19601920 bytes read in 835 ms (22.4 MiB/s)                                      
74464 bytes read in 11 ms (6.5 MiB/s)                                           
2698 bytes read in 8 ms (329.1 KiB/s)                                           
Applying kernel provided DT fixup script (rockchip-fixup.scr)                   
## Executing script at 39000000                                                 
## Loading init Ramdisk from Legacy Image at 06000000 ...                       
   Image Name:   uInitrd                                                        
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)                  
   Data Size:    12177328 Bytes = 11.6 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 f5385000, end f5f21fb0 ... OK                             
   Loading Device Tree to 00000000f530a000, end 00000000f5384fff ... OK         
                                                                                
Starting kernel ...                                                             
                                        

 

And the  working image from Jan 5 2020 - Armbian_19.11.7_Firefly-rk3399_bionic_legacy_4.4.208_desktop.img

 

Spoiler

U-Boot 2019.10-armbian (Jan 05 2020 - 23:21:21 +0100)                           
                                                                                
Model: Firefly-RK3399 Board                                                     
DRAM:  3.9 GiB                                                                  
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0                                     
Loading Environment from EXT4...                                                
** Unable to use mmc 0:auto for loading the env **                              
In:    serial@ff1a0000                                                          
Out:   serial@ff1a0000                                                          
Err:   serial@ff1a0000                                                          
Model: Firefly-RK3399 Board                                                     
rockchip_dnl_key_pressed: adc_channel_single_shot fail!                         
Net:   eth0: ethernet@fe300000                                                  
Hit any key to stop autoboot:  0                                                
switch to partitions #0, OK                                                     
mmc0(part 0) is current device                                                  
** No partition table - mmc 0 **                                                
switch to partitions #0, OK                                                     
mmc1 is current device                                                          
Scanning mmc 1:1...                                                             
Found U-Boot script /boot/boot.scr                                              
2940 bytes read in 6 ms (478.5 KiB/s)                                           
## Executing script at 00500000                                                 
Boot script loaded from mmc 1                                                   
188 bytes read in 5 ms (36.1 KiB/s)                                             
9024550 bytes read in 572 ms (15 MiB/s)                                         
20703240 bytes read in 1303 ms (15.2 MiB/s)                                     
101691 bytes read in 16 ms (6.1 MiB/s)                                          
2698 bytes read in 10 ms (262.7 KiB/s)                                          
Applying kernel provided DT fixup script (rockchip-fixup.scr)                   
## Executing script at 39000000                                                 
## Loading init Ramdisk from Legacy Image at 04000000 ...                       
   Image Name:   uInitrd                                                        
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)                  
   Data Size:    9024486 Bytes = 8.6 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 f5686000, end f5f213e6 ... OK                             
ERROR: reserving fdt memory region failed (addr=0 size=0)                       
   Loading Device Tree to 00000000f5604000, end 00000000f5685fff ... OK         
                                                                                
Starting kernel ...       

 

Possible hint - The later (working) one (u-boot) starts on scanning dev 0 - mmc0(part 0) is current device    and does then scan dev 1

Loading init Ramdisk from Legacy Image at 06000000 ... (not working)  and Loading init Ramdisk from Legacy Image at 04000000 ...  (working)

 

Link to comment
Share on other sites

1. Enable full log mode, most likely there are messages about system startup and there may be answers why there is no startup.

2. Check which DTB is used and try other DTBS from the image. You may be using the default DTB mode that is set in u-boot. this DTB may not work with your model.

Link to comment
Share on other sites

4 hours ago, denni_isl said:

What would be the correct way of starting the kernel with the correct dtb files from /dev/mmcblk1p1 in the /boot directory?

 

I came in part way, forgive me if this is incorrect advice.  But there are some generalized instructions here which have been updated somewhat recently, maybe helpful for you?

Link to comment
Share on other sites

Quote

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                                                      
RunBL31 0x40000         

 

Did try this in u-boot and get error

 

 

And this

Quote

=> booti
Bad Linux ARM64 Image magic!

then this

extload mmc 1:1 0x00008000 /boot/Image
** No partition table - mmc 1 **

and this

ext4load mmc 0 0x00008000 /boot/dtb-5.8.6-rockchip64           
** Unrecognized filesystem type **

 

Link to comment
Share on other sites

On 11/17/2020 at 7:09 PM, denni_isl said:

-  Did the mistake of updating the installation card before the installation to emmc and that did not work.   The upgrade should be done from emmc only.

To be certain....

Do I understand correctly that it works for you if you transfer the older Armbian (v19.11.7) from SD to eMMC (probably by the means of nand-sata-install) and then run the upgrade?

Does the system boot with eMMC after the upgrade?

If it boots... does it recognise the SD card that you insert while the system is running (booted with eMMC)?

Link to comment
Share on other sites

5 hours ago, piter75 said:

To be certain....

Do I understand correctly that it works for you if you transfer the older Armbian (v19.11.7) from SD to eMMC (probably by the means of nand-sata-install) and then run the upgrade?

Does the system boot with eMMC after the upgrade?

If it boots... does it recognise the SD card that you insert while the system is running (booted with eMMC)?

 

Yes,  this is correct but it just recognizance the SD card as a medium not as a booting. 

If I update the SD card with v19.11.7 and and install it with armbian-config to emmc  it will not boot again.  

If I install the v19.11.7 before doing apt update; apt upgrade update to the emmc and then it will bee a fully functional installation

I do have a a SD image from 2017 that I can always boot up from though.

Link to comment
Share on other sites

There are always unallocated partitions left after emmc cleaning with blockthiscard /dev/mmcblk1rmp (unknown 4.2M)and /dev/mmcblkboot0 (read only 4.2M).

It is like the vendor "firefly" is locking the hardware from the software (image) upgrade(?).

 

and use ./upgrade_tool or rkdeveloptool to upload through usb otg -

Btw. is there any way to open up the .img files from those partitions?     Is the Vendor in control here?  

Did - dd if=/dev/zero of=/dev/mmcblk1 bs=4096 status=progress - the /dev/mmcblk1boot0 and /dev/mmcblk1rpmb are still there.

- When booting from Armbian_20.05.2_Firefly-rk3399_buster_current_5.4.43_desktop - u-boot gives this message -


 

Quote

Cannot find regulator pwm init_voltage
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

 

First is how firefly wants to have the partition table - Android stile - Rockchip

Then there is the "empty" emmc with the two boot partitions left.  

 

gpt_partion_table_firefly_emmc.png

mmcblk1boot0.png

mmcblk1rpm.png

sd_firefly_partiton_56MiB.png

Link to comment
Share on other sites

This is the boot messages from trying to boot  Armbian_20.05.2_Firefly-rk3399_buster_current_5.4.43_desktop

Spoiler

U-Boot 2020.07-armbian (Sep 03 2020 - 19:56:25 +0200)

SoC: Rockchip rk3399
Reset cause: POR
Model: Firefly-RK3399 Board
DRAM:  3.9 GiB
PMIC:  RK808
Cannot find regulator pwm init_voltage
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Firefly-RK3399 Board
Net:   eth0: ethernet@fe300000
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
3185 bytes read in 5 ms (622.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
116 bytes read in 5 ms (22.5 KiB/s)
15587897 bytes read in 664 ms (22.4 MiB/s)
27275776 bytes read in 1157 ms (22.5 MiB/s)
75813 bytes read in 11 ms (6.6 MiB/s)
2698 bytes read in 9 ms (292 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15587833 Bytes = 14.9 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 f5038000, end f5f159f9 ... OK
   Loading Device Tree to 00000000f4fbd000, end 00000000f5037fff ... OK

Starting kernel ...

 

Link to comment
Share on other sites

Spoiler

setenv m "1080p60hz" setenv m_bpp "32"

setenv condev "console=ttyS0,115200n8 console=tty0" # on both

setenv bootargs "root=/dev/mmcblk0p1 rootwait rw ${condev} no_console_suspend hdmimode=${m} m_bpp=${m_bpp} vout=${vout} fsck.repair=yes"

setenv loadaddr "0x11000000"

setenv dtb_loadaddr "0x1000000"

setenv initrd_loadaddr "0x13000000"

ext4load mmc 0:1 ${initrd_loadaddr} /boot/uInitrd

ext4load mmc 0:1 ${loadaddr} /boot/Image

ext4load mmc 0:1 ${dtb_loadaddr} /boot/meson64_odroidc2.dtb

booti ${loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}

 

Something similar to above commands might be the right way to bring it up coorectly.

 

Might try something similar to those commands to try to get to the images on the sd card.

How is it possible to obtain the correct addresses corresponding to those?

setenv loadaddr "0x11000000"

setenv dtb_loadaddr "0x1000000"

setenv initrd_loadaddr "0x13000000"

 

Got those messages from u-boot trying to boot Armbian_20.05.2_Firefly-rk3399_buster_current_5.4.43_desktop image, after - Starting kernel ..................

 

Spoiler

Starting kernel ...

SdmmcInit=2 0
BootCapSize=100000
UserCapSize=119276MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=61056MB
FwPartOffset=2000 , 0
StorageInit ok = 65244
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=0xb1cb0
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 OPK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

 

Link to comment
Share on other sites

Those partitions do always remain on the emmc;

/dev/mmcblk1boot0

/dev/mmcblk1rpmb - (Replay Protected Memory Block) "information is always available to the authorized users" .   This is probably

they key of the vendors (manufacturers) ultimate power over the product.  

 

Some well-known use cases include software version authentication - This might be the case.

 

"Secured: write protect can be enabled and disabled only for those who are authorized to
use the RPMB."

 

Boot partitions can be permanent, secured or power-on write protected.

 

So the takeaway from this thread is probably this information - that the newer armbian images for firefly-rk3399 are probably lacking access through the mechanism of Replay Protected Memory Block on the emmc drive.  

 

- My rockpro64 does not have any /dev/mmcblk1rpmb partition - just read only /dev/mmcblk2boot0 - which I have not studied yet.

 

Some reading;

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwi23oiOpo7tAhVvMewKHXaFCrsQFjACegQIAxAC&url=https%3A%2F%2Fdocuments.westerndigital.com%2Fcontent%2Fdam%2Fdoc-library%2Fen_us%2Fassets%2Fpublic%2Fwestern-digital%2Fcollateral%2Fwhite-paper%2Fwhite-paper-emmc-security.pdf&usg=AOvVaw3vy_3cNBFO1aNLZVNwA-aK

Link to comment
Share on other sites

4 hours ago, denni_isl said:

So the takeaway from this thread is probably this information - that the newer armbian images for firefly-rk3399 are probably lacking access through the mechanism of Replay Protected Memory Block on the emmc drive.

Armbian does not use those hardware eMMC partitions.

 

Can you try to boot this image (https://users.armbian.com/piter75/Armbian_20.11.0-trunk_Firefly-rk3399_buster_current_5.9.9_minimal.img.xz) with SD and provide console logs - it should be more verbose that the default one.

Link to comment
Share on other sites

2 hours ago, piter75 said:

Armbian does not use those hardware eMMC partitions.

 

Can you try to boot this image (https://users.armbian.com/piter75/Armbian_20.11.0-trunk_Firefly-rk3399_buster_current_5.9.9_minimal.img.xz) with SD and provide console logs - it should be more verbose that the default one.

 

This is the output

 

Spoiler

U-Boot 2020.07-armbian (Nov 19 2020 - 14:46:07 +0100)

SoC: Rockchip rk3399
Reset cause: POR
Model: Firefly-RK3399 Board
DRAM:  3.9 GiB
PMIC:  RK808
Cannot find regulator pwm init_voltage
MMC:   mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Firefly-RK3399 Board
Net:   eth0: ethernet@fe300000
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
3185 bytes read in 6 ms (517.6 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
117 bytes read in 4 ms (28.3 KiB/s)
12434832 bytes read in 534 ms (22.2 MiB/s)
27574784 bytes read in 1170 ms (22.5 MiB/s)
76119 bytes read in 11 ms (6.6 MiB/s)
2698 bytes read in 9 ms (292 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    12434768 Bytes = 11.9 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 f533a000, end f5f15d50 ... OK
   Loading Device Tree to 00000000f52bf000, end 00000000f5339fff ... OK

Starting kernel ...


CTRL-A Z for help | 1500000 8N1 | NOR | Minicom 2.7.1 | VT102 | Online 15:48 | ttyUSB0 

 

And for comparison  the image actually working - Armbian_19.11.7_Firefly-rk3399_bionic_legacy_4.4.208_desktop

 

Spoiler

U-Boot 2019.10-armbian (Jan 05 2020 - 23:21:21 +0100)

Model: Firefly-RK3399 Board
DRAM:  3.9 GiB
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from EXT4...
** Unable to use mmc 0:auto for loading the env **
In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Firefly-RK3399 Board
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
** No partition table - mmc 0 **
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2940 bytes read in 6 ms (478.5 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
187 bytes read in 5 ms (36.1 KiB/s)
8626223 bytes read in 548 ms (15 MiB/s)
20492296 bytes read in 1290 ms (15.1 MiB/s)
101178 bytes read in 15 ms (6.4 MiB/s)
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    8626159 Bytes = 8.2 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 f56e7000, end f5f20fef ... OK
ERROR: reserving fdt memory region failed (addr=0 size=0)
   Loading Device Tree to 00000000f5665000, end 00000000f56e6fff ... OK

Starting kernel ...

[   55.308735] mali ff9a0000.gpu: Failed to get pvtm
[   55.317459] ERROR: Bad of_node_put() on /gpu@ff9a0000
[   60.044499] CONFIG-ERROR) dhd_conf_set_bufiovar: country setting failed -2

Armbian 19.11.7 Bionic ttyFIQ0

firefly login:
CTRL-A Z for help | 1500000 8N1 | NOR | Minicom 2.7.1 | VT102 | Online 15:52 | ttyUSB0

 

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines