The J-Link also has the option of further software enhancements with the production flash programming utility (J-Flash). As can be seen on the above table, it is in fact six times slower than SEGGER’s J-Link. Since I-jet can only be used with the IAR Embedded Workbench for ARM, it is already quite limited compared to J-Link’s flash programming speed. This makes J-Link + flash breakpoints the only real option to debug in QSPI flash on these devices.
Note: Hardware breakpoints are not usable in QSPI flash on many Cortex-M based devices. GDB based ones) can easily download to flash without the need to add any custom flash algo in the IDE J-Link does all the work Flash breakpoints (unlimited number of breakpoints when debugging in flash).writing in the memory window can be used to change constants in flash) Makes flash behave like RAM in the debugger (e.g.
With J-Link, all features known from internal flash are also available in memory-mapped QSPI flash:
However, it eventually became a full replacement and even successor of parallel NOR flash. In the beginning, SPI NOR flash was usually a custom connection and not standardized, with advanced MCUs and QSPI flash memory-mapped made visible in the MCU address space. J-Link supports the programming of memory-mapped QSPI NOR flash via the standard methods described above.
0 kommentar(er)
