STSW-WPSTUDIO GUI cannot connect to ST Wireless Charging board

Joshua1 · ‎2024-04-10

Hello,

I purchased a set of Wireless charging evaluation boards (RX & TX) on Mouser.com for $160.

The 2 board names are STEVAL-WBC86TX and STEVAL-WLC38RX.

I use STSW-WPSTUDIO V1.8.4 software to try to connect to the board from my PC and get access to the register setting. But every time I click on the Connect button, there is the same error message appearing:

"Unable to find any [RX]WLC38 device. Please check your connection again."

The issue is the same with both boards.

But it seems the boards are working, because when I place STWLC38 on top of STWBC86, the boards are charging, because I can see the red LED on the receiver board, and Vout is 5V.

So the main issue is the GUI.

I cannot use the ST GUI to connect to any of the ST boards that I paid $200 for ! (with shipping + fee cost)

My computer is Windows 11. And the board is properly connected through a USB-A to USB-C cable.

I followed the steps from the user manual. The 2nd USB-C connector of STWBC86 is connected to 100W USB-C adapter. So the boards are powered on, because I can see the LED turned on. I tried with other USB cables, and it is still the same issue.

And I didn't install any USB driver on Windows because I didn't see mentioned anywhere the requirement to install a driver to use this board.

Do I need to install a USB driver ?

GUI Error message with STWBC86 evaluation board:

"Unable to find any [TX]WBC86 device. Please check your connection again."

STWBC86 GUI connection issue

GUI Error message with STWLC38 evaluation board:

"Unable to find any [RX]WLC38 device. Please check your connection again."

STWLC38 GUI connection issue

I don’t understand why there is such critical issue with new boards right out of the box ??

I have used STM32CubeProgrammer in the past to connect to a low cost $10 STM32 Nucleo board, and I never faced any USB connectivity issue. It was simple as plug and play.

What needs to be done for WPSTUDIO to detect that the computer is attached to the $160 Wireless boards ?

GRB · ‎2024-04-20

What does "recommed you to buy ft260 dongle" mean? How will that make the STM Qi Rx/Tx boards that were working now work again? Volume is >10K. I need support if I am going to use STM because right now nothing is working. I attached a log of trying to connect using Empty and Rx

willzhou · ‎2024-04-20

ft260 dongle link is https://www.st.com/en/evaluation-tools/steval-usbi2cft.html

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.

Joshua1 · ‎2024-04-21

Hello,
I tested the GUI on another Windows 11 laptop, and I still have the same issue with version 2.1.0. It cannot connect to the board and show the error message.

Did ST try the STSW-WPSTUDIO software on a Windows 11 PC ? Or does the GUI only work on Windows 10 ?

Connection ERROR again

I confirm there is NO LOG menu on this version of the GUI. The last menu line that I can see is "Header Generator".

No Log menu visible

I saw in the SETTINGS menu, there is a "Debug Mode" that we can enable.
But even enabled, I still don't see any LOG menu appearing on the main interface.

How did you enable the LOG menu ?

Debug mode enabled doesn't change anything

I tried to click the save button: "save current log to text file". But the log file recorded is meaningless because it is just binary data !!
How can I find out by myself what is the software issue if everything is kept in binary format by ST ??

log file is unreadable

Please help to fix this non working WPSTUDIO software.

Joshua1 · ‎2024-04-21

Which ft260 driver do we need to install ?

Can ST provide the right software driver to use, instead of asking customer to Google any random driver out of the internet ? We paid for these evaluation tools at the end, so we expect ST to provide a working software with it.

Thanks

sjones · ‎2024-04-22

The FTDI Application note at
https://www.ftdichip.com/Support/Documents/AppNotes/AN_394_User_Guide_for_FT260.pdf

Says that (1.1) a custom driver is not needed as HID is natively supported by most operating system, and that there are 2 interfaces (I2C and UART), 1.2.2 lists the 4 endpoints .

The UM3161 doc (Getting started with the STEVAL-WBC86TX) at
https://www.st.com/resource/en/user_manual/um3161-getting-started-with-the-stevalwbc86tx-wireless-power-transmitter-evaluation-board-for-up-to-5-w-qibpp-applications-stmicroelectronics.pdf
Lists the required setup components (page 2) as
power supply
USB cables
The Studio program
I2C drivers
No mention of a dongle being required. Isn't the FT260 on the dev board doing the I2C to HID interface already?

However the UM3164 doc (STSW-WPSTUDIO user guide) at
https://www.st.com/resource/en/user_manual/um3164-stswwpstudio-user-guide-stmicroelectronics.pdf
shows a USB dongle being used and connected to I2C pins on the board. Does this relate to products that do not have an FT260 chip on the board?

Are the drivers actually required and if so is there a link to ones that should be used?

The FTDI website just lists LibFT260 and no driver package.

When I connect the board to the Windows box I see 4 new HID devices appear (USB Input device).
They are using standard Windows HID drivers.

