Tools: Vinculum ii IDE
Chip: 32pin VNC2
Application size has plenty of flash left, only at 227000 bytes.

For some reason when I write a single page of flash, the SPI device stops working...  any ideas?

Basically this is all I am doing, then after that the SPI stops working. Tried other page locations.  What is odd, is the flash write works. I can restart, and read the correct data from the flash.

flash_writePage(0x7ff, temp_string);

HI Petrov,

We are not sure when the next update for the library will be released, however, as the source code is available on the website, customers can make their own changes and rebuild the library for their own use.

Customers can also develop their own code using D2XX direct driver. You can have a look at Command Processor For MPSSE and MCU Host Bus Emulation Modes this will allow you to not rely on LibMPSSE.

Best Regards
FTDI Community 

Is there any update on this issue?
When can we expect the next release of the library?

Complete our customer survey for your chance to win a Holy Stone HS175D drone worth £190!

Your opinion is extremely important to us, and we rely on customer feedback in order to continuously make improvements and ensure that we are addressing any issues. The responses we receive from our Annual Customer Survey are pivotal as part of this process. Plus, every entrant into the survey is entered into our prize draw, and one lucky winner will be awarded with a Holy Stone HS175D drone worth £190!*

Please follow this link to the Survey:  FTDI Survey

*Holystone and their respective logos are trademarks or registered trademarks of Holy Stone.  Holy Stone is not a participant in or sponsor of this promotion.

The promotion runs until 30th of September 2023.

Best Regards,
FTDI Community

Hello,

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 I2C/GPIO in the same code.

Best Regards,
FTDI Community

Hello,

According to LibMPSSE-SPI User Guide when using our MPSSE library it's possible to run at 30Mhz:

uint32 ClockRate
This parameter takes the value of the clock rate of the SPI bus in hertz. Valid range for ClockRate is 0 to 30MHz.

So you can maybe try with our library which has source code provided for reference.

These also may be useful to you:

AN_114 Interfacing FT2232H Hi-Speed Devices To SPI Bus
AN_180 FT232H MPSSE Example – USB Current Meter using the SPI Interface

Other software examples exist:

https://ftdichip.com/software-examples/mpsse-projects/#usb-to-spi-interface

Also please also note, SPI modes 1 and 3 are not supported with our MPSSE engine.
So please check that your SPI device doesn’t work with these modes.

We also have a support office in Taiwan.

Best Regards,
FTDI Community

hi ~
May I ask if using the 0x13 command and 0x11 command can achieve an SPI speed of 30 MHz?
I have found that 3-line SPI (9-bit) cannot achieve 30 MHz. Is there a 9-bit command available?
see AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes .
thank you so mcuh!!

Hi,
Iam using FT2232h module in MPSSE mode for I2c  and how the remaining 4 pins(ADBUS4-ADBUS7) works,iam using libmpsse library 

Hello,

When FT_SetTimeouts() is not used, standard d2xx read and write API's would not return as they are blocking calls.

When FT_SetTimeouts() is set to say 5 seconds, that would give plenty time for Read and Write API calls and it would return if there were any issues with the Read or Write.

Best Regards,
FTDI Community

Hello,

When using our products in electrically noisy environments, you can try in section 5.1 Adjusting the Reset Pipe Retry Count of AN_107 Advanced Driver Options.

You can also edit the registry, opposed from editing the INF files which breaks driver signing.

Note that registry entry may need to be created:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FTDIBUS\Parameters\RetryResetCount
The default value is 50 so you can try increasing to see if it has an effect.
This can stop USB disconnects in electrically noisy environments.

The above might be something additional to try to see if it helps, otherwise modify your hardware to cope in electrically noisy environments might be the best way forward and check if you are using a USB certified and shielded cable.

Best Regards,
FTDI Community