This might be a good starting point:

http://support.microsoft.com/kb/323594

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 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.htm=
l

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. (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.)

Just a few ideas, FWIW.

--Leon

> -----Original Message-----
> From: sftalk-bounce_at_forth.com=20
> [mailto:sftalk-bounce_at_forth.com] On Behalf Of Alan Furman
> Sent: Wednesday, October 21, 2009 10:14 PM
> To: sftalk_at_forth.com
> Subject: [sftalk] Re: USB from SwiftForth
>=20
> "The API is provided in the form of a library file=20
> precompiled under the Keil C51 tool chain. Device firmware=20
> must be developed using the Keil Sofware C51 tool chain." --=20
> Silicon Labs AN169
>=20
> Elizabeth Rather writes:
>=20
> >It seems to be a black art. SwiftX has several targets that=20
> use USB for=20
> >the XTL, but in at least some (maybe all) cases we've had to get the=20
> >cooperation of the board mfr to send us the C source for the=20
> target end=20
> >(they don't like to distribute it). It may be necessary to load the=20
> >mfr's driver somewhere and call it from Forth.
>=20
> This would require me to know more about Keil C than if I=20
> programmed the entire target application in C.
>=20
> I hope someone else here=20
> >is able to be more helpful.
> >
> >Good luck,
> >Elizabeth
>=20
> So far it appears that I can have Forth, or I can have USB,=20
> but not both.
>=20
>=20
> Alan Furman
>=20
> ----------------------------------------------------------------------
> 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
> ----------------------------------------------------------------------
>=20
>=20

----------------------------------------------------------------------
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 - 22:42:11 PDT