This is the error log (debug flag on), trying to connect to TX.

{"Type":1,"Date":"2024-04-22","Time":"10:11:13.620 AM","ThreadId":"1","Message":"STSW-WPSTUDIO V2.2.5","TypeToView":"INFO"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.728 AM","ThreadId":"9","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.730 AM","ThreadId":"9","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"ReadChunk: 240 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ReadChunk: 4091 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ReadChunk: 55 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"WriteChunk: 55 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ReadChunk: 50 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"},
{"Type":3,"Date":"2024-04-22","Time":"10:11:35.736 AM","ThreadId":"6","Message":"Error during enumeration for HidDongleMaster: Unable to load DLL 'HidDongle.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)","TypeToView":"ERROR"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.736 AM","ThreadId":"6","Message":"HidDongle enumerate in 2ms","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.738 AM","ThreadId":"6","Message":"DingDongle enumerate in 1ms","TypeToView":"INFO"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.741 AM","ThreadId":"6","Message":"McpDongle enumerate in 2ms","TypeToView":"INFO"},
{"Type":2,"Date":"2024-04-22","Time":"10:11:35.742 AM","ThreadId":"6","Message":"FT260 Dongle Library Load error ","TypeToView":"WARNING"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.742 AM","ThreadId":"6","Message":"FT260 enumerate in 1ms","TypeToView":"INFO"}

sjones · ‎2024-04-22

There seems to be some confusion here:

The STEVAL-WBC86TX board has an FT260 chip on board. This does the I2C to USB interface, and so (I think) replaces the need for the FT260 dongle mentioned above. The user guide for the board (UM3161) certainly doesn't mention a dongle in the hardware setup.

UM3161 does mention the need for I2C drivers (no link to download them), but this contradicts the FT260 user guide (https://www.ftdichip.com/old2020/Support/Documents/AppNotes/AN_394_User_Guide_for_FT260.pdf) which states:

The FT260 is a full speed USB device which supports I²C and UART communication through
standard USB HID interfaces. The USB HID class is natively supported by most operating systems.
A custom driver is not required to be installed for the FT260.

Here is a (base64) decoded log from V2.2.5 (with debug turned on) of what happens when I attempt to connect:

{"Type":1,"Date":"2024-04-22","Time":"10:11:13.620 AM","ThreadId":"1","Message":"STSW-WPSTUDIO V2.2.5","TypeToView":"INFO"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.728 AM","ThreadId":"9","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.730 AM","ThreadId":"9","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.731 AM","ThreadId":"8","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"ReadChunk: 240 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.732 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ReadChunk: 4091 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ReadChunk: 55 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"WriteChunk: 55 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ConnectionType: ADDRESS_SIZE_2_BYTES bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"ReadChunk: 50 bytes","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.733 AM","ThreadId":"6","Message":"WriteChunk: 50 bytes","TypeToView":"INFO"},
{"Type":3,"Date":"2024-04-22","Time":"10:11:35.736 AM","ThreadId":"6","Message":"Error during enumeration for HidDongleMaster: Unable to load DLL 'HidDongle.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)","TypeToView":"ERROR"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.736 AM","ThreadId":"6","Message":"HidDongle enumerate in 2ms","TypeToView":"INFO"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.738 AM","ThreadId":"6","Message":"DingDongle enumerate in 1ms","TypeToView":"INFO"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.739 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] About to call SetupDiGetClassDevs for class Guid 4d1e55b2-f16f-11cf-88cb-001111000030. Flags: 18","TypeToView":"DEBUG"},
{"Type":0,"Date":"2024-04-22","Time":"10:11:35.740 AM","ThreadId":"5","Message":"[WindowsHidDeviceFactory - GetConnectedDeviceDefinitionsAsync] The call to SetupDiEnumDeviceInterfaces returned ERROR_NO_MORE_ITEMS","TypeToView":"DEBUG"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.741 AM","ThreadId":"6","Message":"McpDongle enumerate in 2ms","TypeToView":"INFO"},
{"Type":2,"Date":"2024-04-22","Time":"10:11:35.742 AM","ThreadId":"6","Message":"FT260 Dongle Library Load error ","TypeToView":"WARNING"},
{"Type":1,"Date":"2024-04-22","Time":"10:11:35.742 AM","ThreadId":"6","Message":"FT260 enumerate in 1ms","TypeToView":"INFO"}]

willzhou · ‎2024-04-23

Please install “Microsoft Visual C++ 2015 Redistributable” package.

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.

willzhou · ‎2024-04-23

@Joshua1 @sjones @GRB

We have confirmed this version GUI is dependent on “Microsoft Visual C++ 2010 X86 Redistributable Package” .

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.

GRB · ‎2024-04-23

A 14 year old Service Patch, why didn't I think of that?

willzhou · ‎2024-04-23

Hi

This is due to FT260 dongle dll file need this Microsoft Visual C++ 2010 driver.

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.