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

Hello,

We're working with you on this issue via email and we can post the final resolution on this forum once we know.

This will be more helpful for other community users rather than speculating what the issue is without knowing the root cause.

Best Regards,
FTDI Community

Hello,

Please ensure that you are opening the correct interface.

For example, FT4222H in Mode 0:

Interface A is for SPI/I2C control.
Interface B is for GPIO control.

If you open the wrong interface in your software this can lead to issues.

It's worthwhile checking your mode configuration and application software as uninstalling Windows Security patches should not be the solution.

Best Regards,
FTDI Community

Hello,

You should browse to the appropriate area like here:

FTDI Community >General Category >Discussion - Software

Then you need to click on New Topic at the top. Make sure you have logged in.

Alternatively you can send an email to your local support office:

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

Best Regards,
FTDI Community

Hello,

FT602 can support resolutions up to 1920x1080@60 frames per second. as per the FT602 SuperSpeed USB3.0 IC Datasheet, Section 4.

The twelve bytes of header 0x0000_820C, 0xBABE_FACE, 0xBABE_FACE are UVC Payload header. First word also could (and should) be 0x0000_820C or 0x0000_830C - with FID bit in Bit field header toggling each new frame. As PTS and SCR bits are cleared, and header length is 12 bytes.
Size of frame after that header is also important. It should be 38400 of 32-bit YUY2 data words for 320x240; 153600 for 640x480 and so on. Calculation assumes that each YUY2 32-bit data word contains two pixels, so (320/2)*240 = 38400.

Before the start of each frame the user should send 0x0000_0055 in 32-bit DATA bus with 0x1 on 4-bit BE bus.

Best Regards

FTDI Community