FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Pages: [1] 2 3 ... 10
 on: August 06, 2020, 01:53:06 PM 
Started by jney - Last Post by FTDI Community

Good catch!
Yes the examples tend to initialize only 1 USB port from the 2 available, and in the case of the V2DIP1-32 this isn't the USB port that is pinned out on the module.

Best Regards,
FTDI community

 on: August 06, 2020, 11:20:38 AM 
Started by jney - Last Post by jney

I've tried what you suggested but without success.

However, I've solved the problem.

Seems like the SPI USB bridge example is not designed for the V2DIP1-32 Evaluation Board.
To make it work I had to change the code to use the second USB device.

Code: [Select]
usbhost_init(VOS_DEV_USBHOST_1, -1, &usbhostContext); to
Code: [Select]
usbhost_init(-1, VOS_DEV_USBHOST_1, &usbhostContext); solved the problem.

 on: August 05, 2020, 03:16:41 PM 
Started by jney - Last Post by FTDI Community

Can I get you to try the following files in your project to see if they help?
BOMS files

Some instructions:
Replace the “.a” files in
C:\ProgramData\FTDI\Vinculum II Toolchain\Firmware\Drivers\lib
and the “.h” files in
C:\ProgramData\FTDI\Vinculum II Toolchain\Firmware\Drivers\include

Unfortunately if these do not help it may indicate the enumeration issue could be related to the USB drives hardware.
Flash drives are a commodity product and are designed as such, often you find these are not designed to the applicable specs.
It may be worth using flash drives you can guarantee from the manufacture which are designed to a standard with proper bill of materials control. And which would guarantee that their devices were identical and would work the same throughout the lifetime of the product.

Best Regards,
FTDI Community

 on: August 05, 2020, 01:51:05 PM 
Started by jney - Last Post by jney

Thanks for the fast responds.

I just had a look and both my USB Sticks are using 512 Bytes per Sector.

What else could be the problem?

 on: August 05, 2020, 01:24:50 PM 
Started by jney - Last Post by FTDI Community

Looks like the firmware cannot enumerate the USB driver.

The Vinculum firmware support BOMS devices formatted in FAT12, FAT16 or FAT32 file systems only where the sector size is 512 bytes.
You can determine the sector size by entering the following command into a windows command promt:
wmic DISKDRIVE get bytespersector, caption
Data displayed:

BytesPerSector  Caption
512             TOSHIBA DT01ACA050 SCSI Disk Device
512             SanDisk Cruzer Blade USB Device

Best Regards,
FTDI Community

 on: August 05, 2020, 10:07:29 AM 
Started by jney - Last Post by jney

I'm using the V2DIP1-32 development module with the VNC2 debug module.
I want to implement a data transfer between SPI and USB mass storage.

Unfortunately the SPI2DSC example (https://www.ftdichip.com/Support/Documents/AppNotes/AN_186_VNC2_SPI_to_USB_Memory_Bridge.pdf) does not recognize my USB device.
It does not get out of the loop in line 273 of SPI2DSC.c where checking usbhost_connect_state:
Code: [Select]
while (usbhost_connect_state(hUSBHOST_1) != PORT_STATE_ENUMERATED)
I've tried two different FAT32 USB Sticks, both with the same result.

Best regards

 on: August 04, 2020, 04:44:42 PM 
Started by williamxie - Last Post by FTDI Community

The symptoms that you are describing is pointing to an issue with the hardware or cable.
Please check your design with the information provided in our previous post.

Also check that you are using a certified SuperSpeed USB cable.

You can also contact your local support team in China to check your hardware design:


Best Regards,
FTDI Community

 on: August 04, 2020, 03:25:52 AM 
Started by williamxie - Last Post by williamxie
    I have tested that once FT_readpipe return 32 occured, I run closehandle immediately, then FT_create after 5 seconds. Ft601 would turn into right state. 
after reopen ft601 device, FT_readpipe return 32 again, it's not use doing that closehandle, FT_create. ft601 device would disppeared from device manager. I have to plug in ft601 device.
I also found that a wifi router device near close to ft601 device FT_readpipie return 32 would occur frequently.
How can i do to escape from return 32? is closehandle and recreate used? is waiting 5 seconds necessary?

 on: August 03, 2020, 12:32:51 PM 
Started by williamxie - Last Post by williamxie
   I want to kown that FT_readpipe return 32(other error) once , how can i correct the device into normal state in sw?

 on: July 30, 2020, 03:22:35 PM 
Started by williamxie - Last Post by FTDI Community

It sounds like there may be some kind of marginality in the hardware or the cables.

It is worth checking your design against these guidelines and the schematics of our evaluation boards provided in the datasheet to see if there are any issues with the hardware. Other external factors such as the power supply can also cause issues.

Best Regards,
FTDI Community

Pages: [1] 2 3 ... 10