Does wceusbsh.sys support interface association descriptor?

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - CETK Doubt........Suspend and resume.. hi all! I am running CETK test cases for my network card which acts as Wifi card. I was checking the One card minport driver test.. My driver is failing the "SuspendResume: test case. (My driver is miniport driver written for SDIO interface) What actually is happening in this test case.i.e suspend resume.???? What i need to add in my driver to support this test case.???? Can any one give some idea abt this.......... I am new to CETK....Learning .... Any help will be really appreaciated.. Thanks, Ragz..... Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111090
  - 2
    - What's the differences of three "Build OS" options? In "Build OS" menu, there are three build options: "Sysgen", "Build and Sysgen" and "Build and Sysgen Current BSP". I wonder when shall I use one of them and which one shall I use? Could anyone tell me the detailed differences of those three build options? Thanks! -- Message posted via PocketPCJunkies.com http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200803/1 Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111084
  - 3
    - What's the differences of three "Build OS" options? In "Build OS" menu, there are three build options: "Sysgen", "Build and Sysgen" and "Build and Sysgen Current BSP". I wonder when shall I use one of them and which one shall I use? Could anyone tell me the detailed differences of those three build options? Thanks! -- Message posted via PocketPCJunkies.com http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200803/1 Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111083
  - 4
    - What's the differences of three "Build OS" options? In "Build OS" menu, there are three build options: "Sysgen", "Build and Sysgen" and "Build and Sysgen Current BSP". I wonder when shall I use one of them and which one shall I use? Could anyone tell me the detailed differences of those three build options? Thanks! Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111082
  - 5
    - Setting up dual Static IP addresses I am using Platform Builder 5.0 for Windows CE 5.0 to create an image for a WinSystems EBC-C3PLUS single board computer. This SBC uses the Intel 82559ER Ethernet driver for both Ethernet ports. The 2nd instance of the Ethernet port (E100CE2) is set correctly, but the first instance (E100CE1) is not, and is instead set to the static address 1.2.3.4. Nowhere in my specified .reg and .bib files have I declared any settings to use this address. I have tried multiple suggestions on google and from co-workers that are using different SBCs to no result. The question is then, where does this address come from? And how can I bypass this to use my requested IP addresses? Also, why is the 2nd instance of my Ethernet port successful where the 1st fails? -------------------------------- Config.bib -------------------------------- MEMORY #if defined IMGRAM16 ; 16 MB of RAM (note: AUTOSIZE will adjust boundary) NK 80220000 009E0000 RAMIMAGE RAM 80C00000 00400000 RAM #elif defined IMGRAM32 ; 32 MB of RAM (note: AUTOSIZE will adjust boundary) NK 80220000 009E0000 RAMIMAGE RAM 80C00000 01400000 RAM #elif defined IMGRAM64 ; 64 MB of RAM (note: AUTOSIZE will adjust boundary) NK 80220000 009E0000 RAMIMAGE RAM 80C00000 03400000 RAM #elif defined IMGRAM128 ; 128 MB of RAM (note: AUTOSIZE will adjust boundary) NK 80220000 009E0000 RAMIMAGE RAM 80C00000 07100000 RAM #elif defined IMGRAM256 ; 256 MB of RAM (note: AUTOSIZE will adjust boundary) NK 80220000 009E0000 RAMIMAGE RAM 80C00000 0EB00000 RAM #elif defined IMGRAM512 ; 512 MB of RAM (note: AUTOSIZE will adjust boundary) NK 80220000 009E0000 RAMIMAGE RAM 80C00000 1E000000 RAM #else ; 28 MB of RAM (default) (note: AUTOSIZE will adjust boundary) ; This value will cause the RAM auto-detect feature to trigger NK 80220000 009E0000 RAMIMAGE RAM 80C00000 01000000 RAM #endif ; Hard reset the system on a software reboot? ; IF BSP_HARDRESET pdwHardReset 00000000 1 FIXUPVAR ELSE pdwHardReset 00000000 0 FIXUPVAR ENDIF EPKTBUF 801DC000 00011F80 RESERVED ; Intel 82559ER Ethernet EPKTBUF 801EDF80 00011F80 RESERVED ; Intel 82559ER Ethernet(2) BOOTARGS 801FFF00 00000100 RESERVED ; Boot arguments EDBG_DMA 80200000 00020000 RESERVED ; EDBG DMA buffer CONFIG AUTOSIZE=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 KERNELFIXUPS=ON ; ; ROMFLAGS is a bitmask of options for the kernel ; ROMFLAGS 0x0001 Disallow Paging ; ROMFLAGS 0x0002 Not all KMode ; ROMFLAGS 0x0010 Trust Module only ; IF IMGTRUSTROMONLY IF IMGNOTALLKMODE ROMFLAGS=12 ELSE ROMFLAGS=10 ENDIF ELSE IF IMGNOTALLKMODE ROMFLAGS=2 ELSE ROMFLAGS=0 ENDIF ENDIF IF _TGTCPUFAMILY=x86 ROMOFFSET=80000000 ENDIF -------------------------------- Platform.reg --------------------------------- ;<<snip non Ethernet related entries>> IF CEPC_INTELFE_PCI ; Generic adapter configuration/description [HKEY_LOCAL_MACHINE\Comm\E100CE] "DisplayName"="Intel(R) Fast Ethernet Controller" "Group"="NDIS" "ImagePath"="e100ce.dll" [HKEY_LOCAL_MACHINE\Comm\E100CE\Linkage] "Route"=multi_sz:"E100CE1","E100CE2" ; Specific configuration for an adapter instance [HKEY_LOCAL_MACHINE\Comm\E100CE1] "DisplayName"="Intel(R) Fast Ethernet Controller" "Group"="NDIS" "ImagePath"="e100ce.dll" [HKEY_LOCAL_MACHINE\Comm\E100CE1\Parms] "BusNumber"=dword:0 "BusType"=dword:5 "BusTypeLocal"=dword:5 ; Shared packet buffer storage, must match reserved memory range "CE_PhysAddr"=dword:801DC000 ; Other adapter-specific Registry parameters may be inserted here "SlotNumber"=dword:a "ScanMethod"=dword:2 ; Settings for DHCP, if enabled IF DHCP [HKEY_LOCAL_MACHINE\Comm\E100CE1\Parms\TcpIp] "EnableDHCP"=dword:1 "DefaultGateway"="" "UseZeroBroadcast"=dword:0 "IpAddress"="0.0.0.0" "Subnetmask"="0.0.0.0" ENDIF ; Settings for static IP configuration, if enabled IF STATIC_IP [HKEY_LOCAL_MACHINE\Comm\E100CE1\Parms\TcpIp] "EnableDHCP"=dword:0 "DefaultGateway"="172.16.0.1" "UseZeroBroadcast"=dword:0 "IpAddress"="172.16.0.1" "Subnetmask"="255.255.255.0" ENDIF ; Specific configuration for a network interface instance [HKEY_LOCAL_MACHINE\Comm\E100CE2] "DisplayName"="Intel(R) Fast Ethernet Controller" "Group"="NDIS" "ImagePath"="e100ce.dll" [HKEY_LOCAL_MACHINE\Comm\E100CE2\Parms] "BusNumber"=dword:0 "BusType"=dword:5 "BusTypeLocal"=dword:5 ; Shared packet buffer storage, must match reserved memory range "CE_PhysAddr"=dword:801EDF80 ; Other adapter-specific Registry parameters may be inserted here "SlotNumber"=dword:b "ScanMethod"=dword:2 ; Settings for DHCP, if enabled IF DHCP [HKEY_LOCAL_MACHINE\Comm\E100CE2\Parms\TcpIp] "EnableDHCP"=dword:1 "DefaultGateway"="" "UseZeroBroadcast"=dword:0 "IpAddress"="0.0.0.0" "Subnetmask"="0.0.0.0" ENDIF ; Settings for static IP configuration, if enabled IF STATIC_IP [HKEY_LOCAL_MACHINE\Comm\E100CE2\Parms\TcpIp] "EnableDHCP"=dword:0 "DefaultGateway"="172.16.1.1" "UseZeroBroadcast"=dword:0 "IpAddress"="172.16.1.1" "Subnetmask"="255.255.255.0" ENDIF ; Link between adapter and protocol stack [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage] ; This should be MULTI_SZ ; This is the list of llip drivers to load "Bind"=multi_sz:"e100ce1","e100ce2" ENDIF Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111069
  - 6
    - .Net Compact Framework disabled in SDK Development Languages tab C Using PB for CE5.0, I have added .Net CF 2.0 Headless and its OS Dependencies to my project from catalog. It builds and runs successfully, and .Net CF works on it. However, when I try to create an SDK in PB, the Development Languages tab item ".Net Compact Framework" is grayed out. Why? I believe I need to check this box to generate an SDK that will allow VS 2005 to successfully create a .Net project for the device, and allow it to be able to connect to the device. Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111068
  - 7
    - usb function mass storage driver hi? Is it possible to make ce device as a usb mass storage device to host? Of cource, using activesync I can connect the ce device via usb line with host. But I found if I remove the activesync catalog from my os design, then the ce device was no longer detected from host. what should I do if I wanna make my ce device as a usb mass storage device without using activesync? Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111063
  - 8
    - colorkeying failing. Hi friends, I am trying to load an image to an overlay surface in MS windows 5.0 device. I want to make the surface transparent. I guess for that we need to use colorkeying mechanism. However when I call UpdateOverlay , its returning E_INVALIDARG. Please help. DDOVERLAYFX fx; memset(&fx, 0, sizeof(fx)); fx.dwSize = sizeof(fx); fx.dckDestColorkey.dwColorSpaceLowValue = 0; fx.dckDestColorkey.dwColorSpaceHighValue = 0; fx.dckSrcColorkey.dwColorSpaceLowValue = 0; fx.dckSrcColorkey.dwColorSpaceHighValue = 0; DWORD flags = DDOVER_SHOW | DDOVER_KEYDESTOVERRIDE; // Show the overlay surface HRESULT hr; hr = overlay->UpdateOverlay(&rcSrc, primary, &rcDst, flags, &fx); I am a novice in multimedia technology. Please let me know I have missed something. Thanks in Advance. Sunil Raj Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111053
  - 9
    - colorkeying failing. Hi friends, I am trying to load an image to an overlay surface in MS windows 5.0 device. I want to make the surface transparent. I guess for that we need to use colorkeying mechanism. However when I call UpdateOverlay , its returning E_INVALIDARG. Please help. DDOVERLAYFX fx; memset(&fx, 0, sizeof(fx)); fx.dwSize = sizeof(fx); fx.dckDestColorkey.dwColorSpaceLowValue = 0; fx.dckDestColorkey.dwColorSpaceHighValue = 0; fx.dckSrcColorkey.dwColorSpaceLowValue = 0; fx.dckSrcColorkey.dwColorSpaceHighValue = 0; DWORD flags = DDOVER_SHOW | DDOVER_KEYDESTOVERRIDE; // Show the overlay surface HRESULT hr; hr = overlay->UpdateOverlay(&rcSrc, primary, &rcDst, flags, &fx); I am a novice in multimedia technology. Please let me know I have missed something. Thanks in Advance. Sunil Raj Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111052
  - 10
    - colorkeying failing. Hi friends, I am trying to load an image to an overlay surface in MS windows 5.0 device. I want to make the surface transparent. I guess for that we need to use colorkeying mechanism. However when I call UpdateOverlay , its returning E_INVALIDARG. Please help. DDOVERLAYFX fx; memset(&fx, 0, sizeof(fx)); fx.dwSize = sizeof(fx); fx.dckDestColorkey.dwColorSpaceLowValue = 0; fx.dckDestColorkey.dwColorSpaceHighValue = 0; fx.dckSrcColorkey.dwColorSpaceLowValue = 0; fx.dckSrcColorkey.dwColorSpaceHighValue = 0; DWORD flags = DDOVER_SHOW | DDOVER_KEYDESTOVERRIDE; // Show the overlay surface HRESULT hr; hr = overlay->UpdateOverlay(&rcSrc, primary, &rcDst, flags, &fx); I am a novice in multimedia technology. Please let me know I have missed something. Thanks in Advance. Sunil Raj Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111050
  - 11
    - Why SD Card require to Format in WinCE 5.0? Hi all, I am using both SD and MMC card on Quantum board i fetch some problem with SD card. When i use MMC card it automatically detected but when i use SD card it only shown in Storage Manager not in Explorer, it requires format then and then only it display on Explorer. Is any budy know how to solve this problem Why only SD card is require to format? Is any Register settings or any program code need to be change? Thanks in Adavance Best Regards Swapnil Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111048
  - 12
    - USB Mass storage problem Hi All, I have WindowsCE 5.0 OS running on my target with USB function driver. I have tested active sync connectivity and also RNDIS functionality with it. I have USB 2.0 function driver. But I am unable to get mass storage profile working. I am trying to expose internal flash drive. When I plug USB cable the USBMSFn driver is able to get disk information correctly, I can see Removable disk in my PC. But it is showing the properties as "0 bytes". Also the recognition happens only one time. If I take out the USB cable and plug it back, I get USB unrecognised message. Can any help me in solving the issue?. Here is the KITL debug message when I plug USB cable. 115823 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 115824 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: ++ 115824 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: DeviceName = DSK1: 115825 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: Removable not present; default is true 115825 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: Removable = 1 115826 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: opened store DSK1: 115826 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: IOCTL_DISK_GETINFO passed 115826 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: bytes per sector = 2048 115827 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: cylinders = 1620 115827 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: flags = 0x8 115828 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: heads = 1 115828 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: sectors = 64 115828 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: total sectors = 103680 115835 PID:c3958402 TID:43930afa Desktop Window QI, Unknown interface Unloaded symbols for 'M:\PBWORKSPACES\Test\RELDIR\CLONE_ARMV4I_RELEASE \DISKCACHE.DLL' Unloaded symbols for 'M:\PBWORKSPACES\Test\RELDIR\CLONE_ARMV4I_RELEASE \FATFSD.DLL' 116042 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: -- 116042 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116043 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116043 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116044 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116045 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116045 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116046 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116054 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116054 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Close: ++ 116055 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Close: forcing storage manager to re-examine \StoreMgr\DSK1: 116055 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Close: -- 116056 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116056 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116056 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: ++ 116057 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: DeviceName = DSK1: 116058 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: Removable not present; default is true 116058 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: Removable = 1 116058 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: opened store DSK1: 116059 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: IOCTL_DISK_GETINFO passed 116059 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: bytes per sector = 2048 116060 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: cylinders = 1620 116060 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: flags = 0x8 116060 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: heads = 1 116061 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: sectors = 64 116061 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: total sectors = 103680 116062 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: -- 116062 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116062 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116063 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- Unloaded symbols for 'M:\PBWORKSPACES\Test\RELDIR\CLONE_ARMV4I_RELEASE \MSPART.DLL' 116104 PID:645977ae TID:2459ab8e FMD_OEMIoControl: unrecognized IOCTL (0x71c24). Loaded symbols for 'M:\PBWORKSPACES\Test\RELDIR\CLONE_ARMV4I_RELEASE \MSPART.DLL' 116188 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116188 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116188 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116189 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- Loaded symbols for 'M:\PBWORKSPACES\Test\RELDIR\CLONE_ARMV4I_RELEASE \FATFSD.DLL' 116304 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116305 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116305 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116305 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116307 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116307 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116308 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116308 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116310 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116310 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116311 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116311 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116313 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116313 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116314 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116314 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116315 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116316 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116316 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116316 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116318 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116318 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116318 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116319 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116321 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116321 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116321 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116322 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- Loaded symbols for 'M:\PBWORKSPACES\Test\RELDIR\CLONE_ARMV4I_RELEASE \DISKCACHE.DLL' 116414 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116414 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116415 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116415 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116417 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116417 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116418 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116418 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116419 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116420 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116420 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116421 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116422 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116422 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_OpenInterface: ++ 116423 PID:645977ae TID:a3d8f0b2 UsbMsFn!ReceiveCBW: ++ 116423 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_SetupRx: ++ 116424 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_SetupRx: -- 116473 PID:645977ae TID:a3d8f0b2 UsbMsFn!ChangeMscState: State change: idle -> command transport 116481 PID:645977ae TID:a3d8f0b2 UsbMsFn!ReceiveCBW: -- 116481 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_OpenInterface: -- 116481 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116483 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116483 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116483 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116484 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116528 PID:645977ae TID:2459ab8e FMD_OEMIoControl: unrecognized IOCTL (0x71c54). 116529 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116529 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116530 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: Class request 116530 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleClassRequest: ++ 116530 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleClassRequest: Get max LUN class request 116531 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_SetupTx: ++ 116531 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_SetupTx: -- 116532 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleClassRequest: -- 116532 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116532 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116533 PID:645977ae TID:a3d8f0b2 BOT DefaultTransferComplete setting event 116533 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: Transfer 0 116534 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: 1 bytes transferred 116535 PID:645977ae TID:a3d8f0b2 BOT DefaultTransferComplete setting event 116535 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: Transfer 2 116536 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: 31 bytes transferred 116536 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBOPipeTransfer: ++ 116536 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBOPipeTransfer: Received CBW 116538 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: ++ 116538 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: Length: 0x0024 Flags: 0x80 CBWLen: 0x6 116538 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: ++ 116539 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: command 0x12 116539 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: INQUIRY 116540 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: -- 116540 PID:645977ae TID:23da3e5e UsbMsFn!ChangeMscState: State change: command transport -> data in transport 116540 PID:645977ae TID:23da3e5e UsbMsFn!BOT_ExecuteCB: ++ 116541 PID:645977ae TID:23da3e5e UsbMsFn!STORE_ExecuteCommand: ++ 116541 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: ++ 116542 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: command 0x12 116542 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: INQUIRY 116542 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: -- 116543 PID:645977ae TID:23da3e5e UsbMsFn!STORE_ExecuteCommand: command 0x12 116543 PID:645977ae TID:23da3e5e UsbMsFn!STORE_ExecuteCommand: SCSI INQUIRY 116544 PID:645977ae TID:23da3e5e UsbMsFn!STORE_ExecuteCommand: -- 116544 PID:645977ae TID:23da3e5e UsbMsFn!BOT_ExecuteCB: Command : passed 116544 PID:645977ae TID:23da3e5e UsbMsFn!BOT_ExecuteCB: -- 116545 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: request length = 36 116545 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupTx: ++ 116546 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupTx: -- 116546 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: -- 116547 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBOPipeTransfer: -- 116547 PID:645977ae TID:a3d8f0b2 BOT DefaultTransferComplete setting event 116548 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: Transfer 1 116548 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: 36 bytes transferred 116549 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBIPipeTransfer: ++ 116549 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: ++ 116549 PID:645977ae TID:23da3e5e UsbMsFn!ChangeMscState: State change: data in transport -> status transport 116551 PID:645977ae TID:23da3e5e UsbMsFn!BOT_BuildCSW: ++ 116551 PID:645977ae TID:23da3e5e UsbMsFn!BOT_BuildCSW: -- 116552 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupTx: ++ 116552 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupTx: -- 116553 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: -- 116553 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBIPipeTransfer: -- 116554 PID:645977ae TID:a3d8f0b2 BOT DefaultTransferComplete setting event 116555 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: Transfer 1 116555 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: 13 bytes transferred 116555 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBIPipeTransfer: ++ 116556 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: ++ 116556 PID:645977ae TID:23da3e5e UsbMsFn!ChangeMscState: State change: status transport -> idle 116556 PID:645977ae TID:23da3e5e UsbMsFn!ReceiveCBW: ++ 116556 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupRx: ++ 116557 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupRx: -- 116558 PID:645977ae TID:23da3e5e UsbMsFn!ChangeMscState: State change: idle -> command transport 116558 PID:645977ae TID:23da3e5e UsbMsFn!ReceiveCBW: -- 116558 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: -- 116559 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBIPipeTransfer: -- 116559 PID:645977ae TID:a3d8f0b2 BOT DefaultTransferComplete setting event 116560 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: Transfer 2 116560 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: 31 bytes transferred 116560 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBOPipeTransfer: ++ 116560 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBOPipeTransfer: Received CBW 116561 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: ++ 116562 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: Length: 0x00fc Flags: 0x80 CBWLen: 0xa 116563 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: ++ 116563 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: command 0x23 116563 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: unsupported command 0x23 116563 PID:645977ae TID:23da3e5e UsbMsFn!STORE_IsCommandSupported: -- 116564 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: command not supported 116564 PID:645977ae TID:23da3e5e UsbMsFn!ChangeMscState: State change: command transport -> wait for reset 116565 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: -- 116566 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBOPipeTransfer: -- 116566 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116567 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: ++ 116567 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleClearFeature: ++ 116567 PID:645977ae TID:a3d8f0b2 UsbMsFn!ChangeMscState: State change: wait for reset -> status transport 116568 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_BuildCSW: ++ 116568 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_BuildCSW: -- 116568 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_SetupTx: ++ 116569 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_SetupTx: -- 116569 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_HandleRequest: -- 116570 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116571 PID:645977ae TID:a3d8f0b2 BOT DefaultTransferComplete setting event 116571 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: Transfer 1 116571 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: 13 bytes transferred 116572 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBIPipeTransfer: ++ 116572 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: ++ 116573 PID:645977ae TID:23da3e5e UsbMsFn!ChangeMscState: State change: status transport -> idle 116574 PID:645977ae TID:23da3e5e UsbMsFn!ReceiveCBW: ++ 116575 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupRx: ++ 116575 PID:645977ae TID:23da3e5e UsbMsFn!BOT_SetupRx: -- 116576 PID:645977ae TID:23da3e5e UsbMsFn!ChangeMscState: State change: idle -> command transport 116576 PID:645977ae TID:23da3e5e UsbMsFn!ReceiveCBW: -- 116577 PID:645977ae TID:23da3e5e UsbMsFn!BOT_HandleCBW: -- 116577 PID:645977ae TID:23da3e5e UsbMsFn!ProcessBIPipeTransfer: -- 116580 PID:645977ae TID:a3d8f0b2 BOT DefaultTransferComplete setting event 116580 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: Transfer 2 116581 PID:645977ae TID:23da3e5e UsbMsFn!BOT_TransferThread: 0 bytes transferred 116581 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116582 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Close: ++ 116585 PID:645977ae TID:2459ab8e FMD_OEMIoControl: unrecognized IOCTL (0x71c54). 116923 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Close: forcing storage manager to re-examine \StoreMgr\DSK1: 116924 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Close: -- 116925 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: -- 116925 PID:645977ae TID:a3d8f0b2 UsbMsFn!BOT_DeviceNotify: ++ 116925 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: ++ 116926 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: DeviceName = DSK1: 116927 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: Removable not present; default is true 116927 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: Removable = 1 116927 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: opened store DSK1: 116928 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: IOCTL_DISK_GETINFO passed 116928 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: bytes per sector = 2048 116929 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: cylinders = 1620 116929 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: flags = 0x8 116929 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: heads = 1 116930 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: sectors = 64 116930 PID:645977ae TID:a3d8f0b2 UsbMsFn!STORE_Init: total sectors = 103680 Messages during the device boot time are as follows: Loaded symbols for 'M:\PBWORKSPACES\Test\RELDIR\CLONE_ARMV4I_RELEASE \USBMSFN.DLL' 67528 PID:645977ae TID:6459778a UsbMsFn!BOT_InternalInit: ++ 67529 PID:645977ae TID:6459778a UsbMsFn!BOT_Configure: ++ 67529 PID:645977ae TID:6459778a UsbMsFn!BOT_ReadConfigurationValue: + + 67530 PID:645977ae TID:6459778a UsbMsFn!BOT_ReadConfigurationValue: -- 67530 PID:645977ae TID:6459778a UsbMsFn!BOT_Configure: -- 67532 PID:645977ae TID:6459778a UsbMsFn!BOT_ReadConfigurationValue: + + 67532 PID:645977ae TID:6459778a UsbMsFn!BOT_ReadConfigurationValue: -- 67533 PID:645977ae TID:6459778a UsbMsFn!BOT_InternalInit: BOT transfer thread priority = 100 67533 PID:645977ae TID:83da3db6 UsbMsFn!BOT_TransferThread: ++ 67536 PID:645977ae TID:6459778a UsbMsFn!BOT_InternalInit: -- Thanks -Milind Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111047
  - 13
    - WinCE Support BDA? Dear All, I am studying how to set up a complete direct show filter chain for digital TV player. I find Microsoft provide Broadcast Driver Architecture to support receiveing and displaying broadband digital and analog broadcasts on Windows XP. Does WinCE have BDA? If no, what can I follow to create my own DS filter? Thanks Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111044
  - 14
    - ANN: March Windows CE Live Chat Tomorrow! Just a note that we'll be hosting an online chat tomorrow concerning Windows Mobile and Windows Embedded CE! Members of the development team will be on hand ready to answer your questions, so bring 'em on! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Title: Windows CE Live Chat! Tuesday, March 25, 2008 9:00 - 10:00 A.M. Pacific time Additional Time Zones: http://www.timeanddate.com/worldclock/fixedtime.html?month=3&day=25&year=2008&hour=9&min=0&sec=0&p1=234 Description: Do you have tough technical questions regarding Windows CE or Windows Mobile for which you're seeking answers? Do you want to tap into the deep knowledge of the talented Microsoft Embedded Devices Group members? If so, please join us for a live Windows CE chat and bring on the questions! Windows CE is the operating system that is powering the next generation of 32-bit, small-footprint and mobile devices. This chat will cover the tools and technologies used to develop devices using the Windows CE operating system. To join this chat, please log on via the main MSDN chat page at: http://msdn.microsoft.com/chats/ Chat Transcripts: Missed a recent chat? We welcome you to visit the Transcript Archive. Transcripts are usually posted within two weeks of the live event. http://msdn.microsoft.com/chats/transcripts/mobileembedded/default.aspx ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sue sloh@microsoft.com (remove "online" from reply-to address) http://blogs.msdn.com/ce_base/ _____________________________________________________________ This posting is provided "AS IS" with no warranties, and confers no rights. _____________________________________________________________ Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111039
  - 15
    - Start Menu Icons Hello All: I am using WinCE 5.00 platform, and I like to eliminate "Favorites", "Documents", "Settings" and "Help" from start menu, Any help? Thanks Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111038
  - 16
    - GDI CETK failures and cursor I am receiving several GDI CETK test failures. I am debugging these failures, and I am observing "screen halves mistmatch" failures. When I view my LCD, the cursor is active and appears to be causing the discrepancies between the two screen halves. Is it known that having the cursor active during GDI CETK test runs can cause test failures? Thanks, Danny Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111036
  - 17
    - WinCE 4.20 not supporting all hard drives? Hello. We have been using a stable WinCE 4.20 platform for about 4 years in our product, and we're seeing a problem which we can only attribute to using a new line of hard drives. In the past, we have used our Image on a wide collection of hard disks: various pen drives, CompactFlash drives, rotary drives - of all brands. Last week, we attempted to use this same image on a Transcend 256 MB Solid State disk ( http://ec.transcendusa.com/product/ItemDetail.asp?ItemID=TS256MDOM44H ) It doesn't work! After the Image loader has finished its progress, the screen goes black - and we receive no debug messages from WinCE, and nothing else happens. We have used the aforementioned image on the 32 and 64 MB versions of the Transcend disks with absolutely no problems. We tried rebuilding a smaller image for testing purposes, and it works "a little" better, this image boots to the desktop, and after a short while "hangs" - no adverse debug messages are seen. We are currently investigating further, but we're wondering if anyone has seen anything like this with the particular drive, or any other drive. Grateful for any ideas -P Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111030
  - 18
    - How to handle with IDirectDrawSurface::UpdateOverlayZOrder in display Dear all, I'm developing WinMobile 6.0 display driver with ddraw multiple overlay surfaces support. Now my display driver can overlay multiple surfaces on the primary surface. But I don't know how to determine their z order when they are overlapped with each other. According to MSDN, IDirectDrawSurface::UpdateOverlayZOrder is defined in DDraw API layer, but it doesn't explain clearly about which DDHAL callback function will be called in display driver? It confused me for a long time, and any comment or suggestion will be very appreciated. Thanks. Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111029
  - 19
    - How to communicate with a driver from OAL to replace calls to Hi, I have been asked to device a way to replace a few calls to SC_CreateEvent from several modules within the OAL that we are using because these calls are not supported in WM7 (they never were as I found out). What is the recommended way to do this? I read that in WM7 since you can have kernel mode drivers, one can write such a driver to emulate that capability. I imagine that the driver would have to send a customed IOCTL to AOL and register some callback function that OAL can call to let the driver know that data is available? Thanks Pedro Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111027
  - 20
    - SD controler of s3c2440 can support SDHC card? SD controler of s3c2440 can support SDHC card? If yes, how to modify SD card driver? Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111016
  - 21
    - SD Card Detection in WINCE 5.0 Hi, I have some questions related to the SD and MMC card drivers under Windows CE 5.0. Let me first explain the behaviour that I am observing :- The MMC card works fine without any modifications to the existing driver for MMC which is under :- C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\SDCARD\SDCLIENTDRIVERS\SDMEMORY. Now, when I try to plug in an SD card then the card does not show up in explorer. But it appears in Storage manager. When I formatted the SD Card and after that mounting it, it shows in Explorer. I have done the detection of SD Card in manually (i.e. Formatting and mounting ) and by changing the reg. enteries as: [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles] "PartitionDriverName"="mspart.dll" "DefaultFileSystem"="FATFS" "AutoPart"=dword:00000001 "MountFlags"=dword:00000000 "AutoMount"=dword:00000001 "AutoFormat"=dword:00000001 "Folder"="Mounted Volume" "ActivityEvent"="PowerManager/ActivityTimer/SystemActivity" It directly appear in Storage manager and in Explorer but in formatted format. Can any budy help me to solve these problem I want to use same SD Card in both WIN XP and WIN CE without formatting it. When Card is formatted in WINCE I can't use it in XP it requires Formatting of Card and viceversa. Thanks in advance Best Regards Swapnil Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111015
  - 22
    - Does Windows Embedded CE 6.0 support IMGFS? Hello! I have experienced IMGFS(Image File System) at Windows Mobile 5.0 based platform. Does Windows Embedded CE 6.0 support IMGFS??? MSDN doesn't almost mention IMGFS... thanks Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111013
  - 23
    - A question about freespinlock in E100bex code. Hi , I'm reading the e100bex source code in WinCE 5.0 platform builder and I've found that the sendlock / recvlock has been just allocated ,used but never freed. It's here got to be something necessary to hold it forever? -- Thanks Yu Hao Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111010
  - 24
    - Deploy app to root folder Hi group, I am working with a Windows CE 6.0 device and I want to download my custom application from VS2005 IDE. After build my app I go to "Tools", "options", click on "Device Tools", "Devices", click on Properties of my device and in default location in my device I configure "Root Folder" ot "My Documents Folder" but when I deploy my project, app is not placed in root or my Documents, the application is always placed in "Program Files" folder is this a VS2005 bug? or is a problem with my device? Best Regards, Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111006
  - 25
    - How to protect HKEY_LOCAL_MACHINE keys from user mode access under Hello, I work with CE6 and would like to protect all HKEY_LOCAL_MACHINE registry keys so that (malicious) applications running in the user mode cannot modify them (for example device driver registry keys!). CE6 distinguishes between user and kernel mode, so it must be possible to do that, doesn't it? Thank you, Peter Tag: Does wceusbsh.sys support interface association descriptor? Tag: 111003
