Error start Debug with MiniProg4 on cy8c6247BZI-D54

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
ravo
Level 5
Level 5
10 likes received 5 comments on blog 5 solutions authored

Dears in Modus Toolbox 3.0 I got very often this error "Error in final launch sequence" when starting Debug sessionfor demo project "USB Audio Device (FreeRTOS)https://github.com/Infineon/mtb-example-psoc6-usb-audio-device-freertos

Error message:

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: Connection timed out.
Failed to execute MI command:
-target-select remote localhost:3333
Error message from debugger back end:
localhost:3333: Connection timed out.
localhost:3333: Connection timed out.

What could be wrong ?

Regards

Radim

0 Likes
1 Solution
lyubun
Employee
Employee
First solution authored First like received First reply posted

Hi all,

Error messages from the problem statement can be shown in the various situations. One of common situation is when target is not powered. In that case, use "kitprog3 power_config on 3300" command to set power power on target via Miniprog4 or use external power. If the issue is still reproduced after that, provide logs from the console to better understand the problem.

View solution in original post

4 Replies
VitaS_81
Employee
Employee
10 sign-ins 5 replies posted First solution authored

Radim, could you please attach the full log from ModusToolbox when this happens and describe the exact steps to reproduce? From the message above, looks like the openOCD is not launched or port is blocked for some reason (e.g., by firewall)

YuZh
Moderator
Moderator
Moderator
100 replies posted 10 likes received 50 sign-ins

Hi:

It seems your launch sequence is wrong. Please try other examples to see if you have the same problem.

And the following answer from my colleague is right,  your PC block or stop mtb tools to start connect to minprog4. Close all unrelated software processes。

zhichao

0 Likes
Vison_Zhang
Moderator
Moderator
Moderator
First comment on KBA 750 replies posted 250 sign-ins

Did you external power your PSOC6 board because when you try to program/debug the P6 from MTB, miniprog4 not powered the external board by default. 

0 Likes
lyubun
Employee
Employee
First solution authored First like received First reply posted

Hi all,

Error messages from the problem statement can be shown in the various situations. One of common situation is when target is not powered. In that case, use "kitprog3 power_config on 3300" command to set power power on target via Miniprog4 or use external power. If the issue is still reproduced after that, provide logs from the console to better understand the problem.