version number, for example, V2_220). The directory has a "Readme.txt" file and few subdirectories that contain other
package components, including host device drivers, MCU-Link firmware, and scripts to program CMSIS-DAP and J-Link
firmware.
Host drivers are usually installed automatically during firmware package installation. In case you need to install the drivers
manually, refer to the "Host Configuration" section of the "Readme.txt" file.
Before powering up the board for updating MCU-Link firmware, you must switch MCU-Link to ISP mode (USB1).
5. To force MCU-Link to boot in ISP mode (USB1), short jumper JP25.
6. Connect the J1 connector on the board to the USB port of the host computer through a USB micro-B cable. MCU-Link
gets powered up in ISP mode (USB1). The red MCU-Link status LED (D16) lights up (for more details on MCU-Link
LEDs, see
). The board gets enumerated as a human interface device (HID) class device.
7. Program the MCU-Link firmware into the MCU-Link internal flash using the instructions provided in the "Firmware
Installation Guide" section of the "Readme.txt" file. Use the scripts provided to program the CMSIS-DAP or J-Link
firmware.
8. Disconnect the board from the host computer, remove jumper JP25, and reconnect the board.
Now, the system behaves differently based on whether the CMSIS-DAP or J-Link firmware was programmed:
• If the CMSIS-DAP firmware was programmed, then the red status LED (D16) fades in/out repeatedly (“breathing”),
while the green USB status LED (D14) stays ON constantly. In this case, four devices (three HID devices and one
VCOM port) get enumerated, as shown in the figure below.
Figure 15. MCU-Link enumerated devices for CMSIS-DAP firmware
• If the J-Link firmware was programmed, then only the green VCOM LED (D17) is used to indicate status. The VCOM
LED lights up when MCU-Link boots. Then, when you start a new debug session, the LED blinks to indicate that debug
activity is in progress. In this case, two devices (one J-Link driver USB device and one J-Link CDC UART port VCOM
port) get enumerated.
Now, your LPC55S36-EVK board is ready for use. If you use the board with MCUXpresso IDE version 11.3 or higher, you are
notified in case a more recent firmware version is available for MCU-Link. If you use the board with a different IDE, ensure that
latest MCU-Link firmware version is installed on the board.
3.3 Supported MCU-Link features
The table below summarizes the MCU-Link features supported on the LPC55S36-EVK board.
Table 24. Supported MCU-Link features
Feature
Description
Serial wire debug (SWD) / serial wire debug
trace output (SWO)
Allows SWD-based debugging with SWO for profiling and/or low overhead
debug standard I/O communication
Virtual communication (VCOM) serial port
Adds a serial COM port on the host computer, and connects it to the
target MCU by using MCU-Link as a USB-to-UART bridge
USB serial input/output (USBSIO
) port
Adds a USB serial I/O port on the host computer, and connects it to the
target MCU by using MCU-Link as a USB-to-SPI bridge or USB-to-I2C
bridge. It also allows MCU-Link to be used as a USB-to-GPIO bridge to
connect the MCU-Link LPC55S69 target to the host computer.
Table continues on the next page...
NXP Semiconductors
MCU-Link Debug Probe
LPC55S36-EVK Board User Manual, Rev. 1, 24 January 2022
User Manual
43 / 49