shingadaddy
New Member
My second post here so hello all. Hope you're all safe and warm. ICE storm here last night and today
Just started posting/monitoring the electronic boards again after a several year hiatus. Using a Vinculum device and trying to get it to go into data mode by asserting DATAREQ (pin 36) low. Using UART config for interface. I can talk to the Vinculum and I can read and write to flash drives so I know my comm is good. If I have Nothing plugged into the USB ports or if I have a flash drive plugged into the HOST USB port 2, I never get DATAACK (pin 35) to go low like MFG doc's says it should. ( Yes there is no need for DATA MODE with a flash disk but MFG says DATAACK should go low.) I *CAN* get it to go low if I plug in a USB BLUETOOTH adapter. Goes low just as expected but of course the Vinculum firmware reports "UNKNOWN DEVICE". I can however QP and QD it and I get the expected responses back from the bluetooth dongle. Like I said, anyone using this device in data mode? I have this setup on 2 completely identical circuit cards and both do the same thing.
Firmware I am running is VDAP 3.66 downloaded from FTDI's site
Connections and signals all confirmed with a scope. It's gotta be a connection its unhappy with or a firmware oddity.
Any comments suggestions appreciated.
Thanks in advance.
Just started posting/monitoring the electronic boards again after a several year hiatus. Using a Vinculum device and trying to get it to go into data mode by asserting DATAREQ (pin 36) low. Using UART config for interface. I can talk to the Vinculum and I can read and write to flash drives so I know my comm is good. If I have Nothing plugged into the USB ports or if I have a flash drive plugged into the HOST USB port 2, I never get DATAACK (pin 35) to go low like MFG doc's says it should. ( Yes there is no need for DATA MODE with a flash disk but MFG says DATAACK should go low.) I *CAN* get it to go low if I plug in a USB BLUETOOTH adapter. Goes low just as expected but of course the Vinculum firmware reports "UNKNOWN DEVICE". I can however QP and QD it and I get the expected responses back from the bluetooth dongle. Like I said, anyone using this device in data mode? I have this setup on 2 completely identical circuit cards and both do the same thing.
Firmware I am running is VDAP 3.66 downloaded from FTDI's site
Connections and signals all confirmed with a scope. It's gotta be a connection its unhappy with or a firmware oddity.
Any comments suggestions appreciated.
Thanks in advance.
Last edited: