Re: DEBUG Image does not boot (CE5.0)

Generally there are a few issues that always occur when we start to build
debug images. So, check the following

#1. If you are downloading NK.NB0 file directly, a image size increase can
make you have multiple pieces, depending on the size setting in your
CONFIG.BIB.

#2. The image size will be much larger for storage and memory. Make sure you
have room available. Are you executing the NK image in flash or RAM? Did you
make sure the BIB setting allow for the larger image?

....clint....





"Peter K." <PeterK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4EF5D199-C777-4702-A307-B304A09F9671@xxxxxxxxxxxxxxxx
>I am working on an Intel 855 Wince 5.0 product. I have configured the
> HIVE-BASED Registry and it works fine in my release build. If I create a
> debug build my image stops with the message "FILESYS: Starting device and
> waiting for boot file system."
>
> I am not sure why it is working perfect in release build.
>
> My system:
>
> X86, Compact Flash (IDE), Hive-Bases Registry, Mount as Rom, Mount as
> Root,
> ROM-ONLY Filesystem, Windows CE 5.0
>
> This is my debug output:
>
> Booting kernel with clean memory configuration:
> Memory Sections:
> [0] : start: 83385000, extension: 0001d000, length: 1c25e000
> X86Init done, OEMAddressTable = 8023e298.
> Windows CE KernelInit
> Updated eptr->e32_vsize to = 0008d000
> Scheduling the first thread.
> 0x9f5ff030: KernelInit2: pCurThread=9f5ff030 hCurThread=1f5ff1de
> hCurProc=1f5ff002, KernelInit = 802613b0
> 0x9f5ff030: Updated eptr->e32_vsize to = 00005000
> 0x9f5ff030: Updated eptr->e32_vsize to = 00022000
> 0x9f5ff030: Updated eptr->e32_vsize to = 00007000
> 0x9f5ff030: Updated eptr->e32_vsize to = 00018000
> 0x9f5ff030: Starting kernel debugger software probe (KdStub) - KD API
> version 18
> 0x9f5ff030: Calling KDEnableInt (FALSE, NULL) without previously calling
> KDEnableInt (FALSE, p)
> 0x9f5ff030: >>> Loading module NK.EXE at address 0x80220000-0x802AD000 (RW
> data at 0x83310000-0x83361A9F)
> 0x9f5ff030: first = 00d20000, last = 02000000, SharedDllBase = 021a0000
> 0x9f5ff030: >>> Loading module coredll.dll at address
> 0x03F40000-0x03FF4000
> (RW data at 0x01FFE000-0x01FFF765)
> 0x9f5ff030: Did not find emulation code for x86... using floating point
> hardware.
> 0x9f5ed9dc: >>> Loading module coredll.dll at address
> 0x03F40000-0x03FF4000
> (RW data at 0x01FFE000-0x01FFF765)
> 0x9f5ed9dc: >>> Loading module filesys.exe at address
> 0x04010000-0x04070000
> 0x9f5ed9dc: CertMod.dll not found, using old OEM Trust Model
> 0x9f5ed9dc: FileSystem Starting - starting with clean file system
> 0x9f5ed9dc: FS: initializing ROM-only file system
> 0x9f5ed9dc: SC_CreateAPIHandle: pvData == NULL
> 0x9f5ed9dc: FS: Registering file system ROM, index 3, flags 0x00000031
> 0x9f5ed9dc: FS: Mount complete (ROM, index 3, flags 0x00000031)
> 0x9f5ed9dc: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func
> 35
> 0x9f5ed9dc: FSVOL: Opening existing volume
> 0x9f5ed9dc: FSVOL: Volume heap already initialized
> 0x9f5ed9dc: FSREG: Mounted ROM portion of boot registry
> 0x9f5ed9dc: FSVOL: Creating clean virtual volume
> 0x9f5ed9dc: FSVOL: Initializing volume heap
> 0x9f5ed9dc: FSREG: Mounted RAM portion of boot registry
> 0x9f5ed9dc: PCIReg(key: , device: 0/0/0)
> 0x9f5ed9dc: FS: Creating signal event SYSTEM/DevMgrApiSetReady
> 0x9f5ed9dc: FS: Creating signal event SYSTEM/PowerManagerReady
> 0x9f5ed9dc: FS: Creating signal event SYSTEM/GweApiSetReady
> 0x9f5ed9dc: FSREG: Unable to read value "Start DevMgr" under
> HKEY_LOCAL_MACHINE\init\BootVars
> 0x9f5ed9dc: FILESYS: Starting storage manager.
> 0x9f5ed9dc: >>> Loading module fsdmgr.dll at address 0x03C70000-0x03C93000
> (RW data at 0x01FCE000-0x01FCE810)
> 0x9f5ed9dc: FS: Registering file system StoreMgr, index 4, flags
> 0x00000001
> 0x9f5ed9dc: InitSharedHeap: 54200000 10000 c
> 0x9f5ed9dc: InitSharedHeap: return 54200060
> 0x9f5ed9dc: FILESYS: Restarting storage manager.
> 0x9f5ed9dc: FILESYS: Starting device and waiting for boot file system.
> 0x9f5ef800: >>> Loading module coredll.dll at address
> 0x03F40000-0x03FF4000
> (RW data at 0x01FFE000-0x01FFF765)
> 0x9f5ef800: >>> Loading module pm.dll at address 0x03EE0000-0x03EFD000 (RW
> data at 0x01FF6000-0x01FF6708)
> 0x9f5ef800: >>> Loading module devmgr.dll at address 0x03F20000-0x03F35000
> (RW data at 0x01FFC000-0x01FFC6B4)
> 0x9f5ef800: >>> Loading module device.exe at address 0x06010000-0x06013000
> 0x9f5ef800: InitSharedHeap: 54200000 0 c
> 0x9f5ef800: InitSharedHeap: return 54200060
> 0x9f5ef800: *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x9f57cd9a
> ***
> 0x9f5ef800: +InitDeviceFileSystems
> 0x9f5ef800: FS: Registering file system $device, index 5, flags 0x00000001
> 0x9f5ef800: FS: Registering file system $bus, index 6, flags 0x00000001
> 0x9f5ef800: -InitDeviceFi0x9f5ed9dc: FS: Waiting for device to signal
> BootPhase1 completion
> leSystems: status is 1
> 0x9f5ef800: >>> Loading module ceddk.dll at address 0x03BE0000-0x03BE7000
> (RW data at 0x01FC2000-0x01FC20CC)
> 0x9f5ef800: Ceddk!CalibrateStallCounter: Enter
> 0x9f5ef800: Ceddk!CalibrateStallCounter: Could not find stall counter
> 0x9f5ef800: Ceddk!BeginCalibration: min(1194) max(1326)
> 0x9f5ef800: Ceddk!BeginCalibration: Elapsed is 1210
> 0x9f5ef800: Ceddk!BeginCalibration: Delay is 180
> 0x9f5ef800: DEVICE!DevloadInit
> 0x9f5ef800: DEVICE!InitDevices: Root Key is Drivers\BuiltIn.
> 0x9f5ef800: DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2
> 0x9f5ef800: DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2
> 0x9f5ef800: >>> Loading module busenum.dll at address
> 0x03F00000-0x03F07000
> (RW data at 0x01FF8000-0x01FF850C)
> 0x9f5ef800: DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\JInitBM\BusPrefix) returned 2
> 0x9f5ef800: >>> Loading module jinitbm.dll at address
> 0x00FB0000-0x00FB4000
> 0x9f5ef800: JInitBM: Enabling PCI Busmastering
> 0x9f5ef800: DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\Prefix) returned 2
> 0x9f5ef800: DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\BusPrefix) returned 2
> 0x9f5ef800: >>> Loading module pcibus.dll at address 0x01220000-0x01239000
> 0x9f5ef800: PCIBUS!PCIRequestResources: I/O Resource Manager request for
> I/O
> range 0x0-0x3 failed
> 0x9f5ef800: PCIbus!PCIEnum: WARNING: Resource request for device 0:31:1
> failed
> 0x9f5ed9dc: FILESYS: Starting device and waiting for boot file system.
>
> Thanks for your help!
>
>


