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 - FTDI Community

Pages: [1] 2 3 ... 59
1
Discussion - Hardware / Re: Fastest I2C transfer rate on FT2232HQ?
« on: February 14, 2024, 04:42:46 PM »
Hi,

yes, FT2232H is a high-speed device. The driver can only operate with 1ms latency minimum.

Best regards
FTDI Community

2
Discussion - Hardware / Re: Fastest I2C transfer rate on FT2232HQ?
« on: February 13, 2024, 02:02:36 PM »
Hi,

You can try setting the latency timer to 1ms. This will make the device ran as fast as it can.

Best Regards
FTDI Community

3
Discussion - Hardware / Re: FT600q communication problem
« on: January 19, 2024, 04:19:30 PM »
Hello,

There are 2 kinds of delays / pauses.

1. Occurs when FIFO switches from ping to pong buffer. There are 2 FIFO Buffers and when current one gets filled, hardware moves to second FIFO. There will be a brief delay during this period.
2. Occurs when a session is ended and a new session is created. This delay can be slightly larger than the above one.
A session will be ended when the length of transferred data equals with the stream length set by FT_SetStreamPipe API (if not in stream mode, then the length passed in Read Pipe API), or when an unaligned write happens.
 
Between the end of session and start of new session, there could be some delay as observed.

If the stream length is shorter, this delay will be seen often.
The recommended stream length is, several multiples of the FIFO size.
For example, if the FT600 configuration uses 4K FIFO size, it's best to make the stream length as multiples of 4K - Say 10 times or 100 times of 4K.
This way, instead of seeing a long delay every 4K, the long delay will happen only at 400K transfer boundaries.

The FPGA is expected to buffer at least a FIFO size worth of data so that the delay does not cause any issues such as overflow.

If you have any additional questions please contact us via email as we have already been in contact with you.

Best Regards,
FTDI Community

4
Discussion - Software / Re: LibMPSSE I2C Library ACK Issue
« on: January 09, 2024, 01:36:13 PM »
Hi,

This is a known issue, and there is a fix. if you send an email to support1@ftdichip.com, we can send you a fixed version.

Best Regards
FTDI Community

5
Hi,
If you use FT_SetBitMode to reset (zero for reset)   
https://ftdichip.com/wp-content/uploads/2023/09/D2XX_Programmers_Guide.pdf (Page 66, D2xx programmers guide)

Regards
FTDI Community

6
General Discussion / Re: Change Manufacturer/Description/String string
« on: January 03, 2024, 04:36:55 PM »
Hello,

There are no issues with changing the Manufacturer/Description/Serial string without change VID/PID.

Best Regards,
FTDI Community

7
Discussion - Hardware / Re: FT600q config problem
« on: December 22, 2023, 03:55:46 PM »
Hello,

Please provide the USBView details and screenshot for analysis.

Please send this via email to your local support team:

https://ftdichip.com/technical-support/

Best Regards,
FTDI Community

8
Hello,

We are aware of the feedback and will continue to support you via email.

Best Regards,
FTDI Community

9
Hi,
We don't have any experience with "Linux Docker" although i note that they have a community page also.
https://www.docker.com/community/

Our D2xx driver as well as the libFT4222 files are available from our website   
https://ftdichip.com/drivers/
https://ftdichip.com/wp-content/uploads/2022/06/libft4222-linux-1.4.4.170.tgz

Regards
FTDI Community

10
Discussion - Hardware / Re: FT600q config problem
« on: December 21, 2023, 04:12:15 PM »
Hello,

I wonder if you also changed the VID and PID?

Please check the device details with USBView Utility:

https://ftdichip.com/utilities/#microsoft-usbview

Does the device appear in Device Manager if you are using Windows?

If the VID/PID is changed then it might explain if the device can't been seen.

If that's the case then you can try editing the D3xx Driver files to include changed VID/PID numbers.
Note that this breaks driver signing so you may need to install via disabling driver signature enforcement or using test mode. Both are detailed in this external link:
https://maxedtech.com/about-testmode/

Then hopefully you can use the configuration tool to change back to defaults:

https://ftdichip.com/utilities/#ft60x-configuration

Best Regards,
FTDI Community

11
Test and Review Area / Re: LibMPSSE Beta
« on: December 15, 2023, 11:17:05 AM »
Hello All,

We have a beta version of libMPSSE 1.0.4 which fixes all known issues.

Please contact support1@ftdichip.com for this version before we release it to our website.

Let us know if you have any feedback please.

Best Regards,
FTDI Community

12
Hello,

We have a new libmpsse version that you can try (V1.0.4).

Please contact your local support team for this:

https://ftdichip.com/technical-support/

The alternative is not to use LibMPSSE library and use D2xx driver direct which will give you more control:

To use I2C/SPI as a master (no slave functionality), see AN_135 MPSSE Basics and our existing MPSSE Example projects:
 
https://ftdichip.com/software-examples/mpsse-projects/
 
There are two options to use I2C/SPI modes with the MPSSE engine:
 
a.   Use LibMPSSE libraries. Example code is provided with the download. Source code is also provided.
b.   Use D2XX drivers direct. Example code is shown at I2C / SPI. AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information.
 
Option b is the best option to use the D2XX drivers direct (no dependency on libMPSSE library).

Best Regards,
FTDI Community

13
Discussion - Software / Re: About LibMPSSE_1.0.3 Linux
« on: December 13, 2023, 01:19:12 PM »
Hi Terry,

we see no issue with this.

if you are looking for more control, you can utilize the MPSSE engine using the D2XX drivers directly. This will mean you will not have to rely on LibMPSSE.

To use I2C/SPI as a master (no slave functionality), see AN_135 MPSSE Basics and our existing MPSSE Example projects:
 
https://ftdichip.com/software-examples/mpsse-projects/
 
There are two options to use I2C/SPI modes with the MPSSE engine:
 
a.   Use LibMPSSE libraries. Example code is provided with the download. Source code is also provided.
Note there is a known issue with this library with I2C. See LibMPSSE Beta 1.0.2 which shows the source code change to allow you to rebuild.
b.   Use D2XX drivers direct. Example code is shown at I2C / SPI. AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes provides the necessary information.
 
Option b is the best option to use the D2XX drivers direct (no dependency on libMPSSE library).

Best Regards
FTDI Community

14
Hello,

could you please email your schematic to support1@ftdichip.com? we can then review it for you to see if there is anything that could be causing your issue.

Best regards
FTDI Community

15
Discussion - Drivers / Re: How to use the FTDI device from kernel mode
« on: November 27, 2023, 04:35:41 PM »
Hello,

Our devices can't simulate regular flash memory.

Best Regards,
FTDI Community

Pages: [1] 2 3 ... 59