- 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
- 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
-
- NXP Tech Blogs
- Home
- :
- MCUXpresso Software and Tools
- :
- Kinetis Design Studio
- :
- PE Micro Multilink and Windows 10 problem
PE Micro Multilink and Windows 10 problem
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
PE Micro Multilink and Windows 10 problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just installed KDS on a new windows 10 machine and am having problems with the PE micro Multilink universal debugger. The drivers are installed. In device manager I see Jungo with USB multilink 2.0 and windriver. On my win 7 machine if I plug in the debugger the lights come on on the PE Micro even without KDS running. On win 10 they do not. Obviously I get an error when I try to debug on win 10. Are there different drivers for win 10? I came across a link for a patch to fix PE Micro driver problems but when I click on it, the link says the download does not exist. http://www.pemicro.com/downloads/download_file.cfm?download_id=460
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, I have it working. In KDS I had to go into Install new software, and select PE Micro updates and check PE Micro software and click next to install new stuff. I then had to go into the debugger settings and re-select the target micro.
Hopefully this will help someone...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was losing my mind. You are a life saver Larry.
For others, this worked for me. IF you are using SWD protocol make sure to check the box "SWD protocol" in the Debug Configurations menu
Alice_Yang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Larry,
Thanks for your sharing.
BR
Alice
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did find an updated driver:
Look for PE Hardware interface drivers Version 12 (Win XP/Vista/7/8/10) Its in small type.
and now the lights come on, but when I try to debug I get the following error:
Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:7222
Error message from debugger back end:
localhost:7222: The system tried to join a drive to a directory on a joined drive.
localhost:7222: The system tried to join a drive to a directory on a joined drive.
Any ideas what it means and how to fix?
BlackNight
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One reason for that message is that the 'launch' checkbox is not checked in the debug configuration, see
Fix for GDB and “The system tried to join a drive to a directory on a joined drive” | MCU on Eclipse
I hope this helps,
Erich
