- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 1365251_en-US
1365251_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1365251_en-US
1365251_en-US
Hi,
I am trying to use an MCU-LINK on a new PC (Windows 10 laptop) unfortunately without much success!
I installed mcuxpresso, and when I plug the MCU-LINK into a USB port it makes the usual noise like it is enumerating, but mcuxpresso cannot see the probe and in Windows device manager, there is a yellow warning triangle next to the "USB composite device" that appears with a message in device status that says "This device cannot start (Code 10). Insufficient system resources exist to complete the API"
I also tried manually downloading the MCU-LINK driver installer for Windows 10 from the NXP website, but still no success.
Any pointers please? This is a relatively new laptop which I would not expect to be short on resources for this.
Many thanks
-Nick
Hello,
I found myself with the exact same problem.
I just managed to solve it, so hopefully it can be usefull. I did the following:
Going to C:\nxp\LinkServer_26.6.137\MCU-LINK_installer\scripts , click in "program_CMSIS", then follow the instructions on the command pannel (i.e., Short Jumper J3 of the MCU-link -> Connect via USB the MCU-link -> press space bar).
(Otherwise you can try write "CMSIS" or look for "Program MCU-Link CMSIS-DAP" in the search bar of Windows to find directly the file).
After perfoming this, the device was properly recognised without warnings by the computer in Device Manager and i could successfully debug my board.
Not sure if related, or if it helped to work (maybe not required), but before performing that firmware update of the mcu-link i did:
1- Did "Windows Security" -> "App & browser control" -> Smart App Control settings -> off.
2- I re-installed the LinkServer installer, which you can find in "LinkServer for Microcontrollers" on nxp website.
Also, after doing firmware update:
1- open mcuxpresso IDE with "run as administrator", and then on the project Explorer, i opened the project folder, and in the bottom i deleted the folder "(*project_name*)_ LinkServer Debug.launch" before debugging the code.
This is the way that it worked for me. Hope someone finds it useful as well.
Best, Kans.
hi, im also using mcu-link, its working fine, when its connected directly to the laptop port, but when im using a usb hub, and connecting the mcu -link through that usb hub, the debbugging is not working, its throws an error, how can i overcome this?, im only having one port in my laptop, so its neccessary to use via an hub
I can think of two other alternatives:
One is making sure your Antivirus is not detecting the MCU-LINK as a threat, and disabling it for good measure.
The second is trying with a different computer. If the problem persists with a different machine, then we have reasons to believe that the problem could be MCU-LINK related. Otherwise, I believe the problem is most likely related to the OS or the cable.
I hope this helps.
thanks @EdwinHz
Yes, we downloaded the drivers from that location.
We are not using a USB hub, this is a direct connection.
Will try a different USB cable, but this seems unlikely.
Any other suggestions please? Thanks!
Hi @nickwallis,
The drivers that you installed manually were from the “MCU-Link installer for Windows 10” software found at the bottom of the MCU-Link Debug Probe website? If not, I would recommend reinstalling the drivers using this installer.
Check the connection to your MCU-LINK. If it’s connected to a USB hub try connecting it directly to the machine. Also try using a different USB cable.
Regards,
Edwin.