How to make BINFS partition mounted and visible in explorer?

Hi All,

I make two partitions on a 64MB NAND flash of my board.
MBR at Block 0
part00, BINFS, 16MB
part01, FAT32, 47MB

After Wince startup, the FAT partition is mounted and visible as a
folder named
"ResidentNandFlash".
But BINFS partition is not mounted, cause I check in Storage Manager,
part00 has no "*" mark beside and is not mounted.

The following is the relevant registry settings in platform.reg
=========================================
[HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable]
"21"="BINFS"
"0B"="FATFS" ;MS-DOS FAT32
[HKEY_LOCAL_MACHINE\System\StorageManager\BINFS]
"Folder"="BINFS"
"FriendlyName"="BIN_FS"
"Dll"="binfs.dll"
"MountFlags"=dword:0 ;MountAsROM, but not Hidden
; "Paging"=dword:1
"BootPhase"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\Nand]
"DriverPath"="Drivers\\BuiltIn\\Nand"
"LoadFlags"=dword:1 ;LoadFlags 0x01 == load
synchronously
"MountFlags"=dword:10
"BootPhase"=dword:0
; "Order"=dword:0
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Nand]
"Prefix"="DSK"
"Dll"="NANDDRV.DLL"
"Order"=dword:2
; "Ioctl"=dword:4
"Profile"="Nand"
"IClass"="{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"Flags"=dword:1000 .
"FriendlyName"="MSFLASH NAND Driver"
"BootPhase"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\Nand]
"DefaultFileSystem"="BINFS"
"PartitionDriver"="mspart.dll"
"Name"="NAND FlashDisk"
"Folder"="ResidentNandFlash"
"AutoMount"=dword:1
"AutoPart"=dword:1
"MountFlags"=dword:10
; "AutoFormat"=dword:1
"BootPhase"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\Nand\FATFS]
; "Dll"="FATFS.DLL"
; "Util"="FATUTIL.DLL"
"MountFlags"=dword:0
"AutoMount"=dword:1
"AutoPart"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"MountFlags"=dword:0
=========================================

Anyone can give me a hint to make BINFS visiable in WINCE explorer?

Thanks in advance.

D.H

darkhorse
Tue Jul 10 04:25:45 CDT 2007

I forgot to tell an issue.

My WINCE image is a single NK.bin ,not multiple XIP image.

Is it the reason that BINFS partition can not be mounted by WINCE
NK.bin image?

Thanks.

Dean
Tue Jul 10 13:04:49 CDT 2007

The BINFS partition is only for running binfs images. Your image apparently
isn't binfs, so there is nothing to mount. Even if there was, what is the
point of mounting it?

--
Dean Ramsier - eMVP
BSQUARE Corporation


"darkhorse" <zhy.sh.cn@gmail.com> wrote in message
news:1184059545.068660.160470@m37g2000prh.googlegroups.com...
>I forgot to tell an issue.
>
> My WINCE image is a single NK.bin ,not multiple XIP image.
>
> Is it the reason that BINFS partition can not be mounted by WINCE
> NK.bin image?
>
> Thanks.
>

darkhorse
Wed Jul 11 04:54:11 CDT 2007

Thanks Dean.
I have built a MXIP image for my board.
There are three bins:
1. NK.bin
2. Drivers.bin
3. chain.bin
Now I download MXIP image with PB and it works fine. NAND flash can
also be founded.
but in Storage Manager, I found the situation is the same.
Part00 for BINFS is not mounted.
Part01* for FATFS is mounted.

I keep the same registry with that described in the top post.
What's wrong with my build process?
Any new configuration is needed?

Br,
D.H

Dean
Wed Jul 11 08:48:34 CDT 2007

Why do you want to see the binfs partition? I haven't tried to do this, so
I can't give you a direct answer. But the BINFS partition is one that you
execute from only, you can't read it or write to it. In my opinion, the
situation you have is the one you want - the portion of the nand that
contains binfs should not be visible to an end user.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"darkhorse" <zhy.sh.cn@gmail.com> wrote in message
news:1184147651.321033.16970@k79g2000hse.googlegroups.com...
> Thanks Dean.
> I have built a MXIP image for my board.
> There are three bins:
> 1. NK.bin
> 2. Drivers.bin
> 3. chain.bin
> Now I download MXIP image with PB and it works fine. NAND flash can
> also be founded.
> but in Storage Manager, I found the situation is the same.
> Part00 for BINFS is not mounted.
> Part01* for FATFS is mounted.
>
> I keep the same registry with that described in the top post.
> What's wrong with my build process?
> Any new configuration is needed?
>
> Br,
> D.H
>

darkhorse
Wed Jul 18 04:02:23 CDT 2007

Dear Dean,

I am not trying to see the BINFS folder in WINCE explorer. I think
that BINFS shoule be visible now that BINFS partition can be mounted
by MXIP image.

Now I encounter a question.

-----------
1. I built a working MXIP image for my board, but I didn't add BINFS
support into my image from CoreOS->File sytem and data store->Binary
ROM image file system.
The image can work fine, but in the Storage Manger, the binfs
partition is not mounted, displayed as "part00", while the FATFS
partition is "part01*"
2. Then I add BINFS support to my image and re-build the MXIP system.
After downloading the image into my board, there are lots of exception
raised during the image startup process.

Based on your rich experience in WINCE, can you give me some hints
about the solution?
Thanks.
D.H