从KITL 启动debug信息看wince6.0启动流程

最新推荐文章于 2017-02-18 14:57:20 发布
最新推荐文章于 2017-02-18 14:57:20 发布
阅读量3.8k 收藏
点赞数
分类专栏： Wince Kernel 文章标签： wince module signal system logging notifications
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/gooogleman/article/details/4247585
版权

(CoreCon) Download service map set to NONE; ignoring download request!
PB Debugger The Kernel Debugger is waiting to connect with target.
4294767296 PID:0 TID:2 Error Reporting Memory Reserved, dump size = 00020000
4294767296 PID:0 TID:2 Setting up softlog at 0x836cc000 for 0x800 entries
4294767296 PID:0 TID:2 Booting Windows CE version 6.00 for (ARM)
4294767296 PID:0 TID:2 &pTOC = 80ecac1c, pTOC = 806b10d4, pTOC->ulRamFree = 80ecf000, MemForPT = 00001000
4294767296 PID:0 TID:2
Old or invalid version stamp in kernel structures - starting clean!
4294767296 PID:0 TID:2 Configuring: Primary pages: 10230, Secondary pages: 0, Filesystem pages = 5115
4294767296 PID:0 TID:2
Booting kernel with clean memory configuration:
4294767296 PID:0 TID:2 Memory Sections:
4294767296 PID:0 TID:2 [0] : start: 80ed1000, extension: 00005000, length: 027f6000
4294767296 PID:0 TID:2 NKStartup done, starting up kernel.
4294767297 PID:0 TID:2 Windows CE KernelInit
4294767305 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first = c0010000, last = c08b0000
4294767308 PID:400002 TID:2 g_pprcNK == 0x80ec8aa0
4294767309 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00036000
4294767311 PID:400002 TID:410002 Initializing Memory Mapped File Support
4294767313 PID:400002 TID:410002 Scheduling the first thread.
4294767314 PID:400002 TID:410002 Detecting VFP...
4294767315 PID:400002 TID:410002  VFP Not Found!
4294767316 PID:400002 TID:410002 LoaderInit: Initialing loader
4294767317 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00036000
4294767320 PID:400002 TID:410002 Updated eptr->e32_vsize to = 000a2000
4294767323 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0001a000
4294767361 PID:400002 TID:410002 PGPOOL: Reserved 768 pages for Loader pool
4294767365 PID:400002 TID:410002 PGPOOL: Reserved 256 pages for File pool
4294767380 PID:400002 TID:410002 OSAXST0: Platform Name = PLATFORM_TYPE
4294767400 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'kd.dll' (0x836AC87C) at address 0xC0010000-0xC0045000 in Process 'NK.EXE' (0x80EC8AA0)
4294767404 PID:400002 TID:410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 22
4294767409 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x80EC8AA0) at address 0x80200000-0x80236000 in Process 'NK.EXE' (0x80EC8AA0)
PB Debugger Kernel debugger connected.
PB Debugger The Kernel Debugger connection has been established (Target CPU is ARM).
PB Debugger Target name: CE Device
PB Debugger Probe name: KdStub
PB Debugger Binary Image should be loaded at 0x80200000 / Data relocated at 0x80e86000
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/NK.EXE'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/COREDLL.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/KITL.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/KERNEL.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/OALIOCTL.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/HD.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/OSAXST0.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/OSAXST1.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/K.COREDLL.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/KD.DLL'
4294767417 PID:400002 TID:410002 HD: Immediate debugger module load notifications ACTIVE (slower boot - non real-time).
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/FILESYS.DLL'
4294767460 PID:400002 TID:410002 Message Queue support initialized, g_hMsgQHeap = d00a0010
4294767482 PID:400002 TID:630002 OSAXST1: >>> Loading Module 'filesys.dll' (0x836824C8) at address 0xC01B0000-0xC0249000 in Process 'NK.EXE' (0x80EC8AA0)
4294767489 PID:400002 TID:630002 OSAXST1: >>> Loading Module 'k.fpcrt.dll' (0x83682600) at address 0xC0190000-0xC01A8000 in Process 'NK.EXE' (0x80EC8AA0)
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/K.FPCRT.DLL'
4294767503 PID:400002 TID:630002 OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x83682748) at address 0xC0520000-0xC0566000 in Process 'NK.EXE' (0x80EC8AA0)
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/FSDMGR.DLL'
4294767505 PID:400002 TID:630002 FSDMGR!DllMain: DLL_PROCESS_ATTACH
4294767507 PID:400002 TID:680002 CertMod.dll not found, using old OEM Trust Model
4294767521 PID:400002 TID:680002 FileSystem Starting - starting with clean file system
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/ROMFSD.DLL'
4294767526 PID:400002 TID:680002 FSDMGR!STOREMGR_Initialize
4294767529 PID:400002 TID:680002 FSDMGR!InitializeStoreAPI
4294767529 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at index 2
4294767530 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 2 (Name="StoreMgr", MountFlags=0x1)
4294767532 PID:400002 TID:680002 FSDMGR!InitializeROMFileSystem: File System=ROM
4294767540 PID:400002 TID:680002 OSAXST1: >>> Loading Module 'romfsd.dll' (0x8366C9F0) at address 0xC0250000-0xC0257000 in Process 'NK.EXE' (0x80EC8AA0)
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/RELFSD.DLL'
4294767543 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index 3
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/SHELL.EXE'
4294767544 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3 (Name="ROM", MountFlags=0x71)
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/TOOLHELP.DLL'
4294767555 PID:400002 TID:680002 FSVOL: Opening existing volume
4294767560 PID:400002 TID:680002 FSVOL: Volume heap already initialized
4294767560 PID:400002 TID:680002 FSREG: Mounted ROM portion of boot registry
4294767561 PID:400002 TID:680002 FSVOL: Creating clean virtual volume
4294767567 PID:400002 TID:680002 FSVOL: Initializing volume heap
4294767603 PID:400002 TID:680002 FSREG: Mounted RAM portion of boot registry
4294767622 PID:400002 TID:680002 FS: Creating signal event SYSTEM/DevMgrApiSetReady
4294767622 PID:400002 TID:680002 FS: Creating signal event SYSTEM/PowerManagerReady
4294767622 PID:400002 TID:680002 FS: Creating signal event SYSTEM/GweApiSetReady
4294767625 PID:400002 TID:680002 FS: Creating signal event ReleaseFSD
4294767628 PID:400002 TID:680002 FSREG: Unable to read value "Start DevMgr" under HKEY_LOCAL_MACHINE/init/BootVars
4294767628 PID:400002 TID:680002 FILESYS: Starting boot phase 0.
4294767631 PID:400002 TID:680002 FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1)
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/DEVICE.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/DEVMGR.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/K.CEDDK.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/PM.DLL'
4294767633 PID:400002 TID:680002 FSDMGR: File security disabled.
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/BUSENUM.DLL'
4294767634 PID:400002 TID:680002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/NDIS.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/CXPORT.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/AFD.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/UDEVICE.EXE'
4294767638 PID:400002 TID:680002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System/StorageManager/AutoLoad, FileSystem_t=ObjectStore
4294767644 PID:400002 TID:680002 FILESYS: RAM File System FSD_MountDisk registering folder "Object Store"
4294767644 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolumeName: Registered "Object Store" at index 4
4294767644 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4 (Name="", MountFlags=0x46)
4294767651 PID:400002 TID:680002 FILESYS: Starting boot phase 1.
4294767652 PID:400002 TID:680002 FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0)
4294767653 PID:400002 TID:680002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1
4294767657 PID:400002 TID:680002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=1, RootKey=System/StorageManager/AutoLoad, FileSystem_t=Relfsd
4294767670 PID:400002 TID:680002 OSAXST1: >>> Loading Module 'relfsd.dll' (0x8364692C) at address 0xC04F0000-0xC04FF000 in Process 'NK.EXE' (0x80EC8AA0)
4294767677 PID:400002 TID:9f0002 FSDMGR!PNPThread: Using PNPUnloadDelay of 4096
4294767679 PID:400002 TID:9f0002 FSDMGR!PNPThread: PNPThread starting!
4294767681 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolumeName: Registered "Release" at index 5
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/TCPSTK.DLL'
4294767681 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 5 (Name="Release", MountFlags=0x0)
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/DHCP.DLL'
4294767684 PID:400002 TID:680002 Mounted ReleaseFSD volume '/Release'
4294767774 PID:400002 TID:680002 size of 'dbglist.txt' = 00000010
4294767898 PID:400002 TID:680002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=1, RootKey=System/StorageManager/AutoLoad, FileSystem_t=SMFLASH
4294767898 PID:400002 TID:680002 FSDMGR!AutoLoadBlockDevice: Auto-loading block driver from "Drivers/BuiltIn/SMFLASH"
4294767900 PID:400002 TID:680002 FSDMGR!MountStore: Attaching new storage device "SMFLASH"
4294767906 PID:400002 TID:680002 FSDMGR!MountStore: Failed mounting store "SMFLASH"; error=126
4294767906 PID:400002 TID:680002 FSDMGR!StoreDisk_t::~StoreDisk_t: deleting store (D0045F50)
4294767907 PID:400002 TID:680002 FSDMGR!AutoLoadFileSystems: Unable to auto-load HKLM/System/StorageManager/AutoLoad/SMFLASH; error=126
4294767910 PID:400002 TID:680002 FILESYS: Waiting for bootable file system to be mounted.
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/NOTIFY.DLL'
4294767914 PID:400002 TID:680002 FILESYS: Device started.  Boot file system ready.
4294767914 PID:400002 TID:680002 FSREG: Unable to read value "SystemHiveInitialSize" under HKEY_LOCAL_MACHINE/init/BootVars
4294767922 PID:400002 TID:680002 FSVOL: Opening existing volume
4294767927 PID:400002 TID:680002 FSVOL: Volume heap already initialized
4294767927 PID:400002 TID:680002 FSREG: Mounted ROM portion of system hive
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/NETBIOS.DLL'
4294767928 PID:400002 TID:680002 FILESYS: Loading system hive from /Documents and Settings/system.hv.
4294767932 PID:400002 TID:680002 FSREG: Mounting clean system hive
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/WS2INSTL.DLL'
4294767932 PID:400002 TID:680002 BuildPath: Documents and Settings
4294767935 PID:400002 TID:680002 FSVOL: Creating new volume (size=28672 bytes)
4294767946 PID:400002 TID:680002 FSVOL: Initializing volume heap
4294768016 PID:400002 TID:680002 FSREG: Taking down boot registry.  Any open keys will be invalid.
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/UDEVICE.EXE'
4294768106 PID:400002 TID:680002 FILESYS: Registry in place.
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/WS2SERV.DLL'
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/WS2.DLL'
4294768107 PID:400002 TID:680002 FSREG: Unable to read value "RegistryFlags" under HKEY_LOCAL_MACHINE/init/BootVars
4294768164 PID:400002 TID:680002 FSVOL: Using system database volume "/Documents and Settings/default.vol"
4294768164 PID:400002 TID:680002 BuildPath: Documents and Settings
4294768168 PID:400002 TID:680002 FSVOL: Creating new volume (size=28672 bytes)
4294768178 PID:400002 TID:680002 FSVOL: Initializing volume heap
4294768227 PID:400002 TID:680002 FSREG: Unable to read value "RequireCertMod" under HKEY_LOCAL_MACHINE/init/BootVars
4294768228 PID:400002 TID:680002 FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE/init/BootVars
4294768228 PID:400002 TID:680002 FSREG: Logging in default user.
4294768231 PID:400002 TID:680002 FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE/init/BootVars
4294768233 PID:400002 TID:680002 SetCurrentUser: Logging out (nobody), logging in default
4294768234 PID:400002 TID:680002 BuildPath: Documents and Settings
4294768236 PID:400002 TID:680002 BuildPath: Documents and Settings/default
4294768239 PID:400002 TID:680002 FSREG: Mounting ROM portion of user hive
4294768244 PID:400002 TID:680002 FSVOL: Opening existing volume
4294768249 PID:400002 TID:680002 FSVOL: Volume heap already initialized
4294768250 PID:400002 TID:680002 Mounting user hive from /Documents and Settings/default/user.hv
4294768253 PID:400002 TID:680002 FSREG: Mounting clean user hive
4294768254 PID:400002 TID:680002 FSVOL: Creating new volume (size=28672 bytes)
4294768265 PID:400002 TID:680002 FSVOL: Initializing volume heap
4294768390 PID:400002 TID:680002 FSREG: Unable to read value "RegistryFlags" under HKEY_LOCAL_MACHINE/init/BootVars
4294768390 PID:400002 TID:680002 FSDMGR!STOREMGR_StartBootPhase BootPhase=2 (PrevBootPhase=1)
4294768391 PID:400002 TID:680002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=2, LoadFlags=1
4294768403 PID:400002 TID:9f0002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=2, LoadFlags=2
4294768409 PID:400002 TID:680002
Initializing Database
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/GWES.DLL'
4294768423 PID:400002 TID:680002 DB:Validation: Name already exists DB_notify_events
4294768423 PID:400002 TID:680002 DB:CeCreateDatabase failed
PB Debugger Loaded symbols for 'H:/WINCE600/OSDESIGNS/TRY2440CE6/TRY2440CE6/RELDIR/QXCE6BSP_ARMV4I_DEBUG/S3C2440DISP.DLL'
4294768428 PID:400002 TID:680002 Filesystem initialized!
4294768432 PID:400002 TID:680002 FILESYS: Waiting for kernel to be ready to launch apps
4294768441 PID:400002 TID:630002 InitMUI: Langs=409 0 0 0 0 0
4294768447 PID:400002 TID:680002 FS: Creating signal event SYSTEM/DevMgrApiSetReady
4294768447 PID:400002 TID:680002 FS: Creating signal event SYSTEM/PowerManagerReady
4294768447 PID:400002 TID:680002 FS: Creating signal event SYSTEM/GweApiSetReady
4294768450 PID:400002 TID:680002 FS: Creating signal event ReleaseFSD
4294768452 PID:400002 TID:680002 FS: Creating signal event system/events/notify/APIReady
4294768454 PID:400002 TID:680002 FS: Creating signal event SYSTEM/ShellAPIReady
4294768454 PID:400002 TID:680002 FILESYS: Launching apps
4294768456 PID:400002 TID:680002 FILESYS: Launching shell.exe
4294768464 PID:e90002 TID:ea0002 OSAXST1: >>> Loading Module 'coredll.dll' (0x836CA6CC) at address 0x40010000-0x400DB000 in Process 'shell.exe' (0x83686E94)
4294768465 PID:e90002 TID:ea0002 OSAXST1: >>> Loading Module 'shell.exe' (0x83686E94) at address 0x00010000-0x00026000 in Process 'shell.exe' (0x83686E94)
4294769178 PID:400002 TID:ea0002 OSAXST1: >>> Loading Module 'toolhelp.dll' (0x83610B70) at address 0x40130000-0x40136000 in Process 'NK.EXE' (0x80EC8AA0)
4294769180 PID:e90002 TID:ea0002 OSAXST1: >>> Loading Module 'toolhelp.dll' (0x83610B70) at address 0x40130000-0x40136000 in Process 'shell.exe' (0x83686E94)
4294769733 PID:400002 TID:680002 FILESYS: SignalStarted loop = 1
4294769734 PID:400002 TID:680002 FILESYS: Launching device.dll
4294769742 PID:400002 TID:680002 OSAXST1: >>> Loading Module 'device.dll' (0x83610D8C) at address 0xC0450000-0xC0455000 in Process 'NK.EXE' (0x80EC8AA0)
4294769755 PID:400002 TID:680002 OSAXST1: >>> Loading Module 'devmgr.dll' (0x83610EC4) at address 0xC0460000-0xC0487000 in Process 'NK.EXE' (0x80EC8AA0)
4294769759 PID:400002 TID:680002 OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x822EE000) at address 0xC0570000-0xC057E000 in Process 'NK.EXE' (0x80EC8AA0)
4294769775 PID:400002 TID:680002 OSAXST1: >>> Loading Module 'pm.dll' (0x822EE148) at address 0xC04B0000-0xC04D7000 in Process 'NK.EXE' (0x80EC8AA0)
4294771406 PID:400002 TID:680002 *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
4294771408 PID:400002 TID:680002 Filesys: Loaded device.dll
4294771419 PID:400002 TID:1000002 +InitDeviceFileSystems
4294771420 PID:400002 TID:1000002 FSDMGR!MountTable_t::RegisterVolumeName: Registered "$device" at index 6
4294771420 PID:400002 TID:1000002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 6 (Name="$device", MountFlags=0x1)
4294771423 PID:400002 TID:1000002 FSDMGR!MountTable_t::RegisterVolumeName: Registered "$bus" at index 7
4294771425 PID:400002 TID:1000002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 7 (Name="$bus", MountFlags=0x1)
4294771426 PID:400002 TID:1000002 -InitDeviceFileSystems: status is 1
4294771429 PID:400002 TID:1000002 Ceddk!CalibrateStallCounter: Enter
4294771432 PID:400002 TID:1000002 Ceddk!CalibrateStallCounter: Could not find stall counter
4294771432 PID:400002 TID:1000002 Ceddk!BeginCalibration: min(171) max(189)
4294771512 PID:400002 TID:1000002 Ceddk!BeginCalibration: Elapsed is 183
4294771512 PID:400002 TID:1000002 Ceddk!BeginCalibration: Delay is 22
4294771558 PID:400002 TID:1000002 DEVICE!DevloadInit
4294771559 PID:400002 TID:1000002 DEVICE!InitDevices: Root Key is Drivers/BuiltIn.
4294771559 PID:400002 TID:1000002 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers/BuiltIn/Prefix) returned 2
4294771560 PID:400002 TID:1000002 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers/BuiltIn/BusPrefix) returned 2
4294771578 PID:400002 TID:1000002 OSAXST1: >>> Loading Module 'busenum.dll' (0x822F9630) at address 0xC04A0000-0xC04AB000 in Process 'NK.EXE' (0x80EC8AA0)
4294772478 PID:400002 TID:1000002 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers/BuiltIn/SMFLASH/BusPrefix) returned 2

 

