FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

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

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

Pages: [1]
1
If you are talking about the AppleUSBFTDI driver, yes we've done that. Not doing that would give us a different error which was not as complicated as what we're facing now. We used either the D2XX helper or "kextunload" to do that and we also used "kextstat | grep FTDI" to double-check.

2
We have done that. In fact, on some of the computers we didn't install the VCP driver at all.

3
Discussion - Software / Ft_SetFlowControl Failed. FT245RL chip can't read.
« on: September 20, 2021, 08:08:44 PM »
Hi,

We are currently having some issues with the FT245RL chip which communicates with an FPGA. We have our own software to use that chip to send data to our computer, but our computer can't get any data. We saw Ft_SetFlowControl failed. Our computer is currently running macOS High Sierra 10.13.5, and the same computer with the same software worked well in the past when it was running Sierra 10.12.3. We've tried two versions of D2XX drivers (we're using direct drivers), 1.4.4 (old) and 1.4.24 (latest), getting the same problem.

We also tested the "simple" code under /Samples/Simple in the driver package (which just writes some data to the chip and then reads the data back), and even that code ran into errors. The number of bytes in D2XX receive-queue was always a zero or a bunch of zeros and the readings were just junk. We tried this piece of simple code on several different computers running macOS Sierra 10.12.6, High Sierra 10.13.5, and Catalina 10.15.7. All of them showed similar results. We also tried another board that has the same design and we still got the same result.

Does anyone have any idea on how to fix this? Thanks in advance!

Pages: [1]