Driver for Capture Interface (camera) for PXA27x

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - Ram size recognizing; Hi , I have a small problem in my image, Win Ce5.0: on board, Geode gx300, we installed a RAM of 128 Mbyte but system continuing to recognize only 64Mbyte. There is a mode to fix it . Thank you. Tiziano Fabbri Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67202
  - 2
    - booting from compact flash, x86_geode Hi Luca, Hi Jimbo thank you for yours replys. Today is an experiment's event: double language !! //**// I try to focalize about my boot from compact flash problem using BLDR, project "Loader" %WINCEROOT\public\common\oak\csp\x86\ biosloader\loader: I make modification regarding the definition READ_BUFFER_LENGTH_MAX in fat.h, and building the project by right cliccking on root name "Loader" and selecting menu's row "Build Current Project", all OK. Problem now is exchange new bldr in the floppy disk because in generally I use the utility named setupdisk.144 that, by intuition, looks like a compacted file that by Websetup utility it de-compacted in the floppy disk all necessary (inside there is a bldr version dated April 22th 2004) Over my intuition I did 2 test: starting from a floppy disk made by utility setupdisk.144, compile loader, one with the modification and one in the original format, and one after other one, these are copied to the floppy disk manually: 2 different time 2 different tests. Last operation is preparing the compact flash, that I do on my Geode board, and only at least I copy by hands 3 files, NK.bin, splash.bmx, boot.ini (I make a substitution of eboot.bix with nk.bin in the "BinFile" key in boot.ini), and launching mkdisk c: that prepare disk c:, CF, to boot by bldr. Now I answer at your question Luca, what I see by serial debug: nothing. Bldr continuing sending the comment of this elaborated instruction: {main.c} // Display loader startup banner. RTLMSG(TRUE, ("%s %s.%s (Built %s)\r\n", BLDR_SPLASH_MESSAGE, BLDR_VERSION_MAJOR, BLDR_VERSION_MINOR, __DATE__)); and after system reboot. This is a redundant effect: message and reboot. On video I can see only the ram test and after the reboot. Remember I repeated test one time with the original and one time with modified file but same method of compiling and copy to floppy disk. My conclusion is that although the modification I never tested it !!! One more specify: if I use a floppy disk made with setupdisk.144 in original format, so the contents has been created by utility less than I did any manual operations on it, starting and the debug messages keep sense (look my first newsgroup thread regarding this problem, I don't repeat thread message because I did a long test on 3 differents devices). Please let me know which operations I must to do to use new BLDR. Thank you very much, Tiziano Fabbri //**// Vedo di focalizzare il problema del boot da compact flash utilizzando BLDR, progetto Loader %WINCEROOT\public\common\oak\csp\x86\ biosloader\loader: ho fatto la modifica riguardo la definizione READ_BUFFER_LENGTH_MAX in fat.h, eseguo il building di progetto via tasto destro del mouse clicckando sulla radice loader e selezionando la voce di menu' Build Current Project, tutto ok. Il problema ora Ã¨ sostituire il nuovo bldr nel dischetto visto che generalmente io utilizzo l'utility setupdisk.144 la quale, vado a intuito, sembra essere un file compattato il quale per mezzo dell'utility Websetup si scompatta nel dischetto. Oltre all'intuito ho fatto 2 prove: parto da un dischetto preparato con setupdisk.144, compilo loader uno con la modifica e uno originale e prima uno poi l'altro li copio manualmente sul dischetto che utilizzerÃ². L'operazione finale della preparazione della compact flash, che io faccio a bordo della scheda Geode, e solo in ultimo copio 3 file manualmente per mezzo di card writer/reader: NK.bin, splash.bmx, boot.ini (faccio poi la sostituzione di eboot.bix con nk.bin nella chiave "BinFile" nel file boot.ini), Ã¨ di lanciare mkdisk c:, l'utility prepara c: al boot anche attraverso bldr. Vengo alla domanda che mi hai fatto Luca, cosa vedo via seriale: quasi niente. Bldr mi spedisce il commento elaborato da questa istruzione: {main.c} // Display loader startup banner. RTLMSG(TRUE, ("%s %s.%s (Built %s)\r\n", BLDR_SPLASH_MESSAGE, BLDR_VERSION_MAJOR, BLDR_VERSION_MINOR, __DATE__)); e poi il sistema fa il reboot. Questo effetto Ã¨ ridondante: scritta e reboot. A livello video si vede solo il test della ram e poi c'Ã¨ il reboot. Ricordate ho ripetuto la prova una volta con il bldr originale e l'altra con il progetto modificato, ma utilizzando la stessa tecnica di compilazione e copia manuale sul dischetto. La conclusione Ã¨ che nonostante la modifica ESSA io non l'ho mai testata. Altra precisazione: se utilizzo il dischetto setupdisk.144 in formato originale, il cui contenuto Ã¨ stato creato dall'utility senza che io abbia fatto interventi manuali sopra, l'avviamento e i messaggi in uscita hanno senso (vedi mio primo thread nel newsgroup a riguardo, non sto a ripetere perchÃ¨ avevo fatto un test molto lungo su tre tipi di dispositivi). per favore mi spiegate le operazioni che devo fare per utilizzare il nuovo BLDR. Grazie a tutti. Tiziano Fabbri Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67200
  - 3
    - smdk2410 registry key question? Hi, I am transferring my platform from x86 to smdk2410. If I flash my nk.bin to smdk2410 nand flash, which registry key architecture should I use? Hive ? or Implement the ReadRegistryFromOEM? Is it necessary use the MS Flash driver? Thanks. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67198
  - 4
    - Run-Time Image for the Emulator tutorial doesn't work I'm trying to make the Win CE first tutorial work, but I can't in spite of the fact that I've followed all the instructions one by one. I tried to make it work yesterday and again today with a new project but I've obtained the same error message. Tutorial: Building a Run-Time Image for the Emulator - Step 1: Creating a Custom OS Design for the Emulator Done, everything OK. - Step 2: Building the Custom Run-Time Image for the Emulator Done, everything OK, 0 errors and 4 warnings (the tutorial says not to worry about the warnings) - Step 3: Setting Up a Connection to the Emulator and Downloading the Run-Time Image Doesn't work. I can read on the debugger: Failed to connect debug message service! Please check the transport settings. Transport service failed to connect Warning: One or more services failed to connect. Make sure that the service is properly configured. ***************************************** Since I'm trying to work with the Emulator there are no settings available on Target - Connectivity options - Transport. I would really appreciate if someone could help me. Yours Asier Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67197
  - 5
    - usb host isp1160 issue I use isp116x driver from Philips,and modified the mem address,interrupt,msc.. however,it can't works,when I plug in the usb device,it run to deviceattach:DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS and at WaitForSingleObject( m_hHubStatusChangeEvent, INFINITE ) waiting forever. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67193
  - 6
    - UserKInfo array or API Hook question. Hi I am working with the CE API hook method and able to hook few coredll functions. I am using the API sets from the UserKInfo[KINX_APISETS] array. Some of the coredll functions are in SH_WIN32 API set. The API set for HT_SOCKET is empty (number of methods = 0). I am trying hook the following function AFDConnect in wsock.h(this header is in kernel code that come with platform builder) #define AFDConnect WINSOCK_CALL (DWORD, 4, \ (SOCKHAND Socket, \ LPSOCKADDR Address, \ DWORD AddressLength, \ CRITICAL_SECTION *pDllCS)) My guess is the HT_SOCKET API set in UserKInfo[] array probably gets filled after a SOCKET HANDLE is created thru AFDSocket() call. Since AFDSocket() is under API set SH_COMM and I am able to hook it. I tried to dump the UserKInfo[KINX_APISETS] inside the AFDSocket() hook after the call to original AFDSocket() has returned. Even then HT_SOCKET set in UserKInfo says the number of methods is 0 (Not filled yet). So I am unable to hook HT_SOCKET calls. Can some please let me know when this HT_SOCKET API set gets filled or is it possible to hook HT_SOCKET calls? Thanks very much for any help. Have a good day Ganesan Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67191
  - 7
    - Windows CE virtual Modem Driver - Not Dynamically being added to TAPI modem list. I have written a virtual modem driver for CE5.0. I register the device in the _Init function. I initially had a DeviceType of 1 for an external modem. I tried to change it to 7 for a dynamic modem. When I load it after a cold boot, the device is in the registry but doesn't show up on a modem list (ex when creating a new dial-up connection) until after a warm boot. It is as if TAPI locks out reenumeration of the modem list after a warm boot. Is there something I'm doing wrong? I have looked in the TSPI_lineOpen call in tspi.c and I think I'm doing the same thing. The only thing I may not be doing like TSPI_lineOpen is the use of he instance context blob (parameter 4 in RegisterDevice). I can't seem to find good documentation on this parameter. Thanks. Gene Chang Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67174
  - 8
    - USB Transport option in PB5 What exactly is the USB transport option in the PB kernel transport configuration dialog box? When selected, "(USBDevice)" is listed underneath the dropdown box. How is this different from SERIAL when using a USB serial function driver on the device side? Help doesn't provide much info at all - just states that when using USB-KITL as the transport - you can disable logging of all KITL packets via a "usbserkitl" key in the registry. What host side driver does PB use when configured for this USB transport? Thanks, -Chris Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67173
  - 9
    - CEPC BSP for P4 Does anyone know of a third party BSP for a motherbaord with a P4 processor. The CEPC x86 BSP shipped with PB 5.0 supports only P5,PII,PIII,Celeron,K6x and Athlon processors as per MSDN documentation. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67171
  - 10
    - Bluetooth Manager - Scanning devices Hi! I'm facing a problem and I can't figure out what is causing it. To my image I've added bluetooth support (SYSGEN_BTH and SYSGEN_BTH_USB). When I launch the Bluetooth Manager and scan for devices I find other devices but not the profiles they support, i.e the devices only appear in the "UNTRUSTED" list with a '?' icon. This is when running CE 5.0. But when doing the exact same thing with 4.2 on the same platform it works, i.e. the different profiles are enumerated in the list. I'm starting to believe that I'm experiencing problems with the communication to the USB dongle because sometimes no devices are found and sometimes only a few (5.0), besides the fact that at no time have I found a profile using 5.0. Any suggestions? Sincerely, Nicklas Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67168
  - 11
    - Why the performance of media player in WinCE 4.2 is worse than that in PPC2003? Hi, In same H/W platform, I have PPC 2003 and WinCE 4.2 OS images. I use the same audio and display drivers to build the two OS images. I found using media player to play WMV is smooth in PPC, but it is bad in WinCE 4.2. Why ? How to improve the performance of media player in WinCE 4.2 ? Thanks. Yu. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67161
  - 12
    - How to eliminate the "BUILD: [01:0000001496:INFO ]" In Windows CE 5.0, is there any setting whilc can filter the "BUILD: [01:0000001496:INFO ]" in build.log? Thanks Charles Wang Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67159
  - 13
    - Adding a new codec I've been looking into how to add a new codec to Windows CE, to support the decoding of an audio format. The obvious way to do this seems to be to add an ACM (Audio Compression Manager) driver dll. Is this the best way to do it or should I be considering any other options? I have been looking at the faad2 AAC decoder, with a view to establishing how much effort would be involved in porting this to CE 5. Thanks Matt Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67138
  - 14
    - Several Storage Manager profiles using one block driver Hello CE world. Is it possible to create several Storage Manager profiles using the same block driver? I would like to have several profiles (eg. one hidden with AutoPart, AutoMaunt and AutoFormat disabled and another one vsisible with AutoPart, AutoMaunt and AutoFormat enabled) using the same block driver. I tried the following settings in registry: HKEY_LOCAL_MACHINE\Drivers\Strorage\MyBlockDriver1 "Dll"="MyBlockDriver.dll" "Prefix"="DSK" "Profile"="MyProfile1" .... HKEY_LOCAL_MACHINE\Drivers\Strorage\MyBlockDriver2 "Dll"="MyBlockDriver.dll" "Prefix"="DSK" "Profile"="MyProfile2" .... [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MyProfile1] "Name"="Private Storage" "Folder"="Private Storage" .... [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MyProfile2] "Name"="Public Storage" "Folder"="Public Storage" .... Everything seems to work as expected except one thing: after loading folder names are assigned as MyProfile1 -> Private Storage MyProfile2 -> Private Storage2 (instead of "Public Storage") Any ideas? Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67134
  - 15
    - ISP1362 on WIndows CE4.2 (or actually PPC2003se) Function driver Hi All, We are currently integrating the ISP1362 drivers from philips in our PocketPC BSP (PPC 2003 SE, based on Windows CE 4.2). What we're trying to do (first) is get the Device controller up and running, we can initialize the driver supplied by Philips. But we can't seem to find a function driver for the serial protocol (required by activesync). Should this have been supplied by Accelent/Vibren or Philips to us since we're using their devkits, or must we use the USBF_Serial driver for the cotulla and adapt it to the ISP1362? Kind regards, Niels Brouwers Chess iT Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67130
  - 16
    - cannot load WLAN drives in release Dear I have a 802.11b Wireless CompactFlash Card (CWB1K), I use ISLP2NDS driver It can work correctly in debug ,But can not work Release . It prompt 'Can not access PCMCIA FCR . Request IRQ without accessing FCR is Illegal. It may hang the system' . Thanks Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67128
  - 17
    - About USB BulkTransfer error... Hi, all: I wrote a usb client device driver for wireless modem on WinCE.NET 4.2. And my driver have passed the usb enumeration process sucessfully. When executing IssueBulkTransfer() to write data to wireless modem, then wait_timeout occurred. Could someone tell me why? Thanks!! -Kemin The log msg are as following: 4294896994 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write wait for CritSec 50b40. 4294896995 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write Got CritSec 50b40. 4294896996 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write wait for CritSec 50c14. 4294896997 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write got CritSec 50c14. 4294896997 PID:63c7872a TID:2387cfb2 0x8386db70: COM_Write released CritSec: 50c14. 4294896998 PID:63c7872a TID:2387cfb2 0x8386db70: DoPutBytes wait for CritSec 50c14. 4294896999 PID:63c7872a TID:2387cfb2 0x8386db70: DoPutBytes got CritSec 50c14. 4294897000 PID:63c7872a TID:2387cfb2 0x8386db70: TxRead = 0, TxLength = 3, TxBytesAvail = 3. 4294897000 PID:63c7872a TID:2387cfb2 0x8386db70: About to copy 3 bytes 4294897001 PID:63c7872a TID:2387cfb2 0x8386db70: +SerTxIntr 0x4FEC0 4294897002 PID:63c7872a TID:2387cfb2 0x8386db70: >USBCDC_Write(0xe018854, 3) 4294897002 PID:63c7872a TID:2387cfb2 0x8386db70: USBCDC_Write timeout due in 606 msec 4294897003 PID:63c7872a TID:2387cfb2 0x8386db70: +USBD:IssueBulkTransfer, pipe:50730, dwFlags:0x0, Bufsize: 3 vBuf:0xE018854, pBuf:0x0 4294897005 PID:63c7872a TID:2387cfb2 +CHcd::IssueTransfer - address = 66, pipe = 5, dwFlags = 0x0, lpvControlHeader = 0x0, lpvBuffer = 0xe018854, dwBufferSize = 3 4294897007 PID:63c7872a TID:2387cfb2 +CHub(Root tier 0)::IssueTransfer, address = 66, pipe = 5 4294897008 PID:63c7872a TID:2387cfb2 +CHub(External tier 1)::IssueTransfer, address = 66, pipe = 5 4294897010 PID:63c7872a TID:2387cfb2 +CFunction(tier 2)::IssueTransfer 4294897011 PID:63c7872a TID:2387cfb2 +CPipe(Bulk)::IssueTransfer, address = 66 4294897012 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897012 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897013 PID:63c7872a TID:2387cfb2 +CBulkPipe::GetNumTDsNeeded 4294897014 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897015 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897015 PID:63c7872a TID:2387cfb2 -CBulkPipe::GetNumTDsNeeded, returning 1 4294897016 PID:63c7872a TID:2387cfb2 +CBulkPipe::AddTransfer 4294897017 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897018 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897019 PID:63c7872a TID:2387cfb2 CBulkPipe::AddTransfer dwFlags(0x0), packetsize=0x40 4294897019 PID:63c7872a TID:2387cfb2 -CBulkPipe::AddTransfer, returning success 4294897020 PID:63c7872a TID:2387cfb2 +CBulkPipe::ScheduleTransfer 4294897021 PID:63c7872a TID:2387cfb2 +CBulkPipe::AreTransferParametersValid 4294897022 PID:63c7872a TID:2387cfb2 -CBulkPipe::AreTransferParametersValid, returning BOOL 1 4294897023 PID:63c7872a TID:2387cfb2 +CPipe::AddToBusyPipeList - new pipe(Bulk) 0x50780, pri 0 4294897024 PID:63c7872a TID:2387cfb2 -CPipe::AddToBusyPipeList - new pipe(Bulk) 0x50780, pri 0, returning BOOL 1 4294897026 PID:63c7872a TID:2387cfb2 +CUHCIFrame::HandleReclamationLoadChange - Add Reclamation Transfer 4294897026 PID:63c7872a TID:2387cfb2 -CUHCIFrame::HandleReclamationLoadChange - Add Reclamation Transfer 4294897030 PID:63c7872a TID:2387cfb2 -CBulkPipe::ScheduleTransfer, returning HCD_REQUEST_STATUS 1 4294897031 PID:63c7872a TID:2387cfb2 -CPipe(Bulk)::IssueTransfer - address = 66, returing HCD_REQUEST_STATUS 1 4294897033 PID:63c7872a TID:2387cfb2 -CFunction(tier 2)::IssueTransfer - returing HCD_REQUEST_STATUS 1 4294897035 PID:63c7872a TID:2387cfb2 -CHub(External tier 1)::IssueTransfer address = 66, pipe = 5, returing HCD_REQUEST_STATUS 1 4294897035 PID:63c7872a TID:2387cfb2 -CHub(Root tier 0)::IssueTransfer address = 66, pipe = 5, returing HCD_REQUEST_STATUS 1 4294897037 PID:63c7872a TID:2387cfb2 -CHcd::IssueTransfer - returing BOOL 1 4294897038 PID:63c7872a TID:2387cfb2 0x8386db70: -USBD:IssueBulkTransfer, pTransfer:0x520E0 4294897646 PID:63c7872a TID:2387cfb2 0x8386db70: OUT:WAIT_TIMEOUT on hT:0x520e0 Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67125
  - 18
    - Profiling of code I want to speed up the execution of code. To do it I have to profile only those portion of the code that is been frequently accessed in the Platform builder. How do I achieve it? Any pointers to it will be of great help. Thanks in advance for helpers. Rgds, Rams Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67121
  - 19
    - How to replace the ATADISK.dll Dear All: I have modifed the ATADisk driver and I want replace the original, but when I replaced the atadisk.dll by the file that I generated I alway failed. Does any setting I missed? Thanks... Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67120
  - 20
    - multiple irq -> sysintr possible? hey, is multiple irq->1 sysintr numbers possible? Or in other words is it permitted? I cannot see anything stopping me from doing that. Of course, how that could be useful is something i am not considering right now (prob. for some diagnostics?), though would like to know if it is possible. Why i am asking this is oalintrtranslatesysintr() (not fully implemented in PQOAL of WinCE5.0..) takes as argument the variable count, which seems to suggest this combo (multiple irq->1 sysintr) is possible. -- cheers, Joseph Garibaldi. B'lore, India. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67110
  - 21
    - Any Progress on "Bad Directory Prefix" bug in PB 5.0 ? After extended struggles with what turned out to be a faulty vendor BSP [See: http://groups.google.com.au/groups?hl=en&lr=&threadm=OY08HfeHFHA.400%40TK2MSFTNGP14.phx.gbl&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26selm%3DOY08HfeHFHA.400%2540TK2MSFTNGP14.phx.gbl ] the vendor gave me the option of leaving PB 4.2 and either moving back to 4.1, or forward to their beta 5.0 BSP. I chose to move to 5.0, and had immediate success with the network problems that had been blocking me for so long. However when I went to move my applications so they wouild build under 5.0, rather than using the executables I had built under 4.2, I ran into the problem described in these threads: http://groups.google.com.au/groups?hl=en&q=%22Bad+directory+prefix%22+BUILD&btnG=Search This is the problem where PB5.0 requires source files to be in the project directory, rather than in whatever directories they happen to be in, as with PB 4.2, eVC++, Visual Studio, GCC under Linux and Tru64 Unix, and just about anything else. This is one heck of a bug, and a virtual show stopper for us. Our source is in a structure dating back some 15 years, with common source compiled in place by all the above as well as Aztec C running on an Amiga Emulator. I know that we can pull things out of source control to different locations, but that is terribly inconvenient, the way it is we can just make one edit and then fire off all the build systems and check for problems immediately. On a Unix system we could just use soft-links but we are hosting on Windows, and they never really got that area figured out. And as a related issue, why can't there be either a standard project file format for Visual Studio, PB (various versions), and eVC, rather than different ones that do mostly the same thing, or at least a translator or import/export system, it is such a pain first building and then maintaining the different ones. Back to the original problem, the referenced messages show that this problem has been known for some time. Can someone (MS?) let me know has anything been done to fix it, is anything in the works to do so, are we waiting for VS2005, or what the plan here is? Thanks for your help, David Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67106
  - 22
    - Where the definition of KernelIoControl? Hi,all, Where can I find the definition of KernelIoControl in wince500 source code? PB Help Doc says it calls OEMIoControl. Thanks. -- Best Regards Wang Yeqing *********************************************************** Intelligent Grouping Research and Development Institute Amoi Electronics Co., Ltd Tel: 86-592-6516777-6523 *********************************************************** Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67104
  - 23
    - How to format the external card ? Dear all: Here I want to finish the Format feature on device. And I use OpenStore/FormatStore functions to format external card like mmc, sd, cf etc. But openstore can return true, formatstore return false. Why ? I refer to shared codes in control pannel and found no differences. Is there any other steps need to take ? Thanks a lot ! Jack. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67102
  - 24
    - Multiple Input Language Hi I have a working for the multi input language. and mui. i want to support that us, german, french, italian key board and so on.. MUI feature is working well. but i have some queston in multi keyboard support. i test in project.reg to [HKEY_CURRENT_USER\Keyboard Layout\Preload\2] @="00010409" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Layouts\00000407] "Layout File"="kbdmouse.dll" "Layout Text"="german" "PS2_AT"="kbdmouse.dll" not changed default setting in commin.reg [HKEY_CURRENT_USER\Keyboard Layout\Preload] @=LOC_HKL_DEFAULT [HKEY_CURRENT_USER\Keyboard Layout\Preload\1] @=LOC_HKL_DEFAULT after image loading, i see the enabled "EN" tray icon. and us and german menu appear when mouse right click. but cant change to german menu. i think mismatching kbdmouse.dll of german locale(00000407) in project.reg file. i want to know how to make keyboard dll of german, french .... Regards. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67100
  - 25
    - Do I really need all these features? I'm trying to get a CEPC attached to our network and found that our platform didn't have the right driver for the prototype's NIC. So I added the "RealTek RTL8139" feature and was pretty surprised to see everything else that PB added for me: Updating the feature and driver list for your platform. - Toolhelp API feature (SYSGEN_TOOLHELP) - Core Server Support feature (SYSGEN_SERVICES) - Standard I/O (STDIO) feature (SYSGEN_STDIO) - Standard I/O ASCII (STDIOA) feature (SYSGEN_STDIOA) - Internet Explorer Multiple-Language Base API feature (SYSGEN_MLANG) - Web Server (HTTPD) feature (SYSGEN_HTTPD) - Windows Internet Services feature (SYSGEN_WININET) - URL Moniker Services feature (SYSGEN_URLMON) - RAM and ROM File System feature (SYSGEN_FSRAMROM) - Tahoma (Subset 1_07) feature (SYSGEN_FONTS_TAHOMA_1_07) - XML SAX feature (SYSGEN_MSXML_SAX) - Courier New (Subset 1_30) feature (SYSGEN_FONTS_COUR_1_30) - RAM-based Registry feature (SYSGEN_FSREGRAM) - National Language Support (NLS) feature (SYSGEN_CORELOC) The feature and driver list update successfully. Do I really need all these new features? Tahoma, Courier New (both of which I already had), a web server (?!)--are these really necessary? Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67089
