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

Studio Bluetooth Forum Discussions

sylvain_77176
Level 2
Level 2
First solution authored 5 replies posted 25 sign-ins

Hello infineon community,

I am contacting you because we are not able to program the CYBT343026-01 that is used on our prototype,

The configuration is :

1. Hardware:

we are using the HCI interface of an CYBT-343026-EVAL board,  switch are configured to low (if  we consider the position given in the screen below) and wires have been soldered to connect eval board to our prototype.

sylvain_77176_0-1650993939448.png

Detail of CYBT343026-01 connection on PROTOTYPE :

sylvain_77176_1-1650994677377.png

uarts, "Reset" and "Recover" pin are connected to a microcontroller that is setting the connected pin to high impedance during flash.

2. Software:

Before starting programming the sequence given below is realized:

“Press and hold the 'Recover' button on the kit.

Press and hold the 'Reset' button on the kit.

Release the 'Reset' button.

After one second, release the 'Recover' button.”

Then ChipLoader programming tool is used to program the CYBT and the result is given below :

C:\Cypress\Wiced_Smart_SDK\WICED-Smart-SDK\Tools\ChipLoad\Win32>ChipLoad.exe -BLUETOOLMODE -PORT COM5 -NOVERIFY -MINIDRIVER C:\Cypress\Wiced_Smart_SDK\WICED-Smart-SDK\Tools\ChipLoad\Win32\minidriver.hex -BTP C:\Cypress\Wiced_Smart_SDK\WICED-Smart-SDK\Tools\ChipLoad\Win32\CYP_TCV4.btp -CONFIG C:\Cypress\Wiced_Smart_SDK\WICED-Smart-SDK\Tools\ChipLoad\Win32\CYP_TCV4_download.hex
Download minidriver successfully had written 249 bytes to address 0x000D0200
Download minidriver successfully had written 249 bytes to address 0x000D02F9
Download minidriver successfully had written 249 bytes to address 0x000D03F2
Download minidriver successfully had written 249 bytes to address 0x000D04EB
Download minidriver successfully had written 249 bytes to address 0x000D05E4
Download minidriver successfully had written 249 bytes to address 0x000D06DD
Download minidriver successfully had written 249 bytes to address 0x000D07D6
Download minidriver successfully had written 249 bytes to address 0x000D08CF
Download minidriver successfully had written 249 bytes to address 0x000D09C8
Download minidriver successfully had written 249 bytes to address 0x000D0AC1
Download minidriver successfully had written 249 bytes to address 0x000D0BBA
Download minidriver successfully had written 249 bytes to address 0x000D0CB3
Download minidriver successfully had written 249 bytes to address 0x000D0DAC
Download minidriver successfully had written 249 bytes to address 0x000D0EA5
Download minidriver successfully had written 249 bytes to address 0x000D0F9E
Download minidriver successfully had written 249 bytes to address 0x000D1097
Download minidriver successfully had written 249 bytes to address 0x000D1190
Download minidriver successfully had written 249 bytes to address 0x000D1289
Download minidriver successfully had written 249 bytes to address 0x000D1382
Download minidriver successfully had written 249 bytes to address 0x000D147B
Download minidriver successfully had written 249 bytes to address 0x000D1574
Download minidriver successfully had written 249 bytes to address 0x000D166D
Download minidriver successfully had written 249 bytes to address 0x000D1766
Download minidriver successfully had written 249 bytes to address 0x000D185F
Download minidriver successfully had written 249 bytes to address 0x000D1958
Download minidriver successfully had written 249 bytes to address 0x000D1A51
Download minidriver successfully had written 249 bytes to address 0x000D1B4A
Download minidriver successfully had written 249 bytes to address 0x000D1C43
Download minidriver successfully had written 249 bytes to address 0x000D1D3C
Download minidriver successfully had written 249 bytes to address 0x000D1E35
Download minidriver successfully had written 249 bytes to address 0x000D1F2E
Download minidriver successfully had written 249 bytes to address 0x000D2027
Download minidriver successfully had written 249 bytes to address 0x000D2120
Download minidriver successfully had written 249 bytes to address 0x000D2219
Download minidriver successfully had written 249 bytes to address 0x000D2312
Download minidriver successfully had written 237 bytes to address 0x000D240B
Launch minidriver at 0x000D0200 succeeded
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Executing -- erasing chip
Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Terminated with error
Chip erase timeout (nLastProgressReportTime)

Any solution would be really appreciated 😄

Regards

0 Likes
1 Solution

Hello,

 

Thank you for your reply, the problem has been solved by the suppression of D17 and C119.

Best regards

View solution in original post

0 Likes
2 Replies
Owen_Zhang123
Moderator
Moderator
Moderator
500 solutions authored 250 sign-ins 1000 replies posted

Please pull the Reset pin to high after the recover. You may also use the module programmer tool:

https://community.infineon.com/t5/Knowledge-Base-Articles/WICED-Module-Programmer-User-Guide-KBA2250...

0 Likes

Hello,

 

Thank you for your reply, the problem has been solved by the suppression of D17 and C119.

Best regards

0 Likes