- 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
- :
- 2406635_en-US
2406635_en-US
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2406635_en-US
2406635_en-US
Hello,
I am using an S32K566 board with S32 Design Studio 3.6.10 and an S32 Debug Probe.
I followed the tutorial step by step. The project builds successfully, but when i start debugging i get this error.
"Launching anomaly detection" has encountered a problem.
Error in services launch sequence
Timed out trying to launch GDB
I have already tried creating a new debug configuration and checking the GDB paths, but the issue remains
Could you please advise what may cause this error?
Thanks,
Hi,
The error is quite generic and can be caused by several issues. Could you please provide more information to address this?
1. Console log — the full text from the S32DS Console tab (not a screenshot). This can show exactly where the connection times out (probe found? target power? SWD/JTAG connect? reset?).
2. Verify that the S32DS installation is complete, updates and desired extensions installed
3. Hardware - Is it an NXP EVB or a custom board? How is the probe connected — USB or Ethernet?
4. Previously programmed state - Was the MCU previously programmed with anything (especially HSE/security-related firmware, or a bootloader that modifies DAP access)?
Was it ever debugged successfully on this board before?
5. Simple project test — does the same failure occur with a freshly created Hello World / empty project on a clean workspace? This helps isolate whether it's project-specific or a board/probe/environment issue.
6. Debug Configuration screenshot — specifically the Debugger tab, to verify the correct device, interface speed, and connection settings.
2. Verify that the S32DS installation is complete, updates and desired extensions installed
3. Hardware - Is it an NXP EVB or a custom board? How is the probe connected — USB or Ethernet?
4. Previously programmed state - Was the MCU previously programmed with anything (especially HSE/security-related firmware, or a bootloader that modifies DAP access)?
Was it ever debugged successfully on this board before?
5. Simple project test — does the same failure occur with a freshly created Hello World / empty project on a clean workspace? This helps isolate whether it's project-specific or a board/probe/environment issue.
6. Debug Configuration screenshot — specifically the Debugger tab, to verify the correct device, interface speed, and connection settings.
BR, Petr
No ratings