Re: WCE5: ps/2 port driver fails - where to look ?
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Thu, 5 Oct 2006 11:02:09 -0700
Build a debug build of the OS, making sure that you have selected the "8042
Keyboard Mouse English" item from the catalog. You'll also want to add the
"Mouse" item from the Shell and User Interface section of the catalog. Make
sure that you've set the correct base I/O address, interrupt, etc. in your
registry to match the hardware. Make sure that you OAL is properly handling
the physical interrupt when it occurs and returning the SYSINTR value that
the 8042 driver added above calls InterruptInitialize() with (I don't
recall; this may be in the registry, too). Then, you can debug the
keyboard/mouse driver from Platform Builder and see what you're not getting
that you should.
Obviously, GWES should be loading the driver on startup. If not, your
registry is broken.
When GWES loads the driver, it should be calling PS2_8042_Entry(). If not,
I don't think that you've ended up with the right keyboard driver in your
image. Maybe your BSP has its own. You'll have to figure that out, if so.
Trace through the execution of PS2_8042_Entry() to make sure that the right
values are being read from the registry, that the I/O mapping is being done
correctly (the base address is being used as an I/O address, not memory).
Trace into the creation of the PS2Port object and make sure that everything
goes fine there. If you have a keyboard and/or a mouse installed, trace the
identification and initialization of those.
Paul T.
"SergeiR" <rusakov@xxxxxxxxxxxxxx> wrote in message
news:O%23HS7RK6GHA.4708@xxxxxxxxxxxxxxxxxxxxxxx
Hi Remi,
thanks for keep looking. Yes, this dev board has BIOS (natural fro x86
ones to have BIOS, WinCE won't need it though). Yes, I can run MS-DOS and
kbd and mouse work well (they use BIOS, WinCE isn't...). Further, as I
mentioned before Embedded Linux runs on it well supporting ps/2 kbd and
mouse as well as usb mouse - with exact same cmos settings as I am trying
for WinCE.
Based on that I suspect the problem is not in hardware of this VIA Luke
dev board, but is something like a) Microsoft code from Windows CE 5 isn't
fully compatible with that board or b) VIA BSP has a problem for thsi
specific hardware.
Well... I would probably be able to to tell my boss that, hey who nowadays
uses ps/2 devices, let's drop it and go ahead with usb kbd and mouse, but
... on this specific dev board usb driver fails very early and we don't
have any usb connectivity at all.
So... I am about to think to dig into 8042 specs maybe since that way
would be easier still that fighting with VIA Luke usb (we won't write our
own usb driver for this dev board)...
SergeiR
"Remi de Gravelaine" <gravelaine at aton dash sys dot fr> wrote in message
news:OvPadDG6GHA.1736@xxxxxxxxxxxxxxxxxxxxxxx
Hi Sergei,
Sorry for having been lazy when reading your initial post: I don't like
to repeat things either...
Do you have a BIOS? Can there be a configuration issue such as Valter
suggested, such as IRQ12 being reserved for PCI or something like that?
Can you boot MS-DOS? Does you keyboard work then?
Good luck!
Remi
.
- Follow-Ups:
- References:
- Re: WCE5: ps/2 port driver fails - where to look ?
- From: Remi de Gravelaine
- Re: WCE5: ps/2 port driver fails - where to look ?
- From: Sergei R
- Re: WCE5: ps/2 port driver fails - where to look ?
- From: Remi de Gravelaine
- Re: WCE5: ps/2 port driver fails - where to look ?
- From: SergeiR
- Re: WCE5: ps/2 port driver fails - where to look ?
- Prev by Date: Re: Sending parameters to ISR dll
- Next by Date: Re: Sending parameters to ISR dll
- Previous by thread: Re: WCE5: ps/2 port driver fails - where to look ?
- Next by thread: Re: WCE5: ps/2 port driver fails - now I know what exactly fails
- Index(es):
Relevant Pages
|