- Next
  - 1
    - TFAT registry settings (more info needed) Does anyone have any more information on this FATFS_DISABLE_AUTOSCAN 0x00000004 disable automatic ScanVolume() registry setting for TFAT. I see that microsoft recommends setting this when using TFAT (both atomic and non-atomic). It seems to me to be something that would be a good thing to do. Everytime I boot this up it does a scanvolume and checks everything is fine. Where is the harm in that. Also, does anyone know how to turn debug messages on for TFAT. I assume I need to compile a debug build within platform builder but I would only like to print out the tfat debug messages, not everything else. Mark Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67084
  - 2
    - CEMAPI.H Our device uses CE 4.2 not PPC2003. We have a customer that is trying to use CEMAPI.H but that is not in the WINCE420 directory or in the SDK directory. Is there a CE 4.2 Equivalent or is CEMAPI only supported on PPC? Thanks. -- Matthew Townsend Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67079
  - 3
    - Unsatisfactory performance with DirectDraw & D3DM I'm experiencing unsatisfactory performance with Windows CE 5.0 and a CEPC running applications using Direct Draw and Direct 3D. In particular, I'm using an ATI Rage XL PCI graphics card (because a) it was included in the CE Catalog and b) it was available for purchase from our supplier). I'm also using the Microsoft-supplied Direct 3D Mobile (D3DM) driver (d3dm_nulldrv.dll). Note: adding this driver to the platform resulted in a "Special Feature Notification" dialog which mentioned (in part) that "The source code and binaries for this technology may be used for testing and evaluation purposes, but they may not be shipped (in whole or in part) as a production Direct3D mobile driver with a CE run-time image." The display is set to 1280 x 1024 x 24bpp. The Microsoft-provided D3DM sample applications will run only if "-ref" is added on the command line. (E.g., Target (menu), Run Programs..., select "d3dm_lights.exe" and append "-ref".) The application will run windowed; it's running at about 1.5 to two frames per second. My GDI applications run satisfactorily in 1280 x 1024 x 24bpp. My Direct Draw and Direct 3D applications do _not_ run in anything but 640 x 480 (presumably due to limitations of d3dm_nulldrv.dll). Also, when they do run at that resolution, they run unsatisfactorily slow (about 1.5 to two fps). Questions: 1. Is CE 4.2 or 5.0 a viable OS for Direct Draw and D3DM applications looking for about 5 to 10 fps performance at 1280 x 1024 x 24bpp? 2. Hey, vendors, who is shipping CE (versions 4.2 or 5.0) PQD for their GPUs? Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67072
  - 4
    - Pocket PC BSP on PB 5.0 I need to set my target device to PPC 2003 in platform builder 5.0. Anyone know how to do this?? JR Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67071
  - 5
    - .reg files and /windows/startup folder Hi there, I am having a problem with trying to run the .reg files on a warm boot for above folder. The .reg files are associated correctly and if double-clicked on do get into the registry. By placing the .reg file into above folder it did get executed all up to PB 4.1. On 4.2 it just does not work. Any .cab or .exe in there does run on warm-boot. Any clue? Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67061
  - 6
    - Unresolved symbol: OALPAtoVA Hi, I have created a new driver DLL as described in the MSDN, using driver wizard. The driver compiles OK and works. After I added a call to OALPAtoVA (), and built the project, I am getting the messages: error LNK2019: unresolved external symbol OALPAtoVA referenced in function ..... I added the oal_memory_pxa27x.lib to the libraries to be included in the link, but then there are other unresolved externals referenced from the oal_memory_pxa27x.lib library. Is there a simple way to let the system look for the libraries needed for the project? I believe that I just missed something when I built the project, and thats why I have to add the libraries myself. Thanks in advance, Lrz Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67059
  - 7
    - boot CE5.0 too long Hi, I'm new to CE5.0, I build 4.2 image before for my Compact Flash disk, now I install PB5.0 and get a new NK.bin, I just copy NK.bin to my CF replace old 4.2 one, then I start CEPC, loadepc.exe will boot NK.bin, but after go to "Jump to...", it takes forever to boot CE5.0, sometimes takes morn than 5 or 10 minutes to go to CE5.0. Do I need change any other files in CF? Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67054
  - 8
    - wince ndis driver Does any digfference between winCE ndis driver of 3.0 and 5.0 ? At least WinCE5.0 covers all the ndis functions of the winCE3.0. thanks, Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67049
  - 9
    - i82551er and Windows CE debugging Hi. I'm searching for loadcepc.exe and eboot.bin files for my x86 platform : the files supplied with Windows CE 5 only work with NE2K ethernet controllers. Does any one have any idea where I can download these files for an intel i82551er controller? In advance, thanks. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67045
  - 10
    - USB mouse - second time attach fails Hi All! I have a strange problem: The first time I attach my USB mouse to the system everything works fine, and when detaching the mouse the systems detects it according to the debug messages. However after that the port seems dead, I cannot attach anything. I've tried to put a breakpoint at HubStatusChangeThreadStub in CDevice.cpp but it is not triggered. Anybody having any clues? System info: Intel IXC1100 (ARMV4I) Windows CE 5.0 ISP1561 USB chip from Philips If I suspend/resume my system the port works again! Sincerely, Nicklas Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67039
  - 11
    - fatfs doesn't load on RAMdisk WCE50 This is a multi-part message in MIME format. ------=_NextPart_000_0103_01C544E2.1FA1C400 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear experts, i just built ramdisk driver on WCE5.0, trying to load it on x86 = emulator. The ramdisk.dll loads fine, i can see RAMdisk as a disk in = Storage Manager, however, it is not mounted (FATFS) with following = error: 4294768786 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: >>> Loading module = ramdisk.dll at address 0x01E10000-0x01E16000 Loaded symbols for = 'C:\WINCE500\PBWORKSPACES\TEST01\RELDIR\EMULATOR_X86_DEBUG\RAMDISK.DLL' 4294768826 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: Opened the store = hStore=3D83FA773A 4294768826 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: NumSec=3D2048 = BytesPerSec=3D512 FreeSec=3D0 BiggestCreatable=3D0 4294768826 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: Partition PART00 = NumSectors=3D2048 4294768846 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: >>> Loading module = fatfsd.dll at address 0x03EA0000-0x03EC7000 (RW data at = 0x01FF2000-0x01FF265C) Loaded symbols for = 'C:\WINCE500\PBWORKSPACES\TEST01\RELDIR\EMULATOR_X86_DEBUG\FATFSD.DLL' 4294768866 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FSD_MountDisk: mounting = volumes for hDsk=3D00092D60 4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: = access time updates disabled 4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: event = logging enabled 4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: = automatic scanning disabled 4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: write = verify disabled 4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: extra = FAT on format disabled 4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: force = write through enabled 4294768886 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: = Codepage =3D 1 4294768886 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: = Number of path cache entries =3D 50 4294768886 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!InitVolume: = invalid BPB, volume deemed invalid 4294768896 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!InitVolume: FAT = version: 12 4294768896 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!InitVolume: = Cluster Size (Sectors): 144 4294768896 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!InitVolume: TFAT = enabled: FALSE 4294768906 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!UnmountDisk: = unmounting all volumes on disk 000 4294768916 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!FATDetach = complete (0 sectors written in 0 requests) 4294768916 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: <<< Unloading module = fatfsd.dll at address 0x03EA0000-0x03EC7000 (RW data at = 0x01FF2000-0x01FF265C) Unloaded symbols for = 'C:\WINCE500\PBWORKSPACES\TEST01\RELDIR\EMULATOR_X86_DEBUG\FATFSD.DLL' What does "invalid BPB" mean, please? THANX for help buzz ------=_NextPart_000_0103_01C544E2.1FA1C400 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV><FONT face=3DArial size=3D2>Dear experts,</FONT></DIV> <DIV><FONT face=3DArial size=3D2>i just built ramdisk driver on WCE5.0, = trying to=20 load it on x86 emulator. The ramdisk.dll loads fine, i can see RAMdisk = as a disk=20 in Storage Manager, however, it is not mounted (FATFS) with following=20 error:</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DCourier size=3D1>4294768786 PID:c3fc8c1a TID:c3fc8bea = 0x83fc8a3c:=20 >>> Loading module ramdisk.dll at address=20 0x01E10000-0x01E16000<BR>Loaded symbols for=20 'C:\WINCE500\PBWORKSPACES\TEST01\RELDIR\EMULATOR_X86_DEBUG\RAMDISK.DLL'<B= R>4294768826=20 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: Opened the store=20 hStore=3D83FA773A<BR>4294768826 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: = NumSec=3D2048=20 BytesPerSec=3D512 FreeSec=3D0 BiggestCreatable=3D0<BR>4294768826 = PID:c3fc8c1a=20 TID:c3fc8bea 0x83fc8a3c: Partition PART00  = NumSectors=3D2048<BR>4294768846=20 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: >>> Loading module = fatfsd.dll at=20 address 0x03EA0000-0x03EC7000 (RW data at = 0x01FF2000-0x01FF265C)<BR>Loaded=20 symbols for=20 'C:\WINCE500\PBWORKSPACES\TEST01\RELDIR\EMULATOR_X86_DEBUG\FATFSD.DLL'<BR= >4294768866=20 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FSD_MountDisk: mounting volumes = for=20 hDsk=3D00092D60<BR>4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c:=20 FATFS!OpenVolume: access time updates disabled<BR>4294768876 = PID:c3fc8c1a=20 TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: event logging = enabled<BR>4294768876=20 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: automatic = scanning=20 disabled<BR>4294768876 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: = FATFS!OpenVolume:=20 write verify disabled<BR>4294768876 PID:c3fc8c1a TID:c3fc8bea = 0x83fc8a3c:=20 FATFS!OpenVolume: extra FAT on format disabled<BR>4294768876 = PID:c3fc8c1a=20 TID:c3fc8bea 0x83fc8a3c: FATFS!OpenVolume: force write through=20 enabled<BR>4294768886 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: = FATFS!OpenVolume:=20 Codepage =3D 1<BR>4294768886 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c:=20 FATFS!OpenVolume: Number of path cache entries =3D 50<BR>4294768886 = PID:c3fc8c1a=20 TID:c3fc8bea 0x83fc8a3c: FATFS!InitVolume: <STRONG><FONT = color=3D#ff0000>invalid=20 BPB, volume deemed invalid</FONT></STRONG><BR>4294768896 PID:c3fc8c1a=20 TID:c3fc8bea 0x83fc8a3c: FATFS!InitVolume: FAT version: 12<BR>4294768896 = PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: FATFS!InitVolume: Cluster Size = (Sectors):=20 144<BR>4294768896 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: = FATFS!InitVolume: TFAT=20 enabled: FALSE<BR>4294768906 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c:=20 FATFS!UnmountDisk: unmounting all volumes on disk 000<BR>4294768916 = PID:c3fc8c1a=20 TID:c3fc8bea 0x83fc8a3c: FATFS!FATDetach complete (0 sectors written in = 0=20 requests)<BR>4294768916 PID:c3fc8c1a TID:c3fc8bea 0x83fc8a3c: = <<<=20 Unloading module fatfsd.dll at address 0x03EA0000-0x03EC7000 (RW data at = 0x01FF2000-0x01FF265C)<BR>Unloaded symbols for=20 'C:\WINCE500\PBWORKSPACES\TEST01\RELDIR\EMULATOR_X86_DEBUG\FATFSD.DLL'</F= ONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>What does "invalid BPB" mean, = please?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>THANX for help</FONT></DIV> <DIV><FONT face=3DArial size=3D2>buzz</FONT></DIV></BODY></HTML> ------=_NextPart_000_0103_01C544E2.1FA1C400-- Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67034
  - 12
    - system tick period effects. hi all, i am confused here with something in WinCE5.0. In the PQ OAL support provided by MS, there's a way to configure the system to different system tick periods. i was using the ILTiming tool when i just wanted to try with the different values for the system tick period. I didn't actually expect much difference, but when i used the "maximal period" for the Tick Period (using the term of PQ OAL), along with the VarTicks implementation, the system seemed to be performing poorly (i am referring to the ILTiming results, a considerable difference of 5micro.seconds was noted for -i5 in the IST latency and some variations in the ISR latency as well) when compared to when i use 1mS system tick period. I haven't run OSBench.exe as of now. I was wondering what could be the reasons of such a behaviour. The only effect that i can see when the system is configured to 1mS system tick period vs having a bigger system tick period is that the interrupts overhead increase along with the associated cache/TLB flushings. Now, these will affect the overall system when you see from above the OS (applications, OS calls etc). And going by this, the system with 1mS interrupts should be relatively doing poor and not otherwise, as suggested by ILTiming. And yeah, the sleep accuracy is much much better with lower system tick periods. But, how do these (system tick period) affect your ISR and IST latency? -- cheers, Joseph Garibaldi. B'lore, India. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67031
  - 13
    - How to get the snapshot of display screen with overlay ? Dear all: My device is playing a movie, while I want to get the snapshot of whole screen, how to accomplish it ? Thanks a lot! Jack. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67030
  - 14
    - Hive-based registry setting Hi, how is going ?? this is Tiziano Fabbri. I'm trying to setup the hive-based registry and I have some question about: - I'm following the help in platform builder "Using the Hive-Based Registry", the hive-based registry catalog Item is added on my image. - Each referement of this chapter is for "Platform.reg" but I find all in "Common.reg" file. Is correct ? - At third point, (3.), is ask to add this: "Set the following registry value in the Platform.reg file for your OS design to determine the default hive to load. [HKEY_LOCAL_MACHINE\init\BootVars] "DefaultUser"="<username>" my question is: in "Platform.reg" or "Common.reg" there isn't "Default User" key. I must insert this key with "<username>" definition, "<username>" is generic definition, mandatory definition, or I must have a personal definition ??? - This my definition is OK ??: ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION ; Valid Bits for Flags registry value ; If no flags are set, the hive will be stored in the object store. ; ; 0x00000001 Start storage manager in boot phase 1 for hive-based registry ; 0x00000002 Start device manager in boot phase 1 for hive-based registry ; 0x00000004 Start storage manager in boot phase 1 for registry in ; external ROM (such as BINFS) ; 0x00000008 Start device manager in boot phase 1 for registry in ; external ROM (such as BINFS) [HKEY_LOCAL_MACHINE\init\BootVars] "SystemHive"="Documents and Settings\\system.hv" "ProfileDir"="Documents and Settings" "Start DevMgr"=dword:1 ;modifica del 18/04/05 "DefaultUser"="" ;modifica del 15/04/05 ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF FILESYS_FSREGHIVE - or is better that ??: ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION ; Valid Bits for Flags registry value ; If no flags are set, the hive will be stored in the object store. ; ; 0x00000001 Start storage manager in boot phase 1 for hive-based registry ; 0x00000002 Start device manager in boot phase 1 for hive-based registry ; 0x00000004 Start storage manager in boot phase 1 for registry in ; external ROM (such as BINFS) ; 0x00000008 Start device manager in boot phase 1 for registry in ; external ROM (such as BINFS) [HKEY_LOCAL_MACHINE\init\BootVars] "SystemHive"="Documents and Settings\\system.hv" "ProfileDir"="Documents and Settings" "Start DevMgr"=dword:1 ;modifica del 18/04/05 "DefaultUser"="<username>" ;modifica del 15/04/05 ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF FILESYS_FSREGHIVE Regarding "Start DevMgr", on top of declaration there is the comment about Flags. Flags is a Key or the referement is for "Start DevMgr" ??? I setted value to 1 following the comment, is right ?? - Next assertion is: "Verify that all registry entries necessary for starting drivers in the first boot phase are wrapped in the comments. The following code example shows typical comments. ; HIVE BOOT SECTION <your registry settings> ; END HIVE BOOT SECTION These tags are commands that tell the ROM registry builder to add the entries to the boot hive. " All registry entries is refered just on "Platform.reg" and "Common.reg" or alls reg files in WinCE500 root and its sub-directories ?? - Fifth point: "Set the following flag bit on each driver that is loaded during the first boot phase. [HKEY_LOCAL_MACHINE\Drivers\...] "Flags"=dword:1000 The flags are a bitmask to OR with any existing settings. This flag tells the Device Manager to load your driver in the first boot phase with the boot registry, and not to load it a second time in the second boot phase with the system registry. It prevents the driver from being started twice." How I can know which drivers we need to boot in the first phase, whithout system registry, to prevents twice starting ?? And I must follow alls "; HIVE BOOT SECTION | <your registry settings> ; END HIVE BOOT SECTION" definitions to be sure on the right effects ?? Or someone drivers is without notes or referement so I need to find it for my self ?? - Sixth point: This, at me, looks good, do you confirm ?? " [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\FATFS] "EnableCacheWarm"=dword:0 "MountFlags"=dword:2 " - Seventh point: Done !! I added a project in the platform where I call "RegFlushKey" for 2 keys: HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE. Please, Help me !!! Thanks, Tiziano Fabbri Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67015
  - 15
    - booting from compact flash, x86_geode Hello guys, I have a problem with biosloader under my Geode-Gx300. Is a board named E3412 from E-Value with on board a compact flash IDE saws like second HD IDE. My winCe image recognize perfectly this device and alls operations on CF are possible. Problems growing up if I want use BLDR and and left LOADCEPC. I tried from IDE1, normal HD, but I have lot of messages from COM1 likes 0xE, 0x2, 0x17 (debug.h explain meaning about). I have two kinds of CF: 1Gb and 512Mb; First has behaviour likes HD: messages are 0x1, 0x3, 0x8; Second is almost interested; no error messages, splash screen run, but the Jumping to address has a value of 0 (zero). I looked on source and suppose that each step, for last CF, is OK , unless the return parameter from function LOADBINFILE. I checked my NK.BIN by Viewbin.exe utility everything looks right: Image start:00220000, lenght: 0100ABF4, Start address: 00228F38, ROMOFFSET: 0x80000000; Someone else has same experience on Geode, maybe ECM3412, to help me ??? thank you Tiziano Fabbri Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67012
  - 16
    - Why does windows CE 5.0 start up very slowly? Starting my windows CE 5.0 up will take about 3 mins . Why so slowly? Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67009
  - 17
    - PB for WinCE version 4.21 ? When we install our device driver (i.e. double click on the .CAB file) on a hand held that is running CE version 4.21, a pop-up window comes up complaining that the driver was built for an older version of Windows. Such a warning does not occur for PPCs on version 4.20. Is there an upgrade to Platform Builder, or to anything else, that would allow us to build the driver for version 4.21 of the OS and eliminate the warning ? We've already tried modifying the [CEDevice] section of the .inf file as suggested in http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnppcgen/html/whatsnew2003se.asp, but it doesn't help. Thanks, Cristian Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67005
  - 18
    - Re: CEPC does not detect HDD! and another Registry entry: HKLM, System, Storage Manager: FATFS MSPART Partition Table Profiles, HDProfile, FATFS Tag: Driver for Capture Interface (camera) for PXA27x Tag: 67004
  - 19
    - CEPC does not detect HDD! I am trying to get my CEPC image to detect my HDD, I have a FAT16 primary partition. I can boot up the CEPC and use the operating system but cannot see the "hard disk folder". Has anyone encountered this problem? I have added FAT file system storage for the file system as well as device drivers for ATAPI PCI/IDE block storage. Any advice or suggestions would be greatly appreciated. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 66993
  - 20
    - Problem in using ActiveSync on COM2 on WinCE 4.2 Hi, We are building a platform for X86 target device. Device contains two serial port and through changes in the debug.c , we disabled the debug port and we are using both ports for our purpose. When we tried to connect null modem cable on COM1 and try the activesync, it is able to communicate with the desktop. But if we try to use active sync on COM2, we are not able to do that. Is any body knows , whether active sync is able to work on COM2 or not? If so what is steps to do so? Can any body have a glue on that? Thanks in advance, Ravindran Ramaraj, Senior engineer, Bells Softech Ltd, India. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 66986
  - 21
    - Building PPC 2002 apps with Platform builder 5.0 Hi, I am new to the world of platform builder. I recently obtained a copy of the evaluation version of platform builder 5.0 but I am having trouble moving any project that I build on it to Pocket PC 2002 and 2003. When I move it to the test PDA it gives the error mesage "not a valid PocketPC application" I want to be able to use the SDIO drivers that PB 5.0 provides with earlier versions of windows. Thanks for any help. JR Tag: Driver for Capture Interface (camera) for PXA27x Tag: 66981
  - 22
    - USB RNDIS Function Driver-XP-.inf file and name of .sys Drivers Dear All, I am using USB RNDIS Function drivers for XP Operating system. I see a lot of posts succesful in setting up the environment. Can any one pls send me the contents of the .inf file and .sys files. It would be a gr8 help for me because I am worried with this issue for more than a week. Pls let me know the contents of the .inf file and the name of the .sys files. Has the USB RNDIS driver working with win2k? Cheers, Lakshman Tag: Driver for Capture Interface (camera) for PXA27x Tag: 66976
  - 23
    - USB RNDIS Fn Driver- Unable to start the device-USB STALL happens Dear All, This is regarding the USB RNDIS Function driver. When my WindowsCE device is connected to my XP Host the following error message happens "The device cannot start(Error Code 10). On a XP machine, I am using the rndismpx.sys and usb8023x.sys files as drivers When analysed the problem with a CATC protocol analyser, a SETUP packet of length 24 doesnt reach the device properly....Only 16 bytes have reached the device and after that a STALL happens. The 16 bytes which goes to the device are as follows 02 00 00 00 18 00 00 00=>ACK 02 00 00 00 01 00 00 00=>STALL I am using the OHCI driver provided by Platform Builder only. Pls suggest/advice Cheers, Lakshman Tag: Driver for Capture Interface (camera) for PXA27x Tag: 66971
  - 24
    - Save registry setting for CE5.0 Hello, I use CE4.2 PB before, I just install PB5.0, I create a simple image and test it, I found I can't save registry setting after I reboot computer, how can I let CE 5.0 save changes after reboot computer? Thank you! Tag: Driver for Capture Interface (camera) for PXA27x Tag: 66967
  - 25
    - NDIS Driver - tray icon Does anyone know if it is possible for a NDIS driver to prevent the tray icon from being displayed when there isn't a connection to it? I'm developing a NDIS driver for CE5.0 and the "disconnected" tray icon shows up when I drop the connection. Thanks. Tag: Driver for Capture Interface (camera) for PXA27x Tag: 66966

Hi,

According to Intel's web site, the BSP for the PXA27x released with
platform builder 5.0 should include driver for the quick capture
interface. I could not find any driver or documentation for it, except for
a header file with some definitions and prototypes.

Is there any driver for the capture interface?

Thanks,
Lrz

Top