On 24 Nov 2002, Charles Blackburn wrote:

> I was wondering whether anyone had got any experience in using a
> Microchip PIC microcontroller with USB in conjunction with linux?
>
> What sort of things would I need to look out for when writing the driver
> for it?
>
> The app is remote logging of equipment with USB data d/l.
>
> any other thoughts on this?

I'm doing that right now as a matter of fact.  I'm using the FTDI chip
and the serial interface so I can use a lot of my legacy code with little
trouble.  Only it's been a *lot* of trouble.

If you start with a 2.4.14 kernel or later, you won't have any where near
the problems I've got.  My legacy code sits on a 2.2.20 system, and while
that has usb capability, the FTDI driver isn't working right.  I tried to
upgrade my kernel to 2.4, and blew a lot of things away.  It's taken me 3
days to recover the 2.2.20 system (at 2 - 3 hours a day, not full time :-)

I don't think you'll need too much of a driver if you can tie into the
existing drivers and API's.  I haven't dug into a lot of detail yet, so
I'm not a usb guru (yet).  I have seen my PIC respond to the FTDI chip
RFX and RD/WR lines on the 'scope.  So I know it will work, but I haven't
got data from the high level code down to the PIC and back yet.

There's a lot of detail, but it can be made to work.  Just how much work
you want to do, and where you want to tie into linux is up to you.  It's
wide open to the point where you can write a driver that talks directly to
usbcore or you can work at a much higher level and use the FTDI driver
that's already there.

Patience, persistence, truth,
Dr. mike




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to