OK3399使用OTG升级变砖
使用OTG升级烧录update.img过程中，USB线松了导致升级失败，重新插入后再试，发现AndroidTool提示的是“发现MASKROM”而不是“发现Loader”，并且在第一步“下载Boot”就会失败，串口此时也无效了。改用TF卡尝试烧录后，串口有输出，但是最后是提示“WARNING:Please contact Forlinx”：
DDR Version 1.23 20190709
In
Channel 0: LPDDR3, 800MHz
CS = 0
MR0=0x58
MR1=0x58
MR2=0x58
MR3=0x58
MR4=0x2
MR5=0x1
MR6=0x5
MR7=0x0
MR8=0x1F
MR9=0x1F
MR10=0x1F
MR11=0x1F
MR12=0x1F
MR13=0x1F
MR14=0x1F
MR15=0x1F
MR16=0x1F
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
Channel 1: LPDDR3, 800MHz
CS = 0
MR0=0x58
MR1=0x58
MR2=0x58
MR3=0x58
MR4=0x2
MR5=0x1
MR6=0x5
MR7=0x0
MR8=0x1F
MR9=0x1F
MR10=0x1F
MR11=0x1F
MR12=0x1F
MR13=0x1F
MR14=0x1F
MR15=0x1F
MR16=0x1F
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x20
ch 1 ddrconfig = 0x101, ddrsize = 0x20
pmugrf_os_reg = 0x3280D280, stride = 0x9
OUT
Boot1: 2019-03-14, version: 1.19
CPUId = 0x0
ChipType = 0x10, 245
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=15028MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 79443
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 part:0, name: Main Data Partition, start:0x800, size:0x3b7138f
GPT part:1, name: UEFI:NTFS, start:0x3b71b8f, size:0x400
recovery gpt success!
no find partition:uboot.
LoadTrust Addr:0x4000
No find bl30.bin
Load uboot, ReadLba = 2000
hdr 0000000003380880 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,
Load OK, addr=0x200000, size=0xdace0
RunBL31 0x10000
NOTICE:BL31: v1.3(debug):22b599a
NOTICE:BL31: Built : 11:03:32, Jul 10 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 TEE-CORE:init_primary_helper:337: Initializing (1.1.0-223-g45f58ab9 #165 Thu Aug 15 00:59:09 UTC 2019 aarch64)
INF TEE-CORE:init_primary_helper:338: Release version: 1.2
INF 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 (Mar 10 2021 - 02:48:14 +0000)
Model: Forlinx OK3399 Evaluation Board
PreSerial: 2
DRAM:2 GiB
Sysmem: init
Relocation Offset is: 7dbe9000
Using default environment
no mmc device at slot 1
Found IDB in SDcard
dwmmc@fe320000: 1 (SD), sdhci@fe330000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 50Mhz
PartType: EFI
rockchip_get_boot_mode: Could not found misc partition
boot mode: None
init_resource_list: failed to get boot part, ret=-1
init_resource_list: failed to get resource part, ret=-1
Read kernel dtb failed, ret=-19
RKPARM: Invalid parameter part table
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Forlinx OK3399 Evaluation Board
board_modify_fdt
Writing to MMC(0)... done
display device not found
rockchip_set_serialno: could not find efuse device
switch to partitions #0, OK
mmc1 is current device
Found IDB in SDcard
Bootdev(atags): mmc 1
CLK: (uboot. arml: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
CLK: (uboot. armb: enter 24000 KHz, init 24000 KHz, kernel 0N/A)
aplll 816000 KHz
apllb 24000 KHz
dpll 800000 KHz
cpll 24000 KHz
gpll 800000 KHz
npll 600000 KHz
vpll 24000 KHz
aclk_perihp 133333 KHz
hclk_perihp 66666 KHz
pclk_perihp 33333 KHz
aclk_perilp0 266666 KHz
hclk_perilp0 88888 KHz
pclk_perilp0 44444 KHz
hclk_perilp1 100000 KHz
pclk_perilp1 50000 KHz
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
WARNING:Please contact Forlinx
系统是win10，请问接下来该如何处理 加密信息丢失，需要返厂重新刷加密信息 MASKROM设备是从安卓系统烧录其他系统时，没有擦除flash第一次升级失败而出现的，我都是再点一次升级就没问题了，正常烧写，然后就编程loader设备了 你好，请问你这个问题解决了吗，我也出现了相同的问题 这个板子发回我司后，没有重新刷加密信息，直接操作OTG烧写尝试，想要复现问题，但是直接OTG烧写成功，这种情况按手册操作OTG烧写即可。 现发现不同电脑的USB口驱动能力不同，也会导致如帖问题，出现该问题也可尝试更换USB口重新烧写验证。
页:
[1]