topic Re: MCU-Link is not found by Device Manager on Windows 10 in LPC Microcontrollers

MCU-Link is not found by Device Manager on Windows 10

Kratz — Tue, 19 Jan 2021 17:34:19 GMT

When using windows 10, the device manager does not show the MCU-Link as connected, it does not show "ports", and it makes no difference whether J3 is jumped or not. The driver files were installed. MCUXpresso cannot find MCU-Link either. MCUXpresso finds the P&E just fine. I will try to restart my computer next and try again.

What should I do to get Windows 10 to find the USB connection to the MCU-Link?

Re: MCU-Link is not found by Device Manager on Windows 10

ZhangJennie — Wed, 20 Jan 2021 01:51:20 GMT

I use win10, I can use MCU-Link on it without issue.

Please make sure you download the driver information files and utility MCU-LINK CMSIS package to update the firmware. Note that MCUXpresso IDE 11.2.1 or later will automatically install the driver information files.

Please strictly follow the steps as this video shows.

https://www.nxp.com/document/guide/get-started-with-the-mcu-link:GS-MCU-LINK

Have a nice day,

Jun Zhang

Re: MCU-Link is not found by Device Manager on Windows 10

Kratz — Wed, 20 Jan 2021 13:30:36 GMT

Thank you Jun for responding. MCUXpresso version 11.3.0.5222 is being used. I have followed the video. It seems the problem is that my computer is not picking up the board. Both drivers installed correctly. A re-start of the computer was performed. When J3 is jumped the red LED lights up like the video, but the script does not behave the same as the video. Also the MCU-Link does not show up as a USB device. I plan to try a different USB cable thinking perhaps this cable is only good for charging not data. Is that possible? Is there any other driver my computer needs to find the USB-Multilink?

Re: MCU-Link is not found by Device Manager on Windows 10

Kratz — Wed, 20 Jan 2021 19:33:31 GMT

A programming cable solved the problem. The charging cable was the issue.

Re: MCU-Link is not found by Device Manager on Windows 10

Kratz — Tue, 26 Jan 2021 15:12:51 GMT

For some reason my computer would not run the script. Running the script on another computer allowed the program to be updated. My original computer now shows the debugger connected.