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 ... 44 45 [46] 47
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

Discussion - Hardware / Re: USB-I2C converter - Cypress CY8C9560A
« on: October 06, 2017, 04:19:38 PM »
Hello Júlio,

We have not used these adapters ourselves unfortunately, but hopefully some of the other forum members can help.

One thing we did notice is that the 5 bytes of the command need to be sent together and so please check that your PC application does this without gaps between.

Best Regards,
FTDI Community


Please follow the steps outlined in the Driver Uninstallation procedure which will remove and reinstall all FTDI drivers from your machine:

If you are still having problems after following these steps please can you contact support1@ftdichip.com with full details of your problem and a copy of your schematic so that we may review it, quoting this forum topic.

FTDI Community

Discussion - Hardware / Re: USB Printer emulator
« on: October 04, 2017, 05:06:50 PM »

Welcome to the Forum,

I'm afraid our USB-serial bridging devices such as the FT232R don't support other USB classes and so could not be programmed to appear as a USB printer. A few applications may still support sending print data to a COM port as some printers (e.g. label printers) still connect over RS232.

If you are looking to send data (in a text file for example) from one PC to the other, you might also be able to re-direct that data to a COM port using an application such as a terminal program (send file option) or by writing a small program which parses the file and sends it out over the COM port. In this case, you could use a USB-COM232-PLUS-1 on the sending PC and another on the receiving PC and link them with a null-modem RS232 cable.

There is also a USB-NULL-MODEM cable with two FT232Rs inside which performs the same function provided that you only need a couple of meters of cabling.

Hope this helps,
FTDI Community

Discussion - Drivers / HLK Studio Error
« on: October 03, 2017, 02:16:34 PM »
Some of our customers are having problems with Driver Reseller Rights for our submission ID 1152921504627044695.
When they open the .hlkx files in HLK Studio, the following error appears:

"Package (Shell_1152921504627044695.hlkx) with a version ( is not compatible with this instance of PackageManager.  This instance of Package Manager accepts versions,,,"

This appears to be a problem with the latest version of HLK Studio version 1703:


If you download 'Get the HLK Insider Preview' at the link above, the issue is resolved with this preview version.
Note: You need to be a member of the Windows Insider program to download this preview version.

Microsoft plan to release this updated version of HLK Studio.

FTDI Community

Discussion - Drivers / FTDI Driver Reseller Rights
« on: October 03, 2017, 02:03:49 PM »
Microsoft has moved to a new Hardware Dev Center for resell rights, replacing Sysdev:


A resell submission is now called Shipping Label.

We have some reseller guidance on the process which was kindly shared by another customer:

Reseller Guidance.pdf

Note: You need a Microsoft Azure Domain Account.

More information can be found on Microsoft’s website since it’s their process.
If you need additional support, contact Microsoft.

FTDI Community

Discussion - Drivers / Create a Project Using the D2XX Drivers
« on: October 03, 2017, 11:27:30 AM »
The user can create 32bit or 64bit dynamic or statically linked projects using the D2XX drivers.

Read more in TN_153 Instructions on Including the D2XX Driver in a Visual Studio Express 2013 Project

The necessary driver files can be downloaded here:

D2XX Drivers

Note: The current free version of Visual Studio is Visual Studio Community 2017.
It allows you to use for 30 days without a Microsoft account. However, after this period it asks you to sign in. You can create a free Microsoft account which will allow you to continue to use Visual Studio for free.

The following simple code can be used as a test:

#include "stdafx.h"
#include <windows.h>
#include "ftd2xx.h"
int main()
FT_HANDLE ftHandle;
FT_STATUS ftStatus;
ftStatus = FT_Open(0, &ftHandle);
ftStatus |= FT_SetUSBParameters(ftHandle, 4096, 4096); // Set USB transfer sizes
ftStatus |= FT_SetChars(ftHandle, false, 0, false, 0); // Disable event characters
ftStatus |= FT_SetTimeouts(ftHandle, 5000, 5000); // Set read/write timeouts to 5 sec
ftStatus |= FT_SetLatencyTimer(ftHandle, 16); // Latency timer at default 16ms
ftStatus |= FT_SetFlowControl(ftHandle, FT_FLOW_NONE, 0x11, 0x13); // No flow control
ftStatus |= FT_SetBaudRate(ftHandle, 9600); // Baud rate = 9600
ftStatus |= FT_SetDataCharacteristics(ftHandle, FT_BITS_8, FT_STOP_BITS_1,
if (ftStatus != FT_OK) printf("ftStatus not ok %d\n", ftStatus); //check for error
char data_out[12] = "Hello World";
DWORD w_data_len = 12;
DWORD data_written;
ftStatus = FT_Write(ftHandle, data_out, w_data_len, &data_written);
char data_in[12];
DWORD r_data_len = 12;
DWORD data_read;
ftStatus = FT_Read(ftHandle, data_in, r_data_len, &data_read);
if (ftStatus != FT_OK)
printf("ftStatus not ok %d\n", ftStatus);
printf("Data Read: %s\n", data_in);
ftStatus = FT_Close(ftHandle);
printf("Press Return To End Program");
return 0;

Test and Review Area / libMPSSE Beta
« on: October 03, 2017, 11:25:29 AM »
Hi Everyone,

We have a new beta version of our libMPSSE library below:


This has several updates compared to the release currently on the website including:
- Resolves issue with multi-byte reads on I2C
- Resolves issue with opening device on some USB3 ports (opens by Description instead of location ID)
- Sends I2C Stop condition if the Master terminates a transaction
- Improved clock granularity in I2C_CLOCK_HIGH_SPEED_MODE
- Fix for clock resolution issue on FT2232D

We are currently testing the beta and hope to release it soon but if you have any feedback on the new beta then please let us know.

Thanks, FTDI Community

Pages: 1 ... 44 45 [46] 47