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.

AWR6843: MSS not getting an abort when accessing the L3 DSS dedicated memory

Part Number: AWR6843

Hello,

My customer want to ensure that unwanted MSS accesses to the L2 DSS dedicated memory are properly trapped by an abort exception, but this does not happen.

As per the directions given in the Image Creation document, they set SHARED_MEM_ALLOC to 0x00000006 so to dedicate to DSS all banks 0-5.

They experimented on CCS and the TI EVM. Their code is a test code that on the MSS side accesses all the 0x5100_0000-0x51FF_FFFF range, i.e. all L2 banks from 0 to 7. They did not get an abort at any time and could see on the DSS side that the related MSS write accesses were reflected in the DSS memory window, addresses 0x2000_0000-0x201F_FFFF (They have set a breakpoint on the abort handler and observed that it is never executed.)

This contradicts the technical reference manual that says that "Any access to the DSP-dedicated space by the MSS results in an ABORT".

Could you please help understanding this behavior? Is there something else to configure so to trap such unwanted accesses? Thank you.


Best regards,
François.