For debugging,I remove all input devices and it`s drivers,
and winCE halted after explorer.exe excuted.But with no souce
code,it`s hard to debug the explorer.exe.
I guess that is because there is no input devieces.
Is it so?or
some any good and conveniency core debug method?
3x.

Re: With no input device,Does winCE can boot? by Steve

Steve
Mon Jan 31 09:13:42 CST 2005

1) Why do you think you need to remove input devices for debugging?
2) If you provide the NOP keyboard driver then you should be OK as a
keyboard only system is certainly feasible

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: With no input device,Does winCE can boot? by cool_harber

cool_harber
Mon Jan 31 10:05:54 CST 2005

Because I want to migrate the PXA255 lubbock BSP to my own platform.
But my platform just only has LCD(no touchscreen) and a SPI keyboard.
To debug the driver of the keyboard nees the kernel started.so I want
to boot the kernel first but without keyboard.

"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> дÈëÏûÏ¢ÐÂÎÅ:eoLn4d6BFHA.2460@TK2MSFTNGP14.phx.gbl...
> 1) Why do you think you need to remove input devices for debugging?
> 2) If you provide the NOP keyboard driver then you should be OK as a
> keyboard only system is certainly feasible
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>



Re: With no input device,Does winCE can boot? by Dave

Dave
Mon Jan 31 11:31:33 CST 2005

On Tue, 1 Feb 2005 00:05:54 +0800, "cool_harber"
<cool_harber@hotmail.com> wrote:

>Because I want to migrate the PXA255 lubbock BSP to my own platform.
>But my platform just only has LCD(no touchscreen) and a SPI keyboard.
>To debug the driver of the keyboard nees the kernel started.so I want
>to boot the kernel first but without keyboard.
>
>"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> дÈëÏûÏ¢ÐÂÎÅ:eoLn4d6BFHA.2460@TK2MSFTNGP14.phx.gbl...
>> 1) Why do you think you need to remove input devices for debugging?
>> 2) If you provide the NOP keyboard driver then you should be OK as a
>> keyboard only system is certainly feasible
>>
>> --
>> Steve Maillet
>> EmbeddedFusion
>> www.EmbeddedFusion.com
>> smaillet at EmbeddedFusion dot com

As Steve said, include the NOP keyboard driver in your build. My
experience is that WinCE does not like it when there is no keyboard
driver in the build. The NOP driver just stubs out many of the driver
routines and it provides the keystroke translation functions that make
CE happy.


Dave Heil
Vytek Inc.