Hi,

You can have a look at Establishing Synchronous 245 FIFO Communications using a Morph-IC-II. This gives an example utility you can try, along with some sample code. The sample code can be found here: https://ftdichip.com/wp-content/uploads/2020/12/Synchronous%20245%20Morph-IC-II%20Application.zip.

Best Regards
FTDI Community

Hi Yvonne,

This can happen when the HID device is toggling DATA0/DATA1 without handshakes from the host. HID devices can do that sometimes, it’s even mentioned in the USB spec. You need to do a ClearFeature endpoint halt on the interrupt endpoint before reading it again.

In the code you are using to clear the halt state, the endpoint should be the interrupt endpoint instead of epCtrl in line 2. If you change this, it should clear the halted endpoint.

Best Regards

FTDI Community

Hi,

Have a look at FT260 User Guide. This shows how to set the buad rate on FT260.

Best Regards

FTDI Community

Hello,

The solution would be to only use Serial Number or Description with ASCII characters.

You can use D2xx Programming functions in Linux to reprogram or you can use FT_PROG on Windows.

The alternative driver that you can try is LibFTDI which is an open source library/driver but is not created/supported by FTDI:

https://www.intra2net.com/en/developer/libftdi/

This third party solution includes the source so may suit you if you need to make changes to the source.

Best Regards,
FTDI Community

Hi Suman,
As you have already contacted us via email on this subject and we have an ongoing discussion there i will continue with the email rather than posting here

Regards
FTDI Community

Hi Yvonne,

The 1MHz clock should be theoretically possible. It states in section 4.2.1.1 of the VNC2 user guide that The SPI Slave and SPI Master can operate at frequencies up to one quarter of the CPU clock frequency. The SPI Master can go as low as 1/256th of the CPU clock frequency.

You should have a look at section 6 of Vinculum II User Guide, this goes over the interrupt library available on VNC2. The sample code you have modified had interrupts disabled, but you can enable them. you can try to use the function attachInterrupt() on vos_dev_write to see if this fixes your issue.

 

Hello,

The feedback from our R&D team is that there is nothing that can be done with the library.

The issue is not related to the driver but the I2C IP.

Adding a delay is the only solution.

Best Regards,
FTDI Community

Hi Rich,

The recommended way of connecting VBUS depends on your application:

 (a)  For self-power application, refer to the UMFT600x/UMFT601x datasheet;

(b)  For bus-power application, VBUS is the 5V power input for all circuits. If a 5V to 3.3V regulator is used, connect the 3.3V to the FT601 VBUS pin.

 Note, the voltage divider in the Development Module between the USB power and VBUS pin is used to lower the voltage level from 5V to 3.3V so that FT601 can take it as a 3.3V logic input for VBUS sensing purpose.

 If you haven’t already, please refer to AN_412 FT600/FT601 Bridge Chips Integration.. This application note is for designers who want to integrate the FT60x into new designs.

regarding the errata, we don't have access to the EEPROM contents/structure. Customers should only use the utility. This may help you:

common problem customers encounter is the clock not working. The reason for this is that the device will enter suspend mode 10 seconds after enumeration if there is no device activity. Entering suspend mode also turns 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), although basic info on the Set and Get APIs are detailed below:-
 
FT_SetSuspendTimeout
-          Takes handle and a timeout value in seconds as input.
-          When the timeout is set to zero, driver will disable the suspend feature.
 
FT_GetSuspendTimeout
-          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 value.

Best Regards
FTDI Community