论坛 › 飞凌RK3399开发板技术支持专版 › RK3399重新烧写boot.img后系统一直重启

lvzeshuai 发表于 2021-10-22 10:15:55

RK3399重新烧写boot.img后系统一直重启

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, 246
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=15028MB
FwPartOffset=2000 , 100000
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=7695MB
FwPartOffset=2000 , 0
StorageInit ok = 260376
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
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
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
Found IDB in SDcard
dwmmc@fe320000: 1 (SD), sdhci@fe330000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 50Mhz
PartType: RKPARM
boot mode: recovery (misc)
## Resetting to default environment
Writing to MMC(0)... done
switch to partitions #0, OK
mmc1 is current device
Found IDB in SDcard
Bootdev(atags): mmc 1
Load FDT from recovery part
DTB: rk-kernel.dtb
I2c0 speed: 400000Hz
PMIC:RK808
vdd_center 900000 uV
vdd_cpu_l 900000 uV
vdd_log 930000 uV
In:    serial
Out:   serial
Err:   serial
Model: Forlinx OK3399 Board(Linux)
board_modify_fdt
Writing to MMC(0)... done
Display force mode in dtb
Writing to MMC(0)... done
Error binding driver 'fixed regulator': -22
"Synchronous Abort" handler, esr 0x96000010
* Relocate offset = 000000007dbe9000
* ELR(PC)    =   0000000000251644
* LR         =   00000000002517ec
* SP         =   000000007bddcc80

* ESR_EL2    =   0000000096000010
      EC == 100101, Exception from a Data abort, from current exception level
      IL == 1, 32-bit instruction trapped

* DAIF       =   00000000000003c0
      D == 1, DBG masked
      A == 1, ABORT masked
      I == 1, IRQ masked
      F == 1, FIQ masked

* SPSR_EL2   =   00000000a0000349
      D == 1, DBG masked
      A == 1, ABORT masked
      I == 0, IRQ not masked
      F == 1, FIQ masked
      M == 0, Exception taken from AArch64
      M == 1001, EL2h

* SCTLR_EL2=   0000000030c51835
      I == 1, Icaches enabled
      C == 1, Dcache enabled
      M == 1, MMU enabled

* HCR_EL2    =   000000000800003a
* VBAR_EL2   =   000000007dde9800
* TTBR0_EL2=   000000007fff0000

x0 : 0000000008400009 x1 : 00000000fff0bdf7
x2 : 0000000000000020 x3 : 0000000000000023
x4 : 000000007dea5fd0 x5 : 0000000000006c70
x6 : 000000000000000a x7 : 0000000000000044
x8 : 0000000000000003 x9 : 0000000000000008
x10: 00000000ffffffe0 x11: 000000007de8ed6b
x12: 000000007dea91d0 x13: 000000007dea8ff0
x14: 0000000008300000 x15: 00000000ffffffff
x16: 0000000000008080 x17: 0000000000a80181
x18: 000000007bde0d10 x19: 000000000830bc7c
x20: 000000007be38be0 x21: 0000000000003738
x22: 000000007be397d0 x23: 000000007be12d20
x24: 000000007de95b45 x25: 000000007be12a08
x26: 000000007be38fb0 x27: 000000007de98938
x28: 0000000000000000 x29: 000000007bddce60

SP:
7bddcc80:00000000 00000000 00000000 00000000
7bddcc90:00000000 00000000 7de99a9d 00000000
7bddcca0:00000000 00000000 00000000 00000000
7bddccb0:7de99ae4 00000000 7de99b0a 00000000
7bddccc0:7de99b57 00000000 7de99ba4 00000000
7bddccd0:7de99be4 00000000 7de99c24 00000000
7bddcce0:7de99c61 00000000 00000000 00000000
7bddccf0:00000000 00000000 7de99c9e 00000000
7bddcd00:7bddce60 00000000 7dde9a0c 00000000
7bddcd10:0830bc7c 00000000 7be38be0 00000000
7bddcd20:7fff0000 00000000 0800003a 00000000
7bddcd30:30c51835 00000000 7bddcc80 00000000
7bddcd40:a0000349 00000000 7dde9800 00000000
7bddcd50:000003c0 00000000 96000010 00000000
7bddcd60:7de3a644 00000000 08400009 00000000
7bddcd70:fff0bdf7 00000000 00000020 00000000


