PSoC™ 6 SDK Forum Discussions

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

Hello,

When I use modus,through the function uxTaskGetStackHighWaterMark(),I could confirm the task stack.

But,I don't know how to comfirm the maximum usage of system stack .

Question 1  : Is there any way to do it？

※When I use Keil, an htm file will be generated after the project is compiled, and I can find the maximum usage of the stack through this file.　

Question 2:  Is there a similar file after compiling?

Hi,

As title. Does CE222221 PSoC 6 MCU Voice Recorder sample code support in Modustoolbox??

I found below thread. It seems only on PSoC creater??

https://community.infineon.com/t5/PSoC-6-SDK/PSoC-62-transfer-I2S-input-to-I2S-output/m-p/170225#M211

Austin

ref: https://community.infineon.com/t5/AIROC-Bluetooth/MTB-PSoc6-BLE-OTA-Bootloader/m-p/330105#M1173

The example from the discussion posting above implements DFU for BLE with a non-upgradable stack. Has anyone successfully implemented the upgradable stack example for MTB? 

Thanks!

Josh

I am trying to use the example mtb-example-psoc6-mcuboot-basic on CY8CKIT-062_BLE, but I cannot get it to compile following the instructions on github (https://github.com/Infineon/mtb-example-psoc6-mcuboot-basic). I am using MTB 2.4.0.

I created a new ModusToolbox Application and selected my board (CY8CKIT-062-BLE) then selected "MCUboot-Based Basic Bootloader". After attempting to build; however, I was greeted by 328 errors like the ones below which aren't making sense to be because the macro is clearly defined above in the file.

The discussion post (https://community.infineon.com/t5/PSoC-6-SDK/Example-project-build-errors-mtb-example-psoc6-mcuboot-basic/m-p/266495) seems to discuss a similar issue with the older version of this MCUboot example that was caused by MCUboot v1.8.1, but the current version of the MCUboot example I am using (release-4.0.0) was released 5 days ago, and claims it solves this issue. 

Any help would be greatly appreciated. I have been developing in PSOC Creator, and I am trying to decide if it is worth converting the project to MTB asap, but if I can't even get a basic OTA working soon, I will have to forget it. 

如附件 是modus2.4操作QSPI的工程，gImage_2_2[20]这个数组没有烧录到外部flash中，读取的数据是外部flash原来的数据。 同样的代码modus2.2就操作正常，请大神帮我看下是什么问题，已经折腾我三天了。这个代码以前也是赛普拉斯AE帮我搞的，现在为了方便开发，需要移植到modus2.4上面。