topic Re: S32K324: Why are variable changes in Cache not visible in the debugger? in S32K

S32K324: Why are variable changes in Cache not visible in the debugger?

aprilaaa — Mon, 26 Jan 2026 06:23:11 GMT

I am currently working with the S32K324 and noticed an issue when use trace32 observing variables during debugging. Specifically, I can observe changes to variables in non-cacheable sections, but not those in cacheable sections.

// This change is visible
volatile uint32 g_cnt __attribute__((section(".non_cacheable_data")));

// This change is NOT visible
volatile BaseType_t testResult = 0x33U;

g_cnt++; // Observed change: OK
testResult = 0x5AU; // Observed change: FAIL (Value remains 0x33 or unchanged in memory window)

aprilaaa_0-1769408579878.png

aprilaaa_0-1769408474300.png

Re: S32K324: Why are variable changes in Cache not visible in the debugger?

davidtosenovjan — Mon, 26 Jan 2026 09:17:32 GMT

There are some TRACE32 options affecting this

(1) OnCE access - SYStem.CpuAccess

(2) NEXUS access - SYStem.MemAccess and SYStem.Option DUALPORT

Also it depends on used access class (you may see it in the memory dump window for instance) - see attached manual screenshot.

access_classes.png

Try to use access class DC.

Otherwise I would recommend to contact Lauterbach support.

Re: S32K324: Why are variable changes in Cache not visible in the debugger?

rweiss — Mon, 23 Feb 2026 13:40:01 GMT

The screenshot shows the state before the assignment takes place. You would have to do at least one more step to execute the variable assignment.