-----Original Message-----
>From: Leon Wagner <leon_at_forth.com>
>Sent: Oct 22, 2009 1:41 AM
>To: sftalk_at_forth.com
>Subject: [sftalk] Re: USB from SwiftForth
>
>This might be a good starting point:
>
>http://support.microsoft.com/kb/323594

This page seems to be about writing custom Windows drivers. Not practical for me.

>As Elizabeth mentioned earlier, we interface to a number of USB debug =
>interfaces (Silicon Labs, P&E Micro, TI, Rowley Associates, and some =
>others I can't remember at the moment). ALL of these are called via =
>vendor-supplied DLLs, some of which are user-space device drivers (or =
>they call user-space drivers).

I had hoped that someone, somewhere, had communicated between a Forth windows app and a device programmed in Forth (FTDI chips aside). Instead, it appears, SwiftForth and SwiftX still do not talk to each other via USB.

>I notice that the P&E Microsystems BDM =
>DLLs come along with Jungo WinDriver components, so it might be worth =
>checking out what Jungo has to offer.
>
>http://www.jungo.com/st/windriver_usb_pci_driver_development_software.html

I will take a look.

>As you are discovering, the USB slave side is much easier than the =
>Windows (or Linux) side. The sample code we sent you for the USB flash =
>drive takes advantage of the fact that support for the the Mass Storage =
>Class (MSC) is built into Windows. I have also noticed that the USB =
>debug interfaces that do not install custom or special drivers seem to =
>be using the HID class, which is also built into Windows (and Linux and =
>OS X for that matter).
>
>I'm sure you've read this, but if not...
>
>http://en.wikipedia.org/wiki/USB_human_interface_device_class
>
>That reference at the end of the article leads to Beyond Logic, which =
>has a lot of interesting info, including this:
>
>http://www.beyondlogic.org/usb/usbdevdrvs.htm
>
>And this:
>
>http://www.beyondlogic.org/usb/ftdi.htm
>
>If you can emulate what the FTDI chips are doing (maybe with a USB =
>sniffer (like SniffUSB or USB-Snoop) you could just use their driver and =
>act like a COM port.

And maybe not. What then?

>(I have used the FTDI chips as a "way in" to =
>connect a terminal to a Forth interpreter in an embedded system. Works =
>great, but not quite what you are looking for here.)

No, I am trying to talk to SwiftX Forth on the C8051F320.

>Just a few ideas, FWIW.
>
>--Leon

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and
bug reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Wed Oct 21 2009 - 23:30:06 PDT