社区导航

 

搜索
查看: 2820|回复: 6

CE6.0加载后不能运行,串口输出如下,貌似是显示驱动或硬盘电源问题

[复制链接]

82

TA的帖子

0

TA的资源

一粒金砂(初级)

Rank: 1

发表于 2009-10-20 14:15 | 显示全部楼层 |阅读模式
搞了好几天了,人都要崩溃了
开机用DOS引导,loadcepc加载nk.bin
凌动z530,芯片组US15W

加载内核后,屏幕出现
Jumping to ox00226E20
然后串口开始输出调试信息
串口输出最后几行如下,貌似是显示驱动或硬盘电源问题:
RdrMain: DLL_PROCESS_ATTACH, hInst:0x88D6A1C0
  +RDR:Redir helper func: Ctxt:0x0, OpCode:1
  +RDR:InitRedir
Rdrofgt:ntaieeiCni:
        ClearTextPasswordAllowed: FALSE
        ServerTimeoutMs: 10000
        FindCacheMaxSize: 8192
        ResourceExpiryInt: 600
        ReceiveBufferSize: 9000
        RegisterFileSystemRoot: TRUE
        ReceiveThreadPriority: 251
        AllowedAuthMethods: 3
        TimeZoneBias: 480
  +RDR:InitNetBIOS
NETBIOS: NB_NET_NOTIFY for callback at address 0xc0999600Browser initialized
  +RDR:FSAPIInit
FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 1 (Name="Network", MountFlags=0x80)  -RDR:FSAPIInit
DEVICE!RegReadActivationValues RegQueryValueEx(Comm\Devices\Redir\BusPrefix) returned 2
  -RDR:InitRedir:  initialization successful
        !AFD: Unable to load library 'IPNat.dll'
OSAXST1: >>> Loading Module 'ws2instl.dll' (0x88D6F5BC) at address 0xC06D0000-0xC06D8000 in Process 'NK.EXE' (0x827C1C80)
Ws2Instl dllentry() -1999178308
Ws2Instl:IsStackInstalled - LoadLibrary(irdastk) failed 126
Ws2Instl:IsStackInstalled - LoadLibrary(btd) failed 126
Ws2Instl:IsStackInstalled - LoadLibrary(tcpip6) failed 126
OSAXST1: >>> Loading Module 'k.ssllsp.dll' (0x88D6F874) at address 0xC0720000-0xC0731000 in Process 'NK.EXE' (0x827C1C80)
OSAXST1: >>> Loading Module 'k.ws2.dll' (0x88D6FB2C) at address 0xC06B0000-0xC06BF000 in Process 'NK.EXE' (0x827C1C80)
Kernel DLL 'k.ws2.dll' needs thread creation/deletion notification
OSAXST1: <<< Unloading Module 'k.ws2.dll' (0x88D6FB2C) at address 0xC06B0000-0xC06BF000 in Process 'NK.EXE' (0x827C1C80)
OSAXST1: <<< Unloading Module 'k.ssllsp.dll' (0x88D6F874) at address 0xC0720000-0xC0731000 in Process 'NK.EXE' (0x827C1C80)
        !AFD: Unable to load library 'DhcpV6L.dll'
        !AFD: Unable to load library 'tcpip6.dll'
        !AFD: Unable to load library 'irdastk.dll'
        !AFD: Unable to load library 'btd.dll'
        !AFD: Unable to load library 'IPNat.dll'
        !AFD: Unable to load library 'DhcpV6L.dll'
