MCU-Link installation

[#1]

This article was updated on July 10th to reflect the new, improved and simplified methods to install and program the firmware on MCU-Link probes. The same information is being added to the Getting Started page for MCU-Link and MCU-Link Pro. LinkServer is the utility that should be used instead of the old MCU-Link firmware update utility. The article is based on the standalone MCU-Link and MCU-Link Pro probes, but the same information applies to all FRDM and EVK boards with MCU-Link (check the correct jumper for MCU-Link ISP mode on your board, if needed).

Note: MCU-Link moved from using USB-HID to WinUSB, so for older versions of MCUXpresso IDE (11.6.1 and older) or other systems that cannot use WinUSB we retained the old firmware update utility for version 2.263 of the firmware. As many customers were inadvertently using this old version, we now only have this posted on the MCU-Link Architecture page.

Overview of MCU-Link installation

Setting up your MCU-Link debug probe is very simple. MCU-Link debug probes are supported on host computers running a Windows 10/11, MacOS X, or Ubuntu Linux operating systems (OS). The debug probe works with standard OS drivers.

The LinkServer utility package provides all the required and for Windows platforms this also includes information files to provide user-friendly device names. LinkServer itself provides a GDB server, flash programming and other features, along with MCU-Link firmware update capability. You may also see an MCU-Link firmware update utility for version 2.263, but only install this if you cannot use WinUSB drivers for MCU-Link or if you are using MCUXpresso 11.6.1 or an earlier version (see your board user guide for more information).

If the MCU-Link firmware version is 3.122 or later, an automatic firmware update can be done using LinkServer (version 1.4.85 or later), otherwise a manual update is necessary after placing the MCU-Link into In-System Programming (ISP) mode. The ISP jumper for MCU-Link is J3 and for MCU-Link Pro it is J4.

Installation steps

Download and install the LinkServer utility package, change directory to the installation directory and follow the steps below:

Plug in your MCU-Link / MCU-Link Pro and use the LinkServer application to ensure it is detected by using the linkserver probes command:

Now use the LinkServer auto update command to attempt to update the firmware, using the probe identifier number (#) from the last step:

If the update is successful the new version will be reported, and you are ready to use your MCU-Link.

If the update fails, unplug your MCU-Link, install the ISP jumper and reconnect. Then run the program_CMSIS.cmd script from the scripts directory:

Next steps and other utilities

You MCU-Link should now work with any IDE that supports CMSIS-DAP probes, but is guaranteed to work with MCUXpresso IDE or MCUXpresso for Visual Studio Code with no further setup needed. As future releases of firmware become available these IDEs will inform you.

There are several useful commands and utilities included with LinkServer; refer to the readme markdown file in the installation for more details.

MCU-Link probes can also be used with the LIBUSBIO library to provide USB to serial bridges for test and development. MCU-Link is also fully supported by the FreeMASTER debug tool, which provides very powerful, customizable visualization and control of variables. Also note that MCU-Link probes are fully compatible with the MCUXpresso SEC secure programming / provisioning tool and the Secure Provisioning SDK which provides the source for the utilities that it uses.

[Riven]

I can't find the mcu link install program. I want to upgrade my board fw via windows' program.

[ErichStyger]

You can find it in the LinkServer installer here: https://nxp.com/linkserver

See as well https://mcuoneclipse.com/2023/05/14/linkserver-for-microcontrollers/

[AAlex]

Hi,

I'm having issues with updating the firmware on the MCU-link regardless of the method used. It appears the ISP mode is not detected on the board. The red LED does light up though (see attached SS).

Additionally, there is a typo in your UM11931 manual, in paragraph 3.2:. It mentions J4 but it's actually J3:

To update the MCU-Link’s firmware it must be powered up in (USB) ISP mode. To do this insert jumper J4 then connect MCU-Link to your host computer using a micro B USB cable connected to J1.

[ErichStyger]

Yes, it is J3 for the MCU-Link and J4 for the MCU-Link Pro (this article has it correct).

Just to be sure (for MCU-Link, not Pro):

1) set J3 jumper (upper green jumper as seen below )

- re-power the board with the jumper installed (the jumper is only checked at power-up)

Otherwise: what is your device manager showing? It should show up as HID device:

I hope this helps,

Erich

[ErichStyger]

Just some other thoughts:

if doing update with the command line, no jumper setting is needed (see https://mcuoneclipse.com/2024/05/11/updating-mcu-link-cmsis-dap-debug-probe-firmware-jumper-less/).

Linkserver probes

should list the connected probes.

then run

Linkserver probe #1 update auto

to update it

[AAlex]

Hi @ErichStyger ,

I tried the auto method first, without the jumper and it didn't work either.

Device manager is showing the probe as a Vcom Port. 

[brendonslade]

Hi @AAlex 

You can only use the auto method if the version of firmware in your MCU-Link is 3.122 or later. This is because the older firmware doesn't have the bootloader needed to support the auto update. If this is the case then you have to power up the board in ISP mode and using the program_CMSIS.cmd script to update the firmware. The linkserver probes command will show you the firmware version you have.

Can you confirm you have version 3.122 or later when trying to do the auto update?