debug launch fails: Timed out trying to launch GDB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

debug launch fails: Timed out trying to launch GDB

45 Views
jportero
Fresh Out Contributor
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,
 
0 Kudos
Reply
1 Reply

9 Views
PetrS
NXP TechSupport
NXP TechSupport

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.
 
BR, Petr
0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2406635%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3Edebug%20launch%20fails%3A%20Timed%20out%20trying%20to%20launch%20GDB%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2406635%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CDIV%3E%3CSPAN%3EHello%2C%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EI%20am%20using%20an%20S32K566%20board%20with%20S32%20Design%20Studio%203.6.10%20and%20an%20S32%20Debug%20Probe.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EI%20followed%20the%20tutorial%20step%20by%20step.%20The%20project%20builds%20successfully%2C%20but%20when%20i%20start%20debugging%20i%20get%20this%20error.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%22Launching%20anomaly%20detection%22%20has%20encountered%20a%20problem.%3C%2FDIV%3E%3CDIV%3EError%20in%20services%20launch%20sequence%3C%2FDIV%3E%3CDIV%3ETimed%20out%20trying%20to%20launch%20GDB%3C%2FDIV%3E%3CDIV%3EI%20have%20already%20tried%20creating%20a%20new%20debug%20configuration%20and%20checking%20the%20GDB%20paths%2C%20but%20the%20issue%20remains%3C%2FDIV%3E%3CDIV%3ECould%20you%20please%20advise%20what%20may%20cause%20this%20error%3F%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3EThanks%2C%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2406859%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20debug%20launch%20fails%3A%20Timed%20out%20trying%20to%20launch%20GDB%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2406859%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CDIV%3EThe%20error%20is%20quite%20generic%20and%20can%20be%20caused%20by%20several%20issues.%20Could%20you%20please%20provide%20more%20information%20to%20address%20this%3F%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3E1.%20Console%20log%20%E2%80%94%20the%20full%20text%20from%20the%20S32DS%20Console%20tab%20(not%20a%20screenshot).%20This%20can%20show%20exactly%20where%20the%20connection%20times%20out%20(probe%20found%3F%20target%20power%3F%20SWD%2FJTAG%20connect%3F%20reset%3F).%3CBR%20%2F%3E2.%26nbsp%3BVerify%20that%20the%20S32DS%20installation%20is%20complete%2C%20updates%20and%20desired%20extensions%20installed%3CBR%20%2F%3E3.%20Hardware%20-%26nbsp%3BIs%20it%20an%20NXP%20EVB%20or%20a%20custom%20board%3F%20How%20is%20the%20probe%20connected%20%E2%80%94%20USB%20or%20Ethernet%3F%3CBR%20%2F%3E4.%20Previously%20programmed%20state%20-%26nbsp%3BWas%20the%20MCU%20previously%20programmed%20with%20anything%20(especially%20HSE%2Fsecurity-related%20firmware%2C%20or%20a%20bootloader%20that%20modifies%20DAP%20access)%3F%3CBR%20%2F%3EWas%20it%20ever%20debugged%20successfully%20on%20this%20board%20before%3F%3CBR%20%2F%3E5.%20Simple%20project%20test%20%E2%80%94%20does%20the%20same%20failure%20occur%20with%20a%20freshly%20created%20Hello%20World%20%2F%20empty%20project%20on%20a%20clean%20workspace%3F%20This%20helps%20isolate%20whether%20it's%20project-specific%20or%20a%20board%2Fprobe%2Fenvironment%20issue.%3CBR%20%2F%3E6.%20Debug%20Configuration%20screenshot%20%E2%80%94%20specifically%20the%20Debugger%20tab%2C%20to%20verify%20the%20correct%20device%2C%20interface%20speed%2C%20and%20connection%20settings.%3C%2FDIV%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%3EBR%2C%20Petr%3C%2FDIV%3E%3C%2FLINGO-BODY%3E