How to debug a device driver on a PPC?

I am developing an intermediate device driver in a platform builder for a
3rd party's Pocket PC. In our case, our driver need not to talk to the
hardware directly. After our driver is developed, we will install the driver
to the PPC to verify whether the driver works or not. I would like to know
how we can debug our driver in such a case where we cannot access the 3rd
party's BSP.


.

Relevant Pages

  • Re: Any console/shell avaiable for Pocket PC 2003 verion 2?
    ... Pocket PC 2003 doesn't provide a console. ... driver can be seen in the registry. ... character mode driver for the display. ...
    (microsoft.public.windowsce.app.development)
  • Re: Platform builder or Visual Studio
    ... You built it for the correct processor for the Pocket PC, ... DLLs built ... for the emulator won't run without being recompiled on Pocket PCs. ... You could have the driver open a log file when it is initialized and ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Fail to load driver in the PXA270 platform
    ... There's no such thing as an SDK for a *processor*. ... Pocket PC/WM5 devices, you'd use the Pocket PC SDK. ... Get the driver writer's ... Index/Order value of registry, ...
    (microsoft.public.windowsce.embedded)
  • Re: Linksys wireless-G notebook adapter pings Cisco each second
    ... G2/1.0 on a Pocket PC. ... Notebook Adapter WPC54G V3 #2". ... Driver Provider: The Linksys Group, ... and install 4.100.15.5 1/29/2007. ...
    (alt.internet.wireless)
  • SDIO driver issues going from Pocket PC 2003 to Mobile 5.0
    ... Windows Pocket PC 2003 and a Veo Photo Traveler 130s SDIO camera (which we ... There is no update for the driver available. ... appears to install successfully on the rx1955 running Windows Mobile 5.0. ...
    (microsoft.public.windowsce.embedded)
Loading