-AFD:Init Complete
DeviceFolder::LoadDevice(Drivers\BuiltIn\AFD) last 949 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Ws2Serv\BusPrefix) returned 2
:
CDriverContext::OpenStream( OUT ) - format (1 2:16 44100 4 176400 flag=1)
CSDHCBase::IST: Thread Starting
CSDHCBase::IST: Thread Starting
IPDispatchDeviceControl returned Status 103
OSAXST1: >>> Loading Module 'coredll.dll' (0x8EFF9630) at address 0x40010000-0x400D3000 in Process 'udevice.exe' (0x88D753EC)
OSAXST1: >>> Loading Module 'udevice.exe' (0x88D753EC) at address 0x00010000-0x00016000 in Process 'udevice.exe' (0x88D753EC)
udevice.exe $udevice_1003
FSDMGR!MountTable_t::RegisterVolumeName: Registered "$udevice_1003" at index 11APISCreateAPIHandle: pvData == NULL
FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 11 (Name="$udevice_1003", MountFlags=0x101)OSAXST1: >>> Loading Module 'ws2serv.dll' (0x88D76C00) at address 0x402E0000-0x402F1000 in Process 'NK.EXE' (0x827C1C80)
OSAXST1: >>> Loading Module 'ws2serv.dll' (0x88D76C00) at address 0x402E0000-0x402F1000 in Process 'udevice.exe' (0x88D753EC)
OSAXST1: >>> Loading Module 'ws2.dll' (0x8EC71B70) at address 0x402A0000-0x402AF000 in Process 'udevice.exe' (0x88D753EC)
DeviceFolder::LoadDevice(Drivers\BuiltIn\Ws2Serv) last 307 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PPP\Prefix) returned 2
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PPP\BusPrefix) returned 2
DeviceFolder::LoadDevice(Drivers\BuiltIn\PPP) last 47 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NDISUIO\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'ndisuio.dll' (0x88D8A648) at address 0xC0800000-0xC080E000 in Process 'NK.EXE' (0x827C1C80)
DeviceFolder::LoadDevice(Drivers\BuiltIn\NDISUIO) last 57 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\autoras\BusPrefix) returned 2
AUTORAS:: ARS_Init()..
AUTORAS:: Reg[Dialer] = [rnaapp.exe]
AUTORAS:: Reg[RasEntryOpt] = [-e]
AUTORAS:: Reg[NoPromptOpt] = [-p]
DeviceFolder::LoadDevice(Drivers\BuiltIn\autoras) last 59 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NdisPower\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'ndispwr.dll' (0x88D8AE1C) at address 0xC0810000-0xC0816000 in Process 'NK.EXE' (0x827C1C80)
DeviceFolder::LoadDevice(Drivers\BuiltIn\NdisPower) last 58 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Ethman\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'ethman.dll' (0x88D8F364) at address 0x40270000-0x40276000 in Process 'NK.EXE' (0x827C1C80)
OSAXST1: >>> Loading Module 'ethman.dll' (0x88D8F364) at address 0x40270000-0x40276000 in Process 'udevice.exe' (0x8EF02414)
OSAXST1: >>> Loading Module 'iphlpapi.dll' (0x88D8F49C) at address 0x40280000-0x40295000 in Process 'NK.EXE' (0x827C1C80)
OSAXST1: >>> Loading Module 'iphlpapi.dll' (0x88D8F49C) at address 0x40280000-0x40295000 in Process 'udevice.exe' (0x8EF02414)
OSAXST1: >>> Loading Module 'ws2.dll' (0x8EC71B70) at address 0x402A0000-0x402AF000 in Process 'udevice.exe' (0x8EF02414)
DeviceFolder::LoadDevice(Drivers\BuiltIn\Ethman) last 188 Ticks[NOTIFY] HandleSystemEvent 7 /ADD SHC2:
[NOTIFY] HandleSystemEvent 7 /ADD UFN1:
[NOTIFY] HandleSystemEvent 7 /ADD IPD0:
[NOTIFY] HandleSystemEvent 7 /ADD TCP0:
[NOTIFY] HandleSystemEvent 7 /ADD RDR0:
[NOTIFY] HandleSystemEvent 7 /ADD WSS1:
[NOTIFY] HandleSystemEvent 7 /ADD UIO1:
[NOTIFY] HandleSystemEvent 7 /ADD ARS1:
[NOTIFY] HandleSystemEvent 7 /ADD NPW1:
[NOTIFY] HaCDriverContext::OpenStream( OUT ) - format (1 2:16 44100 4 176400 flag=1)
FILESYS: SignalStarted loop = 2
FILESYS: Launching gwes.dll
OSAXST1: >>> Loading Module 'gwes.dll' (0x88D98900) at address 0xC0200000-0xC0336000 in Process 'NK.EXE' (0x827C1C80)
Filesys: Loaded gwes.dll
ndleSystemEvent 7 /ADD ETM1:
Ceddk!CalibrateStallCounter: Enter
Ceddk!CalibrateStallCounter: Stall counter loaded from registry(171)
System Default HKL value set to 00000409
Grow Gdi handle table from 0 to 64
LogFontFromRegistry(SYSTEM\GDI\SysFnt), lfHeight = -12OSAXST1: >>> Loading Module 'ddi_flat.dll' (0x88DB33C0) at address 0xC0B60000-0xC0BA5000 in Process 'NK.EXE' (0x827C1C80)
OEMSetMemoryAttributes: nRegNeeded = 6
OEMSetMemoryAttributes: Run out of MTRR registers
AllocSurface - Out of Memory 2
Couldn't allocate primary surface
Exception 'Access Violation' (14): Thread-Id=038d0002(pth=88d98b08), Proc-Id=00400002(pprc=827c1c80) 'NK.EXE', VM-active=00400002(pprc=827c1c80) 'NK.EXE'
PC=c0b6a60a(ddi_flat.dll+0x0000a60a) RA=c0b6e343(ddi_flat.dll+0x0000e343) SP=d0a8f304, BVA=0000001c
*** FAILED TO INITIALIZE DISPLAY DRIVER (ddi_flat.dll)! ***
*** MAKE SURE DISPLAY DRIVER CONFIGURATION SETTINGS ARE CORRECT! ***
Unknown: DEBUGCHK failed in file C:\ymzki\private\winceos\COREOS\gwe\mgdi\base\.\driver.cpp at line 118
  KdTrap: JIT debugging requested, waiting for OEM selection

  KdTrap: JIT debugging accepted

