05022024

Last update2016/05/28 14:38

Back 現在地: Home パートナー segger-tools Model comparison

Model comparison

Model comparison

Model comparison

 

The following tables show the features which are included in each J-Link / J-Trace model.

Hardware 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 string from Segger.

Hardware features
J-Link J-Link Pro J-Link Ultra J-Trace for Cortex-M3 J-Trace
USB
Ethernet no no no no
Supported cores ARM7
(no tracing)
ARM9
(no tracing)
ARM11


(no tracing)


(no tracing)

Cortex-A5
(no tracing)

(no tracing)
Cortex-A8
(no tracing)

(no tracing)
Cortex-M0
(no tracing)
Cortex-M1
(no tracing)
Cortex-M3
(no tracing)
Cortex-M4
(no tracing)
Cortex-R4
(no tracing)

(no tracing)
Renesas RX
(no tracing)

(no tracing)
JTAG
SWD no
SWO no
ETM Trace no no no
Software features
J-Flash
(optional)


(optional)

(optional)

(optional)
Flash Breakpoints2
(optional)

(optional)

(optional)

(optional)
Flash Download1
GDB Server
(optional)

(optional)

(optional)

(optional)
RDI
(optional)

(optional)

(optional)

(optional)

1 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.

2 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.