Re: USB Mass Storage Support




It seems you are still using hive, at least partially.
Have you re-sysgened your design after checking
"RAM Based Registry" feature in the catalog?
Make sure you are sysgening with the "Clean before building"
option turned on.



maite wrote:
Hi voidcoder,

When trying with RAM registry I get a debugging error concerning to
the registry. And of course, the image does not boot.
Should registry type have something to do with USB storage drives?

Thanks a lot.

Here are the messages in case it helps:

PB Debugger The Kernel Debugger is waiting to connect with target.
4294767296 PID:0 TID:0 CEPC Firmware Init
4294767296 PID:0 TID:0 RTC - Status Reg B - 0x02
4294767296 PID:0 TID:0 g_dwCPUFeatures = a7e9f9bf
4294767296 PID:0 TID:0 g_nMtrrCnt = 8
4294767296 PID:0 TID:0 MTRR PhysMask0: 0000000fe0000800
4294767296 PID:0 TID:0 MTRR PhysBase0: 0000000000000006
4294767296 PID:0 TID:0 MTRR PhysMask1: 0000000ffff00800
4294767296 PID:0 TID:0 MTRR PhysBase1: 000000001f700000
4294767296 PID:0 TID:0 MTRR PhysMask2: 0000000fff800800
4294767296 PID:0 TID:0 MTRR PhysBase2: 000000001f800000
4294767296 PID:0 TID:0 MTRR PhysMask3: 0000000f00000000
4294767296 PID:0 TID:0 MTRR PhysBase3: 0000000000000000
4294767296 PID:0 TID:0 MTRR PhysMask4: 0000000f00000000
4294767296 PID:0 TID:0 MTRR PhysBase4: 0000000000000000
4294767296 PID:0 TID:0 MTRR PhysMask5: 0000000f00000000
PB Debugger Kernel debugger connected.
4294767296 PID:0 TID:0 MTRR PhysBase5: 0000000000000000
4294767296 PID:0 TID:0 MTRR PhysMask6: 0000000f00000000
4294767296 PID:0 TID:0 MTRR PhysBase6: 0000000000000000
4294767296 PID:0 TID:0 MTRR PhysMask7: 0000000f00000000
4294767296 PID:0 TID:0 MTRR PhysBase7: 0000000000000000
4294767296 PID:0 TID:0 PhysMask0: 0000000fe0000800
4294767296 PID:0 TID:0 PhysMask1: 0000000ffff00800
4294767296 PID:0 TID:0 PhysMask2: 0000000fff800800
4294767296 PID:0 TID:0 PhysMask3: 0000000f00000000
4294767296 PID:0 TID:0 PhysMask4: 0000000f00000000
4294767296 PID:0 TID:0 PhysMask5: 0000000f00000000
4294767296 PID:0 TID:0 PhysMask6: 0000000f00000000
4294767296 PID:0 TID:0 PhysMask7: 0000000f00000000
4294767296 PID:0 TID:0 g_nMtrrInuse = 3
4294767296 PID:0 TID:0 Looking for rom chain
4294767296 PID:0 TID:0 Rom chain NOT found
4294767296 PID:0 TID:0 Firmware Init Done.
4294767296 PID:0 TID:0 Setting up softlog at 0x83ffc000 for 0x800
entries
4294767296 PID:0 TID:0 Booting Windows CE version 6.00 for (x86)
4294767296 PID:0 TID:0 &pTOC = 81d5df10, pTOC = 81d060e8, pTOC-
ulRamFree = 81d66000, MemForPT = 00003000
4294767296 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
4294767296 PID:0 TID:0 Configuring: Primary pages: 8845, Secondary
pages: 0, Filesystem pages = 4422
4294767296 PID:0 TID:0
Booting kernel with clean memory configuration:
4294767296 PID:0 TID:0 Memory Sections:
4294767296 PID:0 TID:0 [0] : start: 81d6a000, extension: 00005000,
length: 0228d000
4294767296 PID:0 TID:0 X86Init done, OEMAddressTable = 80226d30, RAM
mapped = 04000000.
4294767296 PID:0 TID:0 Windows CE KernelInit
4294767297 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first =
c0010000, last = c0bd0000
4294767297 PID:400002 TID:2 g_pprcNK == 0x81d5bc80
4294767297 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00013000
4294767297 PID:400002 TID:410002 Initializing Memory Mapped File
Support
4294767297 PID:400002 TID:410002 Scheduling the first thread.
4294767298 PID:400002 TID:410002 LoaderInit: Initialing loader
4294767298 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00013000
4294767298 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00074000
4294767298 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0001f000
4294767299 PID:400002 TID:410002 Heap Statistics at 0xC01527A0
4294767299 PID:400002 TID:410002 Did not find emulation code for
x86... using floating point hardware.
4294767300 PID:400002 TID:410002 PGPOOL: Reserved 768 pages for Loader
pool
4294767300 PID:400002 TID:410002 PGPOOL: Reserved 256 pages for File
pool
4294767301 PID:400002 TID:410002 OSAXST0: Platform Name = CEPC
4294767302 PID:400002 TID:410002 OSAXST1: >>> Loading Module
'kd.dll' (0x83FDE678) at address 0xC0010000-0xC003E000 in Process
'NK.EXE' (0x81D5BC80)
4294767302 PID:400002 TID:410002 KD: Starting kernel debugger software
probe (KdStub) - KD API version 22
4294767303 PID:400002 TID:410002 Calling KDEnableInt (FALSE, NULL)
without previously calling KDEnableInt (FALSE, p)
4294767312 PID:400002 TID:410002 OSAXST1: >>> Loading Module
'NK.EXE' (0x81D5BC80) at address 0x80220000-0x80233000 in Process
'NK.EXE' (0x81D5BC80)
PB Debugger The Kernel Debugger connection has been established
(Target CPU is X86).
PB Debugger Target name: CE Device
PB Debugger Probe name: KdStub
PB Debugger Binary Image should be loaded at 0x80220000 / Data
relocated at 0x81d08000
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\NK.EXE'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\NK.EXE'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\COREDLL.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\KERNEL.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\KITL.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\OALIOCTL.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\HD.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\OSAXST0.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\OSAXST1.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\K.COREDLL.DLL'
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\KD.DLL'
4294767351 PID:400002 TID:410002 HD: Immediate debugger module load
notifications ACTIVE (slower boot - non real-time).
4294767478 PID:400002 TID:410002 Message Queue support initialized,
g_hMsgQHeap = d0040750
4294767479 PID:400002 TID:630002 OSAXST1: >>> Loading Module
'filesys.dll' (0x83FBCF44) at address 0xC0170000-0xC01EA000 in Process
'NK.EXE' (0x81D5BC80)
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\FILESYS.DLL'
4294767486 PID:400002 TID:630002 OSAXST1: >>> Loading Module
'fsdmgr.dll' (0x83FB809C) at address 0xC0510000-0xC0546000 in Process
'NK.EXE' (0x81D5BC80)
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\FSDMGR.DLL'
4294767493 PID:400002 TID:630002 FSDMGR!DllMain: DLL_PROCESS_ATTACH
4294767494 PID:400002 TID:680002 CertMod.dll not found, using old OEM
Trust Model
4294767494 PID:400002 TID:680002 FileSystem Starting - starting with
clean file system
4294767495 PID:400002 TID:680002 FSDMGR!STOREMGR_Initialize
4294767495 PID:400002 TID:680002 FSDMGR!InitializeStoreAPI
4294767495 PID:400002 TID:680002 FSDMGR!
MountTable_t::RegisterVolumeName: Registered "StoreMgr" at index 2
4294767495 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolume:
Registered volume at index 2 (Name="StoreMgr", MountFlags=0x1)
4294767495 PID:400002 TID:680002 FSDMGR!InitializeROMFileSystem: File
System=ROM
4294767495 PID:400002 TID:680002 OSAXST1: >>> Loading Module
'romfsd.dll' (0x83F9E1BC) at address 0xC01F0000-0xC01F6000 in Process
'NK.EXE' (0x81D5BC80)
PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS
\OSDESIGN10_INDCTRL\OSDESIGN10_INDCTRL\RELDIR\TESTCEPC_X86_DEBUG
\ROMFSD.DLL'
4294767503 PID:400002 TID:680002 FSDMGR!
MountTable_t::RegisterVolumeName: Registered "ROM" at index 3
4294767503 PID:400002 TID:680002 FSDMGR!MountTable_t::RegisterVolume:
Registered volume at index 3 (Name="ROM", MountFlags=0x71)
4294767503 PID:400002 TID:680002 ERROR: C:\ymzki\private\winceos\COREOS
\filesys\reg\reghive\.\registry.c line 802:
4294767503 PID:400002 TID:680002 FSREG: Unable to mount boot hive from
ROM
4294767503 PID:400002 TID:680002 FSREG: Unable to load system
registry! Registry will be unavailable.
4294767503 PID:400002 TID:680002 FileSys: DEBUGCHK failed in file C:
\ymzki\private\winceos\COREOS\filesys\reg\reghive\.\registry.c at line
1147

