FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - urbanvibes

Pages: [1]
Hi again

Yes you requested contact by email, but I relayed information here, as it might be relevant to others. Not much point in having a community, if issues that are discussed here are moved to mail conversations that are not public.

As my previous post states, I'm not opening the wrong interface. In the original post and in my first mail, I attached an example program that works when compiled and running with 32bit dll's but fails when compiled and running with 64bit dll's.

As I understand it you will now test my example code, I look forward to the result:-)

Sincerely Torbjørn

Hi "FTDI Community"

The device is in CNFMOD2 (Quad SPI master) and as the attached example shows the exact same code works when the application is 32bit and uses 32bit dll's.

You seem to have not read my previous post properly, the quote from FTDI support confirms there's an issue with the 64bit dll's and an internal bug has been raised. This should be of major concern for FTDI, as this problem will spread (for 64bit applications) when customers computers are updated.

It would not work to uninstall security patches in my case anyway, as I'm using Matlab for the "real" application, the attached test program was made to rule out Matlab in the equation, so I would not be able to use a previous version of Visual Studio - since I'm not using Visual Studio.

I hope there will be a solution from FTDI soon, as the workaround is quite tedious. If you are too busy, I'll gladly take a look at the source code, but I guess that's something you keep to yourselves :-)

Sincerely Torbjørn

For anyone else affected by this here is an update on this issue after communicating with FTDI-UK:
Hi Torbjørn,
We think it most likely came from a Windows 10 security Update from August and seems to have an affect around memory allocation

The LibFT4222.dll is working using this configuration:
Using Visual Studio 2022 V17.2 after uninstalling 2x Windows 10 security patches from August: KB5015730 and KB5012170
Using Visual Studio 2022 V17.3 is still not working even after uninstalling the 2 security patches. The Visual Studio 17.3 Update includes security fixes.

We have an internal bug raised for this but I don’t have any specific time frame for a fix at this time 

[name removed by me(Torbjørn)] (FTDI-UK)

Furthermore I ran the test program on a Windows 11 machine with the exact same result.

Sincerely Torbjørn

I have sent a mail to EMEA region support, with this additional info:

Ftd2xx version is file: Product:
LibFT4222 version is: and same product version (but they come from LibFT4222-v1.4.5.zip)
The chip seems to be FT4222HQ 1911-D

Sincerely Torbjørn

I have a setup where 64 bit versions of ftd2xx and LibFT4222 dll's are called through Matlab, this originally worked fine on one PC, but failed on another one.
We had a debug session where we concluded that the first call to a LibFT4222.dll function returns FT4222_DEVICE_NOT_SUPPORTED. We compared installed dll's, made sure we had the same versions, but the same code still only worked on one machine. The morning after I restarted my PC after a Windows update, and now the error was on both machines.

I have attached a C++ test program created in Visual Studio, this works fine when compiling/running in 32 bit, but fails when compiling/running 64 bit.
(The dll paths are relative to my test setup, they might need modification before running)

Any ideas?
Torbjørn Biering Tvermosegaard

Pages: [1]