————后面就是加载流驱动了。上面很明了了，就不再解释。

由于有更重要的事情做，所以以后详细看代码后再做解释。

gooogleman
关注
专栏目录
S3C6410 SD Card一键烧写 WINCE 6.0
clay_xiaoyu的博客
12-27 3241
S3C6410 SD Card一键烧写 WINCE 6.0 下载地址：S3C 6410 烧写工具及 SD Card 启动镜像 提取码：i2z1 下载地址：S3C6410 WINCE 6.0 系统镜像文件 提取码：r0cd PC 上打开 DNW 软件 PC 上右键 此电脑 设备管理器–>> 端口（COM 和 LP） 烧写时所需要的镜像文件及说明 编号 镜像文件 说明 1 STEPLDR.nb0 Steplooder 上电时最先加载，用于引导 Eboot 2 STEPLDR
wince 6.0 bspWinCE下，快速编译驱动及BSP
12-17
在Windows CE 6.0操作系统中，开发和编译驱动程序以及板级支持包(BSP)是一项关键任务，尤其对于嵌入式系统开发者而言。以下是一些关于如何快速编译驱动和BSP的重要知识点： 1. **驱动程序编译**： 当驱动程序的源...
WinCE6.0 KITL概要
龙图腾的博客
12-02 578
KITL（Kernel Independent Transport Layer）即内核独立传输层，它为我们提供了一种调试WinCE的简便方法。KITL将通信服务协议和用于通信的硬件分离开来。所以我们在创建硬件传输层时就省去很多麻烦，否则我们自己必须实现与设备进行数据交互的协议。KITL工作在硬件传输层之上，因此，它无须关心用于通信的具体硬件，我们可以用USB、Serial或者Ethernet作为K
wince 6.0 启动过程
无语僧
02-18 530
以S3C6410为例子,S3C6410的内部SRAM地址为0x0C00 0000 ~ 0x0C00 1FFF,DRAM的Base地址为0x50000000 ,S3C6410支持NAND,SD启动,S3C6410里面有固化的ROM, 当系统上电的时候,将执行固化ROM中的代码,然后检查硬件的GPIO配置,如果配置成NAND 启动,则把NAND的前8K读入内部的SRAM(stepping Stone)
wince6.0启动
金家兴无
12-24 930
以S3C6410为例子,S3C6410的内部SRAM地址为0x0C00 0000 ~ 0x0C00 1FFF,DRAM的Base地址为0x50000000 ,S3C6410支持NAND,SD启动,S3C6410里面有固化的ROM, 当系统上电的时候,将执行固化ROM中的代码,然后检查硬件的GPIO配置,如果配置成NAND 启动,则把NAND的前8K读入内部的SRAM(stepping Stone)...
MIPS wince6.0系统的启动过程
jack1003的专栏
01-06 1206
    总体函数调用的过程步骤，其实与其他ARM等等CPU调用的函数过程都是一样的，只是在代码组织结构上有所不同的，至于ARM资料在网络上很多，在这里我就说说MIPS的系统启动过程，及其每个函数所处的文件和目录位置。  1、  StartUp函数，这是系统启动的第一个函数，这个函数都是BSP实现的，一般都是放在$(_PLATFORMROOT)/BSP的目录/src/oal/StartU
