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 - ganswer

Pages: [1]
Hello, yes I tried also the FTD3XX_NET you provided and the problem is confirmed. I'll write then, thanks

I'm using the FTD3XX_NET wrapper relying on the D3XX driver.
The D3xx driver v. seems buggy in the 64-bit version. In this version, when the wrapper is used for enumerating the connected devices:

FTDI ftdi = new FTDI();
uint nDevices;
ftdi.CreateDeviceInfoList(out nDevices);
List<FTDI.FT_DEVICE_INFO> deviceInfoList;
deviceFtdi.GetDeviceInfoList(out deviceInfoList);

AND in case there are two devices connected, the second device in the list has Description empty and serial 0 (ftdi.GetDescriptio(deviceInfo) and ftdi.GetSerialNumber(deviceInfo)). While in the 32-bit version, the right Description and serial is returned also for the second device.

Looking deeper, when in 64-bit, the deviceInfo of the second device seems to have the data in the byte[] array field for Description (and similarly the one for Serial) shifted:
[0, 0, 0, 0, 70, 84, 68, 73, 32, 83.....]
while the first device has not those 4 initial bytes at 0.

Pages: [1]