Debugging Variable Display Issues on ARM M7 with FreeRTOS using Lauterbach Trace32
Hey guys @MCU, MPU & Firmware i am currently developing a test device using an ARM M7 (NXP S32KXXX) MCU with FreeRTOS and debugging it with Lauterbach Trace32. The device reads Ethernet frames and sends response frames. While debugging, I encountered an issue where variables (locals, globals, stack) always show as 0 in Trace32, even though the code seems to execute correctly (e.g., a loop iterates as expected, but the loop index always appears as 0). The memory dump reflects the same static values, and cache flushing or MPU settings don't help. This issue persists across different hardware and optimization levels. Could this be due to a conflict between FreeRTOS and Trace32, or something related to the NXP S32DS and WindRiver Diab toolchain? How can I resolve this problem?
2 Replies
ensure the build uses debug symbols (-g) and -O0 optimization; verify Trace32's correct processor configuration and use SYStem.Up; temporarily disable cache and review MPU settings that may work
i think this guide will help you https://www2.lauterbach.com/pdf/ide_user.pdf