Re: Troubleshooting the flash driver loading

Hi Dinesh,

the key
HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\...

is NOT for a flash driver but for filesystems! Refere to "Storage Manager
Registry Settings" in the Platform Builder help.

Does the flash driver unload after/during checking the blocks? If not
everything should be fine. To test the Hive-based registy, simply
change/create a registry key when your system has started, then reboot and
see if the changes are still there.

Best regards
-Jochen


"Dinesh" wrote:

Sorry sent the mail prematurely.


And this are some of the last entries I see in kernel debugger log..

....
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\KD.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\OSAXST1.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\OSAXST0.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\HD.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\NK.EXE'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\CELOG.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\COREDLL.DLL'
36172 PID:3fdf002 TID:3fdf266 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ Arrived
TestIOCTLu $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\FILESYS.EXE'
36192 PID:3f9d242 TID:3fa2fc2 +OALIoCtlHalInitRTC(...)
36193 PID:3f9d242 TID:3fa2fc2 +OALIntrStaticTranslate(13, 2)
36193 PID:3f9d242 TID:3fa2fc2 -OALIntrStaticTranslate
36193 PID:3f9d242 TID:3fa2fc2 -OALIoCtlHalInitRTC(rc = 1)
37144 PID:3f9d242 TID:3fa2fc2 In SecureRegistry&^$$&**
37145 PID:3f9d242 TID:3fa2fc2 In SecureRegistry&^$$&**
37165 PID:3f9d242 TID:3fa2fc2 +OALKitlInitRegistry
37170 PID:3f9d242 TID:3fa2fc2 -OALKitlInitRegistry
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\FSDMGR.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\FLASHDRV.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\RELFSD.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\PM.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\DEVMGR.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\DEVICE.EXE'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\CEDDK.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\BDB2\RELDIR\BDB2_ARMV4I_RELEASE\BUSENUM.DLL'
37758 PID:23f6b52e TID:23f6b50a FMD::FMD_Init
37761 PID:23f6b52e TID:23f6b50a FMD_OEMIoControl
37762 PID:23f6b52e TID:23f6b50a FMD::FMD_GetInfo
37770 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_IN : Block No :- 0
37771 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 0
numSectors 1
37771 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_OUT : Block No :- 0,
Status = 0
37772 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 0
numSectors 1
37774 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_IN : Block No :- 1
37774 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 64
numSectors 1
37775 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_OUT : Block No :- 1,
Status = 0
37775 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 64
numSectors 1
37775 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_IN : Block No :- 2
37776 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 128
numSectors 1
37776 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_OUT : Block No :- 2,
Status = c
37777 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_IN : Block No :- 3
37777 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 192
numSectors 1
37778 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_OUT : Block No :- 3,
Status = 0
....
40004 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_IN : Block No :- 1023
40004 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 65472
numSectors 1
40005 PID:23f6b52e TID:23f6b50a FMD_GetBlockStatus_OUT : Block No :- 1023,
Status = 0
40005 PID:23f6b52e TID:23f6b50a FMD_ReadSector_IN: StartSector, 65472
numSectors 1
....

So I can see that after reading Block Status for all the blocks, there is
some issue which is preventing to go any further. But since I don't know
what to expect, I am confused on how to debug this. Please suggest.

Also I have noticed that if the block status is "RESERVED", device.exe is
not reading first sector of the block otherwise it's reading.

Thanks and regards,
Dinesh

"Dinesh" <mittals.dinesh@xxxxxxxxx> wrote in message
news:ukIdb9WYIHA.1188@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have included the catalog item in my OS design. Also I have added
following items in platform.reg file.

; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="Documents and Settings\\system.hv"
"ProfileDir"="Documents and Settings"
"Flags"=dword:3
"Default User"="default"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\FlashDrv]
"Prefix"="DSK"
"Dll"="FLASHDRV.dll"
;"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"Order"=dword:0
"Ioctl"=dword:4
"Profile"="FlashDrv"
"FriendlyName"="MS Flash Driver"
"Flags"=dword:1000

[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\FlashDrv]
"DriverPath"="Drivers\\BuiltIn\\FlashDrv"
"Dll"="flashdrv.dll"
"Paging"=dword:0
"LoadFlags"=dword:1
"BootPhase"=dword:0
"Order"=dword:0

; END HIVE BOOT SECTION

Do you think I should add/remove some more registry items under "HIVE BOOT
SECTION".

Thanks and regards,
Dinesh


"JochenD" <JochenD@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E9BF5F9E-0711-4436-98CE-C32885FB94A1@xxxxxxxxxxxxxxxx
Hi Dinesh,

the Bootphase value is only for autoload filesystems and block devices,
and
not for either device.exe or filesys.exe.

To set up a Hive-based registry you need to include the catalog item in
your
image. All details can be found in the Platform Builder help under
"Hive-based Registry Setup"

best regards
-Jochen

"Dinesh" wrote:

Hi,
I am trying to setup hive based registry on my WINCE 5 handheld device.
I
have configured registry in such a way that device.exe and filesys.exe
are
to be started in boot phase 0.
I am seeing that after loading nk.exe, WinCE is trying to load the flash
driver through device.exe; but after some basic calls into flash
driver(like
FMD_Init, FMD_GetInfo and FMD_GetBlockStatus for all blocks), it's not
doing
anything.
Can somebody explain what's the exact sequence I should expect in terms
of
loading the flash driver through device manager?

Please also comment whether I am right in loading both device.exe and
filesys.exe in bootphase 0.

Any extra help in setting up hive based registry would also be most
appreciated.


Thanks and regards,
Dinesh





.

Relevant Pages

  • Re: Troubleshooting the flash driver loading
    ... ; END HIVE BOOT SECTION ... Do you think I should add/remove some more registry items under "HIVE BOOT ...
    (microsoft.public.windowsce.embedded)
  • Re: Error 4309 returned when writing files
    ... writing to the disk drive. ... registry setting set to 0 by default. ... yet I haven't yet determine a successful solution. ...
    (microsoft.public.windowsce.platbuilder)
  • Hive-based Registry Quest!!help me!
    ... My Platform is SMDK2410+wince50,intel flash is 28sf128 ... i want to save Hive-based Registry in intel flash,but the system is ... system ROM, index 2, flags 0x00000031 ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Persistent Data Storage profile fails while file coping and folder creating
    ... "Unable to determine physical sector address for logical sector" ... storage with the RAM-Based Registry on a 30MB flash portion mounted ... RegReadActivationValues RegQueryValueEx ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Problems with RELFSD/KITL on MainstoneIII BSP
    ... Yes I am using Hive based registry, stored on an Intel PSM filestore. ... via Kitl and it is the entire Kitl link that stops working. ... The Kernel Debugger is waiting to connect with target. ...
    (microsoft.public.windowsce.platbuilder)
Loading