PINE64

I download ROCKPro64_20190417_stock_android_9.0_emmcboot.img and flash it to emmc.

My board stop booting at u-boot.

Please look at below boot message and guide me how to fix this issue.




DDR Version 1.19 20190305
In
channel 0
CS = 0
MR0=0x98
MR4=0x2
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
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x98
MR4=0x2
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
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
Channel 0: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
Channel 1: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x20
ch 1 ddrconfig = 0x101, ddrsize = 0x20
pmugrf_os_reg[2] = 0x3281F281, stride = 0x9
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 237
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=59640MB
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 = 70323
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: ret0)
GPT part:  0, name:            uboot, start:0x4000, size:0x2000
GPT part:  1, name:            trust, start:0x6000, size:0x2000
GPT part:  2, name:             misc, start:0x8000, size:0x2000
GPT part:  3, name:         resource, start:0xa000, size:0x8000
GPT part:  4, name:           kernel, start:0x12000, size:0x10000
GPT part:  5, name:              dtb, start:0x22000, size:0x2000
GPT part:  6, name:             dtbo, start:0x24000, size:0x2000
GPT part:  7, name:           vbmeta, start:0x26000, size:0x800
GPT part:  8, name:             boot, start:0x26800, size:0x10000
GPT part:  9, name:         recovery, start:0x36800, size:0x20000
GPT part: 10, name:           backup, start:0x56800, size:0x38000
GPT part: 11, name:         security, start:0x8e800, size:0x2000
GPT part: 12, name:            cache, start:0x90800, size:0x100000
GPT part: 13, name:           system, start:0x190800, size:0x500000
GPT part: 14, name:         metadata, start:0x690800, size:0x8000
GPT part: 15, name:           vendor, start:0x698800, size:0x100000
GPT part: 16, name:              oem, start:0x798800, size:0x100000
GPT part: 17, name:              frp, start:0x898800, size:0x400
GPT part: 18, name:         userdata, start:0x898c00, size:0x6be33df
find part:uboot OK. first_lba:0x4000.
find part:trust OK. first_lba:0x6000.
LoadTrust Addr:0x6000
No find bl30.bin
Load uboot, ReadLba = 4000
Load OK, addr=0x200000, size=0xe1b90
RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):370ab80
NOTICE:  BL31: Built : 09:23:41, Mar  4 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(1181): pd status 3e
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-195-g8f090d20 #6 Fri Dec  7 06:11:20 UTC 2018 aarch64)

INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2

INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-02833-g5b99639 (Apr 16 2019 - 14:29:24 +0800)

Model: Rockchip RK3399 Evaluation Board
PreSerial: 2
DRAM:  2 GiB
Sysmem: init
Relocation Offset is: 7dbe3000
Using default environment

dwmmc@fe320000: 1, sdhci@fe330000: 0
Bootdev(atags): mmc 0
sdhci_transfer_data: Transfer data timeout
sdhci_transfer_data: Transfer data timeout

I just got this board today. how did you get the logs?

(08-16-2019, 09:47 PM)dazza5000 Wrote: [ -> ]I just got this board today. how did you get the logs?

 You need an Serial interface to connect it on the gpio pins, that will allow you to read and run commands on the board (in u-boot). https://www.amazon.com/stores/DSDTECH/node/14584394011 this is what I'm using, hope I'm not getting banned for external links

(08-17-2019, 05:15 AM)octavian Wrote: [ -> ]

(08-16-2019, 09:47 PM)dazza5000 Wrote: [ -> ]I just got this board today. how did you get the logs?

 You need an Serial interface to connect it on the gpio pins, that will allow you to read and run commands on the board (in u-boot). https://www.amazon.com/stores/DSDTECH/node/14584394011 this is what I'm using, hope I'm not getting banned for external links

, you will not getting banned :-)

Cheers that's good to know.
On topic: I am getting the exact same error when using eMMC and I'm bypassing the SPI flashl

Test with old image (
ROCKPro64_20180518_stock_android_7.1_emmcboot.img
ROCKPro64_20180828_stock_android_8.1_emmcboot.img ) work fine.

But ROCKPro64_20190417_stock_android_9.0_emmcboot image stop at U-Boot.

My emmc is san disk 64G.

(08-17-2019, 05:15 AM)octavian Wrote: [ -> ]

(08-16-2019, 09:47 PM)dazza5000 Wrote: [ -> ]I just got this board today. how did you get the logs?

 You need an Serial interface to connect it on the gpio pins, that will allow you to read and run commands on the board (in u-boot). https://www.amazon.com/stores/DSDTECH/node/14584394011 this is what I'm using, hope I'm not getting banned for external links

I have one of these:

https://store.pine64.org/?product=padi-serial-console

Now I just need to learn how to use it