Model comparison SEGGER J-Link and J-Trace
The following table shows features and supported MC cores related to the different J-Link / J-Trace models.
Hardware features
| J-Link | J-Link Pro | J-Link Ultra | J-Trace CM3 | J-Trace | ||
| USB | ||||||
| Ethernet | ||||||
| ARM 7 | ||||||
| ARM 9 | ||||||
| ARM 11 | ||||||
| Cortex-A5 | ||||||
| Cortex-A8 | ||||||
| Cortex-A9 | ||||||
| Cortex-M0 | ||||||
| Cortex-M1 | ||||||
| Cortex-M3 | ||||||
| Cortex-M4 | ||||||
| Cortex-R4 | ||||||
| Renesas RX | ||||||
| JTAG | ||||||
| SWD | ||||||
| SWO | ||||||
| ETM Trace |
Software features
Software features are features implemented in the software primarily on the host. Software features can either come with the J-Link or be added later using a license key from Segger.
| J-Link | J-Link Pro | J-Link Ultra | J-Trace CM3 | J-Trace | ||
| J-Flash | ||||||
| Flash Breakpoints (4) | ||||||
| Flash Download (3) | ||||||
| GDB Server | ||||||
| RDI |
(3) Most IDEs come with their own flashloaders, so in most cases this feature is not essential for debugging your applications in flash. The J-Link flash download (FlashDL) feature is mainly used in debug environments where the debugger does not come with an own flashloader (e.g. the GNU Debugger). For more information about flash breakpoints, please refer to Flash Download.
(4) The flash breakpoint feature allows setting an unlimited number of breakpoints even if the application program is not located in RAM, but in flash memory. Without this feature, the number of breakpoints which can be set in flash is limited to the number of hardware breakpoints (typically two for ARM 7/9, six for Cortex-M3). For more information about flash breakpoints, please refer to Flash Breakpoints.
