Re: Allocating Internal Flash as Root
- From: Milind <milind.vk@xxxxxxxxx>
- Date: Thu, 07 Jun 2007 21:13:08 -0700
On Jun 7, 4:34 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT no
instrument no spam DOT com> wrote:
Ifmountingas the root was working, you would not have a separate other
folder representing theflash. Something is wrong with your settings that
is causing theflashto be mounted, not as the root, by like a storage card.
Nothing just leaps out at me, but you might verify whether you're running
the ROM Only or ROM & RAM filesystem, etc.
Paul T.
<t...@xxxxxxxxxxxxx> wrote in message
news:1181241197.171931.9850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ok, I have theFlashloading and showing up as adriveon my system. I
have set all the registry settings that I could find in the help
documentation to tell it to mount as the root file system.
How do I tell if it is working? If I create a folder under any of the
standard places (like My Docments) the folder disappears the next time
I boot up the system. Could this be because I am loading, running and
debugging from ram instead of flashing the unit and then trying it? Is
this the right way to verify it?
I looked into the registry and I have the following entries actually
in the file system:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NandFlash]
"Dll"="nandfcd.dll"
"Order"=dword:0
"Prefix"="DSK"
"Profile"="FlashDisk"
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"FriendlyName"="i.MX21 NANDFLASHDriver"
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk]
"Name"="i.MX21 NANDFLASH"
"Folder"="NANDFlash"
"DefaultFileSystem"="FATFS"
"AutoMount"=dword:1
; Auto part and format disk if no partitions are present.
; WARNING! This can cause long boot times when encountering a
fresh disk.
"AutoPart"=dword:1
"AutoFormat"=dword:1
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS]
; Override common setting to enable automatic formatting of
unformatted volumes
"Flags"=dword:00000024
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\Nandfcd]
"DriverPath"="Drivers\\BuiltIn\\NandFlash"
; LoadFlags 0x01 == load synchronously
"LoadFlags"=dword:1
"BootPhase"=dword:0
; Note: if BinFS is used together with PS, then should ensure
; this is loaded after BinFS by setting order to 1 and that
; BinFS autoload order is 0.
"Order"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS]
; System registry in FATFS partition
"MountAsBootable"=dword:1
; To mount FAT partition as root
"MountAsRoot"=dword:1
Notice the MoustAsRoot setting and all.
I looked through the debug log and didn't see any errors. The only
thing I saw that stood out was:
8993 PID:bfc44ee TID:bfc44ca 0x8bfc4288: >>> Loading module
fatfsd.dll at address 0x03E40000-0x03E6B000 (RW data at
0x01FF2000-0x01FF263C)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR
\MX21_ARMV4I_DEBUG\FATFSD.DLL'
9005 PID:bfc44ee TID:bfc44ca 0x8bfc4288: >>> Loading module
fatutil.dll at address 0x03E10000-0x03E27000 (RW data at
0x01FED000-0x01FEE0E8)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR
\MX21_ARMV4I_DEBUG\FATUTIL.DLL'
9009 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New extended boot sector successfully written
9508 PID:bfc44ee TID:bfc44ca 0x8bfc4288:
FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't
exist for logical sector 0x200!!!
10002 PID:bfc44ee TID:bfc44ca 0x8bfc4288:
FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't
exist for logical sector 0x400!!!
10033 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New FAT #0 successfully written
10034 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New root directory successfully written
10036 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume:
New BPB successfully written
10036 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FormatDisk!FormatVolume
complete.
10037 PID:bfc44ee TID:bfc44ca 0x8bfc4288: <<< Unloading module
fatutil.dll at address 0x03E10000-0x03E27000 (RW data at
0x01FED000-0x01FEE0E8)
Unloaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR
\MX21_ARMV4I_DEBUG\FATUTIL.DLL'
It seems to be formatting thedrivewhen it boots. The only thing that
doesn't make sense if that is true is that if I create a folder
directly on thedrivethat is created (NANDFlash) it remains. So if I
create a folder on thatdriveit stays, but if I create a folder in
one of the standard folders they go away when I reboot.
Help?- Hide quoted text -
- Show quoted text -
Hi there,
Thanks for the quick reply. But my question is how should I confirm
that my root is mounted to flash? Becasue we are loosing data after
rebooting the device. Can I have list of catalog items that you have
added apart from those are added in Mobile handheld profile? Also you
have mentioned in the mailing thread that you added '
"MSPART.dll" explicitely.
Also I observed that when OS boots I get to see debug messages from
"FMD_Read" function and never get any calls to FMD_Write. What does
this mean? Are we missing any thing?
Thanks
Milind
.
- Follow-Ups:
- Re: Allocating Internal Flash as Root
- From: Paul G. Tobey [eMVP]
- Re: Allocating Internal Flash as Root
- References:
- Allocating Internal Flash as Root
- From: tony
- Re: Allocating Internal Flash as Root
- From: Paul G. Tobey [eMVP]
- Re: Allocating Internal Flash as Root
- From: tony
- Re: Allocating Internal Flash as Root
- From: Paul G. Tobey [eMVP]
- Re: Allocating Internal Flash as Root
- From: tony
- Re: Allocating Internal Flash as Root
- From: Paul G. Tobey [eMVP]
- Re: Allocating Internal Flash as Root
- From: tony
- Re: Allocating Internal Flash as Root
- From: tony
- Re: Allocating Internal Flash as Root
- From: Paul G. Tobey [eMVP]
- Re: Allocating Internal Flash as Root
- From: tony
- Re: Allocating Internal Flash as Root
- From: Paul G. Tobey [eMVP]
- Allocating Internal Flash as Root
- Prev by Date: How to share a folder on CE
- Next by Date: Re: How to share a folder on CE
- Previous by thread: Re: Allocating Internal Flash as Root
- Next by thread: Re: Allocating Internal Flash as Root
- Index(es):
Relevant Pages
|