Problem with bootpart.lib

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - Making flash the root file system I have been posting and getting responses on the following thread: http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/781ae18f7672e308/9c607c8638e297e8#9c607c8638e297e8 Suddenly I can't post to it. I try to post and it says post successful, but the post never shows up. I waited for an hour and it still didn't show up. Normally it shows up within a few seconds or minutes at the most. I hope noone minds that I start a new thread because of that. If you read that thread you saw that I had trouble just getting the flash driver to load. I have the flash driver loading and a new drive on my device called NAND Flash. I can create folders and files on this drive and everything works fine. I have the following registry settings: [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" ; These can overridden in the particular named profile ; Various Flags ; AutoFormat - Formats the store automatically ; AutoPart - Automatically partitions the store with largest creatable partition ; AutoMount - Automatically Mounts each detected partition (if FSD driver is available) ; MountFlags (deprecated in WinCE 5.0)- Flags on how the partition is mounted ; 1 - Hidden file system ; 2 - May contain system registry ; 4 - Mount as root of file system, "\" ; 8 - Hide ROM when mounting FS root ; 10 - Mount filesystem as an external ROM filesystem ; 20 - Treat all files and subdirectories as system files ; The following registry values replace the MountFlags: ; MountHidden - Hidden file system (same as MountFlags=1) ; MountAsBootable - May contain system registry (same as MountFlags=2) ; MountAsRoot - Mount as root of file system, "\" (same as MountFlags=4) ; MountAsROM - Mount as an external ROM filesystem (same as MountFlags=10) ; MountSystem - Treat all files and subdirectories as system files (same as MountFlags=20) [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 ; Default values for fatfs. These can be overridden per profile ; Flags DWORD See available flags below ; Valid Bits for Flags registry value ;FATFS_UPDATE_ACCESS 0x00000001 update access times if set ;FATFS_DISABLE_LOG 0x00000002 disable event logging if set ;FATFS_DISABLE_AUTOSCAN 0x00000004 disable automatic ScanVolume() ;FATFS_VERIFY_WRITES 0x00000008 verify all writes (as opposed to a handful) ;FATFS_ENABLE_BACKUP_FAT 0x00000010 add a backup FAT to all formats ;FATFS_FORCE_WRITETHROUGH 0x00000020 Force fat to be always writethrough ;FATFS_DISABLE_AUTOFORMAT 0x00000040 disable automatic formatting of unformatted volumes ;FATFS_WFWS_NOWRITETHRU 0x00010000 disable writethrough on WriteFileWithSeek API, ; improve memory-mapped file performance ;FATFS_DISABLE_FORMAT 0x00020000 disable format ;FATFS_TRANS_DATA 0x00040000 transact data on a write (i.e. clone cluster on every write) ;FATFS_TFAT_USECLUS1 0x00080000 Use cluster 1 entry in FAT table for TFAT transaction. ; By default, TFAT uses the NOF field of the boot sector ;FATFS_DISABLE_TFAT_REDIR 0x00100000 Indicates to disable redirect the root directory ; to another hidden directory for FAT12 or 16, ; since root dir isn't transacted in those cases ;FATFS_TFAT_ALWAYS 0x00200000 Always mark transaction status, even only one sector in FAT is changed ;FATFS_FORCE_TFAT 0x00400000 Force TFAT transactioning even if volume isn't formatted as TFAT ; NOTES: common.reg default is "Flags"=dword:00000064 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS] ; Override common setting to enable automatic formatting of unformatted volumes "Flags"=dword:00000024 ; Additional settings for multi xip or persistent storage in NAND ; Entry for nand driver to be loaded by storage manager. ; Once a driver has been loaded by storage manager, it will not ; be loaded again by device manager. ; Note: Needed for Hive registry or persistent storage [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 ; NAND persistent storage settings only [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 As you can see I have set the flash to mount as bootable and mount as root. I also have ROM File System as a part of my platform. How do I tell if it is working? If I create a folder or file under My Documents and reboot it doesn't stay like the ones I create on NAND Flash drive do. I looked through the debug log and don't see any errors. The only thing I do see is that the formatter is running every time it loads. Here is the output: 8943 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 8977 PID:bfc44ee TID:bfc44ca 0x8bfc4288: PD_FormatPartition - type is 6 8979 PID:bfc44ee TID:bfc44ca 0x8bfc4288: NumSec=130720 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 8979 PID:bfc44ee TID:bfc44ca 0x8bfc4288: Partition PART00 NumSectors=130718 8979 PID:bfc44ee TID:bfc44ca 0x8bfc4288: MSPART!PD_OpenPartition: dwStoreId=000B2F30, PartName=PART00 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' 10038 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FSD_MountDisk: mounting volumes for hDsk=000B4CA0 10040 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: access time updates disabled 10040 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: event logging enabled 10041 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: automatic scanning disabled 10041 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: write verify disabled 10041 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: extra FAT on format disabled 10041 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: force write through enabled 10043 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: Codepage = 1 10045 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!OpenVolume: Number of path cache entries = 50 10063 PID:bfc44ee TID:bfc44ca 0x8bfc4288: >>> Loading module diskcache.dll at address 0x03E30000-0x03E39000 (RW data at 0x01FF0000-0x01FF04F4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR \MX21_ARMV4I_DEBUG\DISKCACHE.DLL' 10065 PID:bfc44ee TID:bfc44ca 0x8bfc4288: CreateCache: Successful. Cache Size: 256 KB, Start: 32, End: 1053. 10066 PID:bfc44ee TID:bfc44ca 0x8bfc4288: CreateCache: Successful. Cache Size: 512 KB, Start: 1054, End: 130717. 10480 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!InitVolume: FAT version: 32 10480 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FATFS!InitVolume: Cluster Size (Sectors): 1 10482 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FS: Registering file system NAND Flash, index 4, flags 0x00000002 10483 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FS: Mount complete (NAND Flash, index 4, flags 0x00000002) 10484 PID:bfc44ee TID:bfc44ca 0x8bfc4288: InitSharedHeap: 44000000 10000 c 10485 PID:bfc44ee TID:bfc44ca 0x8bfc4288: InitSharedHeap: return 44000060 10495 PID:bfc44ee TID:bfc44ca 0x8bfc4288: >>> Loading module relfsd.dll at address 0x03E00000-0x03E0B000 (RW data at 0x01FEB000-0x01FEBADC) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\3PLAY\RELDIR \MX21_ARMV4I_DEBUG\RELFSD.DLL' 10501 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FS: Registering file system Release, index 5, flags 0x00000000 10501 PID:bfc44ee TID:bfc44ca 0x8bfc4288: Mounted ReleaseFSD volume '\Release' 10514 PID:bfc44ee TID:bfc44ca 0x8bfc4288: size of 'dbglist.txt' = 00000000 10516 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FS: Mount complete (Release, index 5, flags 0x00000000) 10516 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 10516 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FSREG: Logging in default user. 10517 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 10517 PID:bfc44ee TID:bfc44ca 0x8bfc4288: SetCurrentUser: Logging out (nobody), logging in default 10517 PID:bfc44ee TID:bfc44ca 0x8bfc4288: FS: Using default path "\profiles\" The problem with thinking that is it is that files in NAND Flash stick around after a reboot. Maybe the root is at a different location or partition? Any ideas? Tag: Problem with bootpart.lib Tag: 101416
  - 2
    - WiFi support in WinCE 6.0 Dear All, From the documentation of WinCE 6.0, it mentioned that "Windows Embedded CE 6.0 does not support Native Wi-Fi". So if we want to support Wi-Fi in our OS, do we need to include third-party driver for it, or Wireless LAN (WLAN) 802.11 STA is good enough? Thanks, James Tag: Problem with bootpart.lib Tag: 101412
  - 3
    - Bluetooth File Transfer Dear All: I have Windows CE PXA 270 based platform with CSR uart Bluetooth interface. I am looking for Blutooth file transfer application, from PDA to PC and from PC to PDA. So far no luck. If anyone suggest me where to find or willing to do it for me, it will be grat help. I have added OBEX server and client both to my image. My e-mail is jules.karim@viewsonic.com. Thanks Tag: Problem with bootpart.lib Tag: 101407
  - 4
    - Installing a new BSP Hi All, Can anyone tell me what I did wrong in installing a new BSP to the PB6? The following is what I did: 1. I converted a previous BSP from .cec to .pbcxml file. 2. I created a folder \MyTest\Catalog under \PLATFORM and copied that pbcxml file to that folder. 3. Create a new OS, but my new BSP was not in the available BSP list. Thanks in advance, James Tag: Problem with bootpart.lib Tag: 101406
  - 5
    - Have you succeed to make the nand flash as usb mass storage? Has anybody ever succeeded to make the nand flash as usb mass storage? According to the document, we need to set following REG items: [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Mass_Storage_Class] "Dll"="usbmsfn.dll" "Vendor"=dword:17CC "Product"=dword:2280 "InterfaceSubClass"=dword:06 "InterfaceProtocol"=dword:50 "DeviceName"="DSK1:" "Removable"=dword:0 The key operation is to change the "DeviceName"="DSK1:" I have tried to change the DeviceName, such as "DSK1" , "MSFLASH" etc, but not succeed yet! Is there anyone succeed? (CE5 , S3C2440 BSP) Tag: Problem with bootpart.lib Tag: 101400
  - 6
    - default.fdf file is restored after readRegistryFormOem calls I implemented Read/WriteRegistryToOEM functions on my target (CEPC) and everything worked fine for a while. Since some days, my registry is not more persistent and I dont know why. My readRegistryFromEOM function is called, data seems to be valid (I verified with a checksum computed in both read/write functions), but registry is not updated. I excluded default.fdf file from my image and now, registry is well updated at boot. My conclusions are : 1. my Read/WriteRegistryToOEM functions implementation is OK. 2. for an unknown reason, the system, after having updated registry with readRegistryFromEOM calls, is restoring default registry. Does someone know what could be this reason ? Thanks Dominique Tag: Problem with bootpart.lib Tag: 101396
  - 7
    - Problems with emulation ( Plat. Builder & VS2005 ) Hello, After some problems, I have connected VStudio 2005 with the emulator launched from the Platform builder as is reported in http://msdn2.microsoft.com/en-us/library/ms228708(VS.80).aspx . But know I have another problem: in the SDK I have developed, the only "target" that appears in the visual studio is the "CEPC 86 Release" , but not the "Windows CE 5.0 device" that is the one that connects with the emulator. What I'm doing wrong? Should I develope a SDK that includes the "Windows CE 5.0 device" ? ( I haven`t found how to do it ) Thanks Tag: Problem with bootpart.lib Tag: 101392
  - 8
    - A issue about KITL Hi everyone, I need your help! Now I met a problem when I use USB KITL. I can use USB KITL to download the image, but when the system starts. There is just one message in the PB output window: "Sp=ffffc7cc". Then I can get a debug message from serial debug port:"RndisMini rcv REMOTE_NDIS_RESET_MSG from host!". When I use USB protocol analyzer debug the USB BUS, I found the device send the data packet including debug message "Sp=ffffc7cc" to host, but the host didn't response to this packet. Then when 2 seconds past, the device restransmit it and timeout. After that HOST send REMOTE_NDIS_RESET_MSG to device and the connection failed. From the USB protocol analyzer I didn't find any protocol error. I just want to know why the host side didn't response to the debug message data packet. Thanks. Tag: Problem with bootpart.lib Tag: 101391
  - 9
    - Hive based registry Hi all, I wanted to implement hive based registry in an x86 based board, i am using wince 6.0(We have done the same in wince 5.0 successfully). I wanted to get hive registry in compact flash(I am using atapi driver). I could able to boot the system with "ram based reg", but for hive it is not coming up. i tried with setting PRJ_ENABLE_ FSREGHIVE as 1, no use. So here is the debug output, i deleted something. I have selected RAM and ROM file system also tried with ROM only file system.(See the last few lines) Thanks and Regards, Sankarraj Microsoft Windows CE BIOS Bootloader Version 2.3 (Built Apr 4 2005)INFO: code=0x4. INFO: code=0x4. INFO: code=0x4. Jumping to image (address=0x226DF0) Debug Serial Init SysInit: GDTBase=82474000 IDTBase=8247e8c0 KData=82479800 Windows CE Kernel for i486 Built on Feb 6 2007 at 14:58:03 INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb PCIBIOS:: BIOS Address static map to addr=a00e0000 GetPicRoutingIrqTable: Start search_pci_bios start CE Ethernet Bootloader found 32Bit BIOS Entry master_bios32=a00f0000 bios32_call_offset=10010 for CE/PC Return from First BIOS EAX=49435000 EBX=f0000,ECX=10000 EDX=31 32 PCI BIOS offset located.addr=10031 32 PCI BIOS Present EDX=20494350,EAX=1 EBX=f0210,ECX=10001 +GetRoutingOption search_pci_routing search_pci_routing found entry =a00f3e50 CE/PC GetRoutingOption, found ROM version for Routing table. GetRoutingOption return SUCCESS .AH=0 ScanConfiguredIrq with PCI Exclusive Irq Bit (wExClusive) =0 ScanConfigureIrq: BufferSize = 144 @ address 824777ea OSAXST0: Platform Name = Geode Platform OSAXST1: >>> Loading Module 'kd.dll' (0x83FDC57C) at address 0xC0010000-0xC003E000 in Process 'NK.EXE' (0x8247BC80) KD: Starting kernel debugger software probe (KdStub) - KD API version 22 Calling KDEnableInt (FALSE, NULL) without previously calling KDEnableInt (FALSE, p) OSAXST1: >>> Loading Module 'NK.EXE' (0x8247BC80) at address 0x80220000-0x80233000 in Process 'NK.EXE' (0x8247BC80) Message Queue support initialized, g_hMsgQHeap = d0040750 OSAXST1: >>> Loading Module 'filesys.dll' (0x83FBA198) at address 0xC0170000-0xC01EA000 in Process 'NK.EXE' (0x8247BC80) OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x83FBA2D0) at address 0xC0520000-0xC0556000 in Process 'NK.EXE' (0x8247BC80) FSDMGR!DllMain: DLL_PROCESS_ATTACH CertMod.dll not found, using old OEM Trust Model FileSystem Starting - starting with clean file system FSDMGR!STOREMGR_Initialize FSDMGR!InitializeStoreAPI FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at index 2FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 2 (Name="StoreMgr", MountFlags=0x1)FSDMGR!InitializeROMFileSystem: File System=ROM OSAXST1: >>> Loading Module 'romfsd.dll' (0x83FA43E4) at address 0xC01F0000-0xC01F6000 in Process 'NK.EXE' (0x8247BC80) FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index 3FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3 (Name="ROM", MountFlags=0x71)FSVOL: Opening existing volume FSVOL: Volume heap already initialized FSREG: Mounted ROM portion of boot registry FSVOL: Creating clean virtual volume FSVOL: Initializing volume heap FSREG: Mounted RAM portion of boot registry Override Serial Driver: No COM port selected for serial KITL transport, no override necessary. FS: Creating signal event SYSTEM/DevMgrApiSetReady FS: Creating signal event SYSTEM/PowerManagerReady FS: Creating signal event SYSTEM/GweApiSetReady FS: Creating signal event SYSTEM/BatteryAPIsReady FS: Creating signal event SYSTEM/NLedAPIsReady FSREG: Unable to read value "Start DevMgr" under HKEY_LOCAL_MACHINE\init\BootVars FILESYS: Starting boot phase 0. FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1) FSDMGR: File security disabled. FSDMGR!AutoLoadFileSystems: CurrentBootPhase=FSDMGR!PNPThread: Using PNPUnloadDelay of 4096 FSDMGR!PNPThread: PNPThread starting! 0, LoadFlags=1 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore FILESYS: RAM File System FSD_MountDisk registering folder "Object Store" FSDMGR!MountTable_t::RegisterVolumeName: Registered "Object Store" at index 4FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4 (Name="", MountFlags=0x44)FILESYS: Starting boot phase 1. FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0) FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1 FILESYS: Starting device and waiting for boot file system. OSAXST1: >>> Loading Module 'device.dll' (0x83F889EC) at address 0xC0380000-0xC0384000 in Process 'NK.EXE' (0x8247BC80) OSAXST1: >>> Loading Module 'devmgr.dll' (0x83F88B24) at address 0xC0390000-0xC03AF000 in Process 'NK.EXE' (0x8247BC80) OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x83F88C5C) at address 0xC0600000-0xC060A000 in Process 'NK.EXE' (0x8247BC80) OSAXST1: >>> Loading Module 'pm.dll' (0x83F88DA4) at address 0xC03E0000-0xC0400000 in Process 'NK.EXE' (0x8247BC80) *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 *** Fil+InitDeviceFileSystems FSDMGR!MountTable_t::RegisterVolumeName: Registered "$device" at index 5FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 5 (Name="$device", MountFlags=0x1)FSDMGR!MountTable_t::RegisterVolumeName: Registered "$bus" at index 6FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 6 (Name="$bus", MountFlags=0x1)-InitDeviceFileSystems: esys: Loaded device.dll FILESYS: Waiting for device manager to signal BootPhase1 completion. status is 1 Ceddk!CalibrateStallCounter: Enter Ceddk!CalibrateStallCounter: Could not find stall counter Ceddk!BeginCalibration: min(1194) max(1326) Ceddk!BeginCalibration: Calibration timed out (51 tries). Defaulting to 1 ms resolution. PlatformValidatePMRegistryreturningGDA::Chennai::Power Thread Started RunningDEVICE!DevloadInit DEVICE!InitDevices: Root Key is Drivers\BuiltIn. DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'busenum.dll' (0x83F7C0C0) at address 0xC03D0000-0xC03D8000 in Process 'NK.EXE' (0x8247BC80) DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\CgcePrep\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'cgceprep.dll' (0x83F75BAC) at address 0xC0E10000-0xC0E15000 in Process 'NK.EXE' (0x8247BC80) ERROR!!! Calling SetKMode ERROR!!! Calling SetKMode DeviceFolder::LoadDevice(Drivers\BuiltIn\CgcePrepDEVICE!RegReadActivationValues RegOpenKeyEx(Notify) returned 2. DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Notify' ) last 90 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Prefix) returned 2 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'pcibus.dll' (0x83F75CE4) at address 0xC0C60000-0xC0C7A000 in Process 'NK.EXE' (0x8247BC80) ATAPI:PCIConfig!DeviceConfig+(1) PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 31, Function 3 ATAPI:PCIConfig!DeviceConfig+(1) ATAPI:PCIConfig!DeviceConfig+(1) ATAPI:PCIConfig!DeviceConfig+(1) ATAPI:PCIConfig!DeviceConfig+(1) ATAPI:PCIConfig!DeviceConfig+(1) OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80) OSAXST1: >>> Loading Module 'atapi.dll' (0x83F75EDC) at address 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80) ATAPI:PCIConfig!DeviceConfig+(2) OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80) OSAXST1: >>> Loading Module 'atapi.dll' (0x83F75EDC) at address 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80) ATAPI:PCIConfig!DeviceConfig+(3) OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80) DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'atapi.dll' (0x83F6609C) at address 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80) DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device0\BusPrefix) returned 2 DEVICE!LaunchDevice: Init() failed for device 0xd004ae70 DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0xd029cf20 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device1\BusPrefix) returned 2 DEVICE!LaunchDevice: Init() failed for device 0xd004b070 DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0xd029cf20 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device2\BusPrefix) returned 2 FILESYS: Waiting for device manager to signal BootPhase1 completion. DEVICE!LaunchDevice: Init() failed for device 0xd004b270 DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0xd029cf20 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device3\BusPrefix) returned 2 DEVICE!LaunchDevice: Init() failed for device 0xd004b470 DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll atapi.dll, context 0xd029cf20 DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\ALI14531) last 6365 TicksDeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 10275 TicksDEVICE!RegReadActivationValues RegOpenKeyEx(Notify) returned 2. DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Notify' FILESYS: Waiting for bootable file system to be mounted. FILESYS: Waiting for bootable file system to be mounted. FILESYS: Waiting for bootable file system to be mounted. FILESYS: Waiting for bootable file system to be mounted. Tag: Problem with bootpart.lib Tag: 101389
  - 10
    - BUG: Windows CE 5.0 Update 070430_2007M04 April 2007 QFE I have just spent the best part of three days working out why my platform rebuilt from source control has stopped working. The answer is that the Microsoft PB 5.0 QFE for April 2007 has updated the source files for the default bus driver (defbus.h, defbus.cpp) but has *NOT* provided an update for the precompiled library files (defbuslib.lib, defbuslib.pdb) as is normal practice. Therefore, when you recompile a BSP where the code includes "defbus.h" and links to "defbuslib.lib" you have a mismatch between the library implementation of class DeviceFolder, and what your compiled code assumes!!!! As the class now has a new member variable, this breaks the implementation of the functions that are fully defined in the header file. The problem manifested itself by: sometimes causing memory violation exceptions, and, when no exception, not fully loading all of the detected devices on a bus (mine is PCI bus). The reason being is that the linked list of device folder is broken. WORKAROUNDS: 1. In Platformbuilder, open a workspace and navigate to PUBLIC\COMMON \OAK\DRIVERS\BUSENUM in the FileView tab. Right click and select "Build current project". Do this for both DEBUG and RETAIL builds, and repeat for all of the processors you need to support. Now SYSGEN your platform, specifying "clean before build". -or- 2. Clone the code in PUBLIC\COMMON\OAK\DRIVERS\BUSENUM\BUSDEF into your BSP using SysgenCapture (search the help for how to do this). Modify your existing drivers to use your local copy of "defbuslib.lib", then rebuild your BSP. Then SYSGEN your platform, specifying "clean before build". Regards, Andrew. Tag: Problem with bootpart.lib Tag: 101373
  - 11
    - Unable to expand the directories under PLAFORM in PB window Hi All I need some help regarding the issue which i am facing..i cant expand the directory under the WINCE500\PLATFORM from the wince plaform builder tool's window...ie no bsp is visible under platform. though they are actually there in the G:\wince500 folder(when i browse through the directory by exploring the correct path ), but i cant see it in PB window.... what can be the reason and the correct solution. I am able to buid the workspace successfully. i have tried to reinstall the PB tool but to no help. If someone has faced such a problem and forund the solution plz help me . thanks in advance regards Parsh Tag: Problem with bootpart.lib Tag: 101371
  - 12
    - What happened to all the posts from 6/6? Should I post again? Will it be possible to see them? Tag: Problem with bootpart.lib Tag: 101368
  - 13
    - 128MB SDRAM Configuration Hi All, I'm working on Mainstone II BSP with PXA270 on WinCE 5.0 Platform. My image (Nk.bin) works well when the SDRAM is configured for 64MB. When I configure the SDRAM for 128MB, It just hangs at the following point, EbootSendBootmeAndWaitForTftp ****** OEMVerifyMemory checking physical range [ 0xA0100000 ==> 0xA0DCF3D3 ]... ****** RAM address ****** rom_offset=0x0. ROMHDR at Address 80100044h Download successful! Jumping to image at 0x80101000 - physical 0xA0101000 Got EDBG_CMD_JUMPIMG Got EDBG_CMD_CONFIWindows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00 ProcessorType=0411 Revision=7 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 80106154 Sp=ffffc7cc PXA Configuration: MDCNFG Register --- 0x88000AD1 MDRFER Register --- 0x2093A01E MDMRS Register --- 0x00000000 I have posted my config.bib and oemaddress table for the reference: MEMORY IF IMGFLASH! ; Name Start Size Type ; ------- -------- -------- ---- RSVD 80000000 000FF000 RESERVED ARGS 800FF000 00001000 RESERVED NK 80100000 03000000 RAMIMAGE RAM 83100000 04FFFFFF RAM ENDIF IF IMGFLASH ; Name Start Size Type ; ------- -------- -------- ---- RSVD 80000000 000FF000 RESERVED ARGS 800FF000 00001000 RESERVED NK 94C80000 03F00000 RAMIMAGE RAM 80100000 03F00000 RAM ENDIF ; Reserve ZBANK virtual block (No physical memory ; is required to back this virtual range). ; ZBANK 90700000 00100000 RESERVED CONFIG IF IMGFLASH ROMSTART = 94C80000 ROMSIZE = 03F00000 ROMWIDTH = 32 ELSE AUTOSIZE = ON ENDIF KERNELFIXUPS=ON ; @CESYSGEN IF !NK_NKNOCOMP COMPRESSION=ON ; @CESYSGEN ENDIF !NK_NKNOCOMP ; @CESYSGEN IF NK_NKNOCOMP COMPRESSION=OFF ; @CESYSGEN ENDIF NK_NKNOCOMP IF IMGPROFILER PROFILE=ON ELSE PROFILE=OFF ENDIF OEMAddrtable DCD 0x80000000, 0xA0000000, 128 ; SDRAM bank 0 (64MB). DCD 0x88000000, 0x5C000000, 1 ; Internal memory storage(256KB). DCD 0x88100000, 0x58000000, 1 ; Internal memory control. DCD 0x88200000, 0x4C000000, 1 ; USB host. DCD 0x88300000, 0x48000000, 1 ; Memory control Memory-mapped registers. DCD 0x88400000, 0x44000000, 1 ; LCD Memory-mapped registers. DCD 0x88500000, 0x40000000, 32 ; peripherals Memory- mapped registers. DCD 0x8A500000, 0x3C000000, 16 ; PCMCIA S1 common memory space. DCD 0x8B500000, 0x38000000, 32 ; PCMCIA S1 attribute memory space. DCD 0x8D500000, 0x30000000, 1 ; PCMCIA S1 I/O space. DCD 0x8D600000, 0x2C000000, 16 ; PCMCIA S0 common memory space. DCD 0x8E600000, 0x28000000, 32 ; PCMCIA S0 attribute memory space. DCD 0x90600000, 0x20000000, 1 ; PCMCIA S0 I/O space. DCD 0x90700000, 0xE0000000, 1 ; Zero-bank (in reserved slot - no physical memory required). DCD 0x90800000, 0x14000000, 1 ; nCS5: eXpansion board header. DCD 0x90900000, 0x10000000, 1 ; nCS4: Ethernet controller. DCD 0x90A00000, 0x0A000000, 1 ; nCS2 (upper half): 2MB SRAM. DCD 0x90B00000, 0x08000000, 1 ; nCS2 (lower half): Board registers (FPGA). DCD 0x90C00000, 0x04000000, 64 ; nCS1: Storage(64MB). DCD 0x94C00000, 0x00000000, 64 ; nCS0: Boot Flash1 (64MB). DCD 0x00000000, 0x00000000, 0 ; end of table Also, RAM is contiguos. Am i missing any configuration here??? Tag: Problem with bootpart.lib Tag: 101367
  - 14
    - VIA CN700 Direct 3D Hardware support Hi again to all, we use a JetWay J7F2WE1G5D based on VIA CN700 ChipSet + integrated S3 Unichrome Pro graphics, we tried WinCE 5.0 and 6.0 with all the last update but we are unable to make work the Direct 3D hardware driver (if there is inside the BSP from VIA, no word that say NO 3D). All the 3D Test work using 3D reference driver (-ref parameter) with WinCE 5.0 but not with 6.0, the problem reported is always "unable to create D3DM device" There is someone that have an idea ?? Thanks and regards -- Massimo B. (Italy) R & D department Tag: Problem with bootpart.lib Tag: 101366
  - 15
    - ce 6.0 bsp clone error Hi, all? I'm trying to clone a ce 6.0 bsp to another one. Curiously the original bsp has nor catalog directory and .pbcxml file. But the bsp can be shown at pb 6.0 and I can create a project using the bsp. But when I try to clone the bsp, there happen the following error at the cloning process. "Could not find a part of the path 'C:\wince600\platform\mynewbsp\catalog\mynewbsp.pbcxml'. " How can I solve this error? Is there anybody to help me? Tag: Problem with bootpart.lib Tag: 101365
  - 16
    - Application hangs Hi, I am working with wince 5.0 and PXA270 mainstone II platform. I am running an application which executes some tests(like SD/CF Card read/write, Get wifi signal strength, Audio play etc..like this some test cases) continuously. I am printing "started" before start of first test and printing "end" after last test.After executing the last test again it will execute first test. Means it will print started..end started ..end continuously. This application executed successfully upto 2 hrs after that it is hanging. It is hanging after printing "end"( Task bar and application is hanging . I am not getting any exception in hyperterminal or any fatal error in the application) so i cant able to get the reason for hanging. Can any one tell what may be the reason ? Are there any wince tools are there to debug this issue? Thanks in advance Tag: Problem with bootpart.lib Tag: 101363
  - 17
    - Wince application hangs Hi, I am working with Wince 5.0 and PXA 270 mainstoneII platform. I am running one applicatin which executes some tests (like SD/CF card read/write tests, get wifi signal strength,Audio play etc.. like this some many tests) continuously. I am printing "started" before first test and printing "end" after last test.After executing last test again it will execute the first test .This will happen continuously. Means it will print started..end ..started..end .. This application is running successfully upto 2 hrs after that it is hanging( Task bar and application is hanging. I am not getting any exception in hyper terminal or fatal error in the application while hanging). I cant able to get the reason for this hanging. Can any one tell me what may be the reason. Are there any wince tools are there to debug this issue?? Thanks in advance Tag: Problem with bootpart.lib Tag: 101361
  - 18
    - about .rc file control hi. i have one question. i want to change control panel(power). so i define one vaulue in MYPROJECT.BAT file. the define value is "PLATCFG_BATTERY=1". of course set to MYPROJECT.CMN file. after i checked this value in "\CLPMAIN\power.cpp" result is define TRUE. but i checked this value in cplmain.rc file. result is define FALSE. how to control .rc file? under code is my test code. - MYPROJECT.BAT SET PLATCFG_BACKUPBATTERY=1 - power.cpp #ifdef PLATCFG_BACKUPBATTERY RETAILMSG(1,(_T(" [PM:(power.cpp)] PLATCFG_BACKUPBATTERY is define \n"))); // enter here #else RETAILMSG(1,(_T(" [PM:(power.cpp)] PLATCFG_BACKUPBATTERY is not define \n"))); #endif // PLATCFG_BACKUPBATTERY - cplmain.rc IDD_BATTERY DIALOG DISCARDABLE 0, 0, 132, 140 STYLE DS_CONTROL | WS_CHILD | WS_VISIBLE | WS_CLIPSIBLINGS BEGIN #ifdef PLATCFG_BACKUPBATTERY LTEXT "Charging",IDC_STATIC_CHARGE_MAIN,4,40,122,8 CONTROL "Progress2",IDC_PROGRESS_MAIN,"msctls_progress32", PBS_SMOOTH | WS_BORDER,12,59,102,9 LTEXT "0",IDC_STATIC,5,59,10,8 LTEXT "100",IDC_STATIC,116,59,13,8 LTEXT "Charging",IDC_STATIC_CHARGE_BACK,5,98,122,8 CONTROL "Progress2",IDC_PROGRESS_BACK,"msctls_progress32", PBS_SMOOTH | WS_BORDER,12,117,102,9 LTEXT "0",IDC_STATIC,5,117,10,8 LTEXT "100",IDC_STATIC,116,117,13,8 GROUPBOX "Main Battery",IDC_STATIC,0,24,131,51 GROUPBOX "Backup Battery",IDC_STATIC,0,81,131,51 #else LTEXT "Main battery",IDC_STATIC_MAIN,5,43,43,8 LTEXT "Charging",IDC_STATIC_CHARGE_MAIN,6,52,122,8 LTEXT "Backup battery",IDC_STATIC_BACK,5,53,49,8,NOT WS_VISIBLE GROUPBOX "",-1,25,42,105,6 GROUPBOX "",-1,53,53,74,6,NOT WS_VISIBLE CONTROL "Progress2",IDC_PROGRESS_MAIN,"msctls_progress32",PBS_SMOOTH | WS_BORDER,12,63,102,9 LTEXT "0",-1,5,63,10,8 LTEXT "100",-1,116,63,13,8 LTEXT "Charging",IDC_STATIC_CHARGE_BACK,5,64,122,8,NOT WS_VISIBLE CONTROL "Progress2",IDC_PROGRESS_BACK,"msctls_progress32",PBS_SMOOTH | NOT WS_VISIBLE | WS_BORDER,12,75,102,9 LTEXT "0",-1,5,75,10,8,NOT WS_VISIBLE LTEXT "100",-1,116,75,13,8,NOT WS_VISIBLE #endif no entered "#ifdef PLATCFG_BACKUPBATTERY" construction. what kind of need another control? plz...advice to me. aaplks@hotmail.com Tag: Problem with bootpart.lib Tag: 101360
  - 19
    - Win CE 5.0 Yearly Update (through 12/31/2004) iHello, I want to get the updates for 2004, the link on the WIn CE Home page has been changed to the Download page and this MSI is not available or cannot be found. Does anyone have a copy of this ? Thanks Aidan Tag: Problem with bootpart.lib Tag: 101355
  - 20
    - need help trying to integrate IPSM Hi all, I'm trying to include Intel PSM in our system, but with no success. There are many things that I don't know, or don't understand. We work with windows CE 6.0, PXA270, MAINSTONEIII bsp, P30 single 64MB flash. We have IPSM version 4.0. We work with MCPII_MODULE. The reason we are using PSM is because we want to be able to save some small text files in flash memory. No more than that. I worked according to the instructions in the Porting Guide of the PSM. I calculated the flash starting address according to the table in oemaddrtab_cfg.inc. In the table it is 0x9AA00000, but this is cached. In ifm_sys.c I need to put an uncached address, therefore it is 0xBAA00000. (As far as I understand the gap between them - 0x20000000- is set by DUAL_MAP_OFFSET). But in what situations do I have to change this value? I didn't specify a full map of the flash, only what I need. I only have one SA (Sub-Array), which I located in the address 59MB after flash start, and gave it a size of 4MB(1MB is left for safety). This way I don't touch the boot and the image code. For our needs 4 MB is much more than enough. I don't know whether it's ok to do it like that. In the file psmfsd.reg In the section which is "no root no hive" I erased all extras, and now there is only "PSM1", with volume name "IPSM1". In the other sections of that same .reg file I only changed the volume name to "IPSM1". I don't really understand what I have to write in the batch file- mainstoneiii.bat. Do I need to set ROOT, HIVE_REGISTRY or both? (as of now they're both set). What I want is that when the system comes up, I'll be able to see the directory "IPSM1". I don't really care whether it's inside "My Device", or anywhere else, I just want to be able to know where it is, be able to insert files inside it, write some text to these files, and the files be saved in flash. And what about checking some check-boxes in the catalog? Which ones need to be checked? As of now what I have checked is from Storage Devices\MSFlash Drivers\Intel StrataFlash NOR Driver , from File Systems and Data Store\File System-Internal\RAM and ROM File System, from File Systems and Data Store\Registry Storage\Hive-based Registry. Are these correct? Should I check some others? What happens now in my system is that there is no IPSM in it. I wait until after the system comes up, and then try to look for the IPSM directory, and of course, I can't find it. Probably because it isn't thereâ?¦. Please help me in solving this problem. Thank you all very much for your time Tag: Problem with bootpart.lib Tag: 101349
  - 21
    - build query hi all, I am working in applicaton development on top of bluetooth stack. wince has given some sample drivers in the following path: C:\WINCE500PUBLIC\COMMON\OAK\DRIVERS\BLUETOOTH\SAMPLE In the workspace if I see in the file view these are defaultly excluded from the build. How I can make these are part of my image. by including to the build. Any body who knows about this pls reply me. Thanks and regards, srikanth Tag: Problem with bootpart.lib Tag: 101343
  - 22
    - Attach emulator to Visual studio 2005 Hello, I cant attach my emulator from Platf. Builder with Visaul studio 2005. I have followed all the steps of the topic http://msdn2.microsoft.com/en-us/library/ms228708(vs.80).aspx but it still doesn't works. I launch the emulator with PB and I execute the ConmanClient2.exe and the MCaccept.exe and then I run Tools-> connect to device in the VS2005. but it fails ( after some time) and says "activesync is not instaled". I have configured the VS2005 Tools->Options->device with the IP of the emulator, I also have changed my PC IP address to be in the same network than the emulator ( I dont know if it's necessary).. but it doesn't work. I have also tried enabling and disabling KITL as I have read somewhere... I don't know what I'm doing wrong. The only thing I doubt is about the "target" combobox in the Platform builder, witch I have set to "CE device" ( if I set it to Windows CE 5.0 device when I try to attach it fails with: Warning: Debugger service map is set to none. If your image has debugging support it may not boot properly. Cannot access selected Device from service host. Debugger could not initialize connection. The Kernel Debugger is waiting to connect with target. The Kernel Debugger has been disconnected successfully. ) any idea? thank you very much and sorry for my english Tag: Problem with bootpart.lib Tag: 101338
  - 23
    - catalog query hi all, This is srikanth. I am writing application to test USB driver in the wince 5.0 and I am using intel PXA27x platform (Mainstone II board). I am having very basic doubt in the wince: In the right side catalog items these are the main components: 1. BSP's 2. CORE O.S 3. DEVICE DRIVERS 4. PLATFORM MANAGER. In the BSP's/ INTEL PXA27x Dev Platform: ARMV4, there is a usb host is there, In the CORE O.S/Wince Devices, USB Host Support is there, and in the DEVICE DRIVERS, there is USB Host is there. What is the difference between these three USB Hosts? Any body having idea please differentiate clearly. If I want to test the USB Driver (Let suppose PEN Drive (usb Mass-storage device) by adding componets to the O.S design view. Which host I need to add to the o.s design. and at the same time for client driver: which componet I need to add to the o.s design. i.e I want to test usb driver by using the pen-driver by opening the pendrive and creating a files in that, or open a file in the pen-drive by using application program. I am not getting any icon or any indication in the desktop when I attatch a USB device(pen drive) to the usb port of the intel board. In our board touch screen is not working, only display we can able to see. In my application I used create file function. The code snippet is shown below: int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPTSTR lpCmdLine, int nCmdShow) { HANDLE hFile; hFile = CreateFile((LPCTSTR)"\\USB Disk", GENERIC_WRITE| GENERIC_READ, 0, 0, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL); if( hFile == INVALID_HANDLE_VALUE ) { DEBUGMSG(1, (L"File not Copied successfully*************")); } else { DEBUGMSG(1, (L"File Copied successfully*************")); } return 0; } The createfile was giving invalid handle, because of path was not correct. what path I need to mention in the createfile function. Any body who is having idea on this please reply me. Thanks and regards, srikanth Tag: Problem with bootpart.lib Tag: 101337
  - 24
    - Wince Application is hanging Hi all, I am working with WINCE 5.0 and PXA 27X . I am running one application which will run some tests (like Audio play, SD and CF Card read/write,get wifi signal strength etc..like this so many tests are there) continuously. After the test is executed ,again it will start executing from first test. This should happen continuously. I am printing "started" before start of first test and "end" after last test. The application is running continuously fine for some duration (2 hrs)after that the application is hanging after displaying "end".(Task bar and application is hanging .It is not showing any exception in the hyper terminal or it is not giving any fatal application error) So i cant able to find what test is causing this problem. Because it is hanging after "end" .i am not getting any hint. Can anyone suggest What may be the problem ,how to debug this.Is there any wince tools are there to resolve this issue. Thanks in advance Tag: Problem with bootpart.lib Tag: 101336
  - 25
    - Display problem using ddi_hflat.dll I am using a board that uses SH7760 processor with onboard epson S1D13806 controller for graphics display. I am successful in bringing up the NK.bin by modifying the ddi.c in the OAL to initialize the epson controller. I am able to see the Wince startup screen with start button and taskbar on the LCD display. To verify the working of the hflat driver, a sample application was executed at the OS startup. I have a problem, the display is refreshing abnormally from top to bottom. The LCD resolution is 640 * 480, 8BPP, 60Hz frequency. I saw the previous post on similar issues, but those are not helping me. The same settings are working perfectly on Vxworks. Is there anything related to FQCR settings in the OAL/STARTUP/Startup.src file that i need to make? any pointers on this would be greatly helpful. Tag: Problem with bootpart.lib Tag: 101331
- Next
  - 1
    - wavedev2 driver - multiple channels and sw mixer I have an unusual audio setup! I have three stereo audio output channels (I2S) that I need to support from one CE 6 audio driver. I don't want to do any mixing or volume control of the signals, the "codec" will do that. One application will give me data at 8kHz which I will always need to upsample to 44.1kHz and pass onto the codec on a particular I2S pin. Another will supply 11.025kHz data which I again need to upsample to 44.1kHz and output always on a particular I2S pin. The third application will supply 44.1kHz data which I need to output on a third fixed I2S channel. I intend to support this by returning that my wavedev2 driver supports three output channels in response to the WODM_GETNUMDEVS message, then the application software can supply the correct device ID in calls to waveOutOpen. I have a couple of questions: 1) I understand that I can't use the swmixer because I have more than one output channel? So, I wanted to indicate that my driver can support 8kHz, 11.026kHz and 44.1kHz rates directly, then do the sample rate conversion inside my driver. However, it doesn't appear that I can indicate in a WAVEOUTCAPS that the driver can cope with 8kHz data - only 11.025, 22.05, or 44.1 looking at the defines in mmsystem.h Could I use the swmixer? I don't want it mixing any of the audio streams together, but maybe I could rely on it to do the upsampling? 2) Is there a better way of allowing application software which audio output channel to open when the driver supports several? Regards, Matthew Tag: Problem with bootpart.lib Tag: 101323
  - 2
    - USB mouse Can I connect one USB mouse or any other device into (mini)USB of my Windows CE device and get its input by code? I only need to connect a simple (physical) on/off button into my Windows CE to input a start/stop when my application is running so that is can do something due to this input: any idea? Mhaxx Tag: Problem with bootpart.lib Tag: 101319
  - 3
    - SYSGEN :****** B A T C H R E C U R S I O N exceeds STACK limits ****** Hi all, Do anybody know what this error is for ??? CEBUILD: Running sysgen preproc (for COMMON) Starting sysgen phase for project ( common ) ****** B A T C H R E C U R S I O N exceeds STACK limits ****** Recursion Count=1239, Stack Usage=90 percent ****** B A T C H PROCESSING IS A B O R T E D ****** PlatX_2430 - 0 error(s), 0 warning(s) ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ========== i am getting this error whenever I am trying to sysgen the platform (with all options i have tried out) I dont wanna re-install the platform builder so please if anybody knows it that will be great help to me. :) Thanks, Nagesh Tag: Problem with bootpart.lib Tag: 101318
  - 4
    - bsp clone error Hi, when i try to clone mainstone bsp with ce 6 i get Could not find file 'C:\WINCE600\platform\MainTest\catalog\MainTest.pbcxml'. error. Thanks Tag: Problem with bootpart.lib Tag: 101316
  - 5
    - *_NotInstalled.txt files after installing QFEs We (and our customers) are constantly having problems with QFEs not installing properly: Even when starting from a fresh PB 5.0 installaion and installing QFEs in the proper order, the '\WINCE500\Updates'-folder contains '*_NotInstalled.txt' files, that show that some files of some QFEs didn't get installed. At first we thought it was because the installation routine of such a QFE has found that the patches (or newer ones) to the respective files have already been installed, but we have seen cases where new files (for Net CF 2.0) should have been added, but just weren't installed at all. It seems to make a difference whether we install, e.g. the 2006 RollUp or the monthly 2006 QFEs (in order), whether 2004/2005-RollUps are installed or not, etc. Unfortunately the most obvious way of installation (PB5 -> RollUp2006 -> monthly 2007) does not necessarily result in the least '_NotInstalled'-files. The best result I was so far able to achieve is 'PB5 -> RollUp 2004 -> RollUp 2005 -> Monthly 2006 -> Monthly 2007' but even then 2007M01 and 2007M02 resulted in patches not getting installed (IP and WMT for 2007M01 and DirectX for 2007M02). What is going on here? This is really annoying, because each time one of our customers wants to use one of our BSPs it is a long-time trial-and-error phase until the customer has a QFE combination that works. Can anyone help? Tag: Problem with bootpart.lib Tag: 101313
  - 6
    - Error in DebugVersion of wince5.0 Hi all, I am facing a problem with wince 5.0 debug version. I am using an imx31 board (arm v4i)and wince 5.0 bsp for ur project.I have a GPIO driver for which i need to trigger GPIO Interrupts externally.The IST part, i have implemented in a wince service.Now If i have more than one event(wait for multiple objects will have an array of 2 elements as a parameter), the control goes to D: \WINCE500\PRIVATE\WINCEOS\COREOS\NK\KERNEL\schedule.c..ie inside the function DWORD SC_WaitForMultiple( DWORD cObjects, CONST HANDLE *lphObjects, BOOL fWaitAll, DWORD dwTimeout ) and I am getting a DEBUGCHK Failed message. This is my code for waiting for the event to be signalled... DWORD dwStatus =WaitForMultipleObjects(numberOfEvents, g_hGpioEvent, FALSE, INFINITE); >From this point it goes to schedule.c and the system hangs. But if there is only one event it is working as expected. What would be the cause of this issue??? Earlier I have checked the working of my service(IST) ,by simulating events using an application(not using real external interrupts from arm processor).Then it was working fine for all events... Any help is appreciated.... Thanks in advance Sereena Tag: Problem with bootpart.lib Tag: 101308
  - 7
    - Disable TouchCalibrate I am developing a CE5 device driver, what bothers me is that every time system boot up, a TouchCalibrate program will run automatically. Calibration must be done before desktop opens, spend quite much time. I searched reginit.ini, there is no entry for TouchCalibrate.exe, where does this program be loaded and how to disable it? Tag: Problem with bootpart.lib Tag: 101304
  - 8
    - strataflash P30 and stratad.dll Hi, Does anyone know 100% if the stratad.dll driver supports Intel P30 flash? I am trying to debug it and everything looks fine until it tries to do buffered write and then I get the error messages you can see in the log below. Do I need to write my own flash driver? I found someone was having a similar problem, the last posting was in January but there was no reply to it. Please help. Thanks Anand 4294818162 PID:400002 TID:650002 Kernel DLL 'stratad.dll' needs thread creation/deletion notification 4294854535 PID:400002 TID:900002 FSDMGR!PNPThread: PNPThread starting! 398961 PID:400002 TID:650002 VerifySignatures: invalid block detected, calling FMD_EraseBlock 469004 PID:400002 TID:650002 STRATA Error: Block 0 locked ... Lower flash. 469004 PID:400002 TID:650002 STRATA Error: Block 0 locked ... Upper flash. 469004 PID:400002 TID:650002 FMD_EraseBlock: Unable to whack block signature 469004 PID:400002 TID:650002 VerifySignatures: error in FMD_EraseBlock, bailing 469004 PID:400002 TID:650002 ERROR: FMD_Init: Error while trying to verify block signatures. 469004 PID:400002 TID:650002 Unknown: DEBUGCHK failed in file C:\ymzki\private\winceos\DRIVERS\msflash\src\.\falmain.cpp at line 201 Tag: Problem with bootpart.lib Tag: 101303
  - 9
    - Win CE QFE's Hi We are using a board from a 3rd party supplier who says that all QFE's must be installed prior to Aug 06...not really a problem as such, but I can only find QFE's for 2006, a yearly rollup for 2005 and there is a broken link in the WIndows CE home page to 2004 yearly rollup...my question is how far back do I need to go... I am currently using an Eval copy of Platform Builder...while I'm waiting for my real copy to arrive from the distributor. Has anyone had to anything similar ? Thanks Aidan Tag: Problem with bootpart.lib Tag: 101301
  - 10
    - How to use platform builder to debug a NDIS driver on pocket pc device Hi, I'm trying to use the platform builder to debug a virtual NDIS miniport driver on a pocket pc device. This device has a USB connection to my dev machine. The device already has a CE run-time image from third party. All I'm doing is add a NDIS miniport driver. I wonder how I should set up the "Connectivity Options" without having to download the runtime image so that I can successfully attach to the device add start debugging? Thanks. Daniel Tag: Problem with bootpart.lib Tag: 101296
  - 11
    - Allocating Internal Flash as Root I am sure this has been asked, but I can't for the life of me find the answer I am after. I am creating a new platform based on the MX21 ADS board. It comes with 64MB of flash. My device will power down completely and so I need to set up the file and object store as well as the registry so that it is all stored in the flash instead of RAM. The first thing I need to do is figure out how to configure my system in PB 5 to set aside half of the flash for a file system and then make it the root file system. I was reading the documentation and it seemed to indicate that what I want is the ROM only file system. I am still a little unclear because one place indicated that and another indicated that ROM only file system means there is no place to store stuff. The second thing is to make sure I have the registry settings right so that the hive based registry (which I also chose for my device) will point to the above mentioned flash area. I guess a third question is whether this is a good idea and better than using the RAM based system and doing some kind of backup to flash when the user powers down the unit. Thanks, Tony Tag: Problem with bootpart.lib Tag: 101290
  - 12
    - flash FMD_EraseBlock hangs Hi, I am trying to add support for strata flash disk partition in CE6.0 a MainstoneIII BSP clone. In debug output it hangs after FMD_EraseBlock. I copy the debug output below. Any help will be greatly appreciated. Thanks a lot Igor ..... FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1) FSDMGR: File security disabled. FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore FILESYS: RAM File System FSD_MountDisk registering folder "Object Store" FSDMGR!MountTable_t::RegisterVolumeName: Registered "Object Store" at index 4 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4 (Name="", MountFlags=0x46) FSDMGR!PNPThread: Using PNPUnloadDelay of 4096 FSDMGR!PNPThread: PNPThread starting! FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=MSFlash FSDMGR!AutoLoadBlockDevice: Auto-loading block driver from "Drivers\BuiltIn\StrataFMD" FSDMGR!MountStore: Attaching new storage device "MSFlash" OSAXST1: >>> Loading Module 'stratad.dll' (0x83F83708) at address 0xC0A30000-0xC0A51000 in Process 'NK.EXE' (0x80109AA0) OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x83F83840) at address 0xC05E0000-0xC05EE000 in Process 'NK.EXE' (0x80109AA0) Kernel DLL 'stratad.dll' needs thread creation/deletion notification VerifySignatures: invalid block detected, calling FMD_EraseBlock Tag: Problem with bootpart.lib Tag: 101286
  - 13
    - code page at load time Hello, I have file system drivers, that are loaded during system start. These drivers need to convert a WSTR to an ANSI string using WideCharToMultiByte during startup. This function fails in the first driver and succeeds at the second. With Platform Builder I could see that during the first call the code page was not valid yet. (Inside WideCharToMultiByte the function NormalPageFromPage returns 0.) When are codepages initialized? How can I make sure, that this API is ready? Best regards, Helge -- Time is an ocean but it ends at the shore Tag: Problem with bootpart.lib Tag: 101284
  - 14
    - Indic support I am trying to add indic support(marathi, mangal font) with a DOTNET framework based application on WinCE5.0. It is observed that on addition of the complex sripting support the application paints very slowly. Let's say for a keyboard to be displayed paints the screen line by line When the complex scripting support is removed, the same application works fine. I have added the following catalog items in the image: SYSGEN_FONTS_MANGAL SYSGEN_KBD_MARATHI we are using PXA270 312 MHZ processor with mainstoneii BSP. could some one help me ascertain the cause and solution for the same?? Thanks and Regards, Ann Tag: Problem with bootpart.lib Tag: 101277
  - 15
    - Concepts for saving PB Workspaces Hello there, at the moment I am thinking about saving the different versions (development stages) of a workspace I have. The problems to consider are the following: 1) Different images/workspaces with different catalog items (so v1.1 could have two items more then my v1.0, according to customer wishes) 2) The same platform in a newer workspace (same BSP), but slightly different hardware design (e.g. different bus addresses), which means that the sources of the platform must be changed. Of course I have to go back to my prior platform soures, when I go back to a prior workspace-version. 3) Changes in 3rd party drivers. All these things are of course in different folders, normally in wince500\PBWorkspaces\myWorkspace wince500\Platform\myPlatform wince500\3rdParty\mySpecialDriver The simpliest (and most brutal) way would be to put these folders into a ZIP-archive and call it "MyImageV1.zip". If I make major changes and want to preserve the old version I make a new ZIP-archive called "MyImageV1.1.zip" and so on. So I could always step back. Another way would be a tool like CVS or Subversion or similar. This would be smarter, but the trouble here is the fact, that the things to save are stored in very different folders, and there are a lot of other things on the same folder levels, which need not be saved. At the moment I would prefer the second option, maybe someone has another idea or even experiences? Greetings, Eike Tag: Problem with bootpart.lib Tag: 101276
  - 16
    - Cleanworkspace.bat for CE 6 I am a big fan of the Steve's CleanBSP and CleanWorkspace batch files for CE 5. They scrub the directories so whats left is the minimum needed for source control archiving. I would like to see these updated for CE 6.0. I am assuming CleanBSP is good as is ??? Cleanworkspace should probably: 1) Renamed to CleanOSDesign 2) remove sdk stuff Can you also safely delete the xxx.pbxml.user file? How about the __CEBASE_FEATURES.txt file? I also have a "target" directory under the OAK directory which looks to be some subproject stuff .. can this be blown away. Is there anything else I missed? Tag: Problem with bootpart.lib Tag: 101272
  - 17
    - GWES exception in RELEASE build but fine in DEBUG build after run a fixed time! In my RS485-serial driver, I meet a problem that when run a fixed time(run the test application called the 485-driver about 3 hours) in the RELEASE build enviroment, there is a exception raised like below: --------------------------------------------------------------------------------------------------------- RaiseException: Thread=8b9ec540 Proc=89b17390 'gwes.exe' AKY=00000049 PC=00000000(???+0x00000000) RA=882479c8(NK.EXE +0x000479c8) BVA=00000003 FSR=00000003 Exception 'RaiseException' Thread=8b9ec540 AKY=00000049 PC=88205af4 BVA=00000003 R0=00000000 R1=89b195a0 R2=00000017 R3=00000017 R4=89b16d88 R5=00000001 R6=00000cfd R7=00000190 R8=00000cfd R9=00000000 R10=ffffc764 R11=882479c8 R12=88212080 SP=00000000 Lr=ffffffff Psr=6000009f Halting system --------------------------------------------------------------------------------------------------------- But the same code and the same OS design under DEBUG build will not happen(I run the same test application called the 485-driver about 13 hours). The test application has verified with no memory leak. Does anybody meet this issue before?? Thanks in advance! Tag: Problem with bootpart.lib Tag: 101260
  - 18
    - Intel StrataFlash problem Hi All, I am trying to use the unused upper portion of my flash chip as a disk device to store files. I am using WinCE6.0, MainstoneIII BSP clone. I am posting below the related debug output and my registry settings. Now I am getting error 126 all the time which means "module not found" I think. I checked that stratad.dll module is there. Thanks Igor ... FSDMGR!DllMain: DLL_PROCESS_ATTACH FileSystem Starting - starting with clean file system FSDMGR!STOREMGR_Initialize FSDMGR!InitializeStoreAPI FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at index 2 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 2 (Name="StoreMgr", MountFlags=0x1) FSDMGR!InitializeROMFileSystem: File System=ROM OSAXST1: >>> Loading Module 'romfsd.dll' (0x83F8C000) at address 0xC0270000-0xC0277000 in Process 'NK.EXE' (0x80109AA0) FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index 3 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3 (Name="ROM", MountFlags=0x71) Succeeded on CheckFileRestoreFile(0x00840003) called fDelete = TRUE FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1) FSDMGR: File security disabled. FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore FILESYS: RAM File System FSD_MountDisk registering folder "Object Store" FSDMGR!MountTable_t::RegisterVolumeName: Registered "Object Store" at index 4 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4 (Name="", MountFlags=0x46) FSDMGR!PNPThread: Using PNPUnload Delay of 4096 FSDMGR!PNPThread: PNPThread starting! FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=MSFlash FSDMGR!AutoLoadBlockDevice: Auto-loading block driver from "Drivers\BuiltIn\StrataFMD" FSDMGR!MountStore: Attaching new storage device "MSFlash" FSDMGR!MountStore: Failed mounting store "MSFlash"; error=126 FSDMGR!StoreDisk_t::~StoreDisk_t: deleting store (D0042650) FSDMGR!AutoLoadFileSystems: Unable to auto-load HKLM\System\StorageManager\AutoLoad\MSFlash; error=126 FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0) FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1 FSVOL: Using system database volume "\Documents and Settings\default.vol" BuildPath: Documents and Settings OEM: Not cleaning system hive FSVOL: Creating new volume (size=28672 bytes) FSVOL: Initializing volume heap FSREG: Unable to read value "RequireCertMod" under HKEY_LOCAL_MACHINE\init\BootVars FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars FSREG: Logging in default user. FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars ... -------------------------------------------------------------------------- [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\StrataFMD] "Key"="Drivers\\BuiltIn\\StrataFMD" "Flags"=dword:4 "MemLen"=dword:02800000 "MemBase"=dword:9c180000 "Order"=dword:0 "FriendlyName"="MSFLASH Driver" "IsPairedFlash"=dword:1 "WriteBufferSize"=dword:40 "BlockSize"=dword:40000 "IClass"="{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" "Profile"="MSFlash" "Prefix"="DSK" "Ioctl"=dword:4 "Dll"="stratad.dll" [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\MSFlash] "DriverPath"="Drivers\\BuiltIn\\StrataFMD" ; LoadFlags 0x01 == load synchronously "LoadFlags"=dword:1 "Order"=dword:0 "BootPhase"=dword:0 [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\Relfsd] "BootPhase"=dword:2 "MountFlags"=dword:1 [HKEY_LOCAL_MACHINE\System\StorageManager\FATFS] "Flags"=dword:48 "Util"="fatutil.dll" "CacheDll"="diskcache.dll" "CacheSize"=dword:0 "EnableCache"=dword:1 "Paging"=dword:1 "Dll"="exfat.dll" "DisableAutoFormat"=dword:0 "DisableAutoScan"=dword:1 "FormatExfat"=dword:1 "FriendlyName"="exFAT FileSystem" [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles] "Folder"="Mounted Volume" "PartitionDriverName"="MSPART" "DefaultFileSystem"="" "MountFlags"=dword:0 "AutoFormat"=dword:1 "AutoPart"=dword:1 "AutoMount"=dword:1 ; Support XIP in IMGFS [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\IMGFS] "XIP"=dword:0 "MountAsROM"=dword:1 "MountAsHidden"=dword:0 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash] "MountPermanent"=dword:1 "Folder"="NOR Flash" "Name"="MSFLASH for STRATAFLASH" "MountHidden"=dword:0 "MountAsROM"=dword:0 "PartitionDriver"="mspart.dll" [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS] "MountAsROM"=dword:0 "MountHidden"=dword:0 Tag: Problem with bootpart.lib Tag: 101258
  - 19
    - What is the right way to specify coredll.lib ?? for CE 6.0 drivers I see coredll called out two different ways in the sources file. What is the "correct" way"? 1: TARGETLIBS= \ $(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib 2: TARGETLIBS=\ $(_SYSGENSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib Does ether one have an advantage over the other? Tag: Problem with bootpart.lib Tag: 101240
  - 20
    - Synchronization with kernel thread Hello, I need to run a thread in the WinCE 5.0 OAL. The thread is necessary for synchronizing some operations with several (client) threads. The client thread will enque a request and set an event to make the kernel thread do the work. Therefore I created an event and a thread. The thread function should wait for event, reset it, do the work and wait again. Unfortunately SC_:WaitForMultiple returns WAIT_OBJECT_0 immediately, even if the event has not been set. The event and thread creation is done in context of filesys.exe when the OEM registry is flashed the first time. _WriteRegistryToOEM() { s_hWaitForStart = SC_CreateEvent(NULL, TRUE, FALSE, NULL); hThread = CreateKernelThread(WorkerThread, NULL, 251, 0); } WorkerThread() { while (TRUE) { dwWaitResult = ::SC_WaitForMultiple (1, &s_hWaitForStart, FALSE, INFINITE); ::SC_EventModify(s_hWaitForStart, EVENT_RESET); // do work } } So the synchronization does not work at all, because SC_WaitForMultiple never waits. How can I achieve the synchronization? Best regards, Helge -- Time is an ocean but it ends at the shore Tag: Problem with bootpart.lib Tag: 101236
  - 21
    - Can the serial driver and OEMWriteDebugByte work concurrently? If I use the serial driver to modify the stopbit, it will disconnet KITL. I guess that this is casued by that the serial driver is working when KITL is printing message with OEMWriteDebugByte concurrently. It seems not reasonable that OEMWriteDebugByte can work together with serial driver. But why does the KITL still call OEMWriteDebugByte to print debug message? Please give me some suggestion about this issue. Best regards, Tag: Problem with bootpart.lib Tag: 101233
  - 22
    - USB Host Virtual Serial Drivers CE6 ?? Has anyone been able to get Virtual serial USB Host drivers, particularly the CE 6 ones. FTDI have a driver for CE4.2 to CE5. FTDI say that the driver won't work with CE6, which I haven't tried, and wouldn't expect to work. I have a device built around the FTDI hw so am keen to get a CE6 driver. Tag: Problem with bootpart.lib Tag: 101228
  - 23
    - Write file from http-webserver Hi I have a windows ce device with the http-webserver. I am trying to write a xml-file, or just a txt-file, from an ASP-website. But I cannot figure out how. Somebody got some experience on that? What I tried till now: 1=2E <%@ LANGUAGE =3D "VBSCRIPT"%> <% Dim FSO Dim objStream Set FSO =3D CreateObject("Scripting.FileSystemObject") ... %> Gives me this error: Microsoft VBScript runtime error: '800a01ad' Description: ActiveX component can't create object: 'Scripting.FileSystemObject' 2=2E <script language=3D"JScript">  </script> Gives me the error, that I don=B4t have permissions to write... How can I get permissions or a way to write files on the server-side? Thanks in advance Tag: Problem with bootpart.lib Tag: 101225
  - 24
    - WINCE Idle state Hi Team, We are Implementing power management through Wince for pxa27x. In this, We need to put the processor into idle, standby and sleep mode. We are trying to map user idle <--> Idle, system Idle<-->standby and Suspend <--> sleep. here, my suspend is working properly(it is using OEMpoweroff) but i m a bit confused the regarding IDLE. Which function should be called for the User Idle and System Idle. Can any one make me clear which function(i mean kernel function or OEM function) should be called for user idle and kernel Idle. Thanks and Regards, Ranjit Ranjan EggHeadCafe.com - .NET Developer Portal of Choice http://www.eggheadcafe.com Tag: Problem with bootpart.lib Tag: 101224
  - 25
    - UDP Send issue I'm using GPRS connection to send UDP data to a pc. I will also be sending data from the PC to my wince device thro' GPRS. Situation 1: When I try to send data(72 bytes) immediately after my startup routine(say after creating socket), 'send' function says success but the PC has not received anything. But when I send after receiving some data from the PC, my device is transmitting 72 bytes. Situation 2: When I try to send lesser number of bytes(say 35 bytes) immediately after startup routine, wince device is transmitting properly and the PC is also receiving it. I'm able to send lesser no. of bytes immediately after startup. If I have to transmit more number of bytes(72) I have to wait till I receive bytes from the other end. I'm pasting the code that creates my socket. I'm not able to read the buffer size using getsockopt. It says WSAENOPROTOOPT. (code is under #if 0 below) Any advice guys. bool SL_GSM_Create_Client_Socket(void) { WSADATA wsaData; DWORD dwNonBlock=1; int iResult; byte bData = 1; if(boIsWS2DllLoaded == false) { iResult = WSAStartup( MAKEWORD( 2, 2 ), &wsaData ); if ( iResult != NO_ERROR ) { return FALSE; } else { if ( LOBYTE( wsaData.wVersion ) != 2 || HIBYTE( wsaData.wVersion ) != 2 ) { WSACleanup( ); boIsWS2DllLoaded = false; return FALSE; } else boIsWS2DllLoaded = TRUE; } } /* Create a socket*/ GSMsocket = socket( AF_INET, SOCK_DGRAM, IPPROTO_UDP ); if ( GSMsocket == INVALID_SOCKET ) { return false; } /* Connect to a server. Get the Server IP address from the Sys control module*/ sClientService.sin_family = AF_INET; sClientService.sin_addr.s_addr = inet_addr(cServer_IP_Address); // 10.251.106.101 sClientService.sin_port = htons(3003); if ( connect( GSMsocket, (SOCKADDR*) &sClientService, sizeof(sClientService) ) == SOCKET_ERROR) { switch(WSAGetLastError()) { case WSAECONNREFUSED: { printf("WSAECONN refused"); break; } case WSAENETUNREACH: { printf("WSAENETUN reach"); break; } case WSAETIMEDOUT: { printf("WSAENETUN Time out"); break; } case WSAEWOULDBLOCK: { printf("\nNon Blocking socket\n"); break; } } closesocket(GSMsocket); return false; } /* To make the socket Non-Blocking*/ if(ioctlsocket(GSMsocket,FIONBIO,&dwNonBlock) != 0) { printf( "Error in creating Non Blocking socket: %d \n", WSAGetLastError() ); } GSMinitialised = true; #if 0 // This does not work. Gives an error code 10042 - WSAENOPROTOOPT { char * optval[10]; int i=10, retcode=0; int * optlen=&i; retcode=getsockopt (GSMsocket, SOL_SOCKET , SO_MAX_MSG_SIZE, (char *)optval, optlen); if(!retcode) printf("\nSO_MAX_MSG_SIZE=%lu",*((unsigned long *)optval)); else { retcode = WSAGetLastError(); printf("\noptval ERROR %d", retcode); } } #endif return true; } Tag: Problem with bootpart.lib Tag: 101215

Hi,

I'm developing an bootloader/OAL for a PXA255/32MB StrataFlash in
PB4.2 using as a model the XSCBD BSP. When I try to save an image to
FLASH using bootpart.lib I get the following message:

IsValidMBR: MBR sector = 0xFFFFFFFF
OpenPartition: Invalid MBR. Formatting flash.
Enter LowLevelFormat [0x0, 0x7D].
Erasing flash block(s) [0x0, 0x7D] (please wait): Done.
WriteMBR: MBR block = 0x0.
MD_WriteSector: Timed out writing buffered data
CreatePartition: could not write to block 0x0
Done.

OpenPartition: Partition Exists=0x0 for part 0x21.
CreatePartition: Enter CreatePartition for 0x21.
LastLogSector: Last log sector is: 0xF80F.
CreatePartition: Start = 0x1, Num = 0x661.
Log2Phys: Logical 0x1 -> Physical 0x1
MD_WriteSector: Timed out writing buffered data
CreatePartition: can't mark sector info.
ERROR: OEMLaunch: failed to create/open BINFS partition.

To get at this point takes a lot of time... so, a couple of question
arises:

1. What is the problem?
2. Is this the only way to save the image? I mean, I could use FMD to
write/read it, as it's done with bootloader config info. Is there a
reason to do it this way? does kernel use this partition afterward or
it's just for using the remaining space as an extended partition?

Regards

JSS

Top