Hello,

please refer to the following documents:

https://ftdichip.com/wp-content/uploads/2020/08/AN_163_Vinculum-II_USB_Slave_Detecting_Disconnect.pdf

this application note describes how to detect when a USB slave device has been disconnected from the VNC2.

https://ftdichip.com/wp-content/uploads/2020/08/AN_172_Vinculum_II_Using_the_USB_Slave_Driver.pdf

this application note describes the VNC2 slave driver interface, which controls the USB slave ports on the device.

these should help you with your application.

please let us know if you have anymore questions.

Best regards,

FTDI community

Hi Cgtx32,
From the data sheet.  "There are 4 GPIO pins in the FT4222H that can be configured for different
purposes, such as a suspend indicator output, remote wake up input, an interrupt input or general
purpose Input/Output. These GPIOs can be easily initialized and fully controlled at the USB host side by
the application programming interface (API) defined in LibFT4222."
The link below is for the libFT4222 users guide document. 
http://www.ftdichip.com/Support/Documents/AppNotes/AN_329_User_Guide_For_LibFT4222.pdf

Regards
FTDI Community

Hi
Did you try hitting “Pause” in the debug ribbon?
Calculating the peak stack is transfer intensive so I’d bet it would only be performed when it’s stopped running the actual code on the device. 

Regards
FTDI Community

Hello All,

We have an update for some VNC2 drivers which include some improvements.

Please contact support1@ftdichip.com and we can send you the installer via SFTP.

Note that you must have V2.0.2-SP2 already installed which can be found here:

https://ftdichip.com/firmware/vnc2-tools/

Vinculum II Installer V2.0.2-SP3.exe will be supplied which is a patch to update all the drivers and libraries (stdio, stdlib etc).

The changes are listed here in the patch readme:

2021-10-25

This is patch Version 2.0.2-SP3 release of the Vinculum II Toolchain, comprising updated device drivers and libraries.

All ReadMe file information applies to the updates provided in V2.0.2-SP3.

*** This patch installer must be applied to an installation of V2.0.2-SP2 only. ***

There are no updates to compile, debug, or other build and configuration tools; sample code; VOS kernel; Vinco libraries; IDE; or documentation.

We welcome suggestions for new features or improvements to existing features.

The ReadMe files for previous releases are also available in the installation directory.
 
Drivers Readme
--------------

Fixed Issues:
- USBSlaveFT232.a fix enumeration issue;
    Add in latency timer get and set IOCTL functions,FTDI_SET_LATENCY_TIMER and FTDI_GET_LATENCY_TIMER were present but not implemented;
    Improve data flow so data is passed faster and more reliably to and from the host;
    Implement a dummy EEPROM to enable applications that require EEPROM checks to work.
- USBSlave.a correct remote wakeup behaviour when acting as a USB device and ensure correct ZLP generation for USB verification tests.
- BOMS.a implement changes for 64kB clusters on FAT16.
- FAT.a fix available cluster count.
- USBHostFT232.a correct baud rate settings for High-Speed devices. Added support for new FTDI devices.
- USBHost.a fix VOS_IOCTL_USBHOST_DEVICE_SET_CONFIGURATION to change the configuration of devices on USB host. Note: this will re-enumerate with the new configuration value.
- USBHostCDC code fix bitmaps for notifications.

Restrictions:
- FAT library will not support ATAPI disks.
- FAT library does not support FAT12 format disks. Please use FAT16 or FAT32 format.
- FAT fat_fileCopy function will only copy files to a different disk from the source disk.
- USBHostFT232 driver does not assert RTS or DTR automatically when flow control is enabled.
    This must be done with an VOS_IOCTL_USBHOSTFT232_SET_RTS/DTR before data can be received.

Known Issues:
- N/A

 
Runtime Libraries Readme
------------------------

Fixed Issues:
- Corrected return value of printf(), sprintf(), fprintf().

Restrictions:
- N/A

Known Issues:
- N/A


Best Regards,
FTDI Community

Unfortunately the compiler doesn't do all constant initialisation which you might expect on other compilers.

If the values are expressed as constants without typecasting then it will compile.

    enum {
        g0 = 0x82F63B78,
        g1 = (g0 >> 1) & 0x7fffffff,
        g2 = (g0 >> 2) & 0x3fffffff,
        g3 = (g0 >> 3) & 0x1fffffff,
    };
                               
    static const int table[16] =
    {
        0,                  g3,           g2,          (g2^g3),
     g1,       (g1^g3),      (g1^g2),      (g1^g2^g3),
        g0,       (g0^g3),      (g0^g2),      (g0^g2^g3),
        (g0^g1),  (g0^g1^g3),   (g0^g1^g2),   (g0^g1^g2^g3),
   };
I’ve not checked the values in the code though. They are precompiled (in decimal) to the following values according to the ASM output file:

0, 274646895, 549293790, 820201905, 1098587580, 1361435347, 1640403810, 1905808397, -2097792136, -1834419177, -1572096602, -1307217207, -1014159676, -741088853, -483350502, -210866315

Best Regards,
FTDI Community

Hi,

what programming language are you using? are you able to show a screenshot of your code?

Best regards

FTDI community

Hello,
Link below is for our application note AN_184 - FTDI Device Input Output Pin States.  Page 38 details the FT260 part. 
https://www.ftdichip.com/Support/Documents/AppNotes/AN_184%20FTDI%20Device%20Input%20Output%20Pin%20States.pdf

Regards
FTDI Community

Hello,

The SCK line should normally be a push-pull output on this device (unless your code switches the pin to input mode at any time)

What I/O voltage does your MCU use? Is it a 3v3 I/O

We would recommend to check with a scope or logic analyser with analog capability to see what the waveforms are doing,

Best Regards, FTDI Community