XC164CS Memory corruption when debugging

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
User14151
Level 1
Level 1
Hi, this is the first time that I face this kind of problem:

in my XC164CS application, while debugging with DAS miniWiggler without setting breakpoints and halting the execution manually certain range of memory are corrupted.

If I set some breakpoints this phenomenon doesn't happen.

Anybody have encountered a similar problem? Is there a workaround?

Thanky you,

kind regards
0 Likes
1 Reply
Not applicable
Hello Kornelio,

this sound like a timing issue. I don't know the "DAS miniWiggler" but is it possible to trace some data?
Can you create a breakpoint like "Break and resume" or "Break after the functions was reached e.g. 10 times?
0 Likes