Call trace:
PC:   [< 00251644 >]
LR:   [< 002517ec >]

Stack:
      [< 00251644 >]
      [< 002517ec >]
      [< 002335a8 >]
      [< 002346a8 >]
      [< 00234808 >]
      [< 00242554 >]
      [< 00242bb8 >]
      [< 002335c4 >]
      [< 002346a8 >]
      [< 0023499c >]
      [< 002349c4 >]
      [< 00206d68 >]
      [< 00202dd4 >]
      [< 0027dc28 >]
      [< 00218d4c >]
      [< 0020199c >]

Copy above stack info to a file(eg. dump.txt), and
execute command in your U-Boot project: ./scripts/stacktrace.sh dump.txt

Resetting CPU ...
这是串口打印信息，一直重复

兵兵兵兵鸭 发表于 2021-10-22 13:43:13

请重新烧写update.img，看能否启动，测试是否是镜像的原因。

lvzeshuai 发表于 2021-10-22 14:03:05

兵兵兵兵鸭 发表于 2021-10-22 13:43
请重新烧写update.img，看能否启动，测试是否是镜像的原因。

尝试过了，按照步骤做了张烧写TK卡，插上去上电还是一直在重启，没有进行烧写。

兵兵兵兵鸭 发表于 2021-10-23 13:50:38

lvzeshuai 发表于 2021-10-22 14:03
尝试过了，按照步骤做了张烧写TK卡，插上去上电还是一直在重启，没有进行烧写。

请描述一下拿到开发板时能否正常启动，您进行了什么操作。
您描述说烧写boot导致重启，是OTG分布烧写boot，请尝试OTG烧写update.img
tf卡无法烧写,可能是未识别到tf卡，若尝试后仍不成功，请在工作日通过电话联系我司

lvzeshuai 发表于 2021-10-25 15:03:41

兵兵兵兵鸭 发表于 2021-10-23 13:50
请描述一下拿到开发板时能否正常启动，您进行了什么操作。
您描述说烧写boot导致重启，是OTG分布烧写boo ...

板子到手时是没问题的，使用期间我多次更改设备树，编译镜像，使用OTG将boot.img烧入开发板，没有出现过问题。
只是最近一次，更改了设备树中显示部分的一组参数，编译完成后，使用OTG将boot.img烧入开办板之后，再次开机，打印信息就一直在显示重启。
tf卡烧写update.img也不成功，不知道是不是未识别到。
您所说的尝试OTG烧写update.img，我这边目前电脑上OTG的软件根本就识别不到loader设备，可能是因为一直在重启的原因，也正是因为OTG无法进行烧写才想尝试用tf卡进行烧写的。

兵兵兵兵鸭 发表于 2021-10-25 16:19:46

lvzeshuai 发表于 2021-10-25 15:03
板子到手时是没问题的，使用期间我多次更改设备树，编译镜像，使用OTG将boot.img烧入开发板，没有出现过 ...

识别不到loader设备这个问题，如果操作没有问题的话，请将瑞芯微开发工具解压到全英文的路径下进行尝试

兵兵兵兵鸭 发表于 2021-10-25 16:30:27

lvzeshuai 发表于 2021-10-25 15:03
板子到手时是没问题的，使用期间我多次更改设备树，编译镜像，使用OTG将boot.img烧入开发板，没有出现过 ...
OTG分步烧写boot.img 应该是在发现loader设备后的操作，您可以将过程截图或者录制视频通过销售或者邮件发送至技术服务，帮您排查问题

查看完整版本: RK3399重新烧写boot.img后系统一直重启