VNC1L / VDIP1 problem ...

Go To Last Post
9 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi, not AVR releated, but I thought you guys might know ? (not got this talking to my AVR yet !)

I have a VDIP1 (dev board for VNC1L). I have it connected via RS232 to a PC via a com terminal. I have the latest firmware (v3.66 VDAP).

I can dir, open, close, read, files on my USB stick. But when I try to read a particular number of bytes, I always get the entire file, plus a stream of a funny control char which never ends. I have to reset it. I've tried a couple of different files.

I'm sending :
OPR MYFILE.TXT
RDF 02
The file contains "HELLO" I am expecting "HE", but I get HELLO then a stream of chars that never end ?

Any ideas ?

Thanks.

Jon

Jon Russell

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think it depends on how you specify the number of bytes IIRC. I had a similar problem, may be not enough 0 in the number of bytes.

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think the same thing, but I've tried everything I can think of.

I've tried :

RDF 02
RDF $02
RDF 0002
RDF $0002
RDF 00 02
RDF $00 $02

Whats annoying is the data sheet example is :

RDF 10
helloagain

Which doesn't work for me.

Looks like I'll have to call them Monday.

Jon Russell

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

RTFM ! :-)

"...Note: After reset the monitor defaults to Binary Mode..."

You need to call "IPA" to set the numeric format to ascii. by sending "0002" I was sending 30303032 !

Its all working. :-)

Jon Russell

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
You need to call "IPA"
:oops: That's it. I have used only short command mode for over a year so things are not very clear anymore....well things are not very clear at the best of times anyway. :lol:

I have used over 100 VMUSIC2 (and another 20 systems on order) and just started to use some VDRIVE2.

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello gents,
I am so glad to find someone with experience using VDIP1.
Just like Big Jon, I am using a VDIP1, serial mode. I have no problems writing, making or changing files on a flash drive.
I can connect a Dell USB keyboard to VDIP1 and see the Hex values on terminal.
However, I have developed a USB keyboard for a Honeywell console. This keyboard works great when plug in to console, (console contains drivers for Keyboard).
However, I have to develop a production test and when I plug in my keyboard to VDIP1, keyboard “STALLS”. After set_configuration ( I used a USB analyzer). Any ideas?

Help, please!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Are you following the sequence of negotiation as outlined in J Axelson's USb book? Which version of FW are you running in your VDIP1?

I've also integrated the FTDI chip into some embedded products, starting with the VDIP1 for wirewrap prototyping of code, etc. But, I am using it simple for flash drive/mass storage interfacing.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello, I am following Don Anderson "USB system Architecture"
I am using Firmware version 3.66.

This is my data from a USB analyzer
Transfer 0
GET_DESCRIPTOR
in 80 06 00 01 00 00 40 00
out

Transfer 1
SET_ADDRESS
in 00 05 01 00 00 00 00 00
out

Transfer 2

GET_DESCRIPTOR
in 12 01 00 02 00 00 00 08
in 03 01
out

Transfer 3

GET_DESCRIPTOR

in 09 02 32 00 02 01 04 A0
out

Transfer 4
GET_DESCRIPTOR
in 09 02 32 00 02 01 04 A0
in 32 09 04 00 00 02 03 00
in 00 05 09 21 11 01 00 01
in 22 15 00 07 05 01 03 02
in 00 0A 07 05 82 03 02 00
in 0A 09 04 01 00 00 03 00
in 00 06
out

Transfer 5
SET_CONFIGURATION
in no data
in no data
in addr 1 stall
it never gets out of "stall" mode.

I can't tell if it'son my side or the VDIP1.

regards

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

a USB host should never send a stall under any condition, so the stall is the result of the device sending it.

I do not consider myself a USB expert by any means, but something seems a bit funky about the transaction above - I am not sure if the device is properly responding to the address assigned to it. In any case, it appears that the SET_CONFIGURATION transfer is being rejected by the device, which is allowed if it doesn't support the requested configuration mode.

Have you contacted the tech support guys at FTDI? I have found them to be quite helpful, though they usually take a few days to respond. Sorry that I cannot be of much help at this time.