cancel
Showing results for 
Search instead for 
Did you mean: 

Problems connecting to STEVAL-WPC86TX with STSW-WPSTUDIO

sjones
Associate II

Following on from 

Solved: Cannot connect STWBC86 to WPSTUDIO V1.8.4 - STMicroelectronics Community

I am still getting the "Unable to find an [TX]WBC86 device"' message when' I try to connect.

Originally the log file just showed the 'Failure to load DLL' message

I  installed all the Visual C++ redistributable versions (2005/2008/2010/2012/2013/2015, x86 and x64) as suggested

The log file now shows read/write errors when trying to contact the board
I made a capture of the I2C bus on the board which is below, followed by the WPSTUDIO (v 2.2.5)  log file

sjones_0-1714474956850.png

 

[{"Type":1,"Date":"2024-04-30","Time":"11:54:57.263 AM","ThreadId":"1","Message":"STSW-WPSTUDIO V2.2.5","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.200 AM","ThreadId":"16","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"ReadChunk: 240 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"ReadChunk: 4091 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"ReadChunk: 55 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.201 AM","ThreadId":"16","Message":"WriteChunk: 55 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.202 AM","ThreadId":"16","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.202 AM","ThreadId":"16","Message":"ReadChunk: 50 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.202 AM","ThreadId":"16","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.446 AM","ThreadId":"16","Message":"Could not find any HID dongle: E_STMICRO_DONGLE_NOT_FOUND","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.446 AM","ThreadId":"16","Message":"HidDongle enumerate in 245ms","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.450 AM","ThreadId":"16","Message":"DingDongle enumerate in 2ms","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.455 AM","ThreadId":"16","Message":"McpDongle enumerate in 5ms","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.640 AM","ThreadId":"16","Message":"FT260 Dongle[14] id: \\\\?\\hid#vid_0403&pid_6030&mi_00#7&14549fe0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.651 AM","ThreadId":"16","Message":"FT260 Dongle[15] id: \\\\?\\hid#vid_0403&pid_6030&mi_01#7&f829de2&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.778 AM","ThreadId":"16","Message":"FT260 enumerate in 323ms","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.782 AM","ThreadId":"16","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.782 AM","ThreadId":"16","Message":"ReadChunk: 50 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.783 AM","ThreadId":"16","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.799 AM","ThreadId":"16","Message":"FT260DongleConfig: FW Version: 0x1010300","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.800 AM","ThreadId":"16","Message":"FT260DongleConfig: Chip ID: 0x2600200","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.800 AM","ThreadId":"16","Message":"FT260DongleConfig: SAD: 0x61","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:06.800 AM","ThreadId":"16","Message":"FT260DongleConfig: ClockRate changed to Standard","TypeToView":"INFO"}
{"Type":2,"Date":"2024-04-30","Time":"11:55:07.892 AM","ThreadId":"16","Message":"FT260Dongle: Get Status timeout failed","TypeToView":"WARNING"}
{"Type":3,"Date":"2024-04-30","Time":"11:55:07.892 AM","ThreadId":"16","Message":"FT260Dongle: rawWriteRead Failed","TypeToView":"ERROR"}
{"Type":2,"Date":"2024-04-30","Time":"11:55:08.980 AM","ThreadId":"16","Message":"FT260Dongle: Get Status timeout failed","TypeToView":"WARNING"}
{"Type":3,"Date":"2024-04-30","Time":"11:55:08.980 AM","ThreadId":"16","Message":"FT260Dongle: rawWriteRead Failed","TypeToView":"ERROR"}
{"Type":2,"Date":"2024-04-30","Time":"11:55:10.075 AM","ThreadId":"16","Message":"FT260Dongle: Get Status timeout failed","TypeToView":"WARNING"}
{"Type":3,"Date":"2024-04-30","Time":"11:55:10.075 AM","ThreadId":"16","Message":"FT260Dongle: rawWriteRead Failed","TypeToView":"ERROR"}
{"Type":2,"Date":"2024-04-30","Time":"11:55:10.075 AM","ThreadId":"16","Message":"W[2] ex: FT260Dongle [rawWriteRead] : Failed","TypeToView":"WARNING"}
{"Type":2,"Date":"2024-04-30","Time":"11:55:10.088 AM","ThreadId":"16","Message":"[TX]WBC86 connection ex: FT260Dongle [rawWriteRead] : Failed","TypeToView":"WARNING"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:10.092 AM","ThreadId":"16","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:10.093 AM","ThreadId":"16","Message":"ReadChunk: 50 bytes","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:10.094 AM","ThreadId":"16","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"}
{"Type":3,"Date":"2024-04-30","Time":"11:55:10.095 AM","ThreadId":"16","Message":"FT260Dongle: I2c master Init/slave Adress","TypeToView":"ERROR"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:10.101 AM","ThreadId":"16","Message":"FT260DongleConfig: FW Version: 0x1010300","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:10.102 AM","ThreadId":"16","Message":"FT260DongleConfig: Chip ID: 0x2600200","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:10.102 AM","ThreadId":"16","Message":"FT260DongleConfig: SAD: 0x61","TypeToView":"INFO"}
{"Type":1,"Date":"2024-04-30","Time":"11:55:10.102 AM","ThreadId":"16","Message":"FT260DongleConfig: ClockRate changed to Standard","TypeToView":"INFO"}
{"Type":3,"Date":"2024-04-30","Time":"11:55:10.103 AM","ThreadId":"16","Message":"FT260Dongle: rawWriteRead Failed","TypeToView":"ERROR"}
{"Type":3,"Date":"2024-04-30","Time":"11:55:10.103 AM","ThreadId":"16","Message":"FT260Dongle: rawWriteRead Failed","TypeToView":"ERROR"}
{"Type":3,"Date":"2024-04-30","Time":"11:55:10.103 AM","ThreadId":"16","Message":"FT260Dongle: rawWriteRead Failed","TypeToView":"ERROR"}
{"Type":2,"Date":"2024-04-30","Time":"11:55:10.103 AM","ThreadId":"16","Message":"W[2] ex: FT260Dongle [rawWriteRead] : Failed","TypeToView":"WARNING"}
{"Type":2,"Date":"2024-04-30","Time":"11:55:10.115 AM","ThreadId":"16","Message":"[TX]WBC86 connection ex: FT260Dongle [rawWriteRead] : Failed","TypeToView":"WARNING"}]

 

 

 

4 REPLIES 4
sjones
Associate II

Just a couple more things...

I have jumpers on the SDA, SCL and INT headers of P2

The board has LEDs D6 (power) and D5 (I2C initialised) illuminated.
On power up, or pressing the S1 reset switch I get the following on the I2C bus:

sjones_0-1714478604806.png

 

Hi
The log show I2C read is NAK and data is invalid 0xFF.
Seems ft260 dongle have some issues.
I suggest you change ft260 dongle
https://www.st.com/en/evaluation-tools/steval-usbi2cft.html

 

or other i2c devices, like STM32 MCU refer to this like
https://github.com/STwirelesscharger/STWBC86_NUCLEO_L476RG

 

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hi,

  I did some more testing. 

  I isolated the STM TX chip from the FT260 chip by removing the jumpers on P2.
  I connected a bus pirate board to the I2C SDA/SCLK/GND (and set the 5V pull up on the bus pirate)
  I then used the bus pirate to generate  I2C traffic to the TX chip.

  The TX chip still ACKed the write requests, but NACKed read requests, exactly the same as seen in the recording below where the FT260 chip was generating the I2C traffic.
  When bus pirate scanned the address space for devices it found 0xc2 (0x61 write) but not the expected 0xc3 (0x61 read).
  This indicates that the problem is with the TX chip, not the FT260 chip, and buying an FT260 dongle will not fix the problem.

  It looks like the board is broken. 

willzhou
ST Employee

Hi

also please use attach debug tool to check ft260 connect logs, it is build by python, runing need some time, correct log is like below:

willzhou_0-1715223357155.png

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.