Nov 10, 2017
03:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 10, 2017
03:08 AM
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
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
Labels
- Tags:
- IFX
1 Reply
Not applicable
Nov 16, 2017
10:53 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 16, 2017
10:53 PM
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?
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?