STEVAL-WBC86TX -> Bricked accidentally, any chance of recovery?

[AnkhInnovationsLLC]

Hello,

So I recently received the dev board STEVAL-WBC86TX and was quite impressed with the features. Accidentally the wrong config ID was written to the board. Now I cannot connect to it again using the Windows utility.

The USB to I2C appears to be working normally, but there is an error in the log and the device never connects successfully in the GUI, thus, I cannot flash the original config and nvm patch files from the website, provided as STSW-WBC86FWBPP.

[TX]WBC86 connection ex: Wrong config id 0xDA06 and patch id 0x0000 for TX"

I thought I could edit WBC86.json.enc, which probably contains which ID and such... I'm guessing this is encrypted json.

Is there a way to hard reset this chip to restore connectivity to the dev board?

[AnkhInnovationsLLC]

2024-06-12 10:29:17.416 AM [Info] 1 - ConnectionType: ADDRESS_SIZE_2_BYTES bytes
2024-06-12 10:29:17.416 AM [Info] 1 - ReadChunk: 50 bytes
2024-06-12 10:29:17.416 AM [Info] 1 - WriteChunk: 50 bytes
2024-06-12 10:29:17.496 AM [Info] 1 - FT260 Dongle[0] id: \\?\hid#vid_0403&pid_6030&mi_00#8&3ea09e0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-06-12 10:29:17.512 AM [Info] 1 - FT260 Dongle[1] id: \\?\hid#vid_0403&pid_6030&mi_01#8&1bad9625&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2024-06-12 10:29:17.622 AM [Info] 1 - ConnectionType: ADDRESS_SIZE_2_BYTES bytes
2024-06-12 10:29:17.622 AM [Info] 1 - ReadChunk: 50 bytes
2024-06-12 10:29:17.622 AM [Info] 1 - WriteChunk: 50 bytes
2024-06-12 10:29:17.734 AM [Info] 1 - FT260DongleConfig: FW Version: 0x1010500
2024-06-12 10:29:17.734 AM [Info] 1 - FT260DongleConfig: Chip ID: 0x2600200
2024-06-12 10:29:17.734 AM [Info] 1 - FT260DongleConfig: SAD: 0x61
2024-06-12 10:29:17.734 AM [Info] 1 - FT260DongleConfig: ClockRate changed to Standard
2024-06-12 10:29:17.751 AM [Debug] 1 - W[2]: 00 00 , R[2]: FF FF
2024-06-12 10:29:17.783 AM [Info] 1 - ConnectionType: ADDRESS_SIZE_2_BYTES bytes
2024-06-12 10:29:17.783 AM [Info] 1 - ReadChunk: 50 bytes
2024-06-12 10:29:17.783 AM [Info] 1 - WriteChunk: 50 bytes
2024-06-12 10:29:17.783 AM [Error] 1 - FT260Dongle: I2c master Init/slave Adress
2024-06-12 10:29:17.828 AM [Info] 1 - FT260DongleConfig: FW Version: 0x1010500
2024-06-12 10:29:17.828 AM [Info] 1 - FT260DongleConfig: Chip ID: 0x2600200
2024-06-12 10:29:17.828 AM [Info] 1 - FT260DongleConfig: SAD: 0x61
2024-06-12 10:29:17.828 AM [Info] 1 - FT260DongleConfig: ClockRate changed to Standard
2024-06-12 10:29:17.828 AM [Error] 1 - FT260Dongle: rawWriteRead Failed
2024-06-12 10:29:17.828 AM [Error] 1 - FT260Dongle: rawWriteRead Failed
2024-06-12 10:29:17.828 AM [Error] 1 - FT260Dongle: rawWriteRead Failed
2024-06-12 10:29:17.828 AM [Warning] 1 - W[2] ex: FT260Dongle [rawWriteRead] : Failed

[willzhou]

It read 0xFF 0XFF from i2c reg address 0x0000, and it can not detect chip id anymore.

Let me ask internally to solved this issues.

[AnkhInnovationsLLC]

Okay thanks let me know

[willzhou · Accepted solution]

@AnkhInnovationsLLC 

please use this link tool

Wireless Charging solution Wiki - STMicroelectronics Community

[AnkhInnovationsLLC]

Hi @willzhou you rock!!!

It worked perfectly.

Is a similar tool available for the wbc 86?

[willzhou]

Glad it is working, it is suitable for all wireless charge devices, include wbc86, it will auto read chip id and erase all patch and cfg.

@AnkhInnovationsLLC