Is there a away to solve this? Windows CE 5 stays intact, but all files I copy or drivers I install get lost once you reset it. Is it a Win ce 5 setting in Platform builder or the machine itself? thanx
2440 deleting all files when turned off
Have a look here: http://www.friendlyarm.net/forum/topic/96
Yeah it didn't really help too much cause I cound't even find half the stuff mentioned in the registry. The funny thing is that the registry itself stays intact, meaning the drivers I installed are mentioned in there, but the actual files are gone...
Hi zozie! You must change catalog item "RAM and ROM File System" with "ROM-only File System" and add following lines in platform.reg : [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SMFLASH] "DefaultFileSystem"="FATFS" "PartitionDriver"="mspart.dll" "AutoMount"=dword:1 "AutoPart"=dword:1 "AutoFormat"=dword:1 "Folder"="ResidentFlash" "Name"="Microsoft Flash Disk" "BootPhase"=dword:0 "Flags"=dword:1000 ; add this 3 line IF SYSGEN_FSROMONLY "MountAsBootable"=dword:1 ENDIF [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SMFLASH\FATFS] "FriendlyName"="FAT FileSystem" "Dll"="fatfsd.dll" "Flags"=dword:00280014 "Paging"=dword:1 "CacheSize"=dword:0 "EnableCacheWarm"=dword:0 "EnableCache"=dword:1 "MountFlags"=dword:2 ; add this 5 line IF SYSGEN_FSROMONLY "MountAsRoot"=dword:1 "MountAsBootable"=dword:1 "MountPermanent"=dword:1 ENDIF Then select "Clean before building' and use "Build and sysgen" to make image. Regards!
Hi Nikolay, Thanks for your response. I attempted exactly what you have here. I selected "ROM-only File System" and added the exact registry keys that you mentioned. Couple questions for you: 1. How does the system know to use the SMFLASH with FATFS? No other registry keys relate to this. 2. Do you think there are any other Catalog Items that are required to set up flash card file reads. It seems like whenever I add "ROM-only File System" or "RAM and ROM File System" to the catalog, the system hangs and never loads. After starting the eboot, the Windows CE Debug output window stops at the following: PB Debugger Loaded symbols for 'C:\WORK2\WHITEKING\OS\LAI_PRM550S_V3\LAI_PRM550S_V3\LAI_PRM550S_V3\RELDIR\VIA_M ARK_CEPC_X86_RELEASE\ROMFSD.DLL' 134 PID:400002 TID:680002 Override Serial Driver: serial debug output selected on COM port 1, disabling serial driver for that port. PB Debugger Loaded symbols for 'C:\WORK2\WHITEKING\OS\LAI_PRM550S_V3\LAI_PRM550S_V3\LAI_PRM550S_V3\RELDIR\VIA_M ARK_CEPC_X86_RELEASE\RELFSD.DLL' 134 PID:400002 TID:680002 Override Serial Driver: No COM port selected for serial KITL transport, no override necessary. PB Debugger The Kernel Debugger has been disconnected successfully.
For your first question: [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SMFLASH] "DefaultFileSystem"="FATFS" I think this key is sufficient and he present in original platform.reg file. For the second question: No need to add any other "Catalog Items". I recommend you make image without including "KITL". Did you select "Clean before building' and use "Build and sysgen" to make the image?
Hi Nikolay, I unchecked "KITL" and "kernel debugger" and performed a CLEAN <project name>, and then a BUILD <project name> from the BUILD menu. I do not have "Build and sysgen" on my BUILD menu because of the following post I read a while back (http://guruce.com/blogpost/whattobuildwhen): "The first and most important thing to do is to delete two options from the Platform Builder Build menu: Build and Sysgen and Rebuild and Clean Sysgen. These commands will build the entire tree (so including any source in PUBLIC and PRIVATE)." I haven't made any modifications to the PUBLIC or PRIVATE folders, so would a Build and sysgen still be required? I am doing a Build project each time.
I think a big part of the problem I'm having is that as soon as I add in either "RAM and ROM File System" or "ROM-only File System", my OS will build, but it never boots properly. As it boots up, it stops BEFORE this line: PB Debugger Loaded symbols for 'C:\WORK2\LAI_PRM550S_V3\RELDIR\VIA_MARK_CEPC_X86_RELEASE\SHELL.EXE'
Hi Kevin, What is your board type? I see "VIA_MARK_CEPC_X86_RELEASE" in your log. My post is about mini2440 board with Samsung S3C2440A ARM920T. Regards!
Sadly that is true. I am using an x86 Via Mark board. I was hoping they were similar enough that accessing files on the flashcard would have the same procedures. Thanks for all of your help. It's greatly appreciated.
Hi I use mini2440 for 1week and I have this problem on WinCE5.0. I read all topics about this problem. but I can not download Wince setup and do these things that you said. if any body has WinCE5.0 without this problem I need it (mini2440 (t35)). and my email address is: ali.taroosheh@gmail.com I'm very kind of you if send it for me thanks alot
Hi I found WinCE5 setup on DVD I fixed this problem. everybody can download it: http://www.mediafire.com/?sharekey=201d6b1af76880fdab1eab3e9fa335ca9ac44... but its based on mini2440-T35 and it's not contain the other ones. good luck :)
but your images have another problem os just use only about 30mb of flash icant copy a file bigger than 10mb someone help
Hi About Flash problem (Sammy) I don't have this problem that you said I have copied a big file (about 36MB) in flash without any problem and attached file is for this claim. and about your question Edje11: you need to install winCE5.0 setup. you can find in in Microsoft.
------------------ Maybe a dumb question, but where could the option "ROM-only File System" be found in vb2005 ? ------------------ Edje11, Use Platform Builder. Its on right panel, U will see that option in Core Os->File System And Data Store->File System Internal (Choose 1)
I do all that is exposed here, but after the bootup logo nothing happens, the logo stays there forever... I modified platform.reg, added the hive based registry and rom only fs... what else am I missing? thanks Fernando
I found what was happening, I didnt have the FAT file system added to my OS design... I added it and now it works! I hope this helps to other person with the same problem. Thanks a lot to all who helped me, now I will continue... lets see whats the next trouble!! :) Fernando