ls1046a u-boot is not executed

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ls1046a u-boot is not executed

Jump to solution
997 Views
james13
Contributor I

Hello,

I used the ls1046a to build a customized board. However, the board does not boot. 
As shown in the log below, it stops at SPSR = 0x3c9.

log:
NOTICE: 8 GB DDR4, 64-bit, CL=11, ECC off
INFO: Time used by DDR driver 3020 ms
INFO: SoC workaround for Errata A008850 Post-Phase was applied
INFO: RCW BOOT SRC is SD/EMMC
INFO: esdhc_emmc_init
INFO: Card detected successfully
INFO: init done:
NOTICE: BL2: v2.4(release):LSDK-21.08
NOTICE: BL2: Built : 23:41:57, Aug 30 2022
INFO: Configuring TrustZone Controller
INFO: BL2: Doing platform setup
INFO: BL2: Loading image id 3
INFO: sd-mmc read done.
INFO: sd-mmc read done.
INFO: sd-mmc read done.
INFO: Loading image id=3 at address 0xfbe00000
INFO: sd-mmc read done.
INFO: Image id=3 loaded: 0xfbe00000 - 0xfbe0a62d
INFO: BL2: Loading image id 5
INFO: sd-mmc read done.
INFO: sd-mmc read done.
INFO: sd-mmc read done.
INFO: sd-mmc read done.
INFO: sd-mmc read done.
INFO: Loading image id=5 at address 0x82000000
INFO: sd-mmc read done.
INFO: Image id=5 loaded: 0x82000000 - 0x820e81d6
NOTICE: BL2: Booting BL31
INFO: Entry point address = 0xfbe00000
INFO: SPSR = 0x3cd
NOTICE: BL31: v2.4(release):LSDK-21.08
NOTICE: BL31: Built : 23:41:59, Aug 30 2022
NOTICE: Welcome to ls1046ardb BL31 Phase
INFO: ARM GICv2 driver initialized
INFO: BL31: Initializing runtime services
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x82000000
INFO: SPSR = 0x3c9


Is there a solution?
 
james13_0-1661841399426.png

 

 
0 Kudos
1 Solution
979 Views
yipingwang
NXP TechSupport
NXP TechSupport

Probably the system stuck at the end of ATF or the debugging of u-boot, please debug atf and u-boot to find out where it stuck.

Do you have CodeWarrior for ARMv8 and CodeWarrior TAP?

If yes, please refer to document https://community.nxp.com/t5/CodeWarrior-for-QorIQ-Knowledge/Use-CodeWarrior-for-ARMv8-to-Debug-U-bo... to debug u-boot.

The procedure to debug ATF is similar as debugging u-boot.

View solution in original post

0 Kudos
1 Reply
980 Views
yipingwang
NXP TechSupport
NXP TechSupport

Probably the system stuck at the end of ATF or the debugging of u-boot, please debug atf and u-boot to find out where it stuck.

Do you have CodeWarrior for ARMv8 and CodeWarrior TAP?

If yes, please refer to document https://community.nxp.com/t5/CodeWarrior-for-QorIQ-Knowledge/Use-CodeWarrior-for-ARMv8-to-Debug-U-bo... to debug u-boot.

The procedure to debug ATF is similar as debugging u-boot.

0 Kudos