Hello,

If you want to write a big chunk of slave data you can follow the instructions:

1. Set a very big value for write timeouts
For example : = FT_SetTimeouts(ftHandle, 1000, 5000);  // set write timeout of 5 sec

2. Use FT_Write to write the specific size of data. // the size can be very long

Then the writing data will be a continuous data.

Note:
When FT_write is executed on SPI Slave transaction. The program will be hold until the sending data finished, or timeout occurs.

Best Regards,
FTDI Community

Hi Janos,

if you could email support1@ftdichip.com i can send you an xml file we created for the configuration you are looking for. I can also give you more information about the I2C programming.

Best Regards

FTDI Community

Hi,

Please see the below application notes that should be able to help. They are for different products, but the same principles apply.

Bit Bang Modes for the FT232R and FT245R
AN_373 Bit-Bang Modes for the FT-X Series

Best Regards

FTDI Community

Hello,

Example 1 is provided by a Third Party.

Can you try Example 3 which uses the FTDI C# wrapper?
Please also update it with the latest C# wrapper found at the top of the page.

I'm glad to read that you have solved the original problem though.

Best Regards,
David Paterson

Hello,

JTAG and I2C re controlled by the MPSSE engine which is not configurable in the EEPROM.

MPSSE mode is enabled with FT_SetBitMode API command. See the D2XX Programmer’s Guide for more information.

The only JTAG support can be found here:

https://ftdichip.com/software-examples/mpsse-projects/
(Note this also includes I2C support)

There are two options to use JTAG modes with the MPSSE engine:

1.   Use FTCJTAG DLL library. Example code is provided with the download (This code is no longer supported by FTDI)
2.   Use D2XX drivers direct. Example code is shown at the link above, further down the page (JTAG). 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 our library).

Unfortunately we don’t support OpenOCD. However there might be information online about it or other FTDI Community users can help.

Best Regards,
FTDI Community

Hello,

This can only be done when using D2xx direct and not using LibMPSSE.

When using LibMPSSE, GPIOL[0:3] can only be used as SPI chip selects.
 
When using LibMPSSE, there is no way to control GPIOL[0:3] as GPIO.
 
LibMPSSE demonstrates controlling the higher line bytes (GPIOH) while using SPI on the lower line bytes using the following functions:
 
FT_WriteGPIO
FT_ReadGPIO
 
If you want to control some of the unused lower line bytes on the same ADBUS as SPI then see AN_411 FTx232H MPSSE I2C Master Example in C which demonstrates GPIO usage with MPSSE using D2xx direct (not using LibMPSSE).
This could be used as a base to understand using both SPI/GPIO in the same code.
OK this example is for I2C but the same principles apply to SPI.

Best Regards,
FTDI Community

Hello,

If you use FT4222_SPISlave_Write() to write SPI slave data it will append 0x00 in every time the API FT4222_SPISlave_Write() is called.

You can also try to replace FT4222_SPISlave_Write() with FT_Write() as it does not append 0x00 at the beginning.

There are only two USB FIFOs to store the data from PC Host and each FIFO is 512 bytes (but status bytes occupy 2 bytes).
When the API FT_Write() is called, it will send a bulk transfer.
If the transfer size is <512 , it will be treated a short packet transfer and occupy one USB buffer.
If the transfer size is >=512 and <=1024, it will be treated two packets transfer and occupy two USB buffers.
SPI Slave is a passive transfer.
Also make sure the SPI Master sends the clock and do not let the buffer overflow.

Best Regards,
FTDI Community