Conditional breakpoints in winIDEA can help you stop the CPU on the Xth pass through a function: Each time the breakpoint is run into, t he expression (if present) is evaluated. If it is evaluated as true, it adds one more pass count. When the breakpoint is passed the specified number of t...
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 the option Reserve one breakpointfor high level debugging in the dialog Debug | Debug Options | Debu...
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...
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...
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 | ...
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 sa...
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 .
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...