.



Relevant Pages

  • Help with hive-based registry on CF-card
    ... registry is read from storage but atadisk is loaded after. ... 4294767297 PID:400002 TID:410002 Initializing Memory Mapped File Support ... 4294777932 PID:400002 TID:680002 FSVOL: Volume heap already initialized ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 6 boot hangs
    ... I ran into the same problem with an OMAP35xx platform and found on a ... you might try changing the registry settings for RELFSD ... 7377 PID:400002 TID:410002 KD: Starting kernel debugger software ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 6 boot hangs
    ... You could also try removing the debug shell and see if the problem goes away ... you might try changing the registry settings for RELFSD ... 7377 PID:400002 TID:410002 KD: Starting kernel debugger software ...
    (microsoft.public.windowsce.platbuilder)
  • Re: CE 6 boot hangs
    ... changing it every place it exists, rather than just the one adapter. ... you might try changing the registry settings for RELFSD ... 7377 PID:400002 TID:410002 KD: Starting kernel debugger software ...
    (microsoft.public.windowsce.platbuilder)
  • Re: {newbie} Help getting an NK.BIN image running on a x86 DOS machine
    ... It looks to me like you are using hive-based registry. ... I made some good progress today getting my x86-based "CEPC" target to ... PB Debugger The Kernel Debugger is waiting to connect with target. ...
    (microsoft.public.windowsce.embedded)