Developing NDIS drive for Windows Mobile 5.0

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - Platform Builder 5.0 and Windows Vista Hi, This week I tried Vista. It seams that I can't make Platform Builder 5.0 works under Windows Vista. The program starts but when I try to build it hangs (not responding). Anyone was able to make it work on Vista? Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92996
  - 2
    - design templates in WinCE 6.00 Hi all, Anybody knows how can I make a template similar that custom device template that appears when you create a new Platform Builder project ?? The templates in XML seem that have been removed. Any ideas? Thanks Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92990
  - 3
    - FormatMessage() failed + LocalFree() problem Hi all, when i launch this piece of code (WinCE6 version) : if ( DeviceIoControl (hServices,ui32Function,pvParamIn,ui32InBufferSize, pvParamOut,ui32OutBufferSize,&ui32BytesReturned, NULL) == FALSE) { LPVOID lpMsgBuf; FormatMessage(FORMAT_MESSAGE_ALLOCATE_BUFFER | FORMAT_MESSAGE_FROM_SYSTEM | FORMAT_MESSAGE_IGNORE_INSERTS, NULL, GetLastError(), 0, // Default language (LPTSTR) &lpMsgBuf, 0, NULL); LocalFree (lpMsgBuf); ui32RetVal = 0xFFFF; } then, i have got an error at the line LocalFree(), and a break point at : Coredll: DEBUGCHK failed in file C:\ymzki\private\winceos\COREOS\core\lmem\.\rheap.cpp at line 1344 Olivier Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92986
  - 4
    - How to add splash screen Hi, I want to add splash screen in my( x86 based) winCE 5.0 device . My requirement is just to add still image in splash screen while booting . please tell me the procedure to add the splash screen . Thanks in Advance. Amit Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92985
  - 5
    - Modifying Code in BaseClasses of Directx Hi All, I am using Win CE 5.0. I have modified code in "WinCE\500PUBLIC\DIRECTX\SDK\SAMPLES\DSHOW\BASECLASSES". I had done Build and Sysgen for that project alone. It is generating a strmbase.lib file. Later I am building Run-time Image and download the code to the Target Device, I cannot see any effect of changed code. But in PB help it is written that the Code can be modified. Can anyone help me regarding this issue. Is there any other specific way that needs to be done to see the effect of changed code. Thanks in Advance, Sarath Chandra. B Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92982
  - 6
    - Multiple display modes in WinCE Hi, I have added support for two display modes in display driver (VGAFlat) for emulator in WinCE5.0. My intention was to change the display mode from smaller resolution to higer resolution dynamically (with out restart). I have tried with ChangeDisplaySettingsEx but it returned 0 (fail). Can any one throw some light on this? Is there any way I can change the Display mode in the Emulator dynamically. Thanks in advance. SriV Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92981
  - 7
    - Autobuilds in WinCE 6.00 Hi All, Anybody has any experience in how to do automatic builds using WinCE 6.0? What scripts or configuration files are you using to do that? Thanks! Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92977
  - 8
    - C.I.D. Is it possible to change the C.I.D. (that is the the Card IDentification of an SD card) wrote by the manufacturer? Mhaxx Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92974
  - 9
    - Is there any develpment kit for mainstone III Hi all, Is there any develpment kit for mainstone III? i have upgraded mainstone II BSP to mainstone III.Till now i was using intel pxa270 processor development kit. Whether i can use the same develpment kit? rgds princy Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92970
  - 10
    - Bluetooth - virtual Serial Port Hello, since a few days I'm struggling with the following problem: I'm using the PB 5.0 (XScale platform) sample "comtest" to create virtual Bluetooth COM ports and connect to another BT enabled PC. As long as I'm using client connections (Outgoing), everything works fine. However when I'm using the CE device as server (Incoming), the other PC cannot establish a connection (can't even see it). From the local CE view, everything looks working pretty well, i.e. the virtual COM port is registered successfully, the COM-port can be openend successfully but I'm waiting endless for an incoming connection. Furthermore, I can't see the "Serial" profile on the other PC, only a "Personal Ad-hoc Service" and a "Audio" profile. Establishing a connecting to these other profiles is no problem. Is there a need or way to make this serial profile visible first? Is there a PC-tool which can be used to establish a serial connection direct to a specific BT-ID? Maybe everything works o.k. but it is not visible due to some reason? Thank you very much, Robert Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92968
  - 11
    - lvds Hi all My target work fine with a VGA output , but instead i want to use the LVDS. But nothing on screen when CE boots. Bios and dos is ok (i mean the screen displays the prompt) any idea. regards Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92967
  - 12
    - mis match time stamp problem while building Hi, I tried to make the run time image(project is builded some time back) and I got the error makeimg: run command: romimage E:\WINCE500\PBWorkspaces\intel\RelDir\Emulator_x86_Debug\ce.bib Error: Mismatched time stamp on .rel file for module celog.dll requesting kernel fixup. Valid .rel file is required for kernel fixups. Windows CE ROM Image Builder v4.0.120 Copyright (c) Microsoft Corporation I searched in the gruops and got one solution as rebuild the platform with sysgen and enable the option clean before build. I did but got strange errors in header files ppkfuncs.h Those are not errors and the code is perfect. I tried in another way: removed the all projcets from work space and sysgen with clean before building option enabled. Still got errors is some other header file OAL-intr.h My platform is itself not working. I did many projects in that one. How can I solve this problem? my mail id is embeddedkumar@gmail.com . Rgds, kumar. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92959
  - 13
    - full kernel mode caused first-chance exception I got an error message window of "First-chance exception in xxx.dll (0xC0000005:Access Violation)",when i unset the "enable Full Kernel Mode" in platform setting. And the system is halt. But it is ok, while "enable Full Kernel Mode" is set. How to solve this?? Thanks in advance! Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92958
  - 14
    - How to enable SSP clock? Windows CE 5.0 Intel PXA 270 In ssp/spi driver, I want to enable the ssp1 clock, but I don't know how to do. Here is the same problem: http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/65e8883348499967/1e88f30d6f9f38a1?lnk=gst&q=clock+enable+spi&rnum=3&hl=zh-CN#1e88f30d6f9f38a1 Can anybody explain it in detail? Thanks in advance! Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92957
  - 15
    - Dependencies for custom driver Hi, I am using Plaform Builder for Windows CE .NET 4.2. I have added some custom drivers to the .cec file of my BSP (using CEC Editor) in custom feature groups, but in the catalog they do not behave the same way as the standard driver types. Firstly, custom drivers using the standard driver types (e.g. serial drivers) appear in the catalog under: Third Party -> BSPs -> My BSP -> Device Drivers -> Serial -> My Serial Driver But the non-standard driver type (feature group) doesn't appear, though the driver itself does: Third Party -> BSPs -> My BSP -> Device Drivers -> My Custom Driver I would have expected it to appear in the same way as it looks in CEC Editor: Third Party -> BSPs -> My BSP -> Device Drivers -> My Driver Type -> My Custom Driver Is this normal? Secondly, if I set the RequiredCEModules to anything (e.g. just "device") then I am unable to remove the driver from the platform. If I try to delete it, Platform Builder just adds it back. My understanding is that RequiredCEModules specifies what modules the driver depends on, not what modules depend on the driver, so why would this make the driver "required"? The standard driver types use RequiredCEModules and yet I can add or remove them without problems. Is there a way to fix this? Luke Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92956
  - 16
    - Different between debug and release build Hi all, Can anyone please tell what is the difference between a deub build and release build? Because I have created multiple XIP region and it can be boot up under debug build but not release build. It just hangs in the middle after "IOCTL_HAL_POSTINIT" (The last step of boot-up process described in http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnce50/html/ce50prev.asp). Any comments or debug skill is appreciated. Thanks. Regards, Nicholas Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92955
  - 17
    - Developng a touchpad driver on wince 5.0 Hello, I need help for developing a device driver for a touchpad device on wince-5.0. The touchpad device is connected to i2c lines on a development arm based board. We have the wince BSP for for the board and also the i2c bus driver. But do not have a driver for the touchpad. Which already existing driver (source) in wince should I reference to develop the touchpad driver. Thanks in advance for your help. Thanks, Shiju Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92951
  - 18
    - Wireless Power Manager and intermediate driver (passthru) Hi. I am trying to make an NDIS intermediate driver based on the passthru example included in the platform builder. With both the passthru example from WINCE 5.0 and WINCE 6.0 I run into the same problem: The passthru driver is not compatible with Microsoft's own application for powering WLAN on and off (this is the Wireless Manager or wrlsmgr.exe). After installing passthru and making sure it binds properly between the real WLAN miniport and all the protocols, the wrlsmgr.exe will no longer be able to power on or power off the card. When I enter the wrlsmgr.exe and click to change the power nothing happens. This has been tested with Windows Mobile 5.0 devices and unmodified versions of the passthru example. There are various postings on news suggesting to remove the handling of NetEventSetPower from the protocol edge of the im driver and just return NDIS_STATUS_NOT_SUPPORTED. This workaround changes the behavior wrlsmgr.exe, but it still does not work. When using such a driver wrlsmgr.exe will not show the WLAN card at all. I would very much like to hear from someone in Microsoft on this issue. Thank you, Thor. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92946
  - 19
    - ChangeDisplaySettingsEx in CE 6.0 Dear all, I heard that Windows Embedded CE 6.0 supports dynamical resolution change. I wrote one program that uses ChangeDisplaySettingsEx API, but it always returns DISP_CHANGE_BADMODE. My question is: Does the flat driver supports this feature? Platform: x86 CEPC Display Driver: ddi_flat.dll thanks in advanced, Brain Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92944
  - 20
    - DaVinci---- NDIS miniport driver packet send and stop hi, i am into development of ethernet miniport driver on ARM kernel for davinci board. I have completed the driver init and all the function pointers have been implemented. I have as of now given a static ip which I have confirmed that no device is using. I can see on the ethereal that when my code runs three ARP packets are broadcasted on the network after the queryfunction nd setfunction execution. from capturing the data i can see that it is broadcasting data which ask if anyboady has the ip it has been allocated and this transfer is three times but thats all and after that i cannot see any actvity on the network and log experts pls help me out of this as i am totally unaware as to what data should come after the ARP is broadcasted thanks in advance Waiting for a favorable response -- Thanks Honey Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92939
  - 21
    - Access ROM files Does anybody know if it's possible to read/copy system files from the PocketPC device? I mean those EXE- and DLL-files in Windows folder. It looks like like the OS protects them. For example, i cannot copy CALC.EXE even if it is not running and I always get 'Access denied' or something. Have any ideas? -- BR, Igor Software developer, Mobileyes AB Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92938
  - 22
    - CE5.0 problem adding FATFS I can't add to my project SYSGEN_FATFS When I add it , PB give me the error below. I didn't find in my winceroot fatutil.dll Best Regards Fabio Copyright (C) Microsoft Corporation. All rights reserved. -nodefaultlib -entry:DllMain -pdb:C:\WINCE500\PBWorkspaces\ASEM3\WINCE500\CEPC_ASEM_x86\cesysgen\oak\target\x86\retail\fatutil.pdb /opt:ref -debug -debugtype:cv -incremental:no -map:C:\WINCE500\PBWorkspaces\ASEM3\WINCE500\CEPC_ASEM_x86\cesysgen\oak\target\x86\retail\fatutil.map -savebaserelocations:C:\WINCE500\PBWorkspaces\ASEM3\WINCE500\CEPC_ASEM_x86\cesysgen\oak\target\x86\retail\fatutil.rel -MERGE:.rdata=.text -ignore:4001,4070,4078,4086,4089,4096,4099,4108,4229 /STACK:65536,4096 -subsystem:windowsce,5.00 /base:0x10000000 C:\WINCE500\PBWorkspaces\ASEM3\WINCE500\CEPC_ASEM_x86\cesysgen\sdk\lib\x86\retail\coredll.lib C:\WINCE500\public\common\oak\lib\x86\retail\storeapi.lib C:\WINCE500\public\common\oak\lib\x86\retail\fatutil.res C:\WINCE500\PBWorkspaces\ASEM3\WINCE500\CEPC_ASEM_x86\cesysgen\sdk\lib\x86\retail\coredll.lib C:\WINCE500\public\common\sdk\lib\x86\retail\corelibc.lib C:\WINCE500\PBWorkspaces\ASEM3\WINCE500\CEPC_ASEM_x86\cesysgen\oak\lib\x86\retail\fatutil.exp fatutil.exp : error LNK2001: unresolved external symbol _DefragVolume fatutil.exp : error LNK2001: unresolved external symbol _DefragVolumeEx fatutil.exp : error LNK2001: unresolved external symbol _DefragVolumeUI fatutil.exp : error LNK2001: unresolved external symbol _FormatVolume fatutil.exp : error LNK2001: unresolved external symbol _FormatVolumeEx fatutil.exp : error LNK2001: unresolved external symbol _FormatVolumeUI fatutil.exp : error LNK2001: unresolved external symbol _ScanVolume fatutil.exp : error LNK2001: unresolved external symbol _ScanVolumeEx fatutil.exp : error LNK2001: unresolved external symbol _ScanVolumeUI C:\WINCE500\PBWorkspaces\ASEM3\WINCE500\CEPC_ASEM_x86\cesysgen\oak\target\x86\retail\fatutil.dll : fatal error LNK1120: 9 unresolved externals NMAKE : fatal error U1077: 'link' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\WINCE500\sdk\bin\i386\nmake.exe' : return code '0x2' Stop. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92937
  - 23
    - How to detect Minimal Window Manager Configuration at compile time? Hello experts, I have a small test application which I include in different platforms. On some platforms there is Minimal Window Manager Configuration available and on some other platforms not. If it is not available I want to exclude some tests. How can I set a compiler define, when Minimal Window Manager Configuration is not available? In the sources file I tried !IF ("$(SYSGEN_MINWMGR)" != "1") CDEFINES=$(CDEFINES) -DNO_WMGR !ENDIF But this only works if I add Minimal Window Manager Configuration to my platform manually. If it is added automatically by dependency rules, SYSGEN_MINWMGR is not defined, and this statement doesn't work. I'm using PB5.0 on ARM9. TIA -- Michael Reim reim AT helmut-fischer DOT de Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92936
  - 24
    - Building Problem I am modifying driver projects in PB 5.0. Once I right click the driver project and click "Build Current Project" with "clean before building" and "Make Run-time image After Build" selected, The nk.bin image sometimes doesn't update at all. What will run on the machine is just the old driver version, not what I have modified at all... How to solve it? Thanks in advance!! Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92925
  - 25
    - Help, WinCE Usb ActiveSynch is not stable, but the massStorage is very well Dear Sirs: My platform is S3C2440 CPU+ PHILIPS Isp1582 usb 2.0 chip, the usb function mass storage is very well, but usb activesynch is not stable, when I use Activesynch to transfer data, it will break after well work severial seconds. and the following message will be got on though DNW. Posting WM_NETCONNECT(FALSE) message, ErrorCode = 631(0x277) Please help me, thank you very much. Best Regards Mike Han Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92923
- Next
  - 1
    - Any restrictions/problems with PlatformBuilder 4.2 evaluation vers We created an OS image using Platform Builder 4.2 evaluation version. We see that the device doesn't boot and looks like it hangs up at kernal launch. All the changes we made seem to be correct, but we came to know that there is a restriction with the evaluation version saying that the changes we made at source level like (armtrap.s) are not reflected in the image. Is that true? Is there any restriction in using the evaluation version. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92922
  - 2
    - Command for setting USB client printers Printer processor data type as "Text" (Ascii) Hi All, Can somebody tell me command for setting USB client printers Printer processor data type as "Text" (Ascii) If there is any command to do this then is it universal? Basically i wannt to programmatically set the usb client printers, printer processor data type to "Text" (ASCII) mode If there is any other method please reply. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92921
  - 3
    - Webbrowser in Win CE 5.0 #2 Hello. My name is JeongHo. I am programming a customized web browser with IWebBrowser2 in windows ce 5.0 And I want to embody some functions which copy/cut/paste. I made it in Win32 Application already.. Using by these ways Way1 HRESULT hr = m_pWeb->ExecWB( OLECMDID_COPY, OLECMDEXECOPT_DODEFAULT, NULL, NULL); if (FAILED(hr)) { int n = GetLastError(); ASSERT(false); } Way2 IHTMLDocument2 *pHtmlDoc; hr = pDispatch->QueryInterface<IHTMLDocument2>(&pHtmlDoc); EHResult::CheckException( L"CMainFrame.Copy.QueryInterface<IHTMLDocument2> Fail (0x%08x)", hr); IHTMLSelectionObject *pHtmlObj; hr = pHtmlDoc->get_selection(&pHtmlObj); EHResult::CheckException(L"CMainFrame.Copy.get_selection Fail (0x%08x)", hr); { IDispatch *pRange; hr = pHtmlObj->createRange(&pRange); EHResult::CheckException(L"CMainFrame.Copy.createRange Fail (0x%08x)", hr); IHTMLTxtRange *pText; hr = pRange->QueryInterface<IHTMLTxtRange>(&pText); EHResult::CheckException( L"CMainFrame.Copy.QueryInterface<IHTMLTxtRange> Fail (0x%08x)", hr); VARIANT null; VariantInit(&null); VARIANT_BOOL isOk; hr = pText->execCommand(L"Copy", VARIANT_FALSE, null, &isOk); EHResult::CheckException(L"CMainFrame.Copy.execCommand Fail (0x%08x)", hr); } But It doesn't work in windows ce 5.0 L What should I do now~ And I have one more trouble. I have to control the element's focus (in html document like LINKs or CONTROLs) by arrow key. Is there a way get the current focus of elements?? It also possible to get in Win32 by pHtmlDoc->get_activeElement But Win CE 5.0 L Please Help me. Thank you. ps: Thank you 'Paul G. Tobey [eMVP]' for your help. But the way doesn't work... and I couldn't find the sample in SDKs which I downloaded things... If you don't mind would plz send me the Sample to roamjh@hotmail.com? Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92920
  - 4
    - Unable to find MFC catalog item in PB for Windows CE 6.0 Hello Fellow Creators: The Catalog Item View for Platform Builder for Windows CE 5.0 allowed users to select the "Microsoft Foundation Classes (MFC)" item from the "Applications and Services Development" section. The item does not appear in the Catalog Item View for Platform Builder for Windows CE 6.0. The Help files mention that this item is only available for display-based OS designs. However, regardless of my choice of Design Template or Board Support Package, the item never appears in the Catalog Item View. How can I add the MFC catalog item? Thanks in advance ! Mark. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92917
  - 5
    - USBD.DLL Does anyone know how to get this DLL in my platform? I am working on a USB host driver, and in the debug log I see "could not load USB.DLL". Since I did my USB OHCI driver as a user project, I wonder if I am missing some other component. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92906
  - 6
    - FILESYS cannot access init key eventhough successfully created ?! Hi, I have a TinyKernel + MINGDI OS configuration and are experiencing registry problems during cold boot. FILESYS cannot find the init key and it can also not find the HKLM\System\Events keys. The strange thing is that the keys have been successfully created though: >--- here it creates the HKLM\System\Events keys: 0x8c059000: prgRegCreateKeyExW called hKey=80000002 lpszSubKey=System\Events 0x8c059000: prgRegCreateKeyExW done - returning hKey=00092510 0x8c059000: prgRegSetValueExW called hKey=00092510 lpszValueName=SYSTEM/GweApiSetReady 0x8c059000: prgRegSetValueExW done - returning Success 0x8c059000: prgRegSetValueExW called hKey=00092510 lpszValueName=SYSTEM/PowerManagerReady 0x8c059000: prgRegSet*ValueExW done - returning Success 0x8c059000: prgRegSetValueExW called hKey=00092510 lpszValueName=SYSTEM/DevMgrApiSetReady 0x8c059000: prgRegSetValueExW done - returning Success 0x8c059000: prgRegCloseKey called 0x8c059000: prgRegCloseKey done ---< .. >--- Here it creates the init keys 0x8c059000: prgRegCreateKeyExW called hKey=80000002 lpszSubKey=init 0x8c059000: prgRegCreateKeyExW done - returning hKey=00092510 0x8c059000: prgRegSetValueExW called hKey=00092510 lpszValueName=Depend30 0x8c059000: prgRegSetValueExW done - returning Success 0x8c059000: prgRegSetValueExW called hKey=00092510 l*pszValueName=Launch30 0x8c059000: prgRegSetValueExW done - returning Success 0x8c059000: prgRegSetValueExW called hKey=00092510 lpszValueName=Launch20 0x8c059000: prgRegSetValueExW done - returning Success 0x8c059000: prgRegCloseKey called 0x8c059000: prgRegCloseKey done ---< .. >--- Later I see FILESYS complaining: 0x8c05ea40: prgRegQueryValueExW called hKey=80000002 lpszValueName=AllowSystemAccess 0x8c05ea40: prgRegQueryValueExW done - returning Success 0x8c059000: prgRegOpenKeyExW called hKey=80000002 lpszSubKey=System\Events 0x8c059000: prgRegOpenKeyExW done - returning hKey=00000001 0x8c059000: FS: HKLM\System\Events not available, no signal events created. 0x8c059000: FILESYS: Launching apps 0x8c059000: prgRegOpenKeyExW called hKey=80000002 lpszSubKey=init 0x8c059000: prgRegOpenKeyExW done - returning hKey=006E006F 0x8c059000: ERROR: c:\macallan\private\winceos\coreos\filesys\main\fsmain.c line 4101: 0x8c059000: Unable to locate init key for starting apps! 0x8c059000: FILESYS: Done launching apps 0x8c059000: prgRegOpenKeyExW called hKey=80000002 ---< Because the apps (device.exe, gwes.exe etc.) are not getting started I am dead in the water. I do not have source code of FILESYS so I can't simply determine what is going on. Note that the TinyKernel configuration has no problems running the TKTest (the TinyKernel test program that is a replacement for FILESYS). Can someone who has access to FILESYS source code give me a hint of what is going on ? Thank you ! Ronald Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92899
  - 7
    - DMA and USB Hi All, I am pretty clueless when it comes to DMA, and now I am trying to get the USB Host Stack from WINCE 4.1 (SA11X1) to run under WINCE 4.1 on a PXA 270. I know there is a driver for WINCE 5.0, but that is not an option for me right now because of a very expensive approval process the product went through with WINCE 4.1. The driver seems to compile and load, but doesn't work. There were a few pointers to clock registers, OHIC, etc. that I had to change, and these seemed straight-forward. However what I have a lot of uncertainly about is what the driver calls the OHCIDMABuffer. Trying to map these DMA related addresses as defined in the SA11X1 BSP to something equivalent in not easy since I don't actually have the SA11X1. I cannot imagine this is the address of the DMA Controller register itself, as it is called a buffer. So I believe maybe this is an address to a buffer of DMA memory created else where. In the past, my limited experience with DMA was to dink with the size of a buffer for the video driver, depending on whether I was using 8-bit vs. 16-bit video mode. I have no idea though how DMA is applicable in this instance. I tried to read up on it in the PXA270 Developer Guide, and found myself able to follow in each scenario suggested yet unable to apply any of it to what I am trying to do. Is the USB host stack from WINCE 4.1 using DMA as a buffer in the PDD and passing a pointer to this buffer to the MDD? If so, where is this buffer created? Would this be considered a memory-to-memory transfer? I don't comprehend how this is a "DMA buffer" if I am specifying a source and target memory address. When I think of DMA, I usually think of servicing a peripheral. Obviously I am very confused. If someone has a moment to spell out what I am missing here I'd be much obliged. Thanks! Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92895
  - 8
    - Compile Error: Bad register name symbol `eax` I am migrating one project from VC6 to EVC4. First, I build an OS, export SDK and install it. In EVC4, build a DLL project( I want to build a dll), inport all .cpp and .h files and then build. Here comes the problem, some of them can't pass but others can. Any suggestion? Thanks! The error message is like this: =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD= =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD --------------------Configuration: AVSDECDLL - Win32 (WCE ARMV4I) Debug-------------------- Compiling... avsdeclib.cpp E:\temp\avsdecdll\source\avsdeclib.cpp(80): warning #1011: missing return statement at end of non-void function "OpenAVSDec" } ^ ASXSCCE-E-ERROR[0075]:C:\DOCUME~1\ali88\LOCALS~1\Temp\8962.asm:48:Bad register name symbol `eax` ASXSCCE-E-ERROR[0046]:C:\DOCUME~1\ali88\LOCALS~1\Temp\8962.asm:48:Missing `#` before immediate offset ASXSCCE-E-ERROR[0076]:C:\DOCUME~1\ali88\LOCALS~1\Temp\8962.asm:52:Unknown directive or instruction `bswap` ASXSCCE-E-ERROR[0065]:C:\DOCUME~1\ali88\LOCALS~1\Temp\8962.asm:52:Syntax error in source line ASXSCCE-E-ERROR[0075]:C:\DOCUME~1\ali88\LOCALS~1\Temp\8962.asm:56:Bad register name symbol `tmp` ASXSCCE-E-ERROR[0046]:C:\DOCUME~1\ali88\LOCALS~1\Temp\8962.asm:56:Missing `#` before immediate offset error during compilation xicle44": error: The execution of program 'C:\PROGRA~1\MICROS~1.0\EVC\WCE500\bin\isacc44.exe' was aborted. Error executing C:\Program Files\Microsoft eMbedded C++ 4=2E0\EVC\WCE500\bin\xicle44. avsdeclib.obj - 3 error(s), 1 warning(s) =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD= =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD one file that can't pass =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD= =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD #include "define.h" #include "avsdeclib.h" #include "global.h" #include "decode.h" #include "stream1.h" ////////////////////////////////////////////////////////////////////////// // global variables STREAMINFO strmInfo; AVS_BYTE* pbBuf =3D (AVS_BYTE*)calloc(INBUFLEN*2, sizeof(AVS_BYTE)); VIDEODATA* videoBuf[3]; VIDEODATA* pRefFrame[2]; VIDEODATA* pCurrFrame; VIDEODATA* videoFieldBuf[5]; VIDEODATA* pRefField[4]; MBINFO* pMbInfo; BWREFINFO* pBwRefInfo; bool firstFrame; int OpenAVSDec(BYTE* pbData, int len, SEQ_INFO* pInfo) { if(DWORD_SWAP(*(AVS_DWORD*)pbData)!=3D SEQENCE_START_CODE) return AVS_FALSE; if(len < 20) return AVS_NOT_ENOUGH_DATA; pBwRefInfo =3D new BWREFINFO[MAX_MB_NUM]; pMbInfo =3D new MBINFO[MAX_MB_NUM]; firstFrame =3D 1; GetMem(videoBuf, 3); GetMem(videoFieldBuf, 5); // Init reference frame buffer pRefFrame[0] =3D videoBuf[0]; pRefFrame[1] =3D videoBuf[1]; pCurrFrame =3D videoBuf[2]; InitDecode(pbData, len, &strmInfo); pInfo->image_width =3D strmInfo.SeqInfo.dwWidth; pInfo->image_height =3D strmInfo.SeqInfo.dwHeight; pInfo->frame_rate =3D strmInfo.SeqInfo.fFrameRate; } int GetOneFrameBitsFromBuffer(unsigned char *pFrameBuf, int iBufLen, int *pFrameLen, int* pNoUseDataLen) { AVS_BYTE* pbData =3D pFrameBuf; AVS_INT iLeft =3D iBufLen; AVS_INT iNoUseDatalen =3D 0; *pFrameLen =3D 0; *pNoUseDataLen =3D 0; while (pbData[0] !=3D 0x00 || pbData[1] !=3D 0x00 || pbData[2] !=3D 0x01) { pbData ++; iLeft --; (*pNoUseDataLen) ++; if(iLeft < 4) return 0; } while(1) { switch(pbData[(*pNoUseDataLen)+3]) { case 0xB0: // Sequence Header if(!FindNextPicOrEndStartCode(pbData, iBufLen, (AVS_DWORD*)&iLeft)) return AVS_NOT_ENOUGH_DATA; SeqenceHeader(pbData, iBufLen, &(strmInfo.SeqInfo)); *pNoUseDataLen +=3D iBufLen-iLeft; break; case 0xB5: // Extension if(!FindNextPicOrEndStartCode(pbData+*pNoUseDataLen, iBufLen, (AVS_DWORD*)&iLeft)) return AVS_NOT_ENOUGH_DATA; *pNoUseDataLen +=3D iBufLen-iLeft; break; case 0xB2: // User Data if(!FindNextPicOrEndStartCode(pbData+*pNoUseDataLen, iBufLen, (AVS_DWORD*)&iLeft)) return AVS_NOT_ENOUGH_DATA; *pNoUseDataLen =3D iBufLen-iLeft; break; case 0xB3: // I frame if(!FindNextPicOrEndStartCode(pbData+*pNoUseDataLen, iBufLen, (AVS_DWORD*)&iLeft)) return AVS_NOT_ENOUGH_DATA; *pFrameLen =3D iBufLen-iLeft+*pNoUseDataLen; return 1; case 0xB6: // PB frame if(!FindNextPicOrEndStartCode(pbData+*pNoUseDataLen, iBufLen, (AVS_DWORD*)&iLeft)) return AVS_NOT_ENOUGH_DATA; *pFrameLen =3D iBufLen-iLeft+*pNoUseDataLen; return 1; case 0xB1: // Sequence End return 0; } } } int DecOneFrameFromBuffer(unsigned char *pbData, int iFrameLen, BYTE** ppOutY, BYTE** ppOutU, BYTE** ppOutV) { if(DWORD_SWAP(*(AVS_DWORD*)pbData)=3D=3DI_FRAME_START_CODE || DWORD_SWAP(*(AVS_DWORD*)pbData) =3D=3D PB_FRAME_START_CODE) { DecodeOneFrame(pbData, iFrameLen, &strmInfo, pRefFrame, &pCurrFrame, pMbInfo, pBwRefInfo); } if(firstFrame) { *ppOutY =3D pRefFrame[0]->y; *ppOutU =3D pRefFrame[0]->u; *ppOutV =3D pRefFrame[0]->v; firstFrame =3D FALSE; } else if((strmInfo.ImgInfo.dwImageType !=3D B_IMG )) { *ppOutY =3D pRefFrame[1]->y; *ppOutU =3D pRefFrame[1]->u; *ppOutV =3D pRefFrame[1]->v; } else { *ppOutY =3D pCurrFrame->y; *ppOutU =3D pCurrFrame->u; *ppOutV =3D pCurrFrame->v; } return AVS_NOERROR; } void CloseAVSDec() { delete []pBwRefInfo; delete []pMbInfo; ReleaseMem(videoBuf, 3); ReleaseMem(videoFieldBuf, 5); } =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD= =A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD=A3= =AD=A3=AD=A3=AD=A3=AD=A3=AD=A3=AD Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92887
  - 9
    - How to modify the bootloader to make it support P30 flash hello all. I am working on a PXA270 platform with WINCE 5.0, using intle P30 flash. I want to write the system image to the flash memory, but encounter some problem. If I do not modify the original flash module (it support intel L18 flash) in the bootloader, sometimes, it will download the system image to the flash corretly. But it will fail when it verify the flash erase in other times (the probability is about 20%...) . The error is that one bit is not set to 1 in some address. Can you tell me what I should modify or give me some tips about the difference with the P30 flash? Thanks. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92885
  - 10
    - migrating .cec file from WinCE5.0 to WinCE4.2 I have an .cec file in PB5.0 but now i am working with PB4.2 and i need the same .cec file to be added to my platform. so can anyone tell me how i can migrate it and what are the steps i have to follow up, it would be a great help for me . thanks smith Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92880
  - 11
    - Cetlstub.dll missing in CE6.0 build Hi, I've created a CE6.0 image for the ARM Device Emulator. I added the Platform Manager component but i get the following error from Makeimg - could not find cetlstub.dll on disk. Which component or setting needs adding to get this dll built into release directory. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92877
  - 12
    - WINCE system migration problem Hi, All, I have a working BSP for WINCE4.2 based on S3C2410. Now I have a question. Can I use back the same BSP (with minor modification) on S3C2440 platform? If not, what will be major changes? Please advice. Wanchope Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92875
  - 13
    - suspend Hello to you, I am using ce 5 with a sandgate2p board with pxa270. It has a OFF key that put the system in deep-idle and I have to change it to suspend. As a first step I put a call to keybd_event(VK_OFF, 0, 0, 0) in the keypad IST keeping OEMPowerOff empty, that is: void OEMPowerOff(void) { RETAILMSG(TRUE, (TEXT("OEMPowerOff\r\n"))) ; } In the release configuration, if kitl is enabled the system turn off the video and the audio drivers and then instantly resumes. If kitl is disabled the system hangs. I am new to ce so I don't know anything about the interaction with kitl. Can you help me? Thanks Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92874
  - 14
    - Flash disk and SD card IDs With DeviceIoControl I get the SD card unique ID, and I think it's generated by the SD card producer in factory. What about internal flash disk (NAND file system): with DeviceIoControl I can get its ID.. is it generated in factory, too? It seems to not to be so.. why? Mhaxx Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92872
  - 15
    - How to migrate the BSP(SMDK2440) from CE4.2 to CE5.0? Hi: I have a S3C2440 target board, the OS is CE4.2, and the BSP is SMDK2440. Now, I wanna to use CE5.0, but it is difficult for me to migrate the SMDK2440 about CE4.2 to CE5.0. How to finish this job or where can I download the SMDK2440 about CE5.0? Pls give me some advices. Thanks in advance. Best Regards. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92864
  - 16
    - About SD interface in WinCE 5.0 Helllo everyone. I am using PXA27x and WinCE 5.0. And there's some questions about SD interface. I would like to implement two SD slots. The one is for SD memory and the another is for SDIO-type WLAN module. >From the point of Hardware, It might be possible to use MUX. But there will be some consideration of software. 1. As long as I know, After a SD device is inserted, the bus driver identifies the SD device. and then the bus driver loads the client driver related to the SD device. This operation is initiated by the SD card insertion. And because of the hardware condition, thiis scheme is assumed that the only one device have to be used at a time. But if the SDIO-type WLAN module is trying to send data from SD memory, Is the following procedure evitable? (Now MUX is choosing the SDIO device. and WLAN is trying to send data.) MUX choose the SD device -> SD Insertion -> the Cilent driver for SD memory is loaded -> Read and buffering data -> MUX choose the SDIO device -> SD Insertion -> the Client driver for SDIO is loaded ... 2. The another way is to use a exteranl SD bus host-controller. Which way do you think better? and Is there anyone who met the same problem? If so, I would like to listen your solution. Thank you. Jang Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92859
  - 17
    - What is the meaning of "OAK"? In many folders, they have the name OAK. I guess this is just a abbreviation. A very simple questing, what is the meaning of OAK? What the folder named OAK works for? I can not find it by web searching. Thanks. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92855
  - 18
    - Problem with SDK created in Platform Builder and Windows Vista Hi, Here is my problem. When I install my Windows CE SDK on a Windows XP machine, everything works perfectly. When I try to install the same SDK on in Windows Vista, the SDK doesn't appear in VS 2005 sdk choices. What is the problem here? Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92853
  - 19
    - gethostbyname("ppp_peer"); I am trying to setup a TCP connection from my CE 5.0 device to XP Desktop that has ActiveSync running via USB to the device. I use hostServer = gethostbyname("ppp_peer"); to obtain the IP adr of the host. It returns 192.168.55.100 whereas it should be 192.168.1.100. Why would this be? This appears to be a "magic number" as in my search within this group a number of people report this ip adr (192.168.55.100) in response to gethostbyname("ppp_peer"); Using this result, the connect fails. What should I be doing? Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92844
  - 20
    - Sysgen_capture problem with CE6.0 Hi, I've cloned the FSDSPY directory under the PUBLIC tree to my BSP directory. I've created a SRC and DLL directory. I can build the src directory fine. I then run sygsen_capture fsdspy in the dll directory and it comes back with the following error SYSGEN0000: error in sysgen phase The following is the output of build.log. I have no idea why it is trying to make fsdspy. I just want a sources file created the way it used to in V5.0. Windows CE Version (Release) (Built on Jun 30 2006 16:52:46) makefile.def: Invoked with predefined settings: TARGETNAME: dummy TARGETTYPE: dummy RELEASETYPE: TARGETLIBS: SOURCELIBS: makefile.def: Including C:\WINCE600\public\common\oak\misc\Sources.default makefile.def: BUILDROOT is C:\WINCE600\public\common\cesysgen makefile.def: Including C:\WINCE600\PUBLIC\COMMON\CESYSGEN\sources makefile.def: Including C:\WINCE600\public\common\oak\misc\Sources.CE Directory: C:\WINCE600\PUBLIC\COMMON\CESYSGEN TARGETNAME: dummy RELEASETYPE is not defined. Using DEFAULT. makefile.def: Including C:\WINCE600\public\common\oak\misc\sources.ReleaseType_DEFAULT NMAKE : fatal error U1073: don't know how to make 'fsdspy' Stop. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92840
  - 21
    - Windows CE 5.0 Platform Builder Monthly Update (October 2006) errors Since I installed "Windows CE 5.0 Platform Builder Monthly Update (October 2006)", I get build errors within CESHELL with my ARMV4I build. Is anyone else having this problem? Here is what I am seeing: BUILD: [00:0000000253:PROGC ] Compiling \WINCE500\PUBLIC\SHELL\OAK\HPC\CESHELL\ui\ directory. BUILD: [01:0000000260:PROGC ] Compiling .\api.cpp BUILD: [01:0000000263:PROGC ] Compiling .\ceshell.cpp BUILD: [01:0000000266:PROGC ] Compiling .\ceshellcf.cpp BUILD: [01:0000000269:PROGC ] Compiling .\datatrans.cpp BUILD: [01:0000000272:PROGC ] Compiling .\defshellview.cpp BUILD: [01:0000000275:PROGC ] Compiling .\deskfolder.cpp BUILD: [01:0000000278:PROGC ] Compiling .\desktopview.cpp BUILD: [01:0000000281:PROGC ] Compiling .\drivesfolder.cpp BUILD: [01:0000000284:PROGC ] Compiling .\filechangemgr.cpp BUILD: [01:0000000287:PROGC ] Compiling .\filefolder.cpp BUILD: [01:0000000290:PROGC ] Compiling .\filemenu.cpp BUILD: [01:0000000293:PROGC ] Compiling .\fsdrop.cpp BUILD: [01:0000000296:PROGC ] Compiling .\fsenum.cpp BUILD: [01:0000000299:PROGC ] Compiling .\guid.cpp BUILD: [01:0000000302:PROGC ] Compiling .\idlist.cpp BUILD: [01:0000000305:PROGC ] Compiling .\iniutil.cpp BUILD: [01:0000000308:PROGC ] Compiling .\netfolder.cpp BUILD: [01:0000000311:PROGC ] Compiling .\netrootview.cpp BUILD: [01:0000000314:PROGC ] Compiling .\nsenum.cpp BUILD: [01:0000000317:PROGC ] Compiling .\recbindrop.cpp BUILD: [01:0000000320:PROGC ] Compiling .\recbinmenu.cpp BUILD: [01:0000000323:PROGC ] Compiling .\recbinview.cpp BUILD: [01:0000000326:ERRORE] c:\WINCE500\PUBLIC\SHELL\OAK\HPC\CESHELL\UI\recbinview.h(23) : error C2061: syntax error : identifier 'ChangeNotifyEventData' BUILD: [01:0000000327:ERRORE] c:\WINCE500\PUBLIC\SHELL\OAK\HPC\CESHELL\UI\recbinview.cpp(43) : error C2065: 'ChangeNotifyEventData' : undeclared identifier BUILD: [01:0000000328:ERRORE] c:\WINCE500\PUBLIC\SHELL\OAK\HPC\CESHELL\UI\recbinview.cpp(43) : error C2065: 'pChangeNotifyEventData' : undeclared identifier BUILD: [01:0000000329:ERRORE] c:\WINCE500\PUBLIC\SHELL\OAK\HPC\CESHELL\UI\recbinview.cpp(44) : error C2448: 'CRecycleBinView::HandleChangeNotify' : function-style initializer appears to be a function definition BUILD: [01:0000000330:PROGC ] Compiling .\recyclefolder.cpp BUILD: [01:0000000333:ERRORE] c:\WINCE500\PUBLIC\SHELL\OAK\HPC\CESHELL\UI\recbinview.h(23) : error C2061: syntax error : identifier 'ChangeNotifyEventData' BUILD: [01:0000000334:PROGC ] Compiling .\shelldialogs.cpp BUILD: [01:0000000337:PROGC ] Compiling .\shelllistview.cpp BUILD: [01:0000000340:PROGC ] Compiling .\usersettings.cpp BUILD: [01:0000000343:PROGC ] Linking C:\WINCE500\public\shell\oak\lib\ARMV4I\retail\ceshui.lib BUILD: [01:0000000345:ERRORE] LINK : fatal error LNK1181: cannot open input file 'obj\ARMV4I\retail\recbinview.obj' BUILD: [01:0000000346:PROGC ] Resource Compiling .\ceshui_base.rc BUILD: [01:0000000350:PROGC ] Resource Compiling .\ceshui_vgal.rc BUILD: [01:0000000354:PROGC ] Resource Compiling .\ceshui_qvgap.rc In the mean time, I've restored the four files that this QFE "fixed" within CESHELL.... JimMerkle TwoTechnologies Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92837
  - 22
    - Warnings during build porcess in Platform Builder 5.0 When building an image we recieve many warnings all related to files that came wth the BSP we recieved: BUILD: [01:0000000102:WARNN ] halsurf.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\pxa27x_lcd.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000103:WARNN ] halpalette.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\pxa27x_lcd.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000104:WARNN ] haldd.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\pxa27x_lcd.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000105:WARNN ] halcaps.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\pxa27x_lcd.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000106:WARNN ] dispdrvr.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\pxa27x_lcd.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000107:WARNN ] sa2video.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\pxa27x_lcd.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000135:WARNN ] aclink.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\wm9712touch.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000136:WARNN ] touch.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\wm9712touch.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000164:WARNN ] ohci2.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\ohci2.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000192:WARNN ] serial.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\platform_serial.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000220:WARNN ] usbfn.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\usbfn.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000248:WARNN ] impl.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\sdhc_mmc2.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000276:WARNN ] impl.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\sdhc_mmc1.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000303:WARNN ] LAN91CNDIS_Phy.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\lan91cndis.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000304:WARNN ] LAN91CNDIS_NDIS.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\lan91cndis.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000305:WARNN ] LAN91CNDIS_Miniport.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\lan91cndis.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000306:WARNN ] LAN91CNDIS_Intr.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\lan91cndis.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000307:WARNN ] LAN91CNDIS_Init.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\lan91cndis.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000308:WARNN ] LAN91CNDIS_Filter.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\lan91cndis.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000372:WARNN ] backlight_Mgt.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\backlight.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000373:WARNN ] backlight.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\backlight.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000407:WARNN ] cpld.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\cpld.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000545:WARNN ] kitl.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\kern.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000619:WARNN ] backlightApplet.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\backlightapplet.pdb' is missing debugging information for referencing module; linking object as if no debug info BUILD: [01:0000000653:WARNN ] TouchCalibrate.obj : warning LNK4204: 'c:\wince500\platform\phycore-pxa270-dk\target\armv4i\debug\touchcalibrate1.pdb' is missing debugging information for referencing module; linking object as if no debug info I was told buy one of the software engineers who helped to develop the BSP that this is happening due to the fact a release version of the image is being built, but the same thing happens when a debug version of the image is built as well. I've checked several of these files and they do contain debug messages that are displayed to the output window. Is there something else that should be added to these files, or is there something else I should be doing before starting the build process that will eliminate these warnings? I am performing a Sysgen with the Clean Before Building, Copy Files to Release Directory After Build, and Make Run-Time Image After Build flags set. Thanks for any help you can give. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92835
  - 23
    - How to add some debug outputs to the bootloader Hello, I am working on modifying the flash operation in the bootloader to let it work correctly with intel P30 embedded flash memory. But it does not work correctly, sometimes it will fail when it is erasing the flash. So I want to add some debug outputs to the codes to see some information. But when I add some debug outputs into the image and rebuild it, it seems take no effect. The output does not change at all. Can you tell me how to add the debug outputs to the bootloader? I use Platform Builder with Wince 5.0. Thanks. Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92833
  - 24
    - Adding shortcut file to image fails Hello, I have a problem adding shortcuts to a Windows CE 5.0 image. Building stops with the following error message: Error: Failed reading e32 pointer in module pniod.lnk The entry in platform.bib is: pniod.lnk $(_FLATRELEASEDIR)\pniod.lnk NK SH The shortcut file contains: 18#\windows\pniod.exe Any ideas? Regards, Gerhard Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92831
  - 25
    - Interrupt for beginners Hello, I only have one question "How to implement Interrupts under Windows CE 5.0". Yes I know its easy, but I even do not know how to start. I read a lot of articles in the MSDN, but the basic knowledge is still missing. Does someone have an example implementation, the hardware side is no problem. Which functions do I need, where to place this functions, which header files are need to be used? Can I develope an Interrupt handler without using the Platform Builder? So that I am able to include it to an existing WinCE image? Thanks for your answers. Albert Tag: Developing NDIS drive for Windows Mobile 5.0 Tag: 92830

Hi,
I want to develop a intermediate NDIS driver for a WM 5.0 IntelPXA270
based phone . Actually it is a variation of the passthru driver (a miniport
driver at one end and a protocol driver at the other end). Based on what I
can understand so far, I need to use platform builder for Windows CE 5 to
develop the driver for the targeted platform after creating a OS design using
the Intel PXA27X BSP and then export that as a CAB file which can be
installed on a WM 5.0 device. Is my understanding correct? Thanks in advance.

ravi

Top