The U-Boot does not start on the custom board using the LS1046A

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

The U-Boot does not start on the custom board using the LS1046A

Jump to solution
273 Views
Johnson_s
Contributor III

I am currently checking the boot process on a custom board using the LS1046A. After creating the PBL and U-Boot and writing them to the QSPI, the following log is output, and then nothing further is displayed:

INFO: BL31: Preparing for EL3 exit to normal world

INFO: Entry point address = 0x82000000

INFO: SPSR = 0x3c9

Since I have the LS1046ARDB on hand, I suspect that the hang is due to differences in hardware configuration. On the custom board, USB, SATA, and PCIe are not used, so they are not connected.

Are there any areas in the repository at https://github.com/nxp-qoriq/atf/tree/lf_v2.6 that might affect the operation? (DDR is functioning without any issues.)

0 Kudos
Reply
1 Solution
223 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please comment “erratum_a009007()” in arch/arm/cpu/armv8/fsl-layerscape/soc.c in u-boot source code.

If it doesn't help, please debug BL31 and u-boot with CodeWarrior for ARMv8.

Probably the "Inspect(attaching to the running target)" will help the customer. Please refer to the Inspect icon marked red in attached file inspect.png. After click this icon, CodeWarrior will attach to the target board, not affect the software running on the target board.

Then the disassembly code which the target board is executing will be captured and displayed in CodeWarrior IDE, please refer to the attached file disassemble.png.

Then refer to the following document to debug BL31 and u-boot.

https://community.nxp.com/t5/Layerscape-Knowledge-Base/Debugging-ATF-and-u-boot-with-CodeWarrior-for...

View solution in original post

0 Kudos
Reply
1 Reply
224 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please comment “erratum_a009007()” in arch/arm/cpu/armv8/fsl-layerscape/soc.c in u-boot source code.

If it doesn't help, please debug BL31 and u-boot with CodeWarrior for ARMv8.

Probably the "Inspect(attaching to the running target)" will help the customer. Please refer to the Inspect icon marked red in attached file inspect.png. After click this icon, CodeWarrior will attach to the target board, not affect the software running on the target board.

Then the disassembly code which the target board is executing will be captured and displayed in CodeWarrior IDE, please refer to the attached file disassemble.png.

Then refer to the following document to debug BL31 and u-boot.

https://community.nxp.com/t5/Layerscape-Knowledge-Base/Debugging-ATF-and-u-boot-with-CodeWarrior-for...

0 Kudos
Reply