In some cases where a fatal error appear, the debugger no longer ends with a crash. Download Software Version 8. Breakpoints and memory can now be modified during execution. For Cortex-M3, the debugger sometimes left hardware breakpoints enabled when stepping which made the target seem to be halted on the current address. The alleged promise of proprietary tools is that they just work; the problem is that when they do not, you have little recourse to understand why, verses something like openocd where you can actually debug the tool itself. This has been corrected.
|Date Added:||7 November 2008|
|File Size:||69.51 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
MX Quick start board i. Program corrections Some CPUs do not emit any trace information for certain instructions during single step due to a bug in the silicon.
Must not be used for product development or any other kind of commercial use. This led to that no IRQs were triggered any more.
MX27 Lite board i.
IAR Software for NXP kits
J-Link Ultra can be calibrated to ensure accurate power measurements. It may not be ira for production purposes. When using the restore breakpoints feature and ARM11, the debugger could set two breakpoints at the same address.
We continuously add support for new kits. Email Required, but never shown. Access to specific memory areas no longer results in the fatal error message “Failed to prepare indirect memory access, no RAM area configured! Debugging on custom hardware is not supported and not allowed.
The error message when setting a breakpoint fails was not informative enough. A more obvious warning is now displayed when multiple symbols are found in the debug images. You’re going to have to be far more specific. Unlimited breakpoints in flash available for evaluation only.
CPU reset is now performed properly for Stellaris devices that need special reset handling. When using the Attach to program option and having the stack plugin enabled, the debugger crashed when ending a debug session. C-SPY no longer terminates unexpectedly when stopping on a breakpoint that executes a macro that removes breakpoints.
Sign up using Email and Password.
Possible to show trace timestamps. In addition, it is available in the The diagnostic message “Debugger problem discovered: C-RUN is size-limited to 12 Kbytes of code, excluding constant data. There was an inconsistency between the J-Link control panel and the C-SPY debugger when showing information about the actual breakpoint type used on target. To calibrate Izr Ultra follow these steps: