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

PSoC™ 6 SDK Forum Discussions

ravo
Level 4
10 likes given 50 replies posted 10 questions asked
Level 4

Dears,

when debugging project running on CY8CPROTO-062-4343W kit using KitPro3 after few minutes it stop debugging:

Error: kitprog3: get_power command failed
Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1015 ms). Workaround: increase "set remotetimeout" in GDB
Error: kitprog3: get_power command failed
Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1012 ms). Workaround: increase "set remotetimeout" in GDB
Error: CMSIS-DAP command CMD_DISCONNECT failed.
Error: CMSIS-DAP command CMD_CONNECT failed.
Warn : keep_alive() was not invokedError: Error connecting DP: cannot read IDR in the 1000 ms timelimit. GDB alive packet not sent! (3027 ms). Workaround: increase "set remotetimeout" in GDB
Error: CMSIS-DAP command CMD_DISCONNECT failed.
Error: CMSIS-DAP command CMD_CONNECT failed.

When I disconnect and launch debug again, it will only report

Error: CMSIS-DAP command CMD_INFO failed.

If I close ModusToolbox and try to run Cypress Programmer (standalone) it only write:

Info : [CyBridge] Start API initialization
Info : [CyBridge] Hardware initialization complete 1784 ms
Error: [CyBridge] Error = Timeout sending bulk packet

And I must disconnect USB cable to kit (to reset Kitprog3) and start again. 

I have only idea that it could be due higher room temperature. I did not do any change in code... only doing debug session set breakpoints and watch variables. Prior to this it works normally for at least 2 days.

Could be something else wrong ?

Best Regards

Radim

0 Likes
1 Solution
Qi_Colin
Moderator
Moderator 25 solutions authored 100 replies posted 100 sign-ins
Moderator

Hi Radim:

Ok, I suggest you to do the cross test if this problem occur again.

Best Regard,

Colin

View solution in original post

4 Replies
Qi_Colin
Moderator
Moderator 25 solutions authored 100 replies posted 100 sign-ins
Moderator

Hi @ravo :

Have you done any cross test with another kit?

According to your log information, it seems that the kiprog3 has some troubles after working few minutes.

Best Regards

Colin

0 Likes
ravo
Level 4
10 likes given 50 replies posted 10 questions asked
Level 4

Dear Colin, yes I have another kits, but it look like that it is only on this one. Now today it is working normal.

I get this error when elaborating USB AUDIO demo (as I wrote in another thread, problem with custom launch): https://community.infineon.com/t5/PSoC-6/Unable-to-view-variable-s-value-in-ModusToolbox-Debug-mode/...

Radim

0 Likes
Qi_Colin
Moderator
Moderator 25 solutions authored 100 replies posted 100 sign-ins
Moderator

Hi Radim:

Ok, I suggest you to do the cross test if this problem occur again.

Best Regard,

Colin

ravo
Level 4
10 likes given 50 replies posted 10 questions asked
Level 4

Dear Coli, thanks for response I think so... maybe it was due "overheating"

I will continue to watch this, and If it will become more starts to fail again I will try another kit.

Regards Radim

0 Likes