Hello,
I am currently working on a project involving DSP-ARM communication using mimxrt685-evk and encountering inconsistent memory access exceptions. Here are the details of my setup and the issue:
I'm attaching something like a pseudocode that may help convey my problem better.
Could you please help me understand the potential causes of this exception and provide some suggestions on debugging strategies?
It would also be really helpful if you could give some tips on how to avoid memory access issues.
Thanks in advance!
Best regards,
Shri
Hello Gavin,
Thanks for the response. Can you please elaborate on this because I could make out that there was a memory corruption but I'm seeing these statements on the cmd prompt even before I run the code on DSP and there is no crash point or a line in code where I get this exception, the code runs normally after I hit run. Should I be focusing checking on the M33 side?
Thanks,
shri
Hi @shri00 ,
This is a very strange phenomenon you describe. To be honest I haven't encountered this before.
After running DSP program in Xplorer IDE, xtensa_read_memory starts to work.
I don't quite understand xtensa_read_memory can be used without DSP code execution.
For example, if you use IAR or MCUXPRESSO IDE to debug a CM33 program. You cannot get Xplorer IDE error.
Best regards,
Gavin
Hi @shri00 ,
Thanks for your interest in NXP MIMXRT series!
I will work with you to resolve this issue. I have submitted this issue for internal discussion at the moment, so please give me some time. I will keep you updated here as soon as there are new developments. Thanks for your patience in advance!
Best regards,
Gavin
Hi @shri00 ,
Thanks for your patience.
The following responses, from experts is:
The excause 0xd(13 ) meant LoadStorePIFDataErrorCause Synchronous PIF data error during
LoadStore access and the address is 0x40202bb8.
0x40202bb8 is not a valid address, thus exception occurs.
It is likely a memory corruption issue.
Best regards<
Gavin