The following debug probes are directly supported by LPCXpresso IDE for general debug connections:
The LPC-Link2 debug probe is available as a standalone debug probe or built into LPCXpresso V2 and LPCXpresso V3 boards.
When used in conjunction with the LPCXpresso automatically downloads CMSIS-DAP or "Redlink" firmware into the RAM of the probe. LPC-Link2 can then be used with LPCXpresso IDE to debug all NXP LPC Cortex-M MCUs.
However, the debugging of LPC2000 (ARM7) / LPC3000 (ARM9) parts is not supported by LPCXpresso IDE via LPC-Link2.
Note: CMSIS-DAP and J-Link firmware images suitable for programming into flash (using LPCScrypt) are also available for LPC-Link2 (see below).
CMSIS-DAP is a debug probe protocol defined by ARM. Implementations are available for a number of development boards and debug probes, including:
LPC-Link2 debug probes
LPCXpresso V2 / V3 boards
Various mbed compatible boards, including LPC800-MAX, LPCXpresso824-MAX, mbed LPC1768 and Embedded Artists LPC4088 QuickStart Board
Keil uLink-ME and uLink2 debug probes
CMSIS-DAP support has been implemented in LPCXpresso IDE as a layer in the "Redlink" protocol. This enables CMSIS-DAP debug probes to be used with LPCXpresso IDE to debug all NXP LPC Cortex-M MCUs. However the debugging of LPC2000 (ARM7) / LPC3000 (ARM9) parts is not supported.
The LPC-Link (or LPC-Link1) probe is built in to the original LPCXpresso board. It can be used with LPCXpresso IDE to debug the following MCU series:
LPC2000 (ARM7) / LPC3000 (ARM9)
LPC800 (Cortex-M0+)
LPC1100 (Cortex-M0) - excluding LPC11xxLV
LPC1200 (Cortex-M0)
LPC1300 (Cortex-M3)
LPC1700 (Cortex-M3)
LPC1800 (Cortex-M3)
LPC4000 (Cortex-M4)
LPC4300 (Cortex-M4 + Cortex-M0)
only a single debug connection can be made at a time.
Note: Debugging of parts released in 2014 and later (including LPC11U6x, LPC11E6x, LPC1500 and LPC5410x) may work with LPC-Link, but are not tested or supported combinations.
A debug probe produced by Code Red Technologies before their acquistion by NXP, Red Probe+ (and the earlier Red Probe) can be used with LPCXpresso IDE to debug the following MCU series:
LPC2000 (ARM7) / LPC3000 (ARM9)
LPC800 (Cortex-M0+)
LPC1100 (Cortex-M0)
LPC1200 (Cortex-M0)
LPC1300 (Cortex-M3)
LPC1700 (Cortex-M3)
LPC1800 (Cortex-M3)
LPC4000 (Cortex-M4)
LPC4300 (Cortex-M4 + Cortex-M0)
only a single debug connection can be made at a time.
Note: Debugging of parts released in 2014 and later (including LPC11U6x, LPC11E6x, LPC1500 and LPC5410x) may work with Red Probe+, but are not tested or supported combinations.
A development board produced by Code Red Technologies before their acquistion by NXP, the built-in debug probe (RDB-Link) on this board can be used for debugging by LPCXpresso IDE. Note that only the onboard LPC1768 MCU can be debugged.
A development board produced by Code Red Technologies before their acquistion by NXP, the built-in debug probe on this board is closely related to the LPC-Link2 hardware and can be used for debugging by LPCXpresso IDE using automatically downloaded "redlink" firmware. Note that only the onboard LPC4078 MCU can be debugged.
Support for GDB server based debug connections is also provided by LPCXpresso IDE. This feature enables the use of 3rd party debug probes, such as Segger J-Link and P&E Micro Multilink. When debugging with GDB server connections, some functionality may be disabled (such as peripheral views and trace).
For more information on using Segger J-Link with LPCXpresso, visit: http://www.segger.com/nxp-lpcxpresso.html
For more information on P&E Micro's GDB server and debug probes, visit : P&E Microcomputer Systems: Over 30 years as an Industry leader in Embedded Systems Development Tools...