+KITLRegisterDfltClient, service:2
Exception 'Access Violation' (14): Thread-Id=038d0002(pth=88d98b08), Proc-Id=00400002(pprc=827c1c80) 'NK.EXE', VM-active=00400002(pprc=827c1c80) 'NK.EXE'
PC=80240530(kitl.dll+0x0000d530) RA=8023aea7(kitl.dll+0x00007ea7) SP=d0a8f238, BVA=00000010
Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1 time(s). This OK if KdStub stumbling on its own BP.
  KdTrap: Exception in debugger, Addr=0x80240530 -  attempting to recover

Eax=00000000 Ebx=d0a8f4b8 Ecx=827a6004 Edx=00000000
Esi=00000000 Edi=d0a8f584 Ebp=d0a8f248 Esp=d0a8f238 Eip=80240530
CS=0019 DS=0040 ES=0040 SS=0021 FS=c0110060 GS=d0a80000
URtlDispatchException: returning failure. Flags=0
KPSLExceptionHandler: flags=1 ControlPc=c0240cf3
Eax=80273a50 Ebx=88d98b08 Ecx=d0a8f000 Edx=80273a50
Esi=00000000 Edi=00000003 Ebp=00000000 Esp=d0a8f64c Eip=c0240cf3
CS=0019 DS=82150040 ES=802b0040 SS=0021 FS=ffff0060 GS=0000
URtlDispatchException: returning failure. Flags=1
NK Kernel: DEBUGCHK failed in file D:\yamafp-13\private\winceos\COREOS\nk\kernel\nknormal\..\exdsptch.c at line 333
Recursively calling KDEnableInt(FALSE, psvdThread != NULL) 1 time(s). This OK if KdStub stumbling on its own BP.
  KdTrap: Exception in debugger, Addr=0xC0240CF3 -  unable to recover


Unhandled exception c0000005:
Terminating thread 88d98b08
Secondary thread in proc 00400002 faulted, Exception code = c0000005, Exception Address = c0240cf3!
Terminating Thread 038d0002
CDisk::SetDiskPowerState> Power state (1) not supported
CDiskPower::SetDiskPower: SetDiskPowerState(D1) failed

