Debugger fails to connect with USB HID Class Driver...

Debugger fails to connect with USB HID Class Driver...

Post by Euric » Sat, 22 Feb 2003 00:38:58



Hi,

I have a CEPC platform with WinCE 4.1. I wanted to use it with a USB mouse.
For that, I presume it is necessary to include the USB Human Input
Device (HID) Class Driver feature in my platform.
I did that and then built the platform and tried to download it.
Surprisingly, with the HID driver, my platform fails to boot correctly,
and it is shown a dialog in my development workstation saying that the
de* has lost the connection to the device.

I don't see the relation between the de* connection and the HID
component. And the problem is that, after removing the component and
re-building the platform, the de* connection failure still remains.
Before adding the HID component, everything worked fine (except the USB
mouse, obviously!).

Has anyone noticed this problem before?
Thanks in advance.
Eurico

 
 
 

Debugger fails to connect with USB HID Class Driver...

Post by Eric Bouchar » Sun, 23 Feb 2003 00:26:29


Hi Eurico,

  In order to make your USB mouse work with your CEPC, you
need the HID driver and the Host Controller driver (either
OHCI or UHCI...depending on the actual Host Controller in
your PC)

  For your other problem, have you tried closing and
restarting Platform Builder?  Have you tried rebooting
your PC?

Quote:>-----Original Message-----
>Hi,

>I have a CEPC platform with WinCE 4.1. I wanted to use it
with a USB mouse.
>For that, I presume it is necessary to include the USB
Human Input
>Device (HID) Class Driver feature in my platform.
>I did that and then built the platform and tried to
download it.
>Surprisingly, with the HID driver, my platform fails to
boot correctly,
>and it is shown a dialog in my development workstation
saying that the
>de* has lost the connection to the device.

>I don't see the relation between the de* connection
and the HID
>component. And the problem is that, after removing the
component and
>re-building the platform, the de* connection failure
still remains.
>Before adding the HID component, everything worked fine
(except the USB
>mouse, obviously!).

>Has anyone noticed this problem before?
>Thanks in advance.
>Eurico

>.


 
 
 

Debugger fails to connect with USB HID Class Driver...

Post by Vibre » Sun, 23 Feb 2003 05:28:27


You may have a problem with shared interrupts on the CEPC. Make sure that
the debug ethernet card does not share IRQ with the USB (or any other
hardware), by playingh with the BIOS setup on the target.

--
Richard R. Lee (eMVP) Vibren Technologies


> Hi,

> I have a CEPC platform with WinCE 4.1. I wanted to use it with a USB
mouse.
> For that, I presume it is necessary to include the USB Human Input
> Device (HID) Class Driver feature in my platform.
> I did that and then built the platform and tried to download it.
> Surprisingly, with the HID driver, my platform fails to boot correctly,
> and it is shown a dialog in my development workstation saying that the
> de* has lost the connection to the device.

> I don't see the relation between the de* connection and the HID
> component. And the problem is that, after removing the component and
> re-building the platform, the de* connection failure still remains.
> Before adding the HID component, everything worked fine (except the USB
> mouse, obviously!).

> Has anyone noticed this problem before?
> Thanks in advance.
> Eurico

 
 
 

Debugger fails to connect with USB HID Class Driver...

Post by Jonathan Tanne » Wed, 05 Mar 2003 19:19:13


Another possibility is that your Named Connection has somehow become
corrupted.  To fix this you need to goto the Target->Configure Named
Connection dialog and select Add New.  Then enter the name for a new
connection device and select the Ethernet transports again for download and
transport.

~Jonathan Tanner

--
This posting is provided As-Is with no warranty.
For additional information on Windows CE consulting services
please visit our web site: http://www.veryComputer.com/



> You may have a problem with shared interrupts on the CEPC. Make sure that
> the debug ethernet card does not share IRQ with the USB (or any other
> hardware), by playingh with the BIOS setup on the target.

> --
> Richard R. Lee (eMVP) Vibren Technologies


> > Hi,

> > I have a CEPC platform with WinCE 4.1. I wanted to use it with a USB
> mouse.
> > For that, I presume it is necessary to include the USB Human Input
> > Device (HID) Class Driver feature in my platform.
> > I did that and then built the platform and tried to download it.
> > Surprisingly, with the HID driver, my platform fails to boot correctly,
> > and it is shown a dialog in my development workstation saying that the
> > de* has lost the connection to the device.

> > I don't see the relation between the de* connection and the HID
> > component. And the problem is that, after removing the component and
> > re-building the platform, the de* connection failure still remains.
> > Before adding the HID component, everything worked fine (except the USB
> > mouse, obviously!).

> > Has anyone noticed this problem before?
> > Thanks in advance.
> > Eurico

 
 
 

1. Newbie: How to rebuild USB HID Class Driver?

Hi, I am making changes to the file hid.cpp located in the folder
\WINCE410\PUBLIC\COMMON\OAK\DRIVERS\USB\CLASS\HID and it looks like
Platform Builder is not using my modified modules during platform
build process. I have checked the sources file and I have found
strange comment inside:

...
!IF 0
Note on DOSYSGEN: the sysgen process runs "build" on this sources file to
produce a LIB file, even though the end target will be a DLL or an EXE. This
is because COREDLL, which is linked implicitly to all such targets, can be
componentized and we want to avoid invoking COREDLL APIs that may not be
available after sysgen. If you want to build and link this target AFTER the sysgen
is complete, comment out the following line -- otherwise you will get a LIB
file.
!ENDIF
DOSYSGEN=1
...

What does it mean exactly?
Do I build usbhid.dll or coredll.dll to include hid.cpp module?
Why my sources are not even touched when I choose platform rebuild?
When I order to "rebuild selected feature" pointing to my USB driver
I got sources recompiled and obj files created with my changes, but
I do not see dlls being updated at all...

Anybody could explain that for me, please? I am stuck.

2. Location of MSIE 4 Beta ?

3. A bug in USB HID class driver

4. how to skip the sign-on page & start Windows

5. Kernel debugger failed to connect II...

6. WINE pthread_at fork message during -version

7. Kernel debugger failed to connect...

8. printer stopped in the middle of printing

9. USB hid driver still need kbdmouse driver?

10. Need USB 2.0 drivers to connect my wireless usb adapter - HELP!

11. Hiding classes in class view

12. USB auto connect (Storage Class) removable disk

13. Finding class of control that has focus -- Runtime classes fail?