.

Relevant Pages

  • Hive based registry over block driver boot problem [CE 5.0]
    ... I have a problem with hive based registry in my platform.... ... FileSystem Starting - starting with clean file system ... 0x83fc70cc: FSVOL: Volume heap already initialized ... 0x83fc70cc: FILESYS: Restarting storage manager. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Hive based registry over block driver boot problem [CE 5.0]
    ... I have a problem with hive based registry in my platform.... ... FileSystem Starting - starting with clean file system ... 0x83fc70cc: FSVOL: Volume heap already initialized ... 0x83fc70cc: FILESYS: Restarting storage manager. ...
    (microsoft.public.windowsce.platbuilder)
  • DEBUG Image does not boot (CE5.0)
    ... HIVE-BASED Registry and it works fine in my release build. ... FileSystem Starting - starting with clean file system ... 0x9f5ed9dc: FILESYS: Starting storage manager. ... 0x9f5ed9dc: FILESYS: Starting device and waiting for boot file system. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Kernel hangs while loading udevice.exe
    ... Initializing Memory Mapped File Support ... FSVOL: Volume heap already initialized ... FILESYS: Starting boot phase 0. ... RAM File System FSD_MountDisk registering folder "Object ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Cant run WINCE from a flash drive on my AMD M/B
    ... FILESYS: Starting boot phase 0. ... Starting device and waiting for boot file system. ... PCIBUS!PCICfgCheckBARs: WARNING: No matching registry key was found for ...
    (microsoft.public.windowsce.embedded)