阅读:3449回复:9
OEMIoControl错误信息如何解决?
我的WINCE启动时输出如下信息,
OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45 OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 OEMIoControl: Unsupported Code 0x10100cc - device 0x0101 func 51 OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 请问这些信息是由于下面的IOCTL没有对应的处理函数引起的么?如何不处理这些函数是否会导致系统启动失败? IOCTL_HAL_POSTINIT IOCTL_HAL_GETREGSECUREKEYS IOCTL_EDBG_IS_STARTED IOCTL_HAL_GET_RANDOM_SEED IOCTL_EDBG_SEND IOCTL_HAL_GET_HWENTROPY |
|
沙发#
发布于:2008-07-31 21:15
不会
|
|
板凳#
发布于:2008-08-01 09:52
wenzai,你好,非常感谢你的回答,我自己改了wince5默认的smdk2410包,编译后运行,发现输出如下信息后便没有反应了
OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45 OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 OEMIoControl: Unsupported Code 0x10100cc - device 0x0101 func 51 OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 INFO: CReg2410Uart::CReg2410Uart using processor frequency reported by the OAL (50750000). 你能给点建议,我下面应该检查那些地方可能出错了?再次感谢你的热心。 |
|
地板#
发布于:2008-08-01 12:19
你是在Debug模式吗?
编译个debug的,会有更多的信息让你知道问题在哪里 |
|
地下室#
发布于:2008-08-01 13:37
您好,我定制的release版本的内核里面也有很多OEMIoControl: Unsupported Code....等代码,但是系统运行倒没有发现异常,不知道您的问题解决没,能否指点下,谢谢
|
|
5楼#
发布于:2008-08-01 14:41
不会, 而且下面这个信息,
INFO: CReg2410Uart::CReg2410Uart using processor frequency reported by the OAL (50750000). 说明内核已经起来了, 已经在加载驱动了. 调试口和uart不要 复用. 试试把调试口占的uart的驱动不加载. |
|
6楼#
发布于:2008-08-03 15:59
引用第3楼wenzai于2008-08-01 12:19发表的 : 我又重新编译了DEBUG版本的程序,下载后输出如下信息,请帮我看看那里有问题,谢谢了。或者下一步该做哪些工作,谢谢wenzi 和 high的指点。 Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:21:58 ProcessorType=0920 Revision=0 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8c23fff8 DCache: 8 sets, 64 ways, 32 line size, 16384 size ICache: 8 sets, 64 ways, 32 line size, 16384 size SDMMC config current GPGCON: ff85fdba SDMMC config set GPGCON: ffa5fdba SDMMC config Init Done. Error Reporting Memory Reserved, dump size = 00020000 Booting Windows CE version 5.00 for (ARM) &pTOC = 8c209c1c, pTOC = 8eb51fac, pTOC->ulRamFree = 8f281000, MemForPT = 00000000 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 3421, Secondary pages: 0, Filesystem pages = 1710 Booting kernel with clean memory configuration: Memory Sections: [0] : start: 8f282000, extension: 00001000, length: 00d5d000 Sp=ffffc7cc ARMInit done. Windows CE KernelInit Updated eptr->e32_vsize to = 000de000 Scheduling the first thread. 0x8ffdf024: KernelInit2: pCurThread=8ffdf024 hCurThread=0ffdf266 hCurProc=0ffdf002, KernelInit = 8c24e118 0x8ffdf024: Detecting VFP...0x8ffdf024: VFP Not Found! 0x8ffdf024: Updated eptr->e32_vsize to = 00006000 0x8ffdf024: Updated eptr->e32_vsize to = 00029000 0x8ffdf024: Updated eptr->e32_vsize to = 00009000 0x8ffdf024: Updated eptr->e32_vsize to = 00022000 0x8ffdf024: ERROR: c:\macallan\private\winceos\coreos\nk\kernel\kwin32.c line 777: 0x8ffdf024: ConnectDebugger failed 0x8ffdf024: first = 011f0000, last = 02000000, SharedDllBase = 02110000 0x8ffc88c8: CertMod.dll not found, using old OEM Trust Model 0x8ffc88c8: FileSystem Starting - starting with clean file system 0x8ffc88c8: FS: initializing ROM/RAM file system 0x8ffc88c8: SC_CreateAPIHandle: pvData == NULL 0x8ffc88c8: FS: Registering file system ROM, index 2, flags 0x00000031 0x8ffc88c8: FS: Mount complete (ROM, index 2, flags 0x00000031) 0x8ffc88c8: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 0x8ffc88c8: Succeeded on CheckFile 0x8ffc88c8: RestoreFile(0x6ffb164a) called fDelete = TRUE 0x8ffc88c8: FS: Registering file system StoreMgr, index 3, flags 0x00000001 0x8ffc88c8: InitSharedHeap: 44000000 10000 c 0x8ffc88c8: InitSharedHeap: return 44000060 0x8ffc88c8: OEMIoControl: Unsupported Code 0x10100cc - device 0x0101 func 51 0x8ffc88c8: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 0x8ffc88c8: FSREG: Logging in default user. 0x8ffc88c8: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 0x8ffc88c8: SetCurrentUser: Logging out (nobody), logging in default 0x8ffc88c8: FS: Using default path "\profiles\" 0x8ffc88c8: BuildPath: profiles 0x8ffc88c8: BuildPath: profiles\default 0x8ffc88c8: SetCurrentUser: User hives not supported -- using same registry for all users 0x8ffc88c8: FS: Using default path "Windows\" 0x8ffc88c8: OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 0x8ffc88c8: OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 0x8ffcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9 0x8ffc88c8: FS: Using default path "Windows\" 0x8ffc88c8: FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars 0x8ffc88c8: Initializing Database 0x8ffc88c8: DB:Validation: Name already exists DB_notify_events 0x8ffc88c8: DB:CeCreateDatabase failed 0x8ffc88c8: Filesystem initialized! 0x8ffc88c8: FILESYS: Waiting for kernel to be ready to launch apps 0x8ffc8400: InitMUI: DISABLED (-1039860968) 0x8ffc88c8: FS: Creating signal event SYSTEM/DevMgrApiSetReady 0x8ffc88c8: FS: Creating signal event SYSTEM/PowerManagerReady 0x8ffc88c8: FS: Creating signal event SYSTEM/GweApiSetReady 0x8ffc88c8: FS: Creating signal event ReleaseFSD 0x8ffc88c8: FS: Creating signal event system/events/notify/APIReady 0x8ffc88c8: FS: Creating signal event SYSTEM/ShellAPIReady 0x8ffc88c8: FS: Creating signal event SYSTEM/BatteryAPIsReady 0x8ffc88c8: FS: Creating signal event SYSTEM/NLedAPIsReady 0x8ffc88c8: FILESYS: Launching apps 0x8ffc88c8: FILESYS: Launching shell.exe 0x8ff9b774: InitSharedHeap: 44000000 0 c 0x8ff9b774: InitSharedHeap: return 44000060 0x8ffc88c8: FILESYS: Launching device.exe 0x8ffa6c50: InitSharedHeap: 44000000 0 c 0x8ffa6c50: InitSharedHeap: return 44000060 0x8ffa6c50: *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x8ff9bea2 *** 0x8ffa6c50: +InitDeviceFileSystems 0x8ffa6c50: FS: Registering file system $device, index 4, flags 0x00000001 0x8ffa6c50: FS: Registering file system $bus, index 5, flags 0x00000001 0x8ffa6c50: -InitDeviceFileSystems: status is 1 0x8ffa6c50: Ceddk!CalibrateStallCounter: Enter 0x8ffa6c50: Ceddk!CalibrateStallCounter: Could not find stall counter 0x8ffa6c50: Ceddk!BeginCalibration: min(25376) max(28195) 0x8ffa6c50: Ceddk!BeginCalibration: Calibration timed out (51 tries). Defaulting to 1 ms resolution. 0x8ffc88c8: FILESYS: SignalStarted loop = 2 0x8ffa6c50: DEVICE!DevloadInit 0x8ffa6c50: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 0x8ffa6c50: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2 0x8ffa6c50: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2 0x8ffa6c50: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Battery\BusPrefix) returned 2 0x8ffa6c50: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NLed\BusPrefix) returned 2 0x8ffa6c50: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Serial\BusPrefix) returned 2 0x8ffa6c50: HalTranslateBusAddress: 0 0 0000000056000000 0 --> 0000000056000000 1 0x8ffa6c50: HalTranslateBusAddress: 0 0 0000000050000000 0 --> 0000000050000000 1 0x8ffa6c50: HalTranslateBusAddress: 0 0 000000004a000000 0 --> 000000004a000000 1 0x8ffa6c50: INFO: CReg2410Uart::CReg2410Uart using processor frequency reported by the OAL (50750000). |
|
7楼#
发布于:2008-08-03 16:02
引用第4楼wangxuesi于2008-08-01 13:37发表的 : 出现这个是对应的IOCTRL命令没有对应的处理函数,添加对应处理函数就可以,不过具体函数怎么实现还不知道,估计要看WINCE帮助。 |
|
8楼#
发布于:2008-08-03 18:37
试试 high 的说法
你的调试串口可能冲突了 |
|
9楼#
发布于:2008-08-04 12:58
请问HIGH,按您说的我现在内核已经启动,那么我下面需要做哪些工作,就是完成必须的驱动就可以了?比如LCD,触摸屏和串口么?
|
|