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

Pages: [1] 2 3 ... 10
 on: Today at 02:18:32 PM 
Started by bernie - Last Post by FTDI Community

You could try changing the latency timer (FT_SetLatencyTimer) to 1 or enabling flow control in your application program (FT_SetFlowControl). Have a look at the D2XX Programmer Guide for further details:


FTDI Community.

 on: February 19, 2019, 10:04:03 PM 
Started by TonyZ - Last Post by Kaetemi
The practical use of the glyph address in the font metric block is to allow the font bitmap to be loaded at any RAM address easily. Under ESE it is assumed that you'll manually write the address where the font bitmap is loaded into the address value, after having loaded the data into RAM_G.

Sample code exported from ESE should demonstrate this behaviour.

 on: February 19, 2019, 09:33:33 PM 
Started by scorpioprise - Last Post by Kaetemi
You can manually create an Eclipse project under a subdirectory of the ESD project, and link in all the required source files into the new project.

That will allow you to use the same source base from both ESD and Eclipse at the same time, with some manual project synchronization.

Copy the generated one into a subfolder called Project, edit in notepad, set up the paths to files in the project to PARENT-1-PROJECT_LOC, and use absolute paths for source files that are in the Libraries folder of your installation.

The #ifndef ESD_SIMULATION macro can be used to exclude any platform specific code, and put testing stubs in place instead.

 on: February 19, 2019, 11:01:19 AM 
Started by driver - Last Post by driver
I have been reading all the ANs about FTDI libMPSSE and FTD2XX library, and can not find any explicit description of the proper procedure to use a single MPSSE channel for both I2C and SPI, initialisation and deinitialisation. We are using FTDI2232H. Should we use FT_Purge, FT_Close and FT_Open (with FT_CyclePort if there are any errors), or is just a simple FtdiDevice.SetBitMode(0x00, 0x00); enough to reset the MPSSE interface (and libMPSSE library) to enable initialisation of other protocol?

 on: February 19, 2019, 08:27:54 AM 
Started by bernie - Last Post by bernie
Hi folks,

I’m using the FT201X and ftd2xx.dll with vb .net for my project. I’ve managed to get most needed functions to work neatly. That is interfacing my windows application with an MCU over I2C. But I’m encountering difficulties with two functions. These are ‘FT_GetStatus’ and ‘FT_GetQueueStatus’. These functions return 0 even when TXE# confirms the buffer is full. What I would like to know is if this is a known issue for the FT201 (assuming I’ve done everything correctly) or if this is the result of something else. I need atleast one of these functions to read the buffers efficiently. Thanks in advance.

 on: February 18, 2019, 10:59:35 AM 
Started by Attila - Last Post by scorpioprise
Be aware, caveat ahead!

The screen design will need some interaction with other code / hardware, so both approach will lead to some tweaks.

I found my way using EVE Screen Designer, then editing via Eclipse some of the generated code (which can be done in a easy manner) to obtain desidered behaviour.

 on: February 15, 2019, 04:59:22 PM 
Started by Attila - Last Post by Kaetemi
EVE Screen Editor is aimed at exploring the capabilities of the EVE platform, with a focus on experimenting directly with display list and coprocessor commands. It's helpful for quickly visually prototyping the instructions you need to achieve the result you want. Use this as a learning tool to work with EVE directly.

EVE Screen Designer is a very high level tool, and abstracts most of the complicated details of programming a UI away, providing a drag and drop experience to build a fully interactive UI. It's suitable for quickly prototyping an interactive UI, and the libraries deal with most of the platform specific intricacies for you.

 on: February 08, 2019, 01:05:48 PM 
Started by Flo80 - Last Post by Flo80
Thank your for answer.
I tried putting in practice all your suggestion. I think the problem is not because of using LibMPSSE library.I used the D2XX drivers direct, as you suggest, and also use the LibMPSSE_0_6_Beta and the results are the same. I also tried to verify the influence of the OS and USB Host by copying a large amount of data to several USB Sticks in the same time with writing on the memory. I tried to execute the program on others SO (Windows 7, for example). The results were the same: there are only 2 different writing (or reading) speeds s1 and s2 ~= 3,5*s1.
I have observed the SPI bus with Oscilloscope and I saw that the data were transferred with the SPI clock that was set to, but with big gaps between frames (10ms for s1 speed and 30 ms for s2 speed).
I've made some other tests like: put the USB selective suspend setting on Disable, change the clock from 1MHz to 30MHz, put pullup resistors on MISO and CS memory pins, use ResetMemory() function before writing any data and WriteDisable() function after writing data on the memory. 
In conclusion the results were the same. I don’t know what others test to perform. 
If anyone has any suggestions I will be glad to implement it.

 on: February 08, 2019, 10:23:44 AM 
Started by Cactus - Last Post by Cactus
Hi SwissGuy,
I was unable to get a matlab driver sorted out. Struggled for quite a bit but then I was able to get it sorted on Labview so gave up.

 on: February 06, 2019, 08:27:08 AM 
Started by ganswer - Last Post by n1mm
Please note that the source files are missing for the FTD3XX_Net.dll  linked to on the page: https://www.ftdichip.com/Support/SoftwareExamples/FT60X.htm . They are supposed to be in the file: https://www.ftdichip.com/Drivers/D3XX/FTD3XX_NET.zip but that contains only the DLLs.  The files referenced above compile fine here, and I needed them to backlevel the dll from .Net 4.5 to 4.0. 

You don't want to have users have to come to a community site just to find this, but I am happy I succeeded!

Tom Wagner

Pages: [1] 2 3 ... 10