Difference between revisions of "IDE accesses illegal memory regions"
(Created page with "__TOC__ We have seen some IDEs or 3rd party applications (e.g. GDB) which request memory accesses to invalid memory regions. By default, the J-Link software has to perform th...") |
(No difference)
|
Latest revision as of 14:45, 2 August 2019
Contents
We have seen some IDEs or 3rd party applications (e.g. GDB) which request memory accesses to invalid memory regions. By default, the J-Link software has to perform those requested memory accesses because it does not know if a region is invalid (e.g. reserved memory space) or not. The result of such an illegal memory access highly depends on the device. Some just ignore the request and return an error, others enter a unrecoverable confused state. In latter case, the debug session crashes and a power-on-reset of the target hardware is required.
Solution
Using the J-Link Command String map region, a specific memory range can be set to illegal. Once a range has been set to illegal, the DLL ignores all memory accesses (read / write) to this region.
- J-Link script file template: Exclude illegal memory regions
- How to use J-Link script files: Using J-Link script files