作者:wogoyixikexie@gliet 2008-11-29
我选debug模式编译运行,遇到以下奇怪问题。
=====================================================================================
我再次打开setting菜单
变成如下这个样子
==============================================================================
查看生成NK的路径,居然跑到release模式下的文件夹了
看图
=====================================================================
一般来说,如果以debug模式编译,环境变量会有
WINCEDEBUG=debug.的,现在查看有没有
---------------------------------------------------------------------------
居然有这个环境变量!!!
现在不知道这样编译出来是否能启动。明天试试。
不知道各位是否在以debug模式编译的时候是否会这样,我用家里和公司的电脑都是这样。
================================================================================
刚才来到公司,编译出了debug的NK,
attach device之后
在DNW打印了如下串口信息
--------------------------------------------------------------------------------
DCache: 8 sets, 64 ways, 32 line size, 16384 size
ICache: 8 sets, 64 ways, 32 line size, 16384 size
OALKitlStart : USB SERIAL
Wait for connecting
KeyIndex 0 = -1
KeyIndex 1 = -1
KeyIndex 2 = -1
KeyIndex 3 = -1
KeyIndex 4 = -1
KeyIndex 5 = -4194305
KeyIndex 6 = -4194305
KeyIndex 7 = -1
+KITLRegisterDfltClient, service:0
+KITLRegisterDfltClient, service:1
KITLGlobalState == 0x61
Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0
ProcessAdminMsg: Receive Config message for service DBGMSG
ProcessAdminMsg: Receive Config message for service DBGMSG
ProcessAdminMsg: Receive Config message for service DBGMSG
ProcessAdminMsg: Receive Config message for service PPSH
ARMInit done.
+KITLRegisterDfltClient, service:2
ProcessAdminMsg: Receive Config message for service KDBG
ProcessAdminMsg: Receive Config message for service KDBG
MarshalProcessesAsModules: Process ID 0x03DDF002 (NK.EXE) not using CoreDll.dll, may be in startup or shutdown.
MarshalProcessesAsModules: Process ID 0x03DDF002 (NK.EXE) not using CoreDll.dll, may be in startup or shutdown.
MarshalProcessesAsModules: Process ID 0x03DDF002 (NK.EXE) not using CoreDll.dll, may be in startup or shutdown.
GetProcessDebugInfo: Process ID 0x03DDF002 (NK.EXE) not using CoreDll.dll, may be in startup or shutdown.
KITL: Leaving polling mode...
KITL Checking client registrations
+RegisterClientPart2: Id 0x00000000
KITL Timer thread started, (hTh: 0x23DDBFBA, pTh: 0x83DCA400)
-RegisterClientPart2
+RegisterClientPart2: Id 0x00000001
-RegisterClientPart2
KITL Creating IST
KITL Interrupt thread started (hTh: 0xE3DC8242, pTh: 0x83DC8000), using SYSINTR 19
Enabling adapter ints...
0x83c9b654: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1 time(s). This OK if KdStub stumbling on its own BP.
0x83c9b654: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 2 time(s). This OK if KdStub stumbling on its own BP.
0x83c9b654: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 3 time(s). This OK if KdStub stumbling on its own BP.
0x83c9b654: Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 4 time(s). This OK if KdStub stumbling on its own BP.
....................................................
从这个串口信息看有什么问题?
更加匪夷所思的是在加载过程中出现了如下画面。
这个是什么错误,你们遇到过吗?
——后来我在C盘找对应的路径,找到了打印信息的地方。
============================哎,咋这么多问题呢?
高人们,这是怎么回事啊?
===================================================================================
郁闷,其实KITL已经可行的。是液晶背光驱动不知道怎么回事不行了。
debug加载错误,不管他了。
现在我把怎么么样修改代码和环境变量的图贴出来。对KITL也算做一个交代。