- 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
- :
- 2399883_en-US
2399883_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2399883_en-US
2399883_en-US
Hello,
I am using the S32K344EVB-T172 and am unable to connect to the onboard OpenSDA/PEmicro debugger.
Sometimes, when I connect the Debug USB cable, the Debug LED does not turn ON, and the onboard debugger is not detected by the PC, preventing me from starting a debug session.
I have already tried:
Multiple USB data cables
Different USB ports
Resetting and power cycling the board
Testing with no external hardware connected
Has anyone encountered this issue before? Is there a recommended recovery procedure, firmware update, or hardware/jumper check for the onboard OpenSDA debugger?
Thank you.
Thank you for your response.
Yes, I have updated the PEmicro drivers to the latest version. I was previously able to flash and debug the EVB successfully, but recently the onboard OpenSDA debugger is not detected at times because the Debug LED does not turn ON after connecting the Debug USB.
I have also verified that the jumpers are correctly set as per the S32K3X4EVB-T172 Quick Start guide. Could you please advise if any additional checks or OpenSDA firmware recovery steps are recommended, or if this could indicate a hardware issue?
Hi @SourabhJ
Have you updated the PEmicro drivers to the latest version? Were you previously able to flash the EVB successfully?
Could you also verify that the jumpers are configured as described in the "Set Up Jumpers in the S32K3X4EVB-T172 Evaluation Board" section of the MCU Automotive Board Quick Starts?
BR, VaneB
Hi @SourabhJ
Could you please confirm whether only LEDs D14 and D15 are not turning on, or if the three LEDs located next to the voltage regulators are also OFF?
If you have access to an external debugger, such as a PEMicro Multilink or SEGGER J-Link, could you try connecting through the J12 (20-pin Cortex Debug) connector on the board? This would help us verify whether the S32K344 MCU is still responding properly, independent of the onboard debugger.
Also, what was the last application or firmware that was programmed onto the board before this issue started to occur?