Hello,

Thanks for the information.

We can confirm there is a bug with FT_Prog 3.8.128.448 when using FT2232H and we have created a beta to fix this.

Please find the beta version at the following link:

https://www.ftdicommunity.com/index.php?topic=537.0

Best Regards,

FTDI Community

Hello,

You are already in contact with our support team via email.

Feel free to post any resolution here to help other community users.

Best Regards,
FTDI Community

Hello,

Can I get you to try the following files in your project to see if they help?
BOMS files

Some instructions:
Replace the “.a” files in
C:\ProgramData\FTDI\Vinculum II Toolchain\Firmware\Drivers\lib
and the “.h” files in
C:\ProgramData\FTDI\Vinculum II Toolchain\Firmware\Drivers\include


Unfortunately if these do not help it may indicate the enumeration issue could be related to the USB drives hardware.
Flash drives are a commodity product and are designed as such, often you find these are not designed to the applicable specs.
It may be worth using flash drives you can guarantee from the manufacture which are designed to a standard with proper bill of materials control. And which would guarantee that their devices were identical and would work the same throughout the lifetime of the product.

Best Regards,
FTDI Community

Hello,

The symptoms that you are describing is pointing to an issue with the hardware or cable.
Please check your design with the information provided in our previous post.

Also check that you are using a certified SuperSpeed USB cable.

You can also contact your local support team in China to check your hardware design:

https://www.ftdichip.com/FTContact.htm

Best Regards,
FTDI Community

Hello,

I cannot provide the source for the D2XX DLL itself, but the source for the .net wrapper is available at the following:
https://www.ftdichip.com/Support/SoftwareExamples/CodeExamples/CSharp/FTD2XX_NET.zip

Best Regards,
FTDI Community

Hello,

Yes, you can set the COLOR_A before widgets such as keys and it will set the alpha value to give them transparency.

Large buttons use quite a lot of Display List resources and so if your aim of the large button in the background behind the keys is just to detect if pressed between the keys, a tagged rectangle under the keys would do the same job. You can even make it invisible by setting the alpha to 0 if it is only for touch sensing purposes.

Alternatively, you can set the CLEAR_TAG before calling the CLEAR(1,1,1) at the start of the command list and this will set the tag which you get if you touch any area of the screen which is not containing a tagged object.

You can also make custom keys instead of the keys widget by using small equally sized bitmaps as bitmap cells (thereby allowing you to load many buttons on the same bitmap handle) and so could have icons or images on them.

Best Regards, FTDI Community

Hello,

If you can take a capture using our USBView utility highlighting the device (similar to the attached capture) then we can see if the device in-fact needs the default FTDI drivers.

I am also curious about how you are connecting this to the host PC, did the OEM supply a cable? (as the connection on the box is RJ45).

Best Regards,
FTDI Community