

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
