This website uses cookies so that we can provide you with the best user experience. To read more about the cookies we use and to change your settings see our Cookies Policy.
Access Breakpoint doesn't stop the code execution when a specific memory location is being accessed (and its data value has changed). For example, there is a memory corruption of a global variable and you'd like to find a problematic code. An access breakpoint is configured to hit on write...
Using Logical Built-In Self Test ( LBIST) can cause unexpected resets of the CPU, which disables debug communication and deletes all breakpoints. Possible solution Enable option Quick LBIST detection in Hardware | CPU options | SoC . Explanation Quick LBIST detection means that debug statu...
Hardware breakpoints are set by configuring certain on-chip logic components. Hardware breakpoints are a limited resource , and their number varies, depending on the architecture and the implementation. By default winIDEA reserves one hardware breakpoint for high-level debugging ( Debug / ...
Timestamp messages can fill a lot of (or entire) trace buffer after the CPU reaches a breakpoint but before the debugger detects the CPU has stopped. Possible solution Refer to the Record Trace to a Breakpoint tutorial in winIDEA Help.
Almost every action in winIDEA can be scripted using winIDEA SDK. Combining the scripting feature with the ability to trigger such scripts you get a really powerful combination that can be used for all sorts of things. Solution: 1. Create an initialization script via the Watch Window and s...
To stop the microcontroller on the Xth pass through a function, winIDEA offers option conditional breakpoints: each time the breakpoint is passed the expression (if present) will be evaluated and if it evaluates to true, it will count as one more pass. When the breakpoint is passed as many...
This topic describes what to do if winIDEA Editor window shows inconsistent or no glyph margin (grey strip or column on the left side of the Editor), icons (glyphs, LoC (Line of Code) markers, debug line symbols,...) for debugging of the opened source file thus disabling source-level debug...
For high level debug commands (Run until, Stepping...) hardware execution breakpoints are used. One hardware breakpoint is optionally reserved for these functions. Possible solution: Enable option Reserve one breakpoint f or high level debugging in dialog Debug / Debug Options / Debugging ...
Implementing a software breakpoint means inserting a special breakpoint instruction to the execution memory. This means that the actual memory, containing the code, will be modified. If the Verify option is enabled, winIDEA compares the actual memory with the Program File. Since the memory...
Find a bug in your code using basic debugging principles: Breakpoint bisecting Stepping into and over the code Using microcontroller documentation For a m ore detailed visualization of the whole configuration procedure follow the Breakpoint bisecting Tutorial!