Yes, I know that the FT232 and FT245 can only be opened once. They provide a handle once opened.
This is why I only open it once and save the handle in shared memory so that other programs use it for read and write functions, but it doesn't work. I also have the same problem with the VCP driver
- April 18, 2024, 12:21:26 AM
- Welcome, Guest
News:
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
71
General Category / Discussion - Software / Re: Access to 1 FT245B with 2 different programs simultaneously
on: November 22, 2023, 09:50:04 PM
|
||
Started by Oric - Last Post by Oric | ||
72
General Category / Discussion - Software / Re: Access to 1 FT245B with 2 different programs simultaneously
on: November 22, 2023, 04:07:26 PM
|
||
Started by Oric - Last Post by FTDI Community | ||
Hello,
When using the D2xx driver it can only be accessed by one handle at a time. Note that FT245B is Not Recommended for New Designs (NRND) and is being made EOL. See AN_559 Migrating from FT2xxB however the same limitation applies with the D2xx driver. There could be other FTDI Community members who have experience with sharing a handle in shared memory but it's not something that FTDI support. Best Regards, FTDI Community |
73
General Category / Discussion - Software / Access to 1 FT245B with 2 different programs simultaneously
on: November 21, 2023, 06:57:31 PM
|
||
Started by Oric - Last Post by Oric | ||
Hello FTDI Community
Originally I had a DLL written in Visual Studio 6 ( win98 ) to communicate with an ISA card. Several programs written in Visual Basic 6 can access this DLL and communicate simultaneously with the card. The DLL is written using mutex principles. I replaced the bus part of the card with an Ftdi FT245. I rewrote the DLL to use D2xx driver. I can make the programs work, but only one at a time. I use the FT_Open, FT_Write, FT_Read, FT_Close functions. I tried to share the handle in shared memory. The other programs recover it well and do not open the port if it is already open, and uses the handle retrieved from shared memory to control the FT_Write, FT_Read functions, but these write and read functions return an error. Thank you for your help |
74
on: November 21, 2023, 12:30:59 AM
|
||
Started by DRN - Last Post by DRN | ||
I need to use FT232H to control an I2C bus, on Windows 10, in a C++ application.
I'm using the AdaFruit FT232H Breakout (Product ID: 2264) on a Windows 10 PC. Using the latest FTDI DLL. I've got a Qwiic sensor board connected to the breakout board's Qwiic connector. The sensor board and cable work fine with a Microchip MCP2221 USB-I2C adapter so they're AOK. But I can't access the I2C sensor using the FT232H - library goes into an infinite loop. I understand I should use the FTDI MPSSE library. On your forum I found you have released LibMPSSE 1.0.3 to your website: https://ftdichip.com/software-examples/mpsse-projects/ I downloaded the following and incorporated it into my project: https://ftdichip.com/wp-content/uploads/2022/07/LibMPSSE_1.0.3.zip Unfortunately, inside I2C_InitChannel, FTDI's libMPSEE software goes into an infinite loop in FT_InitChannel. The call stack is attached. Any idea what is going on??? Is there an updated version of the library with bugfixes? Thanks in advance for any help, Best Regards, Dave PS: Here's the program output: Hello World! ftd2xx.dll loaded OK! Found at least one channel on FT232H Information on channel number 0: Flags=0x2 Type=0x8 ID=0x4036014 LocId=0x22 SerialNumber=FTP6SN3W Description=FT232H ftHandle=0x0 (0 unless channel is open) Version Check libmpsse: 00010001 libftd2xx: 00030216 handle=0xc586c8 status=0 >>> Goes into infinite loop inside I2C_InitChannel... PS: With an older version of the library, the channel initialized but I could not access the I2C device (it always reported FT_DEVICE_NOT_FOUND). |
75
on: November 16, 2023, 06:05:07 PM
|
||
Started by jhgorse - Last Post by jhgorse | ||
Hi,
My name is Joe. I have been doing embedded projects since 2001. I have used FTDI for my USB bridges to UART and SPI. Cheers, Joe |
76
on: September 20, 2023, 08:25:21 PM
|
||
Started by xenon68 - Last Post by xenon68 | ||
Tools: Vinculum ii IDE
Chip: 32pin VNC2 Application size has plenty of flash left, only at 227000 bytes. For some reason when I write a single page of flash, the SPI device stops working... any ideas? Basically this is all I am doing, then after that the SPI stops working. Tried other page locations. What is odd, is the flash write works. I can restart, and read the correct data from the flash. flash_writePage(0x7ff, temp_string); |
77
General Category / Discussion - Software / Re: Multi-byte read fails in I2C_DeviceRead, LibMPSSE_1.0.3 - no NACK by FT2232H
on: August 22, 2023, 10:34:48 AM
|
||
Started by bryantsorensen - Last Post by FTDI Community | ||
HI Petrov,
We are not sure when the next update for the library will be released, however, as the source code is available on the website, customers can make their own changes and rebuild the library for their own use. Customers can also develop their own code using D2XX direct driver. You can have a look at Command Processor For MPSSE and MCU Host Bus Emulation Modes this will allow you to not rely on LibMPSSE. Best Regards FTDI Community |
78
General Category / Discussion - Software / Re: Multi-byte read fails in I2C_DeviceRead, LibMPSSE_1.0.3 - no NACK by FT2232H
on: August 21, 2023, 09:07:43 PM
|
||
Started by bryantsorensen - Last Post by Petrov | ||
Is there any update on this issue?
When can we expect the next release of the library? |
79
on: August 21, 2023, 03:33:12 PM
|
||
Started by FTDI Community - Last Post by FTDI Community | ||
Complete our customer survey for your chance to win a Holy Stone HS175D drone worth £190!
Your opinion is extremely important to us, and we rely on customer feedback in order to continuously make improvements and ensure that we are addressing any issues. The responses we receive from our Annual Customer Survey are pivotal as part of this process. Plus, every entrant into the survey is entered into our prize draw, and one lucky winner will be awarded with a Holy Stone HS175D drone worth £190!* Please follow this link to the Survey: FTDI Survey *Holystone and their respective logos are trademarks or registered trademarks of Holy Stone. Holy Stone is not a participant in or sponsor of this promotion. The promotion runs until 30th of September 2023. Best Regards, FTDI Community |
80
on: August 15, 2023, 04:20:12 PM
|
||
Started by kiran - Last Post by FTDI Community | ||
Hello,
When using LibMPSSE, GPIOL[0:3] can only be used as SPI chip selects. When using LibMPSSE, there is no way to control GPIOL[0:3] as GPIO. LibMPSSE demonstrates controlling the higher line bytes (GPIOH) while using SPI on the lower line bytes using the following functions: FT_WriteGPIO FT_ReadGPIO If you want to control some of the unused lower line bytes on the same ADBUS as SPI then see AN_411 FTx232H MPSSE I2C Master Example in C which demonstrates GPIO usage with MPSSE using D2xx direct (not using LibMPSSE). This could be used as a base to understand using both I2C/GPIO in the same code. Best Regards, FTDI Community |