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

Pages: 1 ... 54 55 [56] 57
Discussion - Hardware / Re: Control CBUS with FT230
« on: January 04, 2018, 09:39:16 AM »

We have an example of using CBUS bit-bang with the FT-X series in the application note below.


The FT_Prog utility is a newer version of MPROG and so FT_Prog must be used for the FT-X.

To use CBUS bit-bang, your application for both the UART and the bit-bang needs to be written using D2xx.

You can use FT_Prog to set the CBUS lines to IO Mode as described in AN_373 and can also set D2xx. Note that you can still open a device via D2xx even if the D2xx/VCP EEPROM setting is on VCP so long as the port isn't open in VCP. The D2xx layer is always enabled and this option selects whether the VCP is also enabled (COM port visible) or not. However, for D2xx applications, it is still better to set D2xx mode as this hides the COM port to avoid users or applications opening it which would block access from your D2xx program.

Best Regards, FTDI Community

Discussion - Software / Re: MCU Host Bus mode Example
« on: January 03, 2018, 11:36:23 AM »

AT-Bus with Host Emulation Mode is the only example code we have available for Host Bus Mode.

You can refer to AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes to create your own software in any language.

You may find other examples useful:

Best Regards,
FTDI Community


I believe that the Buffer Flags are set internally by the IC and thus cannot be queried by the driver.
It would be best to check these with an oscilloscope, its worth noting the RD# or WR# strobe inputs must be throttled when the TXE# or RXF# buffer flags stay high for over 400 nSec.

Does you code implement the FT_GetQueueStatus function before performing the FT_Read's? An example of this can be found in the D2XX Programmers Guide:

Best Regards,

FTDI Community.

Discussion - Hardware / Re: Use of a Hub IC to connect 3 FT4232H
« on: December 08, 2017, 09:31:59 AM »

Unfortunately FTDI do not have any recommendations for a USB HUB.

TUSB4041I does look like a good choice.

Maybe someone else in this community can provide recommendations?

Best Regards,
FTDI Community


Thank you for your post.

The following application note covers FIFO Basics and should be of use to you:

Have you included the Buffer Flags in your hardware design? These should help to mitigate data loss.

Does the behaviour change if you remove the 2 second delay or compile the code natively on the Raspberry Pi?

Best Regards,

FTDI Community

Discussion - Hardware / Re: SPI mode clock duty cycle
« on: November 27, 2017, 04:55:04 PM »
Have a look at AN_114 - Interfacing FT2232H Hi-Speed Devices To SPI Bus. It provides details on how to interface and configure the FT2232H to read and write data from a host PC to a serial EEPROM over the serial SPI interface bus. It illustrates, via an example, how to use the MPSSE of the FT2232H to interface with the SPI bus and also shows examples of the read and write waveforms on the SPI interface.

FTDI Community

Discussion - Drivers / Re: FTDI Driver for Win10IoT
« on: November 16, 2017, 01:25:27 PM »

This issue is something our development team are aware of and currently working on.
We hope to have this resolved as soon as possible, but for a more accurate timeline could you please contact: support1@ftdichip.com

Best Regards,
FTDI Community

Discussion - Software / Re: Lower case letter problem
« on: November 13, 2017, 12:58:10 PM »

Yes, you can use images and fonts on the same page of your application.

Please ensure that the font data and image data are not overlapping in the RAM_G or overrunning the end of the RAM_G(especially if your image is being inflated from a compressed file and will therefore be larger when de-compressed). It is also necessary to assign the font and your image with different handles.

Does the font work well when used without the image and likewise does the image work well without the font? And if you display other items after the font (e.g. some points or other shapes) do they display correctly?

Best Regards,
FTDI Community

Discussion - Hardware / Re: FT4222H SPI mode 3
« on: November 13, 2017, 09:53:42 AM »

Are you using the device and an SPI master or slave?

You could refer to the software examples as part of the LibFT4222 download:


There is also UMFT4222EV available for test and development.

Best Regards,
FTDI Community

Discussion - Hardware / Re: FT-X ICs: Power sequencing of VCC and VCCIO
« on: October 27, 2017, 04:24:42 PM »

Please refer to the FT230X Datasheet section 6 USB Power Configurations for some power configurations.

You should either choose a bus powered design, or self-powered design, and nothing in between.

VCC and VCCIO must always be applied at the same time.

You can also use the PWREN# signal (assigned to one of the CBUS pins) which indicates when the device has been enumerated by a USB Host.

The USB Host should also put the device into a low power suspend state, if the USB data bus is idle for >3ms.

Please also reference our Development Modules such as the FT-X Breakout Modules and FT-X Development Modules which can be used for test and development.

Best Regards,
FTDI Community

Discussion - Software / Re: Lower case letter problem
« on: October 27, 2017, 10:13:01 AM »

We advise to use the -a switch instead as shown below.

fnt_cvt.exe -i consola.ttf -s 29 -a -c setfont2

We tested this with the same consola font file and it works well.

Best Regards,
FTDI Community

Discussion - Software / Re: Lower case letter problem
« on: October 25, 2017, 01:16:53 PM »

Could we ask you to send us the code used to load and display the resulting font along with the files you used for the font conversion (consola.ttf and the output files).

Please send them by email to support1@ftdichip.com as a zip file

FTDI Community

Hi Anton,

Could you please check whether the board is connected to a USB2 or USB3 port when doing the programming?

The utility requires a USB3 port in order to program the device and the error from a USB2 port looks the same as the one you mentioned here.

The board can be recovered by connecting to a USB3 port and repeating the programming and should then show up correctly programmed with your new settings.

Best Regards
FTDI Community


Thanks for your question.

When there is no bus transactions on the FT601 for 10 seconds the device will enter selective suspend mode and the driver will suspend the device. Upon entering selective suspend the device will turn off the clock. 
This USB selective suspend can be turned off, or the idle interval at which suspend should occur can be controlled by the FT_SetSuspendTimeout API (detailed info can be found in the D3XX Programmers Guide http://www.ftdichip.com/Support/Documents/ProgramGuides/AN_379%20D3xx%20Programmers%20Guide.pdf),but Ive put basic info on the Set and Get APIs below:-
-          Takes handle and a timeout value in seconds as input.
-          When the timeout is set to zero, driver will disable the suspend feature.
-          Take handle and pointer to ULONG as inputs.
Note: The value for the idle timeout configured using FT_SetSuspendTimeout is valid only for the current instance of the driver. An unplug and re-plug will cause the driver to set the timeout to a default 10 seconds.

Please may I ask you to contact support1@ftdichip.com where we can assist you further with the rest of your questions.

Best Regards,
FTDI Community

Discussion - Software / Re: FT51A output pad configuration
« on: October 11, 2017, 11:24:38 AM »

All our software examples use the 8051 Digital I/O ports P1 and P3 or Analog I/O ports P0 and P2. The pull up/downs are only relevant to the pins when they are inputs, and like the 8051 the pins are open drain when set as outputs.

Also note that traditional 8051 Port 0 (P0) is open-collector, unlike the other ports (P1 to P3).
This means that an external pull-up is required when using P0 as GPIO for example.

FTDI Community

Pages: 1 ... 54 55 [56] 57