

This means longer development times and more debugging frustration. Amongst all the devices tested, it has the lowest performance. While quite affordable, ST-Link is only available for use with STM8 and STM32 microcontrollers. Unlike the J-Link, it cannot set an unlimited number of flash breakpoints. ULINKpro also lacks the additional debugging features and performance that comes standard with SEGGER’s product line. And since it is restricted to KEIL uVision, it is unsuitable for flash programming in a production environment.

ULINKpro can only be used with the KEIL uVision and is more expensive than the industry standard J-Link.

In this test, J-Link is the clear winner. The ability to take full advantage of the development environment using the Unlimited Flash Breakpoint module also means you free your development from the hardware breakpoint restriction. 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
