This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Help to debug boot issue

Hello

I have done a custom PCB based on Olinuxino open-source hardware. I'm having the following messages when I'm trying to boot, can someone help me to identify how to solve this?

U-Boot SPL 2021.04+olimex-1-20211108.075936 (Nov 08 2021 - 08:00:41 +0000)
DRAM: 2048 MiB
Trying to boot from MMC1
ASSERT: lib/xlat_tables_v2/xlat_tables_core.c:1150
BACKTRACE: START: assert
0: EL3: 0x48910
1: EL3: 0x4bd24
2: EL3: 0x4985c
3: EL3: 0x49964
4: EL3: 0x440bc
5: EL3: 0x11fac
6: EL3: 0x1189c
BACKTRACE: END: assert

Thanks in advance.

Top replies

Zhifei Yang over 3 years ago +2

I assume you are using Arm Trusted Firmware from the limited assertion log information. See https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/lib/xlat_tables_v2/xlat_tables_core.c for...

Parents

0 Zhifei Yang over 3 years ago in reply to eric976

It is weird that after "starting kernel...", the code execution flow shows "INFO: BL3-1: Next image address = 0x41000000
INFO: BL3-1: Next image spsr = 0x3c5". From u-boot, you should configure and jump to Linux kernel address, but you jumps the BL31 wrongly or at least BL31 entry point overlaps part of your kernel memory.
Cancel
Up 0 Down

Cancel

Reply

0 Zhifei Yang over 3 years ago in reply to eric976

It is weird that after "starting kernel...", the code execution flow shows "INFO: BL3-1: Next image address = 0x41000000
INFO: BL3-1: Next image spsr = 0x3c5". From u-boot, you should configure and jump to Linux kernel address, but you jumps the BL31 wrongly or at least BL31 entry point overlaps part of your kernel memory.
Cancel
Up 0 Down

Cancel

Children

No data