problem with vinculum vdip1

mulata

I've received a vinculum vdip1 module, and these days Im trying to make basic communication with the module using the UART.
The UART is connected to a PC (FT232 serial-USB Connector), with a terminal program I send some basic commands.
Well the VDIP1 starts in extended command mode (this means afaik, commands must be provided in ASCII mode), at the same time numbers must be provided in hex so far.
In order to configure the UART Ive set the jumpers according to the documentation and I've connected the CTS Pin of the VDIP1 to GND. RXD and TXD are connected to FTDI FT232 Chip in order to connect the module to the PC and establish a connection.
Am I right that the provided USB port on the module is Port 2, so it should be possible to access e.g. an USB stick to send commands to it, but at the same time it should be possible to communicate with a HID devices or a device using a FTDI USB Chip on the USB port of the VDIP1 ?

But, so far the communication is very limited, I can read the firmware version by sending FWV<CR>, I get the answer:
MAIN 01.15VDAPF<CR>
RPRG 1.00R<CR>
\><CR>
but if I connect an USB stick and send e.g DIR<CR>

I receive:
No Disk<CR>
Command Failed<CR>

Sending QP2 should basically return informations about the connected device, but I always receive, independently which device is connected to the USB port:
<NUL><NUL><CR>
\><CR>

At the same time no message occurs if I connect a device (e.g a FTDI Chip, RS232-USB Adapter) to the USB port, but there should occur at least a message like "Device Detected P2".

After supplying the VDIP1 with power, no LED lights.
If I connect I device, LED1 lights.

I really appreciate any help-

thanks
mulata

Mike Green

I suggest you contact Vinculum. They do respond eventually to e-mails. It looks like you have the communications working between the PC and the VDIP1. It also looks like your firmware version is fairly old. I'm using the latest which is 03.50. Vinculum has a firmware update program that will run on your setup (you have to jumper the RESET line ... the program comes with directions). Download it from their support website. Make sure your USB drive is formatted.

mulata

it seems my firmware is pretty old yes.
But nevertheless the module should work, shouldnt it.

Well do you think there might be a problem because I dont use handshaking, I've just connected CTS of the VDIP to ground?

Im wondering why LED1 lights if I connect a device to the USB port, bevause the USB port provided on the module is usb port 2, right? So shouldnt there light LED 2?

thanks
m.

mulata

Now there occured another problem, to ensure that the UART connection is fine, I've connected the handshaking signals of my FT232 USB-Serial Adapter to the pins of the Vdip1. (CTS-RTS, and RTS-CTS).
When I plug the USB Connector of the USB-Serial Adapter, connected to the VDIP1 to the PC, windows can't configure the device, there is no com-port and I cant establish a connection with my terminal program.

But if I connect the FT 232 USB Serial Adapter without the VDIP1 connected to my PC, it get configured fine.

Althoug I was already able to establish a connection, as described above, no it seems it doesnt work anymore, just because I've connected the two handshaking signals?

thanks a lot

Mike Green

I don't know why you're having these problems. I connected both a VDIP1 and a VMUSIC2 to my PC (actually a MacBook, but running WindowsXP) via an FTDI USB to serial adapter (their FT232R-3V3 "smart cable") just last night and both worked normally. Make sure your terminal program configures the handshaking lines correctly.

Unsoundcode

Hi mulata, I would return to your original configuration (CTS to Vss)·for now at least you had a response from the vdip. Getting that far it's odd that it did not detect the usb stick, I assume you did as Mike suggested and formatted the thumbdrive.

I don't know if it will help or not but I ran off a small terminal application specifically to test the monitor port commands in extended and short mode, I never did finish it but it works well to test communications via a usb to serial adapter and virtual com port. If you want to try it then follow this link and look for V2_eval.zip.

http://forums.parallax.com/showthread.php?p=637301

Even then if it says no disk it's not going to do much good.

Jeff T.

mulata

Thanks Jeff for your software I will try this these days.

Well to ensure I have a correct Hardware-Setup, I can connect my VDIP1 just like descriped in the
VPROG.pdf (see attached gif), of course I dont have to connect the RESET and Program Pin.

Im just wondering because, as described I was already able to connect to my VDIP using a terminal program and e.g. read the firmware version, but just in case when I have connected CTS of the VDIP to GND!?
But Jeff and the atteched gif tells me to connect it to VCC, 3.3V !?

Sorry for this very beginer questions and thanks a lot.

thanks
mulata

Unsoundcode

Hi mulata, what I was suggesting was to go back to your original configuration, which was no handshake. So CTS has to be held low to allow the vdip to send back to the terminal.

I would go to the basic configuration

