Re: Allocating Internal Flash as Root
- From: Milind <milind.vk@xxxxxxxxx>
- Date: Thu, 07 Jun 2007 17:23:33 -0700
On Jun 6, 11:33 am, t...@xxxxxxxxxxxxx wrote:
Ok, my dev board comes with a NAND flash sub module and I decided to
try getting it working before I get around to actually implementing
the real hardware.
I plug the board in. I then right click on the BSP component that is
for that board from my BSP maker (freescale). I found it in the
catalog under the third party / bsp / freescale mx21 / storage
drivers / ms flash / nand flash driver. I assume this is the one.
Once it was added to my BSP I got a new set of registry entries in my
reginit.ini file. They are:
[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 NAND FLASH Driver"
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk]
"Name"="i.MX21 NAND FLASH"
"Folder"="NAND Flash"
"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
There are a lot of comments as well, but I cut those out for this
posting.
I then boot my device and can see in the built in devices the above
entries when I use the remote registry editor. What I don't see is a
drive called NAND Flash as the profile indicates.
I then saw in the driver's .reg file an environment parameter called
BSP_PS_NAND and decided to set that in my platform settings. Once I
did that I got these additional entries in the reginit.ini:
[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
I was hoping this would cause the NAND to be used as the main storage.
It doesn't. I am also not sure, but I seem to recall that devices that
actually get loaded are copied from the BuiltIt registry area to the
Active registry area. I didn't see the nand driver anywhere in the
Active section.
Any ideas what I am missing here?
Hi there,
We are also facing very similar problem that you have. our WinCE 5.0
device is having 256MB flash memory. and our run time image is taking
18MB of that. Our bootloader is loading the NK from Flash to RAM and
executing in RAM. But we are not able to store the user data on the
flash (in short we are not able to make use of available
flash(256-18).
Whether we have to mount the remaining flash as separate drive? If so
how to do that?
thanks
Milind
.
- 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
- Allocating Internal Flash as Root
- Prev by Date: Re: Allocating Internal Flash as Root
- Next by Date: Problem with eboot
- Previous by thread: Re: Allocating Internal Flash as Root
- Next by thread: How to use platform builder to debug a NDIS driver on pocket pc device
- Index(es):
Relevant Pages
|