- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
F/W is programming to CYBT-333047-02 mounted on the board as shown in the following thread, but Erace ends without completing.
Programming an EZ-BT WICED Module – KBA223428
I have multiple boards, but I can't program about 3 boards.
What do you think is the problem?
[Command]
ChipLoad -BLUETOOLMODE -REBAUDRATE 115200 -LAUNCHADDRESS 0x00000000 -PORT COM5 -BAUDRATE AUTO -MINIDRIVER uart.hex -BTP CYBT_333032_EVAL_SFLASH.btp -CONFIG ezserial_343026-CYBT_343026_EVAL-rom-ram-Wiced-release.hex
* uart.hex and CYBT_333032_EVAL_SFLASH.btp : From Platform Files for CYBT-333032-EVAL - KBA226800
* ezserial_343026-CYBT_343026_EVAL-rom-ram-Wiced-release.hex: From https://www.cypress.com/documentation/software-and-drivers/ez-serial-ez-ble-module-firmware-platform
[Log]
Trying baudrate 115200 Conn: PORT=COM5 BAUDRATE=115200
Autodetected baudrate 115200
Baudrate change not needed -- already at 115200 baud
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
Transmitting "Chip erase" command 01 CE FF 04 00 00 00 FF
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)
Best regards,
Takahashi
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The recover mode is operated as follows:
1. Pull Recover(SPI2_MOSI) Pin to GND
2. Pull Reset Pin to GND
3. Release the Reset Pin
4. Release the Recover Pin
Then program the module with the module programmer tool with 115200 baudrate. Could you check the above steps and try again?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I saw three device in your description: CYBT-333047, CYBT-333032 and CYBT-343026. Which device are you using?
Could you try to program the device in recover mode with module programmer? WICED Module Programmer User Guide – KBA225060
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I'm programming the module with the module in recover mode.
When I programmed with recovery (SPI2_MOSI) on the evaluation board set to GND, the same log was output.
However, on the actual board, SPI2_MOSI is not set to GND.
Is there anything else you can think of?
Best regards,
Takahashi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The recover mode is operated as follows:
1. Pull Recover(SPI2_MOSI) Pin to GND
2. Pull Reset Pin to GND
3. Release the Reset Pin
4. Release the Recover Pin
Then program the module with the module programmer tool with 115200 baudrate. Could you check the above steps and try again?