- 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
- :
- 2366506_en-US
2366506_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2366506_en-US
2366506_en-US
After flashing the tflm_modelrunner SDK example (FreeRTOS + lwIP, USE_RTOS defined), my FRDM-MCXN947 no longer responds to SWD. LinkServer v25.6 with MCU-Link V3.128 reports Ee(42). Could not connect to core on all operations including mass erase. The MCU-Link probe is detected correctly in Device Manager. When pressing SW3+RESET, Windows detects a USB enumeration but no driver installs and blhost reports no device found.
How can I recover the board?
Update: I was able to download the led_blinky example on Linux, but the problem persists on Windows 10.
Also, on both operating systems, I usually receive the following warning:
"Project is configured for device MCXN947 but the selected probe reports being connected to device MCXN947VDFT. Are you sure you want to continue?"
When trying to download a program for the first time (I don't know if this is related).
Update - RESOLVED:
The issue was resolved by uninstalling the MCU-Link device entries from Windows Device Manager and allowing Windows to re-enumerate them on reconnection.
Specifically, two entries were removed: "MCU-LINK FRDM-MCXN947 CMSIS-DAP" under Universal Serial Bus devices, and the corresponding MCU-Link VCom Port under Ports (COM & LPT). After reconnecting the USB cable, Windows reinstalled both drivers automatically and LinkServer was able to open the probe correctly.
Root cause appears to be a corrupted USB device state in Windows, likely triggered during a previous session with the tflm_modelrunner firmware (FreeRTOS + lwIP). The probe was visible to the system and correctly enumerated, but its handle could not be opened by redlinkserv.exe — causing Ee(42) on all operations including mass erase, flash, and gdbserver. Reinstalling the IDE, replacing redlinkserv.exe, and clearing USB registry entries did not resolve it. Only re-enumerating the device from Device Manager fixed the issue.