87

TA的帖子

0

TA的资源

一粒金砂(初级)

Rank: 1

发表于 2009-10-20 14:29 | 显示全部楼层
ddi_flat.dll 所以是 display driver 的問題

Paul, Chao @ Techware

回复

使用道具 举报

123

TA的帖子

0

TA的资源

一粒金砂(初级)

Rank: 1

发表于 2009-10-20 15:46 | 显示全部楼层
Terminating Thread 038d0002 之后接着是
CDisk::SetDiskPowerState> Power state (1) not supported
CDiskPower::SetDiskPower: SetDiskPowerState(D1) failed
这又貌似是在DiskPower上停止的

回复

使用道具 举报

116

TA的帖子

0

TA的资源

一粒金砂(初级)

Rank: 1

发表于 2009-10-21 08:26 | 显示全部楼层
1. Device driver power state D0~D4. Windows CE 没要求 driver 必须要能全部支援.
http://msdn.microsoft.com/en-us/library/ms798296.aspx 内有一句话.

A physical device does not have to support all of the device power states. The only device power state that all devices must support is the full on state, D0. A driver that is issued a request to enter a power state not supported by its device enters the next available power state supported. For example, if Power Manager requests that it enter D2 and it does not support D2, the device can enter D3 or D4 instead. This can be done if Power Manager supports one of these states. If a device is requested to enter D3 and cannot wake up the system, it should enter D4 and power off, rather than staying in standby. These rules are intended to simplify driver implementation.

所以看起来是 Disk driver D1 没有支援. 但这应该无妨.

Paul, Chao @ Techware

回复

使用道具 举报

128

TA的帖子

0

TA的资源

一粒金砂(初级)

Rank: 1

发表于 2009-10-21 08:48 | 显示全部楼层
建议楼主定制一个微内核,然后逐个添加相应的组件,以确认到底是哪些驱动的问题。

回复

使用道具 举报

82

TA的帖子

0

TA的资源

一粒金砂(初级)

Rank: 1

发表于 2009-10-21 10:10 | 显示全部楼层
多谢,确实如你所说,应该是display driver的问题。原来以为可能是相应的显示驱动没加进去,现在加了还是报同样的错
*** FAILED TO INITIALIZE DISPLAY DRIVER (ddi_flat.dll)! ***
*** MAKE SURE DISPLAY DRIVER CONFIGURATION SETTINGS ARE CORRECT! ***

引用 3 楼 paul_chao 的回复:
1. Device driver power state D0~D4. Windows CE 没要求 driver 必须要能全部支援.
http://msdn.microsoft.com/en-us/library/ms798296.aspx 内有一句话.

A physical device does not have to support all of the device power states. The only device power state that all devices must support is the full on state, D0. A driver that is issued a request to enter a power state not supported by its device enters the next available power state supported. For example, if Power Manager requests that it enter D2 and it does not support D2, the device can enter D3 or D4 instead. This can be done if Power Manager supports one of these states. If a device is requested to enter D3 and cannot wake up the system, it should enter D4 and power off, rather than staying in standby. These rules are intended to simplify driver implementation.

所以看起来是 Disk driver D1 没有支援. 但这应该无妨.

Paul, Chao @ Techware

回复

使用道具 举报

106

TA的帖子

0

TA的资源

一粒金砂(初级)

Rank: 1

发表于 2009-11-4 14:54 | 显示全部楼层
NK有问题,有异常,一般从新SYSGEN,都可以解决吧,我几次都是这样弄的。

回复

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

关闭

站长推荐上一条 /5 下一条

  • 论坛活动 E手掌握

    扫码关注
    EEWORLD 官方微信

  • EE福利  唾手可得

    扫码关注
    EE福利 唾手可得

Archiver|手机版|小黑屋|电子工程世界 ( 京ICP证 060456 )

GMT+8, 2020-2-20 13:12 , Processed in 0.233432 second(s), 19 queries , Gzip On, MemCache On.

快速回复 返回顶部 返回列表