使用U盘制作WinCE6.0的启动盘研究.doc
04-16
总的来说，制作WinCE6.0的U盘启动盘是一个涉及硬件兼容性、驱动程序集成以及系统配置的过程。每个步骤都需要细心操作，并根据遇到的具体问题进行针对性的调整和优化。通过不断的学习和实践，可以逐步克服这些挑战，...
Windows CE6.0启动过程分析
zhengkai_dong的专栏
12-01 277
在Windows CE 6.0中，内核（Kenerl）和OEM代码被分成oal.exe、kernel.dll和kitl.dll三个部分，其中启动代码（startup）和 OAL层的实现部分不再与内核链接生成NK.exe，取而代之的是启动代码（startup）和硬件相关且独立于内核的OAL层的实现部分编译成 oal.exe，而与内核相关且独立于硬件的OAL层代码包含在kernel.dll
kitl
chenyt2007的专栏
09-17 645
KITL(Kernel Independent Transport Layer)是基于Windows CE平台的一种软件技术，开发商基于它可以很容易地支持各种调试功能。因为Windows CE的调试是一种远程调试，所以开发工作站（运行PB的机器）和设备端必须要有相应的通信通道，不同的硬件平台会有不同的通信硬件，这样会增加开发的难度。KITL的目的就是将硬件层和通信协议层分开，开发商只要根据相应的A
WinCE 6.0 KITL 不能使用DM900 网卡驱动修改记录
emowuyi
12-31 138
修改理由： 由于eboot 和KITL 同时调用 DM9000DBG_Init 这个函数，在eboot 掉用时使用的是没有经过映射的地址，当镜像加载完成后，时候的是映射过的地址。 而DM9000DBG_Init 任然时候的是没有经过映射的地址。这样做导致的直接后果是，KITL起来当访问没有这段地址（0x15000000）的时候立马死机。 但是有引出了另外的一个问题，就是这样修改在启动eboot...
WinCE6.0 KITL调试
JXES智能生态系统
08-14 3393
最近，经常需要再KITL下做一些驱动方面的调试，有时候过很久没碰这东西，还真会碰到些稀奇古怪的问题让你捣鼓很久，所以一一做个记录整理，同时，也方便同行查阅，如有写得不对的地方，欢迎指点修正。 其实，介绍KITL的文章很多，不凡大师的文章，下面就贴几个： http://www.cnblogs.com/we-hjb/archive/2008/10/14/1311286.html http://w
WINCE的KITL调试环境
weixin_30679823的博客
05-09 75
目录 前言 适用范围 思路 代码编辑 Platform Builder的配置 调试示例 参考资料 前言 我开发WinCE应用程序时，喜欢设置断点来调试，单步调试时很容易定位问题；开发WinCE驱动时，则是通过从串口输出信息来调试，其实我是想像开发应用程序一样设置断点来调试的，但是公司的BSP包一直不支持，公司里...
USB_KITL(Wince50)使用方法(转)
josh915的专栏
05-27 806
1  platform/SMDK2440A/SMDK2440.bat里修改：   set BSP_KITL=NONE  改成 rem set BSP_KITL=NONE   rem set BSP_KITL=USBSERIAL  改成 set BSP_KITL=USBSERIAL   set BSP_NOUSBFN=  改成 set BSP_NOUSBFN=1   set BSP_
WINCE启动流程
lgb571的专栏
12-30 2394
WINCE实际上是由一些运行中的进程组成的，当系统启动时，至少会创建以下4个进程：1> NK.exe：提供内核服务，是操作系统核心部分。2> GWES.exe：提供用户界面服务和消息管理机制。3> Device.exe：加载和维护系统设备驱动程序。4> Filesys.exe：加载和管理文件系统。由于运行WINCE的硬件平台较
使用2440 5.0BSP KITL功能遇到的问题
gooogleman#foxmail.com
11-27 2876
作者：wogoyixikexie@gliet 2008-11-27//=================================================================== ================如下是Attache device之后在PB的窗口出现的加载信息从信息看来，驱动已经加载成功了，但是就是不能单步，现在不知道哪里出现了问题
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值