Re: usb ce 4.2 host driver
- From: "David Liao \(MS\)" <davli@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 9 May 2005 09:12:41 -0700
I don't know that log. It looks like output from clients driver or some Host
driver which is not from Microsoft.
I can't help here.
Sorry
David Liao
"prashanth" <prashanth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:17DCA56A-464D-4C2A-B3CA-F63F42713865@xxxxxxxxxxxxxxxx
> Hi David,
>
> I received the USB_CLOSE_DEVICE event when i turn off the device. It is
> only
> when i send the command to the device that i have the problem. (I am not
> sure
> if the device detaches and re-attaches when i send this cmd) The USB
> monitor
> program shows the communication log as follows when the RESET cmd is sent.
>
> cmd sent to device and receive ACK
> reset(20ms)
> suspend(96.1ms)
> reset(20ms)
> Enumerates and gives device new address
>
> As i said the generic CDC class driver on a desktop PC doesn't have this
> problem.
>
> I use a CF to USB adaptor from Ratoc systems to provide to host capability
> to the PDA.
>
> Regards,
> prashanth
>
>
>
> "David Liao (MS)" wrote:
>
>> I don't understand what you said. What you mean by "we send a RESET
>> command
>> to our device ". Does it send command to device and then device detached
>> from UBS Bus and re-attached itself again?
>> If device does reattached again, the USB_CLOSE_DEVICE should be called,
>> otherwise, the Device Address shouldn't change.
>>
>> Did you register callback function before device detached? the function
>> name
>> is RegisterNotificationRoutine.
>>
>> David Liao
>> "prashanth" <prashanth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:E0624EC1-BC00-44B8-95BF-71E9E71E4064@xxxxxxxxxxxxxxxx
>> > Hi,
>> >
>> > I have written a custom USB device driver for POCKET PC 2003. The PDA
>> > acts
>> > as the host and communicates with our device.
>> >
>> > As part of the communication, we send a RESET command to our device
>> > which
>> > restarts it. But the host controller enumerates and gives the device a
>> > new
>> > address.
>> >
>> > As such it creates a new device context (eg COM2) and doesn't send a
>> > USB_CLOSE_DEVICE signal which would allow the driver to deallocate the
>> > previous device context (eg COM1).
>> >
>> > I checked the device against a desktop pc running Windows XP/2000. It
>> > always
>> > assigns it device address (1) after RESET.
>> >
>> > Any pointers about resolving the above described problem are greatly
>> > appreciated ...
>> >
>> > Regards,
>> > prashanth
>>
>>
>>
.
- References:
- usb ce 4.2 host driver
- From: prashanth
- Re: usb ce 4.2 host driver
- From: David Liao \(MS\)
- Re: usb ce 4.2 host driver
- From: prashanth
- usb ce 4.2 host driver
- Prev by Date: Permanently save multiple IPs per Adapter
- Next by Date: CE Up down arrow keys
- Previous by thread: Re: usb ce 4.2 host driver
- Next by thread: Re: usb ce 4.2 host driver
- Index(es):
Relevant Pages
|