- Next
  - 1
    - ce6.0 NKwvsprintfW hard locks system Hello, On a CE6.0 ARM platform the following issue has come up: If calling NKwvsprintfW() during OEMInit() the system hard locks. Once OEMInit() returns, it is possible to subsequently call NKwvsprintfW() without problems. Any insights to why this is occurring, or reference to documentation specifying that this is not legal would be appreciated. chris Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110996
  - 2
    - SD Card Experts Hi, I am building wince 5.0 on new hardware, and I am trying to get the my SDmemory card to come up. There are many layers to this driver and I am trying to peel my way through it, but sure could use some help. Device actually supports SDIO , so I have included SDMemory and SDIO Standard Host controller, in the SD card drivers directory there is SD Bus, SD Bus Driver, SdCardLib,SDClientDriver,SDHCDriver,and SDHClib (quite confusing). I have been looking/reading but its pretty daunting at first... anyway, I have enabled as much debug as I could find and I have pasted it below in multiple sections separated by ========= first section is power up/driver load/init with no card inserted, second section is debug when I plug card in, third is card removal,there is an awful lot of debug, and when i first sent the message was too big so I removed PIDs and TIDS and then I removed tsome countdown code that repeated (from 40 down to 1) so I removed a bunch of those counts so I could email. so I'm hoping someone familiar with this driver might be able to help shorten this task... Thanks, Joe W. Power up no card inserted ================== Loaded symbols for 'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_RELEASE\SDBUS.DLL' SDBusDriver: PROCESS_ATTACH SDCard: +SDInitializeCardLib SDCard: -SDInitializeCardLib SDBusDriver: +SDC_Init SDBusDriver: Initialize: Using request list depth of 48 entries SDCard: +SDCreateMemoryList SDCard: -SDCreateMemoryList SDCard: +SDCreateMemoryList SDCard: -SDCreateMemoryList SDBusDriver: BusRequestCompleteDispatch Work Item Starting Up SDBusDriver: Bus Driver instance created : 0x00042DE0 ! -SDC_Ini Loaded symbols for 'C:\WINCE500\PBWORKSPACES\AMDLXZ\RELDIR\GEODELX_X86_RELEASE\SDHC.DLL' 5739 SDCard: +SDInitializeCardLib 5739 SDCard: -SDInitializeCardLib 5739 SDHCDGetHCFunctions: +Init 5741 SDHCDGetHCFunctions: -Init 5744 SDHC +Init 5744 SDHC Active RegPath: Drivers\Active\30 5747 CSDHCBase::InitializeHardware: IRQ 0xA mapped to SYS_INTR 0x16 5747 CSDHCBase::InitializeHardware: Base address -> 0xff900000; length -> 0x100 5807 SDHC: Using timeout control value of 0xd for 2.0 seconds 5807 +DumpStdHCRegs - Slot 0 ------------------------- 5807 SystemAddressLo: 0x0000 5809 SystemAddressHi: 0x0000 5811 BlockSize: 0x0000 5813 BlockCount: 0x0000 5813 Argument0: 0x0000 5815 Argument1: 0x0000 5815 TransferMode: 0x0000 5925 Command: 0x0000 5925 R0: 0x0000 5925 R1: 0x0000 5925 R2: 0x0000 5925 R3: 0x0000 5927 R4: 0x0000 5927 R5: 0x0000 6096 R6: 0x0000 6096 R7: 0x0000 6096 BufferDataPort0: 0x1404 6096 BufferDataPort1: 0x6000 6098 PresentState: 0x1F20000 6098 HostControl: 0x0000 6098 PowerControl: 0x0000 6100 BlockGapControl: 0x0000 6102 WakeUpControl: 0x0000 6104 ClockControl: 0x0000 6106 TimeOutControl: 0x0000 6106 SoftReset: 0x0000 6106 NormalIntStatus: 0x0000 6106 ErrorIntStatus: 0x0000 6106 NormalIntStatusEnable: 0x0000 6106 ErrorIntStatusEnable: 0x0000 6106 NormalIntSignalEnable: 0x0000 6107 ErrorIntSignalEnable: 0x0000 6107 AutoCMD12ErrorStatus: 0x0000 6109 Capabilities: 0x18021A1 6109 MaxCurrentCapabilites: 0x0040 6109 SlotInterruptStatus: 0x0000 6109 HostControllerVersion: 0x0400 6109 -DumpStdHCRegs------------------------- 6109 SDBusDriver: Host Controller "SD Std Host" assigned number 0 6109 CSDHCBase::SlotOptionHandler(0, SDHCDGetSlotInfo) 6110 SDHCSetRate - Clock Control Reg = 101 6110 SDHCSetRate - Actual clock rate = 16500000 6110 SDCard: +SDCreateMemoryList 6112 SDCard: -SDCreateMemoryList 6112 SDBusDriver: SlotStatusChange Work Item Starting Up 6112 SDBusDriver: SlotStatusChange getting message 6112 SDHCInitialize++ 6112 SDHCInitialize-- 6113 SDHC -Init 6122 CSDHCBase::IST: Thread Starting 6122 CSDHCBase::HandleInterrupt: Slot Interrupt_Status=0x0 6122 SDHCControllerIst - Card is Removed Insert Card ==================== 619655 CSDHCBase::HandleInterrupt: Slot Interrupt_Status=0x1 619655 HandleInterrupt (0) - Normal Interrupt_Status=0x40 619655 SDHCControllerIst - Card is Inserted! 619656 CSDHCSlotBase::SetVoltage: Set SDHC_POWER_CONTROL reg = 0x0f 619907 SDHCSetRate - Clock Control Reg = 8001 619907 SDHCSetRate - Actual clock rate = 128906 619910 SDCard: +SDAllocateFromMemList 619910 SDCard: -SDAllocateFromMemList 619910 SDBusDriver: SlotStatusChange Dispatching message event: 2 619910 SDBusDriver: HandleAddDevice+ 619910 SDCard: +AllocateMemoryWithTag 619910 SDCard: -AllocateMemoryWithTag 619910 SDGetClientFunctions: +Init 619912 SDGetClientFunctions: -Init 619912 SDBusDriver: HandleAddDevice - Delaying init: 1 MS 619914 CSDHCBase::SlotOptionHandler(0, SDHCDSetSlotInterface) 619914 CSDHCSlotBase::SlotOptionHandler: Clock Setting: 100000 619914 SHCSDSlotOptionHandler - Setting Host Control Register 0 619914 SDHCSetRate - Clock Control Reg = 8001 619914 SDHCSetRate - Actual clock rate = 128906 619914 SDSetCardInterfaceForSlot - HC ClockRate differs desired setting: desired: 100000 Hz, Actual : 128906 Hz 619914 SDBusDriver: Checking for SDIO card in slot 0 .... 619914 SDCard: SendSynchCommandRequest+ 619915 SDCard: SDBusRequest+ 619916 SDCard: +SDAllocateFromMemList 619918 SDCard: -SDAllocateFromMemList 619918 SDBus: Allocated request 0x00043588 619918 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619918 +++ SDCard: CMD5 CMDArg: 0x00000000 TransferClass:2 ResponseType: R4 619918 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619918 CSDHCSlotBase::BusRequestHandler: CMD:5 619919 CSDHCSlotBase::SubmitBusRequestHandler: CMD:5 619919 Sending command register 0x0502 619919 Sending command Argument 0x00000000 619920 HandleInterrupt (0) - Normal Interrupt_Status=0x8000 619920 CSDHCBase::HandleInterrupt: Slot Interrupt_Status=0x0 619920 SDCard: +SDFreeToMemList 619920 SDCard: -SDFreeToMemList 619921 SDBus: Freed request 0x00043588 619921 SDCard: SDBusRequest- 619921 SDCard: SendSynchCommandRequest- 619921 SDBusDriver: SDIO Card check timeout, moving on 619921 SDBusDriver: Instructing new card in slot 0 to go IDLE 619921 SDCard: SendSynchCommandRequest+ 619921 SDCard: SDBusRequest+ 619922 SDCard: +SDAllocateFromMemList 619922 SDCard: -SDAllocateFromMemList 619922 SDBus: Allocated request 0x00043588 619922 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619922 +++ SDCard: CMD0 CMDArg: 0x00000000 TransferClass:2 ResponseType: NoResponse 619922 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619922 CSDHCSlotBase::BusRequestHandler: CMD:0 619923 CSDHCSlotBase::SubmitBusRequestHandler: CMD:0 619923 Sending command register 0x0000 619923 Sending command Argument 0x00000000 619923 HandleInterrupt (0) - Normal Interrupt_Status=0x01 619924 SDCard: SDBusRequest- 619924 SDCard: +SDFreeToMemList 619924 SDCard: -SDFreeToMemList 619924 SDBus: Freed request 0x00043588 619924 SDCard: SendSynchCommandRequest- 619924 SDBusDriver: Checking for MMC Card in slot 0 619924 SDCard: SendSynchCommandRequest+ 619925 SDCard: SDBusRequest+ 619925 SDCard: +SDAllocateFromMemList 619926 SDCard: -SDAllocateFromMemList 619927 SDBus: Allocated request 0x00043588 619927 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619927 +++ SDCard: CMD1 CMDArg: 0x00300000 TransferClass:2 ResponseType: R3 619927 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619927 CSDHCSlotBase::BusRequestHandler: CMD:1 619927 CSDHCSlotBase::SubmitBusRequestHandler: CMD:1 619928 Sending command register 0x0102 619928 Sending command Argument 0x00300000 619929 HandleInterrupt (0) - Normal Interrupt_Status=0x8000 619929 CSDHCBase::HandleInterrupt: Slot Interrupt_Status=0x0 619929 SDCard: +SDFreeToMemList 619929 SDCard: -SDFreeToMemList 619929 SDBus: Freed request 0x00043588 619930 SDCard: SDBusRequest- 619930 SDCard: SendSynchCommandRequest- 619930 SDCard: SendSynchCommandRequest+ 619930 SDCard: SDBusRequest+ 619930 SDCard: +SDAllocateFromMemList 619930 SDCard: -SDAllocateFromMemList 619930 SDBus: Allocated request 0x00043588 619931 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619931 +++ SDCard: CMD55 CMDArg: 0x00000000 TransferClass:2 ResponseType: R1 619931 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619931 CSDHCSlotBase::BusRequestHandler: CMD:55 619931 CSDHCSlotBase::SubmitBusRequestHandler: CMD:55 619931 Sending command register 0x371A 619931 Sending command Argument 0x00000000 619933 HandleInterrupt (0) - Normal Interrupt_Status=0x01 619933 SDCard: SDBusRequest- 619933 SDCard: +SDFreeToMemList 619933 SDCard: -SDFreeToMemList 619933 SDBus: Freed request 0x00043588 619933 SDCard: SendSynchCommandRequest- 619933 SDCard: SendSynchCommandRequest+ 619934 SDCard: SDBusRequest+ 619935 SDCard: +SDAllocateFromMemList 619935 SDCard: -SDAllocateFromMemList 619936 SDBus: Allocated request 0x00043588 619936 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619936 +++ SDCard: CMD41 CMDArg: 0x00000000 TransferClass:2 ResponseType: R3 619936 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619936 CSDHCSlotBase::BusRequestHandler: CMD:41 619936 CSDHCSlotBase::SubmitBusRequestHandler: CMD:41 619936 Sending command register 0x2902 619937 Sending command Argument 0x00000000 619938 HandleInterrupt (0) - Normal Interrupt_Status=0x01 619938 SDCard: SDBusRequest- 619938 SDCard: +SDFreeToMemList 619938 SDCard: -SDFreeToMemList 619938 SDBus: Freed request 0x00043588 619938 SDCard: SendSynchCommandRequest- 619938 SDBusDriver: SDMemory Card detected in slot 0 619939 SDBusDriver: Device Power Range:0x00FF8000 matches HC desired power: 0x00100000 619939 SDBusDriver: Setting slot 0 power to 0x00100000 619939 CSDHCBase::SlotOptionHandler(0, SDHCDSetSlotPower) 619941 SDCard: SendSynchCommandRequest+ 619941 SDCard: SDBusRequest+ 619941 SDCard: +SDAllocateFromMemList 619941 SDCard: -SDAllocateFromMemList 619941 SDBus: Allocated request 0x00043588 619941 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619941 +++ SDCard: CMD0 CMDArg: 0x00000000 TransferClass:2 ResponseType: NoResponse 619942 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619942 CSDHCSlotBase::BusRequestHandler: CMD:0 619942 CSDHCSlotBase::SubmitBusRequestHandler: CMD:0 619942 Sending command register 0x0000 619942 Sending command Argument 0x00000000 619943 HandleInterrupt (0) - Normal Interrupt_Status=0x01 619943 SDCard: SDBusRequest- 619943 SDCard: +SDFreeToMemList 619943 SDCard: -SDFreeToMemList 619943 SDBus: Freed request 0x00043588 619943 SDCard: SendSynchCommandRequest- 619944 SDBusDriver: Power Set, checking card in slot 0, MaxRetries: 40, Time: 2000 MS, Interval: 50 MS 619944 SDCard: SendSynchCommandRequest+ 619944 SDCard: SDBusRequest+ 619944 SDCard: +SDAllocateFromMemList 619944 SDCard: -SDAllocateFromMemList 619944 SDBus: Allocated request 0x00043588 619944 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619945 +++ SDCard: CMD55 CMDArg: 0x00000000 TransferClass:2 ResponseType: R1 619945 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619945 CSDHCSlotBase::BusRequestHandler: CMD:55 619945 CSDHCSlotBase::SubmitBusRequestHandler: CMD:55 619945 Sending command register 0x371A 619945 Sending command Argument 0x00000000 619947 HandleInterrupt (0) - Normal Interrupt_Status=0x01 619947 SDCard: SDBusRequest- 619947 SDCard: +SDFreeToMemList 619947 SDCard: -SDFreeToMemList 619948 SDBus: Freed request 0x00043588 619948 SDCard: SendSynchCommandRequest- 619948 SDCard: SendSynchCommandRequest+ 619948 SDCard: SDBusRequest+ 619950 SDCard: +SDAllocateFromMemList 619950 SDCard: -SDAllocateFromMemList 619950 SDBus: Allocated request 0x00043588 619950 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 619951 +++ SDCard: CMD41 CMDArg: 0x00100000 TransferClass:2 ResponseType: R3 619951 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 619951 CSDHCSlotBase::BusRequestHandler: CMD:41 619951 CSDHCSlotBase::SubmitBusRequestHandler: CMD:41 619951 Sending command register 0x2902 619951 Sending command Argument 0x00100000 619952 HandleInterrupt (0) - Normal Interrupt_Status=0x01 619952 SDCard: SDBusRequest- 619953 SDCard: +SDFreeToMemList 619953 SDCard: -SDFreeToMemList 619953 SDBus: Freed request 0x00043588 619953 SDCard: SendSynchCommandRequest- 619953 SDBusDriver: Card in slot 0 not ready, countdown: 40 620004 SDCard: SendSynchCommandRequest+ 620004 SDCard: SDBusRequest+ 620004 SDCard: +SDAllocateFromMemList 620004 SDCard: -SDAllocateFromMemList 620004 SDBus: Allocated request 0x00043588 620004 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 620004 +++ SDCard: CMD55 CMDArg: 0x00000000 TransferClass:2 ResponseType: R1 620005 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 620005 CSDHCSlotBase::BusRequestHandler: CMD:55 620005 CSDHCSlotBase::SubmitBusRequestHandler: CMD:55 620005 Sending command register 0x371A 620005 Sending command Argument 0x00000000 620006 HandleInterrupt (0) - Normal Interrupt_Status=0x01 620006 SDCard: SDBusRequest- 620007 SDCard: +SDFreeToMemList 620007 SDCard: -SDFreeToMemList 620007 SDBus: Freed request 0x00043588 620007 SDCard: SendSynchCommandRequest- 620007 SDCard: SendSynchCommandRequest+ 620007 SDCard: SDBusRequest+ 620007 SDCard: +SDAllocateFromMemList 620008 SDCard: -SDAllocateFromMemList 620008 SDBus: Allocated request 0x00043588 620008 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 620008 +++ SDCard: CMD41 CMDArg: 0x00100000 TransferClass:2 ResponseType: R3 620008 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 620008 CSDHCSlotBase::BusRequestHandler: CMD:41 620008 CSDHCSlotBase::SubmitBusRequestHandler: CMD:41 620009 Sending command register 0x2902 620009 Sending command Argument 0x00100000 620010 HandleInterrupt (0) - Normal Interrupt_Status=0x01 620010 SDCard: SDBusRequest- 620011 SDCard: +SDFreeToMemList 620011 SDCard: -SDFreeToMemList 620011 SDBus: Freed request 0x00043588 620011 SDCard: SendSynchCommandRequest- 620011 SDBusDriver: Card in slot 0 not ready, countdown: 39 620062 SDCard: SendSynchCommandRequest+ 620066 SDCard: SDBusRequest+ 620066 SDCard: +SDAllocateFromMemList 620066 SDCard: -SDAllocateFromMemList 620066 SDBus: Allocated request 0x00043588 620067 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 620068 +++ SDCard: CMD55 CMDArg: 0x00000000 TransferClass:2 ResponseType: R1 620068 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 620068 CSDHCSlotBase::BusRequestHandler: CMD:55 620069 CSDHCSlotBase::SubmitBusRequestHandler: CMD:55 620069 Sending command register 0x371A 620069 Sending command Argument 0x00000000 620070 HandleInterrupt (0) - Normal Interrupt_Status=0x01 620070 SDCard: SDBusRequest- 620070 SDCard: +SDFreeToMemList 620070 SDCard: -SDFreeToMemList 620071 SDBus: Freed request 0x00043588 620071 SDCard: SendSynchCommandRequest- 620071 SDCard: SendSynchCommandRequest+ 620071 SDCard: SDBusRequest+ 620071 SDCard: +SDAllocateFromMemList 620073 SDCard: -SDAllocateFromMemList 620073 SDBus: Allocated request 0x00043588 620073 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 620073 +++ SDCard: CMD41 CMDArg: 0x00100000 TransferClass:2 ResponseType: R3 620074 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 620074 CSDHCSlotBase::BusRequestHandler: CMD:41 620074 CSDHCSlotBase::SubmitBusRequestHandler: CMD:41 620074 Sending command register 0x2902 620074 Sending command Argument 0x00100000 620075 HandleInterrupt (0) - Normal Interrupt_Status=0x01 620075 SDCard: SDBusRequest- 620075 SDCard: +SDFreeToMemList 620076 SDCard: -SDFreeToMemList 620076 SDBus: Freed request 0x00043588 ======== Removed repeated countdowns === 38 thru 5 ============ 620076 SDCard: SendSynchCommandRequest-countdown: 4 622159 SDCard: SendSynchCommandRequest+ 622159 SDCard: SDBusRequest+ 622160 SDCard: +SDAllocateFromMemList 622160 SDCard: -SDAllocateFromMemList 622160 SDBus: Allocated request 0x00043588 622160 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 622160 +++ SDCard: CMD55 CMDArg: 0x00000000 TransferClass:2 ResponseType: R1 622161 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 622161 CSDHCSlotBase::BusRequestHandler: CMD:55 622161 CSDHCSlotBase::SubmitBusRequestHandler: CMD:55 622161 Sending command register 0x371A 622161 Sending command Argument 0x00000000 622162 HandleInterrupt (0) - Normal Interrupt_Status=0x01 622162 SDCard: SDBusRequest- 622162 SDCard: +SDFreeToMemList 622163 SDCard: -SDFreeToMemList 622163 SDBus: Freed request 0x00043588 622163 SDCard: SendSynchCommandRequest- 622163 SDCard: SendSynchCommandRequest+ 622163 SDCard: SDBusRequest+ 622163 SDCard: +SDAllocateFromMemList 622163 SDCard: -SDAllocateFromMemList 622164 SDBus: Allocated request 0x00043588 622164 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 622164 +++ SDCard: CMD41 CMDArg: 0x00100000 TransferClass:2 ResponseType: R3 622164 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 622164 CSDHCSlotBase::BusRequestHandler: CMD:41 622164 CSDHCSlotBase::SubmitBusRequestHandler: CMD:41 622164 Sending command register 0x2902 622165 Sending command Argument 0x00100000 622166 HandleInterrupt (0) - Normal Interrupt_Status=0x01 622166 SDCard: SDBusRequest- 622166 SDCard: +SDFreeToMemList 622167 SDCard: -SDFreeToMemList 622167 SDBus: Freed request 0x00043588 622167 SDCard: SendSynchCommandRequest- 622167 SDBusDriver: Card in slot 0 not ready, countdown: 3 622218 SDCard: SendSynchCommandRequest+ 622218 SDCard: SDBusRequest+ 622218 SDCard: +SDAllocateFromMemList 622218 SDCard: -SDAllocateFromMemList 622218 SDBus: Allocated request 0x00043588 622218 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 622218 +++ SDCard: CMD55 CMDArg: 0x00000000 TransferClass:2 ResponseType: R1 622219 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 622219 CSDHCSlotBase::BusRequestHandler: CMD:55 622219 CSDHCSlotBase::SubmitBusRequestHandler: CMD:55 622219 Sending command register 0x371A 622219 Sending command Argument 0x00000000 622220 HandleInterrupt (0) - Normal Interrupt_Status=0x01 622220 SDCard: SDBusRequest- 622220 SDCard: +SDFreeToMemList 622221 SDCard: -SDFreeToMemList 622221 SDBus: Freed request 0x00043588 622221 SDCard: SendSynchCommandRequest- 622221 SDCard: SendSynchCommandRequest+ 622221 SDCard: SDBusRequest+ 622222 SDCard: +SDAllocateFromMemList 622222 SDCard: -SDAllocateFromMemList 622223 SDBus: Allocated request 0x00043588 622223 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 622223 +++ SDCard: CMD41 CMDArg: 0x00100000 TransferClass:2 ResponseType: R3 622223 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 622223 CSDHCSlotBase::BusRequestHandler: CMD:41 622223 CSDHCSlotBase::SubmitBusRequestHandler: CMD:41 622223 Sending command register 0x2902 622224 Sending command Argument 0x00100000 622225 HandleInterrupt (0) - Normal Interrupt_Status=0x01 622225 SDCard: SDBusRequest- 622225 SDCard: +SDFreeToMemList 622225 SDCard: -SDFreeToMemList 622225 SDBus: Freed request 0x00043588 622225 SDCard: SendSynchCommandRequest- 622225 SDBusDriver: Card in slot 0 not ready, countdown: 2 622277 SDCard: SendSynchCommandRequest+ 622277 SDCard: SDBusRequest+ 622277 SDCard: +SDAllocateFromMemList 622277 SDCard: -SDAllocateFromMemList 622277 SDBus: Allocated request 0x00043588 622277 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 622277 +++ SDCard: CMD55 CMDArg: 0x00000000 TransferClass:2 ResponseType: R1 622277 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 622278 CSDHCSlotBase::BusRequestHandler: CMD:55 622278 CSDHCSlotBase::SubmitBusRequestHandler: CMD:55 622278 Sending command register 0x371A 622278 Sending command Argument 0x00000000 622279 HandleInterrupt (0) - NormalInterrupt_Status=0x01 622279 SDCard: SDBusRequest- 622279 SDCard: +SDFreeToMemList 622280 SDCard: -SDFreeToMemList 622280 SDBus: Freed request 0x00043588 622280 SDCard: SendSynchCommandRequest- 622280 SDCard: SendSynchCommandRequest+ 622280 SDCard: SDBusRequest+ 622282 SDCard: +SDAllocateFromMemList 622282 SDCard: -SDAllocateFromMemList 622282 SDBus: Allocated request 0x00043588 622282 SDBusDriver: Submitting bus request:0x00043588 to device TempInitDevice0 622283 +++ SDCard: CMD41 CMDArg: 0x00100000 TransferClass:2 ResponseType: R3 622284 +++ SDCard: Calling Send Handler for HC:SD Std Host. Slot:0, Request:0x00043588 622284 CSDHCSlotBase::BusRequestHandler: CMD:41 622284 CSDHCSlotBase::SubmitBusRequestHandler: CMD:41 622284 Sending command register 0x2902 622284 Sending command Argument 0x00100000 622285 HandleInterrupt (0) - Normal Interrupt_Status=0x01 622286 SDCard: SDBusRequest- 622286 SDCard: +SDFreeToMemList 622286 SDCard: -SDFreeToMemList 622286 SDBus: Freed request 0x00043588 622286 SDCard: SendSynchCommandRequest- 622286 SDBusDriver: Card in slot 0 not ready, countdown: 1 622337 SDBusDriver: HandleAddDevice- 622337 SDCard: +SDFreeToMemList 622340 SDCard: -SDFreeToMemList 622341 SDBusDriver: SlotStatusChange getting message ================================ Remove Card =============== 838589 CSDHCBase::HandleInterrupt: Slot Interrupt_Status=0x1 838589 HandleInterrupt (0) - Normal Interrupt_Status=0x80 838589 SDHCControllerIst - Card is Removed! 838589 SDCard: +SDAllocateFromMemList 838589 SDCard: -SDAllocateFromMemList 838590 SDBusDriver: SlotStatusChange Dispatching message event: 1 838591 SDBusDriver: HandleRemoveDevice+ 838591 SDCard: +SDFreeMemory 838591 SDCard: -SDFreeMemory 838591 SDUnloadDevice: Client Device deleted 838592 SDBusDriver: HandleRemoveDevice- 838592 SDCard: +SDFreeToMemList 838592 SDCard: -SDFreeToMemList 838592 SDBusDriver: SlotStatusChange getting message Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110993
  - 3
    - usbmsfn on wince 5.0 Hi, all I am trying to my device as mass storage to Apple Mac OS. I could not see my device on Mac system. The usb mass storage function is compatible with Mac OS? Please give me some suggestions. Best Regards, Hanko Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110984
  - 4
    - Q965/ICH8 BSP for WINCE 5.0 and WINCE 6.0 Dear Sir, Does anyone have Q965/ICH8 BSP for WINCE 5.0 / WINCE 6.0 platform or where can I get the BSP ? BR, dirw Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110983
  - 5
    - Getting MSMQ to run on BOOT // Another question from Bobby I found this (http://msdn2.microsoft.com/en-us/library/ms905802.aspx) and was wondering if I could use the "QueueManagerGUID" and still have it run on boot? // Original Answer from John We force people to call the commands the first time because MSMQ needs to create a UUID for the machine on 1st use - msmqadm register. If MSMQ tried to get its UUID the 1st time a device ever booted without user intercaction, there's the chance (very slight) that if the system clock weren't set already then we could get the same random # when we call the random # generator since every clock would be 12:00:05AM, 1/1/08. This way people presumably set the clock 1st and then msmqdam register. Now CE's random # generator is better than only relying on current device time, but the original implementor was paranoid. You can check out the MSMQADm source code at \public\servers\sdk\samples\msmq\msmqadm to get a sense of what it's doing. Basically all this stuff is just registry writes. You could potentially implement equivalent of this stuff in .Net, probably easier is to have a boottime program that just does CreateProcess("msmqadm","register",...) on each command. In theory you could also burn the MSMQ device GUID in at ROM creation time, though since it's important GUID's are unique each device would have to have a slightly different img which I imagine is quite hard in practice to make. Finally, if you have followups let's take the conversation to microsoft.public.windowsce.platbuilder newsgroup, copying+pasting what we have, so the whole community can benefit. John // Original Email from Bobby Cannon I would like any help possible. I have a project that I am working on that requires MSMQ. I have create a new Windows CE 6.0 R2 image that includes everything I need (.NET 3.5 Headless, MSMQ, etc...). The problem is that I have to manually start MSMQ with the following three commands. msmqadm register msmqadm enable binary msmqadm start Then run my apps. How can I start the image and have MSMQ already running. Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110981
  - 6
    - kitl debug question Hello, on WINCE 5.0 I have built a debug image, my Device connectivity is set for ethernet, Debugger is KdStub, I can download the image via ethernet but the debugger never switches to Ethernet once the image loads. all my debug messages come out in my serial port console and not via my etehrnet to the debug output window ? what am I missing for the handoff ? Thanks, Joe W. Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110976
  - 7
    - Should I do any other settings except the IMGSDBUS2 to let sdbus2 work? I set the IMGSDBUS2=1 in Platformbuild5. But after builing , I even can not see the directory name for the SD card any more. I thought that my SDHC driver should also link to the SDBUS2 interface, but I have not found which file to be modified for that. Can anyone imply me? I use S3C2410_SDHC drive. Thanks! Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110975
  - 8
    - Relationship between battdrvr and pm Hi All What is the relation ship between power manager and battery driver? How the power manager accesses battery functions. I use sample battery driver supplied with wince 5.0 and unmodified pm code with smdk2440. I get following prefetch abort exception while booting the system -- Message posted via PocketPCJunkies.com http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200803/1 Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110973
  - 9
    - Debug OS CE6 image crash when TAPI is included Hi, I have build a CE6.0 debug image. When using VS2005+PB I can debug my image without problems (LoadCEPC eboot.bin and Target | Attach Device from VS) When I run the image without VS attached (LoadCEPC nk.bin), all output is redirected to COM1 in the bootloader (this is so by default, OK), but when at some point tapi.dll is loaded in memory (see logging), the debug image crashes. If I remove the TAPI dependency from my image, the debug image starts fine. When I run the release version of the image (with TAPI included) it also works fine, but than COM1 is not stolen for debug messages. I guess this problem has to do with a conflict between redirecting debug to COM1 and thus stealing COM1 from the available serial ports in my image. The problem is I can not see what is going on, because the source code of TAPI.DLL is not in the shared source. Does anybody know what might go wrong? This used to work in WinCE5. Werner I want to run the debug image without PB to detect some strange problems I have in a driver (that emits debug logging when something goes wrong with it). Hooking up VS and PB is tooooo slow and I can not deploy this on several devices at the same time. TAPI is included automatically in the image as soon as you include the network UI component which I need for ethernet (ip address,...) Logging of what goes wrong when tapi.dll is loaded... <--- More logging before ---> CardBus.DLL DLL_PROCESS_ATTACH DeviceFolder::LoadDevice(Drivers\BuiltIn\PCCARD) last 109 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Serial\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'coredll.dll' (0x8F5F9630) at address 0x40010000-0x400E4000 in Process 'udevice.exe' (0x8F445570) OSAXST1: >>> Loading Module 'udevice.exe' (0x8F445570) at address 0x00010000-0x00016000 in Process 'udevice.exe' (0x8F445570) udevice.exe $udevice_0003 FSDMGR!MountTable_t::RegisterVolumeName: Registered "$udevice_0003" at index 9APISCreateAPIHandle: pvData == NULL FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 9 (Name="$udevice_0003", MountFlags=0x101)OSAXST1: >>> Loading Module 'notify.dll' (0x8F4368AC) at address 0x400F000 0-0x40107000 in Process 'NK.EXE' (0x82A17C80) OSAXST1: >>> Loading Module 'notify.dll' (0x8F4368AC) at address 0x400F0000-0x40107000 in Process 'udevice.exe' (0x8F445570) [NOTIFY] Module loaded [NOTIFY] Initializing. [NOTIFY] Initialization completed successfully OSAXST1: >>> Loading Module 'coredll.dll' (0x8F5F9630) at address 0x40010000-0x400E4000 in Process 'udevice.exe' (0x8F25C000) OSAXST1: >>> Loading Module 'udevice.exe' (0x8F25C000) at address 0x00010000-0x00016000 in Process 'udevice.exe' (0x8F25C000) udevice.exe $udevice_1001 FSDMGR!MountTable_t::RegisterVolumeName: Registered "$udevice_1001" at index 10APISCreateAPIHandle[NOTIFY] ProcessDatabase::started at local time 03/21/2008 15:07:55 : pvData == NULL FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 10 (Name="$udevice_1001", MountFlags=0x101)OSAXST1: >>> Loading Module 'com16550.dll' (0x8F25B648) at address 0x41CF0000-0x41D05000 in Process 'NK.EXE' (0x82A17C80) OSAXST1: >>> Loading Module 'com16550.dll' (0x8F25B648) at address 0x41CF0000-0x41D05000 in Process 'udevice.exe' (0x8F25C000) OSAXST1: >>> Loading Module 'ceddk.dll' (0x8F25B780) at address 0x40270000-0x4027A000 in Process 'NK.EXE' (0x82A17C80) OSAXST1: >>[NOTIFY] HandleSystemEvent 7 /ADD DMA1: [NOTIFY] HandleSystemEvent 7 /ADD NFY0: > Loading Module 'ceddk.dll' (0x8F25B780) at address 0x40270000-0x4027A000 in Process 'udevice.exe' (0x8F25C000) DeviceFolder::LoadDevice(Drivers\BuiltIn\Serial) last 556 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Parallel\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'parallel.dll' (0x8F0B4818) at address 0xC0E00000-0xC0E0C000 in Process 'NK.EXE' (0x82A17C80) parallel port process attach [LPT_Init]: entry Drivers\Active\4294967292. >RegisterLPTName Regis[NOTIFY] HandleSystemEvent 7 /ADD COM1: terLPTName: adding 'LPT1:' as 'Port5' <RegisterLPTName DeviceFolder::LoadDevice(Drivers\BuiltIn\Parallel) last 108 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NLed\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'nleddrvr.dll' (0x8F0B4960) at address 0xC0E10000-0xC0E15000 in Process 'NK.EXE' (0x82A17C80) DeviceFolder::LoadDevice(Drivers\BuiltIn\NLed)[NOTIFY] HandleSystemEvent 7 /ADD LPT1: [NOTIFY] HandleSystemEvent 7 /ADD NLD1: last 56 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\TAPI\Prefix) returned 2 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\TAPI\BusPrefix) returned 2 OSAXST1: >>> Loading Module 'tapi.dll' (0x8F0B4B58) at address 0xC08C0000-0xC0904000 in Process 'NK.EXE' (0x82A17C80) OSAXST1: >>> Loading Module 'unimodem.dll' (0x8F0B4E10) at address 0xC0910000-0xC0934000 in Process 'NK.EXE' (0x82A17C80) DeviceFolder::LoadDevice(Drivers\BuiltIn\TAPI) last 111 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NTLMSSP_SVC\BusPrefix) returned 2 Exception 'Access Violation' (14): Thread-Id=015e0006(pth=8f0bc1a4), Proc-Id=00400002(pprc=82a17c80) 'NK.EXE', VM-active=00400002(pprc=82a17c80) 'NK.EXE' PC=802aec24(kernel.dll+0x0005cc24) RA=802bd400(kernel.dll+0x0006b400) SP=d064fa40, BVA=d004f000 WriteMsgQueue: copy data error Exception 'Access Violation' (14): Thread-Id=015e0006(pth=8f0bc1a4), Proc-Id=00400002(pprc=82a17c8OSAXST1: >>> Loading Module 'coredll.dll' (0x8F5F9630) at address 0x40010000-0x400E4000 in Process 'udevice.exe' (0x8F0BC5A4) OSAXST1: >>> Loading Module 'udevice.exe' (0x8F0BC5A4) at address 0x00010000-0x00016000 in Process 'udevice.exe' (0x8F0BC5A4) udevice.exe $udevice_1002 FSDMGR!MountTable_t::RegisterVolumeName: Registered "$udevice_1002" at index 11APISCreateAPIHandle: p0) 'NK.EXE', VM-active=00400002(pprc=82a17c80) 'NK.EXE' PC=802af08a(kernel.dll+0x0005d08a) RA=802af27e(kernel.dll+0x0005d27e) SP=d064fa20, BVA=cccccce4 vData == NULL FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 11 (Name="$udevice_1002", MountFlags=0x101)OSAXST1: >>> Loading Module 'ntlmssp_svc.dll' (0x8F0BB888) at address 0x41D30000-0x41D57000 in Process 'NK.EXE' (0x82A17C80) OSAXST1: >>> Loading Module 'ntlmssp_svc.dll' (0x8F0BB888) at address 0x41D30000-0x41D57000 in Process 'udevice.exe' (0x8F0BC5A4) OSAXST1: >>> Loading Module 'rsaenh.dll' (0x8F0BB9E4) at address 0x41D60000-0x41D84000 in Process 'NK.EXE' (0x82A17C80) OSAXST1: >>> Loading Module 'rsaenh.dll' (0x8F0BB9E4) at address 0x41D60000-0x41D84000 in Process 'udevice.exe' (0x8F0BC5A4) <--- Logging stops here---> Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110971
  - 10
    - Develop/debug driver without creating OS? I have a need to develop a USB device driver for Windows CE 5.0. I do have platform builder for that version. But the units I need to run on already have CE installed on them in ROM. All of the help text I've found on debugging CE drivers assume that you're developing an OS image as well. Is it possible to use this for what I need to do, or can I debug my driver with something else, Visual Studio or Embedded VC++? I hope so, printf debugging will be painful. Thanks in advance for any help. Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110963
  - 11
    - Question about AppVerif Hi guys, We develop a x86 device that runs Windows CE 6. A couple weeks ago we started to use AppVerif on many of our applications. We found a lot of handle not closed and some heap leak. Now we suspect that some of our services are causing a memory leak. We would like to use the same application to see where those leaks are. The problem is that we can;t find a way to stop serviced.exe. How can we stop it? Does stopping all services will stop serviced.exe? I would also like to know if someone noticed that all the C Runtime functions are not monitored by AppVerif? A call to fopen without a fclose will not be visible in the appverif log. How can I verify these functions for leaks? Thanks. Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110959
  - 12
    - Determining Driver\Active subkey value Hello, I'm fixing a driver for a custom PCMCIA (CF) card so it works with the latest versions of IPAQs. The problem is that when the CF card is inserted, the Device Manager is now incrementing the socket (Sckt) value each time. This was never the case before and the socket value was always 0x0000. So now my driver has to try to determine what this value is so it can open and return a proper handle to the device. What would be the best way to do this? I started writing a 'for' loop that searched through the active subkeys for the "Name" and then the "Sckt" value, but I got hung up on the fact that I don't know how to find out how many active keys there are and therefore how many times to loop. Does anyone know an easy way to find out what socket value was assigned to an active driver? Thanks, Thomas Magma Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110958
  - 13
    - CE 5.0 - problems booting i855gme-based board Hi all, I'm trying to boot an i855gme-based board with wince 5.0. I'm using loadcepc. Below there is the log I got from the serial port, while booting the eboot.bin and then downloading via ethernet the nk.bin. The display just show a message "jumping to 0x00225738". Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Mar 19 2008 12:22:00 Found ICH with DeviceID=0x3580 Microsoft Windows CE Ethernet Bootloader 3.5 for Intel 855GM/855GME board (Mar 17 2008) Boot Args @ 0x1DF66 and ucLoaderFlags is 1 PCI Device Configurations (2 PCI bus(es) present)... ======================================================== Bus, Device, Function = 0, 0, 1 Vendor ID, Device ID = 0x8086, 0x3584 Base Class, Subclass = 8, 128 => BASE_SYSTEM_DEV Interrupt = 0 ======================================================== Bus, Device, Function = 0, 0, 3 Vendor ID, Device ID = 0x8086, 0x3585 Base Class, Subclass = 8, 128 => BASE_SYSTEM_DEV Interrupt = 0 ======================================================== Bus, Device, Function = 0, 2, 0 Vendor ID, Device ID = 0x8086, 0x3582 Base Class, Subclass = 3, 0 => DISPLAY_CTLR Interrupt = 9 BaseAddress[0] = 0xD8000000 (Memory) BaseAddress[1] = 0xEFF00000 (Memory) BaseAddress[2] = 0xECF8 (I/O) ======================================================== Bus, Device, Function = 0, 2, 1 Vendor ID, Device ID = 0x8086, 0x3582 Base Class, Subclass = 3, 128 => DISPLAY_CTLR Interrupt = 0 BaseAddress[0] = 0xE0000000 (Memory) BaseAddress[1] = 0xEFE80000 (Memory) ======================================================== Bus, Device, Function = 0, 29, 0 Vendor ID, Device ID = 0x8086, 0x24C2 Base Class, Subclass = 12, 3 => SERIAL_BUS_CTLR Interrupt = 9 BaseAddress[4] = 0xECA0 (I/O) ======================================================== Bus, Device, Function = 0, 29, 1 Vendor ID, Device ID = 0x8086, 0x24C4 Base Class, Subclass = 12, 3 => SERIAL_BUS_CTLR Interrupt = 5 BaseAddress[4] = 0xECC0 (I/O) ======================================================== Bus, Device, Function = 0, 31, 1 Vendor ID, Device ID = 0x8086, 0x24CB Base Class, Subclass = 1, 1 => MASS_STORAGE_CTLR Interrupt = 255 BaseAddress[0] = 0x0 (I/O) BaseAddress[1] = 0x0 (I/O) BaseAddress[2] = 0x0 (I/O) BaseAddress[3] = 0x0 (I/O) BaseAddress[4] = 0xECE0 (I/O) ======================================================== Bus, Device, Function = 0, 31, 3 Vendor ID, Device ID = 0x8086, 0x24C3 Base Class, Subclass = 12, 5 => SERIAL_BUS_CTLR Interrupt = 10 BaseAddress[4] = 0xF400 (I/O) ======================================================== Bus, Device, Function = 0, 31, 5 Vendor ID, Device ID = 0x8086, 0x24C5 Base Class, Subclass = 4, 1 => MULTIMEDIA_DEV Interrupt = 10 BaseAddress[0] = 0xE800 (I/O) BaseAddress[1] = 0xEC40 (I/O) BaseAddress[2] = 0xEFFFFC00 (Memory) BaseAddress[3] = 0xEFFFFF00 (Memory) ======================================================== Bus, Device, Function = 1, 7, 1 Vendor ID, Device ID = 0x0000, 0x0000 Base Class, Subclass = 0, 0 => PRE_20 Interrupt = 0 ======================================================== Bus, Device, Function = 1, 7, 2 Vendor ID, Device ID = 0x0000, 0x0000 Base Class, Subclass = 0, 0 => PRE_20 Interrupt = 0 ======================================================== Bus, Device, Function = 1, 7, 3 Vendor ID, Device ID = 0x0000, 0x0000 Base Class, Subclass = 0, 0 => PRE_20 Interrupt = 0 ======================================================== Bus, Device, Function = 1, 7, 4 Vendor ID, Device ID = 0x0000, 0x0000 Base Class, Subclass = 0, 0 => PRE_20 Interrupt = 0 ======================================================== Bus, Device, Function = 1, 7, 5 Vendor ID, Device ID = 0x0000, 0x0000 Base Class, Subclass = 0, 0 => PRE_20 Interrupt = 0 ======================================================== Bus, Device, Function = 1, 7, 6 Vendor ID, Device ID = 0x0000, 0x0000 Base Class, Subclass = 0, 0 => PRE_20 Interrupt = 0 ======================================================== Bus, Device, Function = 1, 7, 7 Vendor ID, Device ID = 0x0000, 0x0000 Base Class, Subclass = 0, 0 => PRE_20 Interrupt = 0 ======================================================== Bus, Device, Function = 1, 8, 0 Vendor ID, Device ID = 0x8086, 0x103A Base Class, Subclass = 2, 0 => NETWORK_CTLR Interrupt = 6 BaseAddress[0] = 0xEFDFF000 (Memory) BaseAddress[1] = 0xDCC0 (I/O) ======================================================== InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 0, dwIoBase = 0, dwDfltType = 2) ... FindI825xx: Searching for I825xxx Ethernet NIC ... FindI825xx: Found Ethernet NIC 0x103A InitKitlNIC: Found Intel NIC (type = 10, IRQ=6, IOBase=0xDCC0). I825xxInitDMABuffer: Start. I825xxInitDMABuffer: End. I825xxInit: Start. eth825xx_init: Baseaddress = DCC0. nicInit link speed (100Mb). I825xxInit: End. Returned MAC Address:00:C0:08:82:8D:66 System ready! Preparing for download... OEMPreDownload ucLoaderFlags is 0 x86KitlCreateName: Using Device Name 'IA3236198' Using device name: IA3236198 Hit ENTER within 3 seconds to enter static IP address!InitDHCP():: Calling ProcessDHCP() ProcessDHCP()::DHCP_INIT Got Response from DHCP server, IP address: 10.11.2.112 ProcessDHCP()::DHCP IP Address Resolved as 10.11.2.112, netmask: 255.255.0.0 Lease time: 5184000 seconds Got Response from DHCP server, IP address: 10.11.2.112 No ARP response in 2 seconds, assuming ownership of 10.11.2.112 +EbootSendBootmeAndWaitForTftp Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Locked Down Link 1 Src IP 10.11.2.112 Port 0800 Dest IP 10.11.2.123 Port 05F6 EthDown::TFTPD_OPEN::boot.bin -EbootSendBootmeAndWaitForTftp Download file information: ----------------------------------------------------- [0]: Address=0x220000 Length=0xF78E94 Name= ****** OEMVerifyMemory Checking Range [ 0x220000 ==> 0x1198E93 ] ****** RAM Address ****** rom_offset=0x80000000. ROMHDR at Address 00220044h OEMLaunch ucLoaderFlags is 7 Download successful! Jumping to image at 00225738h... Got EDBG_CMD_JUMPIMG Got EDBG_CMD_CONFIG, flags:0x00000000 Lauch Windows CE from address 0x225738 Debug Serial Init SysInit: GDTBase=811990e8 IDTBase=811ba860 KData=811c1800 Windows CE Kernel for i486 Built on Feb 8 2007 at 23:34:04 g_pPageDir = 811db000 RTC - Status Reg B - 0x02 X86Init done, OEMAddressTable = 80225758. OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 The same happens if I load the nk.bin from the CF I'm using as local disk. Can anybody help me? Thanks Alessandro Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110957
  - 14
    - Can't hit a breakpoint in CETK source I am trying to debug a GDI CETK failure, but I cannot hit a breakpoint in some source code (I have the shared source installed) that I know is being executed. I believe this is a problem with the Source Path Mapping, but my efforts to fix it have fallen short so far. I looked into the gdiapi.pdb and ddi_test.pdb files and found references to files in the following directories: C:\ymzki\ C:\yzqa\ C:\yzqasp1\ Using the Source Path Mapping tool in PB, I mapped these paths to my Wince root, which is F:\WCE6\WINCE600. Still, I cannot get a breakpoint to hit, or even to show up as a full red circle (I get the unrecognized empty red circle instead). Any pointers on getting a CETK source code breakpoint recognized? Am I missing anything here? Thanks, Danny Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110953
  - 15
    - Autostarting .exe at CE boot I've been doing embedded work for 20 years but I'm new to CE. I kinda got this project dropped on me and time is short. We need to modify an existing and running CE system so that it autostarts a newly written .exe file/app. App is in C#, .net cf 2.0, VS2005. It deploys -- ActiveSync -- and executes on the CE system. We have and can modify the BSP and app source. I've been through various docs several times and have yet to get whatever right! I need to add the .exe to CE such that it autostarts at CE boot. Could someone provide a concise but adequate list of the exact steps we need to do to make that work? Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110951
  - 16
    - OTi 2172 USB Flash Disk Controller 1Hi, I got a board with OTi 272 USB Flash Disk Controller. What should I do to get Wince 6 to load the necessary drivers and recognizes the nand flash memory? Do I need a driver (OYi does not mention any driver for 2172 on it's site) Do I need to change some registry settings? Thanks Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110950
  - 17
    - Accuracy problem in my Touch Driver Hello All, My Touch driver is not working very accurately... when am touching letters or numbers,sometimes BLANK is coming instead of letter or number. And if type something it is deleting the previous character or number (i.e if i type 9 and 2,after i have pressed 2 it is deleting 9) Except the above all the operation like drawing or signature in the notes,calibrations are working fine... Can you please tell me where could be the problem? Thanks in advance Regards Senthil Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110948
  - 18
    - soft keyboard driver I need to modify the sip(software based input panel) in order to support multi-language. I can find the sip is implemented by softkb.dll and the softkb.def says it is composed of SIP_init(), SIP_open(),,,. But I can't find where the source code of softkb.dll is. I need to add some country's keyboard layout to the SIP which is not supported by PB5 default but I can't do it because I didn't find the source code. Is there anybody who can introduce some guide? Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110946
  - 19
    - Does SDBUS support multiple SDHC? Hi All, Currently I am developing a system wtih multiple SD host controller. I meet some issues when card inserted and SD controller could not work well. As I looked into the source code, I found the sdhc controller dll has been load several times and setup different objects for each controller. But SDBUS only be loaded one time. Could this be the issue to impact my design? Any comments are welcome. Thanks in advance. -jimmy Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110942
  - 20
    - WM6 device emulator VS cellular emulator Hi ~ Can anyone tell me how build WM6 pro device emulator image that phone function work with "Cellular emulator"? Any information will be appreciated. Thank you Cheers, SP Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110937
  - 21
    - Command line build Hello, I've set up an Windows Embedded CE 5.0 O/S design. The SYSGEN works fine. I want to run an unattended build on a dedicated machine. The recent source files will be fetched from CVS. I found the "blddemo -q" in the workspace directory of the O/S design would do the job as long as no SYSGEN variables have been changed. What would be the general approach to rebuild the O/S design. The precompiled libs in PUBLIC and PRIVAT must keeped untouched. Andreas Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110935
  - 22
    - KITL Stops polling? I am able to see full functionality of KITL as the device boots. I placed a debug message in OEMEthGetFrame, and I can see every time KITL polls that function to see if debug data is there. However, once the device is done loading, KITL does not call OEMEthGetFrame at all.. It is as if it decided to stop polling. If I run an application that prints a DBGMSG across KITL, then it seems that OEMEthGetFrame gets called again! (just once). My system is in fact set up to use polling: pKitl->Interrupt = KITL_SYSINTR_NOINTR; // use polled mode Below is my debug serial output followed by KITL messages in PB any ideas? Debug serial: ------------------------ Launch: 96CB9000h... ****************************************************** ****************************************************** ****************************************************** ****************************************************** ****************************************************** OEMInitDebugSerial using STUART Windows CE Kernel for ARM (Thumb Enabled) Built on Jan 23 2006 at 13:14:44 ProcessorType=0411 Revision=7 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 96cb94fc Memory controller MDREFR= 11e018 MDCONF= b000bcb MSC0= b9fab9fa MSC1= 7ff07ff4 MSC2= 7ff0fff4 Addr driver globals ba8bb000 Unique ID: 7216:028c:4552:1216 ethernet mac addr 1500 - bfc5 - be89 Addr driver globals ba8bb000 Storing MAC address LAN91C111 MAC Address: 2X- 2X- 2X- 2X- 2X- 2XGPIOReg->GPDR0 = 0xcc98c10 GPIOReg->GAFR0_L = 0x80000000 GPIOReg->GAFR0_U = 0xa5000092 GPIOReg->GPDR1 = 0xcf8880 GPIOReg->GAFR1_L = 0x60918a18 GPIOReg->GAFR1_U = 0xaaa5a0aa GPIOReg->GPDR2 = 0x130c000 GPIOReg->GAFR2_L = 0x6a0aaaaa GPIOReg->GAFR2_U = 0xa400 GPIOReg->GPDR3 = 0x2efc0 GPIOReg->GAFR3_L = 0x0 GPIOReg->GAFR3_U = 0x0 GPIOReg->GPDR1 = 0xcf8880 GPIOReg->GRER1 = 0x0 +OEMKitlInit Checking for LAN91C111 Ethernet controller at B6B00000... Storing MAC address LAN91C111 MAC Address: 2X- 2X- 2X- 2X- 2X- 2X LAN91C111 Configuration Register: 2X LAN91C111 Base Address Register: 2X LAN91C11 1 Revision: 2, Chip: 9 Reading MAC address LAN91C111 MAC Address: 2X- 2X- 2X- 2X- 2X- 2XLAN91C111 Ethernet controller initialized. InitSpecifiedEthDevice: SMSC controller returned: 0.21.197.191.137.190 SMCSetOptions() Dump Driver_Globals (ether stuff only) at : 0xBA8BB000 pDriverGlobals->eth.EbootMagicNum= 0x45424F54 pDriverGlobals->eth.etherEnabled= 0x0 pDriverGlobals->eth.etherFlags= 0x0 pDriverGlobals->eth.TargetAddr.dwIP= 0xCA03A8C0 pDriverGlobals->eth.TargetAddr.wMAC[0]= 0x1500 pDriverGlobals->eth.TargetAddr.wMAC[1]= 0xBFC5 pDriverGlobals->eth.TargetAddr.wMAC[2]= 0xBE89 pDriverGlobals->eth.TargetAddr.wPort= 0x1B07 pDriverGlobals->eth.DownloadHostAddr.dwIP= 0xC803A8C0 pDriverGlobals->eth.DownloadHostAddr.wMAC= 0xBA8BB91C pDriverGlobals->eth.DownloadHostAddr.wPort= 0x1B07 pDriverGlobals->eth.DbgHostAddr.dwIP= 0x0 pDriverGlobals->eth.DbgHostAddr.wMAC= 0xBA8BB928 pDriverGlobals->eth.DbgHostAddr.wPort= 0x0 pDriverGlobals->eth.KdbgHostAddr.dwIP= 0x0 pDriverGlobals->eth.KdbgHostAddr.wMAC= 0xBA8BB934 pDriverGlobals->eth.KdbgHostAddr.wPort= 0x0 pDriverGlobals->eth.PpshHostAddr.dwIP= 0x0 pDriverGlobals->eth.PpshHostAddr.wMAC= 0xBA8BB940 pDriverGlobals->eth.PpshHostAddr.wPort= 0x0 pDriverGlobals->eth.SubnetMask= 0xFFFFFF pDriverGlobals->eth.DHCPLeaseTime= 0x15180 pDriverGlobals->eth.EdbgFlags= 0x0 OEMether IP Addr: 192.168.3.202 OEMether IP netmask: 255.255.255.0 OEMether SMSC on SYSINTR 32: 0 OEMether SYSINTR -1: -14668 Device ISOCHRON35262, IP 192.168.3.202, Port 981 Calling EdbgInitDHCP -OEMKitlInit Got Packet: 98 Host connected Host IP: 192.168.3.200, port 1804 KeyIndex 0 = -1 KeyIndex 1 = -1 KeyIndex 2 = -1 KeyIndex 3 = -1 KeyIndex 4 = -1 KeyIndex 5 = -1 KeyIndex 6 = -1 KeyIndex 7 = -1 +KITLRegisterDfltClient, service:0 +KITLRegisterDfltClient, service:1 KITLGlobalState == 0x61 KitlInit Passed Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0 ProcessAdminMsg: Receive Config message for service DBGMSG ProcessAdminMsg: Receive Config message for service DBGMSG ProcessAdminMsg: Receive Config message for service PPSH ProcessAdminMsg: Receive Config message for service DBGMSG ARMInit done. +KITLRegisterDfltClient, service:2 ProcessAdminMsg: Receive Config message for service KDBG ProcessAdminMsg: Receive Config message for service KDBG KITL: Leaving polling mode... KITL Checking client registrations +RegisterClientPart2: Id 0x00000000 KITL Timer thread started, (hTh: 0x0A4FFF86, pTh: 0x8A4FCB48) -RegisterClientPart2 +RegisterClientPart2: Id 0x00000001 -RegisterClientPart2 0x8a1dc604: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 2 0x8a1dc604: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 2 Platform Builder debug (kitl): ----------------------------------------- Kernel debugger is waiting to connect with target. Kernel debugger failed to connect with target (KDBG open stream failed). Debugger could not initialize connection. Kernel debugger is waiting to connect with target. 0 PID:0 TID:0 Booting Windows CE version 4.20 for (ARM) 0 PID:0 TID:0 &pTOC = 96cc19dc, pTOC = 97a0c770, pTOC->ulRamFree = 97a4a000, MemForPT = 00000000 0 PID:0 TID:0 Old or invalid version stamp in kernel structures - starting clean! 0 PID:0 TID:0 NKEnumExtensionDRAM 0 PID:0 TID:0 Added memory at: 96d4a4f4 for length 7d8 0 PID:0 TID:0 Configuring: Primary pages: 11186, Secondary pages: 16380, Filesystem pages = 6891 0 PID:0 TID:0 Booting kernel with clean memory configuration: 0 PID:0 TID:0 Memory Sections: 0 PID:0 TID:0 [0] : start: 97a4b000, extension: 00003000, length: 02bb2000 0 PID:0 TID:0 [1] : start: 86500000, extension: 00004000, length: 03ffc000 0 PID:0 TID:0 Sp=ffffc7cc 2 PID:0 TID:0 Windows CE KernelInit 4294767297 PID:a4ff002 TID:a4ff262 Updated eptr->e32_vsize to = 000bb000 4294767315 PID:a4ff002 TID:a4ff262 Scheduling the first thread. 4294767347 PID:a4ff002 TID:a4ff262 0x8a4ff024: KernelInit2: pCurThread=8a4ff024 hCurThread=0a4ff262 hCurProc=0a4ff002, KernelInit = 96cdd27c 4294767374 PID:a4ff002 TID:a4ff262 0x8a4ff024: Detecting VFP... 4294767406 PID:a4ff002 TID:a4ff262 0x8a4ff024: VFP Not Found! 4294767439 PID:a4ff002 TID:a4ff262 0x8a4ff024: Updated eptr->e32_vsize to = 00016000 4294767484 PID:a4ff002 TID:a4ff262 0x8a4ff024: >>> Loading module NK.EXE at address 0x96CB8000-0x96D73000 (RW data at 0x97A16000-0x97A42F67) Kernel debugger connected (KDBG stream opened). Kernel Version 1169 loaded at 0x96cb8000, data relocated at 0x97a16000 Debugger connection established (Target CPU is ARM). Loaded symbols for 'C:\WINCE420\PROJECT\HIAD\RELDIR\BVDMAIN-ARMV4IDEBUG \NK.EXE' Loaded symbols for 'C:\WINCE420\PROJECT\HIAD\RELDIR\BVDMAIN-ARMV4IDEBUG \KD.DLL' Finished re-loading kernel modules. 4294767541 PID:a4ff002 TID:a4ff262 0x8a4ff024: first = 01d40000, last = 02000000, SharedDllBase = 027b0000 4294768479 PID:a4ff002 TID:a4ff262 0x8a4ff024: >>> Loading module coredll.dll at address 0x03F10000-0x03FF7000 (RW data at 0x01FFF000-0x01FFFFB8) Loaded symbols for 'C:\WINCE420\PROJECT\HIAD\RELDIR\BVDMAIN-ARMV4IDEBUG \COREDLL.DLL' 4294769063 PID:2a40fb22 TID:2a40fafe 0x8a40f8c0: >>> Loading module filesys.exe at address 0x04010000-0x04091000 Loaded symbols for 'C:\WINCE420\PROJECT\HIAD\RELDIR\BVDMAIN-ARMV4IDEBUG \FILESYS.EXE' 4294769107 PID:2a40fb22 TID:2a40fafe 0x8a40f8c0: FileSystem Starting - starting with clean file system ..... 4294794536 PID:89f59c1e TID:9b0247e 0x89ae5660: NOTIFICATION::XCeRunAppAtEvent 4294794560 PID:89f59c1e TID:9b0247e 0x89ae5660: NOTIFICATION::SetUserNotification (or replacing 00000000) 4294794587 PID:89f59c1e TID:9b0247e 0x89ae5660: NOTIFICATION::SetUserNotification::Registring system watch: event 12 app \\.\Notifications\NamedEvents\DSTTzChange args AppRunAfterTzChange 4294794620 PID:89f59c1e TID:9b0247e 0x89ae5660: NOTIFICATION::XCeRunAppAtEvent 4294794646 PID:89f59c1e TID:9b0247e 0x89ae5660: NOTIFICATION::SetUserNotification (or replacing 00000000) 4294794673 PID:89f59c1e TID:9b0247e 0x89ae5660: NOTIFICATION::SetUserNotification::Registring system watch: event 1 app \\.\Notifications\NamedEvents\DSTTimeChange args AppRunAfterTimeChange 4294794715 PID:6a32d552 TID:8a2e9a5e 0x89cbd4a8: OpenSwMixer - no mixer found 4294794739 PID:6a32d552 TID:8a2e9a5e 0x89cbd4a8: SPS - open failed : 0x1 4294794819 PID:69b5782a TID:69b57806 0x89b02000: <<< Unloading module usbcnect.exe at address 0x10010000-0x10014000 Unloaded symbols for 'C:\WINCE420\PROJECT\HIAD\RELDIR\BVDMAIN- ARMV4IDEBUG\USBCNECT.EXE' 4294804485 PID:6a32d552 TID:ea25182a 0x8a0c98c0: *TCBTimeout: ClearIdleTimerReset 4294804509 PID:6a32d552 TID:ea25182a 0x8a0c98c0: TCBTimeout: setting fTCBTimerOn to 0 4294804536 PID:6a32d552 TID:ea25182a 0x8a0c98c0: *TCBTimeout: NOT Restarting TCBTimer 4294809404 PID:6a32d552 TID:ea25182a 0x8a0c98c0: IPRouteTimeout: setting fIPRouteOn to 0 4294809422 PID:6a32d552 TID:ea25182a 0x8a0c98c0: *IPRouteTimeout: NOT restarting IPRouteTimeout Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110931
  - 23
    - Cannot open the properties of "TCP Connect Transport" Hello, I have strange troubles with the Remote Tools of Visual Studio 2005. I start the Remote Tools using the link in the Start Menu. Than I open the dialog "Target > Connectivity Options". In the list I mark my WinCE6.0 device and hit the "Properties..." button. Now my problem appears: In the dialog "Device Properties" I cannot configure the transport "TCP Connect Transport". If I click on the button "Configure..." no dialog will be opened. Interestingly I can configure the properties of "TCP Connect Transport" using Visual Studio 2005 without any troubles. Does anybody know why I cannot configure "TCP Connect Transport" using the Remote Tools? Regards Peter Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110924
  - 24
    - VoIP codec from CE 5.0 As I known, CE 5.0 support G.711 codec only. If I need to use other enhanced codec, such as G.729, how could I do? Is there any solution ready vendor for VoIP G.729 codec? Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110922
  - 25
    - usbfn mass storage not showing folder in the PC Hi all, I am trying to exposes my storage in my device as mass storage to PC. Wince 5.0 is running on the device.I used the following registry settings ================================================================================= [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers] "DefaultClientDriver"=- ; erase previous default [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers] "DefaultClientDriver"="Mass_Storage_Class" [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Mass_Storage_Class] "Dll"="usbmsfn.dll" "InterfaceSubClass"=dword:06 "InterfaceProtocol"=dword:50 "DeviceName"="DSK1:" "FriendlyName"="Mass Storage" ; idVendor must be changed. 045E belongs to Microsoft and is only to be used for ; prototype devices in your labs. Visit http://www.usb.org to obtain a vendor id. "idVendor"=dword:045E "Manufacturer"="Generic Manufacturer (PROTOTYPE--Remember to change idVendor)" "idProduct"=dword:FFFF "Product"="Generic Mass Storage (PROTOTYPE--Remember to change idVendor)" "bcdDevice"=dword: ===================================================================================== When i connect the device to the host PC.PC is detecting it is mass storage but i am not able to view the folder in the my computer. I can see the icon of mass storage in "safety remove hardware".During this period my "DSK1:" on the device is also unmounted. Anyone know what might be the issue? Prabu Kumar Tag: Does wceusbsh.sys support interface association descriptor? Tag: 110918

Hi,

I am working on composite driver for Wince 6 os.
I am trying to integrate composite driver with my BSp.
Till now I am able to load usb mass storage driver sucessflly single
or with serial_class.
But in case of serial_class, its neither showing wceusbsh.sys or
activesync is working.

Can any body make sure that wceusbsh.sys support IAD.

thanks in advance.

Best regards
Mukesh Modi

Top