Re: USB


Thanks Stephane for your answer,

I have not any problem when I want to read or write descriptor (device,
interface or endpoint) via the ioctl routine of the driver (usb.c). My
problem is that I don't know how to read/write from/to an endpoint. There is
a lot of routines provided with the stack but I can't find the right one to
read/write from/to a pipe.

Regards. Thierry.

<s.cateland@xxxxxxxxx> a écrit dans le message de news:
1142940977.320751.294420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thierry,

actually the lynxos USB stack is based on the NetBSD usb stack.
more precisely on netbsd 1.6.1

the major change in the port are due to the fact Lynxos as a realtinme
system
do not have a discoover device process deamon that wil dynamically
load associated drivers

also a precision a USB driver cannot be a dynamic driver. or all USB
driver has to be install dynamically as one big object which is really
cumbersome.

"Cordialement"
Stephane



Thierry COMPAGNON wrote:
Thanks for your answer, I'll search in HID source; I have already
searched on FreeBSD site, but I didn't find fine information. Your guess
is
right, it's what I want to do, it's quite simple!

If anyone else has ideas...

Regards.

"verenastutts" <verenastutts@xxxxxxxxxxxxx> a écrit dans le message de
news:
43FF1A42.4040904@xxxxxxxxxxxxxxxx
Thierry COMPAGNON wrote:
Hi,

I try to develop a specific software which works over USB bus, to
command a specific hardware with a PIC. I have downloaded from the
Lynxuxworks site the source code for USB; but there is not any
documentation with it.

Has anyone experienced this kind of development and could help me,
I
only want to send and receive data to and from an USB device (my
version
is 4.0); I need a template.

Thanks a lot. Best regards.

Thierry COMPAGNON.
I think the LynxOS USB stack is FreeBSD-based. You might want to look
there. I guess you need to puzzle out how to detect endpoints, then to
read/write endpoints, and finally queue up transfers. If there is
HID-driver source provided, then the mouse, keyboard, or printer drivers
might give provide a lot of clues.


.

Relevant Pages

  • Re: Creating a KMDF NDIS <==> USB driver
    ... I would assume you have to continuously read from the BULK IN endpoint to ... WdfUsbTargetPipeConfigContinuousReader and let KMDF to the reading for you. ... may not be called from within the context of a miniport driver. ... So, to adapt this for USB, it looks like (in addition to initializing ...
    (microsoft.public.development.device.drivers)
  • Re: Can a pipe be bigger than 64 byte?
    ... And My question was not towards USB spec but relative to Microsoft driver layer Can it support 512 like specified in 2.0? ... bMaxPacketSize0 is the maximum packet size of endpoint 0. ...
    (microsoft.public.development.device.drivers)
  • Re: Can a pipe be bigger than 64 byte?
    ... Thanks for the clarification, but my question is in regards to OS driver not USB, what if a later version for USB allow 1-2...KB? ... No matter the date of my driver. ... bMaxPacketSize0 is the maximum packet size of endpoint 0. ...
    (microsoft.public.development.device.drivers)
  • Re: Can a pipe be bigger than 64 byte?
    ... For high speed device bulk pipe, the only max packet size allowed is 512 ... And My question was not towards USB spec but relative to Microsoft driver ... bMaxPacketSize0 is the maximum packet size of endpoint 0. ...
    (microsoft.public.development.device.drivers)
  • How can I register multiple Coms via a virtual serial port driver?
    ... The driver function well using WIN32 applications. ... computer via this pair of bulk endpoint. ... 1.First I have to find a feasible way to register 3 COM symbol, ... 2.Only one PDOis created by lower USB ...
    (microsoft.public.development.device.drivers)