This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: Unhandled External Abort received on 0x80000000 at EL3

Part Number: TDA4VM

Hi,

We are getting Flash Error at booting time.

Please find the attached Crash log, 

U-Boot SPL 2019.01-g66126341c8 (Dec 12 2019 - 21:52:41 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.8.0-v2019.08-3-g8644f (Terri')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Remoteproc 2 started successfully
** File not found /lib/firmware/j7-mcu-r5f0_0-fw **
Starting ATF on ARM64 core...

NOTICE: BL31: v2.1(release):ti2019.02-rc4
NOTICE: BL31: Built : 21:52:20, Dec 12 2019
I/TC:
I/TC: OP-TEE version: ti2019.02-89-ge5a8779-dev (gcc version 8.3.0 (GNU Toolchain for the A-profile 4
I/TC: Initialized

U-Boot SPL 2019.01-g66126341c8 (Dec 12 2019 - 21:52:53 +0000)
Detected: J7X-BASE-CPB rev E3
Trying to boot from MMC2


U-Boot 2019.01-g66126341c8 (Dec 12 2019 - 21:52:53 +0000)

SoC: J721E PG 1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E7
DRAM: 4 GiB
Flash: ERROR: Unhandled External Abort received on 0x80000000 at EL3!
ERROR: exception reason=0 syndrome=0xbf000002
PANIC in EL3 at x30 = 0x000000007000442c
x0 = 0x0000000000000000
x1 = 0x0000000000000060
x2 = 0x0000000000000060
x3 = 0x000000000000000b
x4 = 0x0000000000000062
x5 = 0x0000000000000008
x6 = 0x000000000000003b
x7 = 0x0000000000000000
x8 = 0x00000000fdec3808
x9 = 0x0000000000000008
x10 = 0x00000000000030e8
x11 = 0x00000000fdec35dc
x12 = 0x000000000000305a
x13 = 0x0000000000000da0
x14 = 0x00000000fdec358c
x15 = 0x00000000fdec3808
x16 = 0x000000000000fffc
x17 = 0x0000000000000000
x18 = 0x0000000000000000
x19 = 0x0000000000000000
x20 = 0x00000000bf000002
x21 = 0x00000000fded3950
x22 = 0x00000000800bd8e8
x23 = 0x00000000800b5d75
x24 = 0x00000000800b5d5d
x25 = 0x00000000deadbeef
x26 = 0x0000000000000005
x27 = 0x0000000000000000
x28 = 0x0000000000000000
x29 = 0x0000000070009960
scr_el3 = 0x000000000000073d
sctlr_el3 = 0x0000000030cd183f
cptr_el3 = 0x0000000000000000
tcr_el3 = 0x0000000080803520
daif = 0x00000000000002c0
mair_el3 = 0x00000000004404ff
spsr_el3 = 0x00000000200003c9
elr_el3 = 0x00000000fff3a358
ttbr0_el3 = 0x000000007000e420
esr_el3 = 0x00000000bf000002
far_el3 = 0x0000000000000000
spsr_el1 = 0x0000000000000000
elr_el1 = 0x0000000000000000
spsr_abt = 0x0000000000000000
spsr_und = 0x0000000000000000
spsr_irq = 0x0000000000000000
spsr_fiq = 0x0000000000000000
sctlr_el1 = 0x0000000030d00800
actlr_el1 = 0x0000000000000000
cpacr_el1 = 0x0000000000000000
csselr_el1 = 0x0000000000000000
sp_el1 = 0x0000000000000000
esr_el1 = 0x0000000000000000
ttbr0_el1 = 0x0000000000000000
ttbr1_el1 = 0x0000000000000000
mair_el1 = 0x0000000000000000
amair_el1 = 0x0000000000000000
tcr_el1 = 0x0000000000000000
tpidr_el1 = 0x0000000000000000
tpidr_el0 = 0x0000000000000000
tpidrro_el0 = 0x0000000000000000
dacr32_el2 = 0x0000000000000000
ifsr32_el2 = 0x0000000000000000
par_el1 = 0x0000000000000000
mpidr_el1 = 0x0000000080000000
afsr0_el1 = 0x0000000000000000
afsr1_el1 = 0x0000000000000000
contextidr_el1 = 0x0000000000000000
vbar_el1 = 0x0000000000000000
cntp_ctl_el0 = 0x0000000000000000
cntp_cval_el0 = 0x0000000000000000
cntv_ctl_el0 = 0x0000000000000000
cntv_cval_el0 = 0x0000000000000000
cntkctl_el1 = 0x0000000000000000
sp_el0 = 0x0000000070009960
isr_el1 = 0x0000000000000000
cpuectlr_el1 = 0x0000001b00000040
cpumerrsr_el1 = 0x0000000000000000
l2merrsr_el1 = 0x0000000000000000

Please give me a comment! We don't know the direction to resolve this issue?

  • Hi, 

    Can you give us a few more details about your system environment:

    1) Are you seeing this issue on a TI EVM, or your own custom board?

    2) Which bootmode are you trying to use?

    3) What was the flashing procedure that you used?

    NOTE: if the TDA4VM processor doesn't have access to all the standard devices that are regularly on the TI EVM (e.g., this is your own custom board), then you need to modify the device tree information, for both U-boot and Linux builds, to represent the actual devices that you have on your board.  For instance, if you don't have a Hyperflash device on your board, then make sure to remove that node from the device tree, before you build U-boot or Linux.

    Thanks,

    Jonathan 

  • Hi Jonathan,


    Thanks for the response. I missed the U-boot and dts changes. After the custom changes the issue got resolved.

    Thanks,
    Jegathesan S