ADBUS0(pin31) txd
ADBUS1(pin32)rxd
ADBUS2(pin33)rts#..........leave disconnected
ADBUS3(pin34)cts#...........connect to Vss
ACBUS5(pin46)....... to gnd ......jmp3......2&3
ACBUS6(pin47)........to 3.3v .......jmp4......1&2

connect as above and try your terminal and see what results you get.

Jeff T.

Chris Savage

Do you have access to another brand/type USB Thumb Drive? In our testing of the VDIP1 Module we found that out of 4 different USB Thumb Drives we had, one wouldn’t ever work or be detected by the VDIP1 Module. I think it was either a SimpleTech or a Lexar?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support

mulata

Well so far I have only tested with a CORSAIR 256 MB module, with a FAT32 partition and it didnt work.
work now at first I have to get back to my original configuration in order to be able to establich a connection.

Forrest

I've read on another forum it can take a LONG time to enumerate the thumb drive after you insert it. Long meaning more than 1 minute!

Mike Green

Forrest,
The only time I've seen it take more than 5 or 10 seconds to "mount" a thumb drive is when the thumb drive contains a ROM update. The Vinculum automatically recognizes it, copies it to its internal flash memory and reboots. That seems to have taken maybe 30 seconds and there are status messages that come across from the Vinculum while this is happening.

mulata

Hi,

Well I'm using the configuration as recommended by Unsoundcode, and I'm able to do some basic communication with my terminal program thgrough UART with the vinculum, e.g. I can read the Firmware version.
But If I connect a USB stick to the vinculum vdip1 port, and send the command IDD, I get the answer
No Disk<CR>
Command Failed<CR>

So, maybe I have to update the firmware since I'm using MAIN 01.15VDAPF<CR> RPRG 1.00R<CR>.

However, basically I should be able to access with my recent firmware (01.15) the USB stick.
I've tried two different types of USB sticks.

regards,
mulata

Post Edited (mulata) : 5/25/2007 9:06:35 AM GMT

mulata

Updating the firmware I' able to communicate with the vinculum very well.

But, after connecting some devices, e.g. a specific USB stick or a specific HID decive, I receive in a loop the following sequence:
Device Detected P2<CR>
Device Removed P2<CR>
Device Detected P2<CR>
Device Removed P2<CR>

erusch

Hi all,

I'm currently testing the VDIP1 with SPI interface. the VDIP1 is connected to a pic microcontroller (18F4685). communication seems working well. the read chars are sent to a LCD display connected to the PIC.

I've connected
1 to 5V
6 ADO to SCLK of the PIC
7 gnd to VSS
8 AD1 SDI to SDO
9 AD2 SDO to SDI
10 CS to CS
20 AC4 or DATAREQ# to VDD (5V trough a resistor)
the others unconnected.
and the jumpers: AC6/J4 position 1 (up)
AC5/J3 position 3 (down)

My firmware is version 02.08

So, I can read it, and I also succeeded with SCS command (the prompt changed).
When I plug a flash drive, I can read the message
"Device detected P2".
But if I send "DIR<CR>" command I get "Command Failed<CR> No disk<CR>" or "CF<CR>ND<CR>" in shortenend command set.
if I send "QP2<CR>" command, I can then read a long line of $24(hex).

the diodes blink a short time after powering, then off, and diode2 on when the flash drive is plugged.

I'm probably close to succeed but my commands go wrong, finally my problem looks like mulata's at the beginning of this thread.

can someone help?
thanks...

Mike Green

I'm not certain, but I believe that the Vinculum device doesn't support FAT32 yet. Try formatting your flash drive as FAT16. If it doesn't recognize a valid partition (because the only one is FAT32) it will report "No disk".

erusch

Good remark Mike, i just checked, my drive is actually FAT32 formatted. I'll try to find another one not to erase data... Thanks

Chris Savage

Perhaps you need a firmware update? The current version supports FAT32.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support

erusch

Thans for help,
I've formatted my flash drive inFAT16
now it almost works: I can use DIR, CD, OPW, CLF, RD, MKD, SCS, ECS, IPA commands. However, I can't write to a file. Here is the sequence I use:
(ECS, IPA mode, no file opened)
OPW HELLO.TXT<cr>
WRF 7<cr>BONJOUR
(something already goes wrong here)
CLF<cr>

any suggestion ?

Chris Savage

Assuming you're using the Asynchronous Serial Interface you could try the code located here...Take care.

http://www.parallax.com/dl/docs/prod/comm/DataloggerDemoV1.0.bs2

http://www.parallax.com/dl/docs/prod/comm/DataloggerTestV1.0.bs2

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support