Part Number: AM4372
Other Parts Discussed in Thread: TPS65218
Hello,
Randomly it happens that during secure call execution, during authentication, l3 bus errors is triggered.
[ 363.535361] ------------[ cut here ]------------
/**
* u32 omap_smc2(u32 id, u32 falg, u32 pargs)
* Low level common routine for secure HAL and PPA APIs.
* @id: Application ID of HAL APIs
* @flag: Flag to indicate the criticality of operation
* @pargs: Physical address of parameter list starting
* with number of parametrs
*/
ENTRY(omap_smc2)
stmfd sp!, {r4-r12, lr}
mov r3, r2
mov r2, r1
mov r1, #0x0 @ Process ID
mov r6, #0xff
mov r12, #0x00 @ Secure Service ID
mov r7, #0
mcr p15, 0, r7, c7, c5, 6
dsb
isb
dmb
smc #0
b end_omap_smc2 @ Execution reaches here if there was no
@ interruption in the secure world.
nop @ Execution reaches here if secure world
@ is interrupted.
mov r12, #0xfe
mcr p15, 0, r12, c7, c5, 6
dsb
isb
dmb
smc #0
end_omap_smc2:
ldmfd sp!, {r4-r12, pc}
ENDPROC(omap_smc2)
Can the secure side where ROM code run, trigger an l3 bus error? Bus error is triggered just after executing first smc code above and before leaving the omap_smc2() function