Why Trace 32 Lauterbach debugger GUI always meet data abort in L4 based AMSS

Question: Why Trace 32 Lauterbach debugger GUI always meet data abort in L4 based AMSS?
Answer: This is normal in L4 based software, it is needed for setting up MMU mapping.
Detail:
In L4 based amss software, the data abort is normal, it will cause iguana service to create the mapping between virtual adress and physical address.
And progressive load also depend on it.
To avoid always break in trace32, you need to disable onchip trigger in trace32 menu: Break/On-chip trigger
or add your trace32's config.t32

TRONCHIP.SET IRQ OFF

TRONCHIP.SET DABORT OFF

TRONCHIP.SET PABORT OFF

TRONCHIP.SET SWI OFF

TRONCHIP.SET UNDEF OFF

TRONCHIP.SET RESET OFF

TRONCHIP.SET STEPVECTOR OFF




generally, if you load by cmm script, the on-chip trigger will be disabled in cmm scripts.