Skip to main content

[TriCore] Raised SMU alarm when debugging - Knowledgebase / FAQs by core architecture / TriCore - Lauterbach Support

[TriCore] Raised SMU alarm when debugging

If the SMU is set up strict, some debugger accesses might cause an SMU Alarm (SRI bus error), because the chip can not differentiate between illegal and debugger accesses.

Usually this is caused when the debugger tries to set software breakpoints on a flash memory region. Use the command

MAP.BOnchip < addressrange >

to force the debugger to set onchip breakpoints in the respective memory region.

To prevent all debugger accesses to a certain memory region, the command MAP.DenyAccess < addressrange > can be used.

Helpful Unhelpful

2 of 2 people found this page helpful

Add a comment

To prove you are a human, please tell us the text you see in the CAPTCHA image