Dose the WInce 4.2 support the AGP display driver?

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - about JFlash This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C42E9F.7D33A1B0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable =BF=D5=B0=D7Hi,all: Form the messages shows below,what can tell me?Has one of the Flash = crashed or other? but "read Q,read R and read Y" run well.what should I do? JFLASH Version 2.10.002 - DBPXA250 COPYRIGHT (C) 2000-2002 Intel Corporation PXA250 revision 0x6?? attr: 00510051 There are two 16-bit Flash devices in parallel Characteristics for one device: Number of blocks in device =3D 128 Block size =3D 65536 0x10000 word(16-bit) Device size =3D 8388608 0x800000 word(16-bit) Sample block to address list: Block 0 =3D hex address: 00000000=20 Block 40 =3D hex address: 00A00000=20 Block 80 =3D hex address: 01400000=20 Block 120 =3D hex address: 01E00000=20 The last 66 percent of image file is all zeros Would you like to save time by not programming that area? [y/n]:=20 Starting erase Erasing block 0 =20 Erasing done =20 Starting programming Writing flash at hex address 1000, 1.56% done =20 Writing flash at hex address 2100, 3.22% done =20 Writing flash at hex address 2f80, 4.64% done =20 Writing flash at hex address 4080, 6.30% done =20 Writing flash at hex address 4f80, 7.76% done =20 Writing flash at hex address 5f80, 9.33% done =20 Writing flash at hex address 7100, 11.04% done =20 Writing flash at hex address 8240, 12.72% done =20 Writing flash at hex address 9180, 14.21% done =20 Writing flash at hex address a300, 15.92% done =20 Writing flash at hex address b440, 17.60% done =20 Writing flash at hex address c5c0, 19.31% done =20 Writing flash at hex address d740, 21.02% done =20 Writing flash at hex address e8c0, 22.73% done =20 Writing flash at hex address fa40, 24.44% done =20 Writing flash at hex address 10bc0, 26.15% done =20 Writing flash at hex address 11d80, 27.88% done =20 Writing flash at hex address 12f00, 29.59% done =20 Writing flash at hex address 14080, 31.30% done =20 Writing flash at hex address 15200, 33.01% done =20 Writing flash at hex address 16380, 34.72% done =20 Writing flash at hex address 17500, 36.43% done =20 Writing flash at hex address 18680, 38.13% done =20 Writing flash at hex address 19840, 39.87% done =20 Writing flash at hex address 1a9c0, 41.58% done =20 Writing flash at hex address 1bb40, 43.29% done =20 Writing flash at hex address 1ccc0, 45.00% done =20 Writing flash at hex address 1de40, 46.70% done =20 Writing flash at hex address 1efc0, 48.41% done =20 Writing flash at hex address 20140, 50.12% done =20 Writing flash at hex address 212c0, 51.83% done =20 Writing flash at hex address 22400, 53.52% done =20 Writing flash at hex address 23580, 55.22% done =20 Writing flash at hex address 24700, 56.93% done =20 Writing flash at hex address 25880, 58.64% done =20 Writing flash at hex address 26a00, 60.35% done =20 Writing flash at hex address 27b80, 62.06% done =20 Writing flash at hex address 28d00, 63.77% done =20 Writing flash at hex address 29e80, 65.48% done =20 Writing flash at hex address 2b000, 67.19% done =20 Writing flash at hex address 2c1c0, 68.92% done =20 Writing flash at hex address 2d300, 70.61% done =20 Writing flash at hex address 2e4c0, 72.34% done =20 Writing flash at hex address 2f640, 74.05% done =20 Writing flash at hex address 307c0, 75.76% done =20 Writing flash at hex address 31940, 77.47% done =20 Writing flash at hex address 32ac0, 79.17% done =20 Writing flash at hex address 33c40, 80.88% done =20 Writing flash at hex address 34dc0, 82.59% done =20 Writing flash at hex address 35f40, 84.30% done =20 Writing flash at hex address 37080, 85.99% done =20 Writing flash at hex address 38200, 87.70% done =20 Writing flash at hex address 39380, 89.40% done =20 Writing flash at hex address 3a500, 91.11% done =20 Writing flash at hex address 3b680, 92.82% done =20 Writing flash at hex address 3c7c0, 94.51% done =20 Writing flash at hex address 3d940, 96.22% done =20 Writing flash at hex address 3eac0, 97.92% done =20 Writing flash at hex address 3fc40, 99.63% done =20 Programming done Starting Verify verify error at address =3D 0 exp_dat =3D ea0003fe act_dat =3D ea003fff verify error at address =3D 1 exp_dat =3D 0 act_dat =3D 3ff9 verify error at address =3D 2 exp_dat =3D 0 act_dat =3D 3ff9 verify error at address =3D 3 exp_dat =3D 0 act_dat =3D 3ff9 verify error at address =3D 4 exp_dat =3D 0 act_dat =3D 3ff9 =A1=AD=A1=AD ------=_NextPart_000_000D_01C42E9F.7D33A1B0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE id=3DridTitle>=BF=D5=B0=D7</TITLE><BASE=20 href=3D"file://C:\Program Files\Common Files\Microsoft = Shared\Stationery\"> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"> <STYLE>BODY { MARGIN-TOP: 25px; FONT-SIZE: 10pt; MARGIN-LEFT: 25px; COLOR: #000000; = FONT-FAMILY: =CB=CE=CC=E5, =BA=DA=CC=E5 } P.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; = FONT-FAMILY: =BA=DA=CC=E5, "=CB=CE=CC=E5" } LI.msoNormal { MARGIN-TOP: 0px; FONT-SIZE: 10pt; MARGIN-LEFT: 0px; COLOR: #ffffcc; = FONT-FAMILY: =BA=DA=CC=E5, "=CB=CE=CC=E5" } </STYLE> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD> <BODY id=3DridBody bgColor=3D#ffffff background=3D"Blank Bkgrd.gif"> <DIV>Hi,all:</DIV> <DIV> </DIV> <DIV>    Form the messages shows below,what can tell = me?Has=20 one of the Flash crashed or other?</DIV> <DIV>but "read Q,read R and read Y" run well.what should I = do?</DIV> <P>JFLASH Version 2.10.002 - DBPXA250<BR>COPYRIGHT (C) 2000-2002 Intel=20 Corporation<BR>PXA250 revision 0x6??</P> <P>attr: 00510051<BR>There are two 16-bit Flash devices in parallel</P> <P>Characteristics for one device:<BR> Number of blocks in device = =3D=20 128<BR> Block size =3D 65536 0x10000 word(16-bit)<BR> Device = size =3D=20 8388608 0x800000 word(16-bit)</P> <P>Sample block to address list:</P> <P> Block 0 =3D hex address: 00000000 <BR> Block 40 =3D hex = address:=20 00A00000 <BR> Block 80 =3D hex address: 01400000 <BR> Block = 120 =3D hex=20 address: 01E00000 <BR>The last 66 percent of image file is all = zeros<BR>Would=20 you like to save time by not programming that area? [y/n]: <BR>Starting=20 erase<BR>Erasing block   0   <BR>Erasing=20 done           &nb= sp;           &nbs= p;           &nbsp= ;      =20 <BR>Starting programming<BR>Writing flash at hex = address    =20 1000,  1.56% done    <BR>Writing flash at hex=20 address     2100,  3.22% done    = <BR>Writing flash at hex address     2f80,  = 4.64%=20 done    <BR>Writing flash at hex = address    =20 4080,  6.30% done    <BR>Writing flash at hex=20 address     4f80,  7.76% done    = <BR>Writing flash at hex address     5f80,  = 9.33%=20 done    <BR>Writing flash at hex = address    =20 7100, 11.04% done    <BR>Writing flash at hex=20 address     8240, 12.72% done    = <BR>Writing=20 flash at hex address     9180, 14.21% = done   =20 <BR>Writing flash at hex address     a300, 15.92%=20 done    <BR>Writing flash at hex = address    =20 b440, 17.60% done    <BR>Writing flash at hex=20 address     c5c0, 19.31% done    = <BR>Writing=20 flash at hex address     d740, 21.02% = done   =20 <BR>Writing flash at hex address     e8c0, 22.73%=20 done    <BR>Writing flash at hex = address    =20 fa40, 24.44% done    <BR>Writing flash at hex=20 address    10bc0, 26.15% done    = <BR>Writing flash=20 at hex address    11d80, 27.88% done   =20 <BR>Writing flash at hex address    12f00, 29.59%=20 done    <BR>Writing flash at hex = address    14080,=20 31.30% done    <BR>Writing flash at hex = address   =20 15200, 33.01% done    <BR>Writing flash at hex=20 address    16380, 34.72% done    = <BR>Writing flash=20 at hex address    17500, 36.43% done   =20 <BR>Writing flash at hex address    18680, 38.13%=20 done    <BR>Writing flash at hex = address    19840,=20 39.87% done    <BR>Writing flash at hex = address   =20 1a9c0, 41.58% done    <BR>Writing flash at hex=20 address    1bb40, 43.29% done    = <BR>Writing flash=20 at hex address    1ccc0, 45.00% done   =20 <BR>Writing flash at hex address    1de40, 46.70%=20 done    <BR>Writing flash at hex = address    1efc0,=20 48.41% done    <BR>Writing flash at hex = address   =20 20140, 50.12% done    <BR>Writing flash at hex=20 address    212c0, 51.83% done    = <BR>Writing flash=20 at hex address    22400, 53.52% done   =20 <BR>Writing flash at hex address    23580, 55.22%=20 done    <BR>Writing flash at hex = address    24700,=20 56.93% done    <BR>Writing flash at hex = address   =20 25880, 58.64% done    <BR>Writing flash at hex=20 address    26a00, 60.35% done    = <BR>Writing flash=20 at hex address    27b80, 62.06% done   =20 <BR>Writing flash at hex address    28d00, 63.77%=20 done    <BR>Writing flash at hex = address    29e80,=20 65.48% done    <BR>Writing flash at hex = address   =20 2b000, 67.19% done    <BR>Writing flash at hex=20 address    2c1c0, 68.92% done    = <BR>Writing flash=20 at hex address    2d300, 70.61% done   =20 <BR>Writing flash at hex address    2e4c0, 72.34%=20 done    <BR>Writing flash at hex = address    2f640,=20 74.05% done    <BR>Writing flash at hex = address   =20 307c0, 75.76% done    <BR>Writing flash at hex=20 address    31940, 77.47% done    = <BR>Writing flash=20 at hex address    32ac0, 79.17% done   =20 <BR>Writing flash at hex address    33c40, 80.88%=20 done    <BR>Writing flash at hex = address    34dc0,=20 82.59% done    <BR>Writing flash at hex = address   =20 35f40, 84.30% done    <BR>Writing flash at hex=20 address    37080, 85.99% done    = <BR>Writing flash=20 at hex address    38200, 87.70% done   =20 <BR>Writing flash at hex address    39380, 89.40%=20 done    <BR>Writing flash at hex = address    3a500,=20 91.11% done    <BR>Writing flash at hex = address   =20 3b680, 92.82% done    <BR>Writing flash at hex=20 address    3c7c0, 94.51% done    = <BR>Writing flash=20 at hex address    3d940, 96.22% done   =20 <BR>Writing flash at hex address    3eac0, 97.92%=20 done    <BR>Writing flash at hex = address    3fc40,=20 99.63% done    <BR>Programming done<BR>Starting = Verify<BR>verify=20 error at address =3D 0 exp_dat =3D ea0003fe act_dat =3D = ea003fff<BR>verify error at=20 address =3D 1 exp_dat =3D 0 act_dat =3D 3ff9<BR>verify error at address = =3D 2 exp_dat =3D=20 0 act_dat =3D 3ff9<BR>verify error at address =3D 3 exp_dat =3D 0 = act_dat =3D=20 3ff9<BR>verify error at address =3D 4 exp_dat =3D 0 act_dat =3D 3ff9</P> <P>=A1=AD=A1=AD</P> <P> </P></BODY></HTML> ------=_NextPart_000_000D_01C42E9F.7D33A1B0-- Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51552
  - 2
    - System hangs up on Hard Disk read/writes Hi! I posted it some months ago - now repost it Problem - WriteFile/ReadFile functions hangs up with buffers more then ~1K (~1000 bytes) when working with HDD. Platform is Geode. When I encounter this problem, other WinCE programs, like Media Player also completely hangs up the system when reading audio files - HDD LED stays lightening continiously... system is dead With CF-HDD all goes fine. But ordinal 40Gb HDD sometime work normal, sometime hangs up. For example char* buffer = new char[1000] WriteFile(f, buffer, 700, &Written, 0); - ALL GOES FIN WriteFile(f, buffer, 1000, &Written, 0); - Hang up in this cal I thought, it can be stack problems, but i use dynamic memeory (new or VirtualAlloc - the same result Please help - ANY ideas?!? I checked 3 HDD's and 3 different Geode PC's, many OS configurations - helps not. But is seems, that small disks under FAT16 always fork fine, but FAT32 SOMETIMES works too! Unpredictable error Anyone faced this or near this problem :- Thanks...... Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51548
  - 3
    - WinCE Build problem with New driver Hello, I am working on Display driver using WinCE.NET 4.2. I am unable to build the NK image with new device driver. Tell me What are the necessary changes to be done in .BIB and .REG file? Can any suggest for my problem. Thanks in advance. Paul Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51538
  - 4
    - Help me to Bulid the kernel I have done these changes and builded the image: 1)Removed the Cerdisp folder(containing dummy display source code)from the WINCE420/PLATFORM/DRIVERS/DISPLAY DIR and copied our source code folder in this place and also removed the driver from the BSP listing for display and removed the display icon. 2)Removed the setting and entries regarding dummy display and video.dll from bib and reg files. 3)After adding the our project file ,i have made changes in bib and reg files,which are as under:- In COMMON.BIB FILE,i have added IF DISP_DISPLAY DISP.dll $(_FLATRELEASEDIR)\DISP.dll NK S ENDIF In COMMON.REG FILE,i have added IF BSP_CERDISP [HKEY_LOCAL_MACHINE\System\GDI\Drivers] "Display"="DISP.dll" ENDIF In PLATFORM.BIB , IF BSP_NODISPLAY ! IF BSP_CERDISP DISP.dll $(_FLATRELEASEDIR)\DISP.dll NK SH ENDIF ENDIF In PLATFORM.REG, IF BSP_NODISPLAY ! [HKEY_LOCAL_MACHINE\System\GDI\Drivers] "Display"="DISP.dll" IF BSP_CERDISP "DisplayType"="DISP" "CxScreen"=dword:280 ; 640 "CyScreen"=dword: f0 ; 240 "Bpp"=dword:4 ENDIF ENDIF BSP_NODISPLAY ! In PROJECT.BIB i have added: IF DISP_DISPLAY DISP.dll $(_FLATRELEASEDIR)\DISP.dll NK SH ENDIF In PROJECT.REG,I have added: IF DISP_DISPLAY [HKEY_LOCAL_MACHINE\System\GDI\Drivers] "Display"="DISP.dll" ENDIF these respective changes i have done. tell me one thing sir ,Is there any problem with our code or something or some cpp file missing .actually i am not getting any idea.i am constantly trying doing changes but not getting success. after giving make image command it is giving again the same warnings:- Warning: Found duplicate entry 'DISP.dll NK C:\WINCE420\PUBLIC\CSB337\DISP\CSB337__ARMV4IRel\DISP.dll 00000007' ... skipping Warning: Found duplicate entry 'DISP.dll NK C:\WINCE420\PUBLIC\CSB337\RelDir\CSB337~1\DISP.dll 00000007' ... skipping Warning: Using old fixup style in module DISP.dll I dont know why the process gwes.exe is aborting.As it is giving this error while loading kernel image onto the board. Jumping to OS ...Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 13 2003 at 22:52:56 ProcessorType=0920 Revision=0 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8008e034 Sp=ffffc7cc VBridge:: VB_INITIALIZED returns [0] Data Abort: Thread=81ceb114 Proc=80b38ac0 'gwes.exe' AKY=00000011 PC=000538ac RA=0004c6bc BVA=0a000008 FSR=00000007 Please anybody can help in this above issue. Thanks and Regards Gaurav Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51534
  - 5
    - PlatformBuilder 4.2 - ARM emulator out-of-memory download error I'm using the Intel DBPX250 emulator that ships with PN 4.2. I build it (for either mobil device or phone) and create a Hello-world sample app using the wizard. When I go to download the image I get an error like "emulator device does not have enough memory for boot image", even after I increase the platform memory size to a max of 256M and strip out most features from the OS configuation. The X86 emulator works fine though. Any thoughts? Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51532
  - 6
    - Serial download problem for Xscale Hello, I'm trying to port the CEPC sboot code to the XSC1BD platform, but this don't work. My platform send "kITL»$¥ØXSC1BD" and "Wait for boot ack..." but nothing it's received. Platform Builder is "Waiting for a download request..." indefinitly. Is this code set RTS ? UCHAR uCtrl = (READ_PORT_UCHAR(KitlIoPortBase+comModemControl) & ~MC_RTS); WRITE_PORT_UCHAR(KitlIoPortBase+comModemControl, (UCHAR)(uCtrl | MC_RTS)); And this clear RTS ? WRITE_PORT_UCHAR(KitlIoPortBase+comModemControl, (UCHAR)uCtrl); When I do the same thing by the following code, pDownloadUartPort->mcr |= 0x2; // Set RTS and pDownloadUartPort->mcr &= ~0x02; // Clear RTS, my PC stop running when it open then COM port. I don't impletment the serial KITL, must I do ? What are the Platform builder Remote connection settings (flow control or not) ? Like the Beatles says: Please, HELP ME !!! Olivier SPINELLI Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51531
  - 7
    - Build Platform Error!!! I uses Platfrom Builder Version 4.20 Evaluation Edition on Windows 2000 Professional Service Pack 2 and Create a simple Tiny Kernel with Emulator x86 platform. When I Build Platform, I got error message that I shown following ---------------------------------- makeimg: run command: fmerge -db Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\initdb.ini Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\postproc\common.db Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\postproc\wceshellfe.db Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~T \postproc\wceappsfe.db Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\postproc\datasync.db Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\postproc\project.db Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\postproc\platform.db fmerge for Windows CE (Release) (Built on Oct 22 2002 16:06:00 FMERGE: Error - failed to open Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\postproc\common.db durring preprocess phas makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec) makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec) Error PB2505: Error executing #(Z:\WINCE420\PUBLIC\emu86\RelDir\EMULA~TQ\)makeimg.exe EMU86 - 4 error(s), 0 warning(s --------------------------------------- Above message report fmerge failed to open common.db file but when I browse to that folder I have found common.db. What's happen Thanks in advance Suriyan Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51529
  - 8
    - GetAdapterInfo and Usage Count Increases Why does the usage count on WinSock increase every time I invoke GetAdapterInfo but not for other WinSock APIs like send, recv, etc.? What happens when the Usage Count raps? Will WinSock unload if it wraps to 0? Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51521
  - 9
    - What is the driver API call to register a device What is the driver API available in the WinCE to register a device into the OS ? Ex: When i plug a USB device or a UART based device the OS should show that in the device list. A helping link or and example would help -Esha Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51520
  - 10
    - Problems Building Multi XIP Image Hi, I am trying to build an image with multi XIP regions. In config.bib, I have set AUTOSIZE=ON, ROM_AUTOSIZE=ON. However, I am getting error during makeimg. Here is a snippet of the error I get Adding PHONE's entry to NOPHONE Found XIP MISC in chain file AppenError: Found overlap in records 35) start 81424000 length 00027ffc 0) start 81430000 length 0000003c Fatal error hit, exiting... ding 64 byte signature to file Found XIP EXAPPS in chain file Found XIP COREAPPS in chain file Found XIP BROWSING in chain file I did a search in the log file and couldn't find any entries that started at 81424000. What is happening here? I thought ROM_AUTOSIZE will take care of this problem. Any help is appreciated. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51517
  - 11
    - can CE display driver support both rotation and directdraw? Hi.I am using CE.net 4.2 on intel pxa263. The display driver supports screen rotation by porting the rflat driver. Now,my question is: 1)Will DirectDraw improve the video performance even without hardware acceleration ? 2)Is it possible to develop a driver support both rotating and DirecDraw? The sample Geode Gxvideo can only support one feature at the compilation time. Thanks Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51516
  - 12
    - Question on Bandon / Lubbock Config.bib file: Question on Bandon / Lubbock Config.bib file If the image is loaded into Flash, the full contiguous 64megs of SDRAM is used (32 megs for the OS & 28 megs for the RAM). However, when the OS is run directly from the FLASH, still onl 28megs is allocated for the RAM. Why not all 32+28megs ******From the Bandon (very similar to Cotulla) Config.bib************************* ; Name|Virtual/Cached |Size| Region Typ MEMOR IF IMGFLASH ! IF IMGRECOVERY NK 80288000 02000000 RAMIMAGE ; SDRAM 32MB: [8028 8000 -> 8228 7FFF ELSE ; IMGRECOVERY NK 80289000 001C0000 RAMIMAG ENDIF ; IMGRECOVERY RAM 82288000 01A30000 RAM ; SDRAM 28MB: [8228 8000 -> 83CB 7FFF EDBG 83F8D000 00020000 RESERVED ; x20000 for EBOOT - 3 mem pools of 24 ENDI IF IMGFLASH IF BUILD_ROM_BI NK 98380000 01F80000 RAMIMAGE ; FLASH 32MB - 0x80000: Locate above EBO ENDI IF BUILD_ROM_NB NK 98300000 01E00000 RAMIMAGE ; FLASH 32MB - Replace EBOOT Imag ENDI RAM 820B8000 01C00000 RAM ; SDRAM 28MB: [820B 8000 -> 83CB 7FFF ENDI *****Proposed Change********************************************* If the image is running in flash, should'nt config.bib be changed IF IMGFLASH IF BUILD_ROM_BI NK 98380000 01F80000 RAMIMAGE ; FLASH 32MB - 0x80000: Locate above EBO ENDI IF BUILD_ROM_NB NK 98300000 01E00000 RAMIMAGE ; FLASH 32MB - Replace EBOOT Imag ENDI RAM 800B8000 03C00000 RAM ; SDRAM 28MB+32MB: [800B8000->83CB7FFF ENDI I tried this but could not get winCE to recognize the extra 32megs as RAM. This seems amazing since it works correctly when it boots CE from the SDRAM. This would seem to imply that all the low level stuff, memmap.inc, etc are set correctly to recognize the full 64megs of SDRAM. Thanks in advance for any input, Jef Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51513
  - 13
    - A GSM driver exposes itself as UART or USB.. Hi, A GSM will be connected to UART or USB of a PDA . Now I?m going to write a GSM driver on PCMCIA and claim the hardware resources etc, but exposes itself as a UART or USB. PDA will be running WinCE. Is this possible ? Any clue, hint, sample code or any link is available where I can get more information? Regards Esha Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51510
  - 14
    - PB 5.0 install - error 1335 ! Anybody successfuul on this step ? Hi, we are trying to get a taste of new PB 5.0 Machallan and install it as suggested by Microsoft. A small ( ~3 mb) setup file is downloaded from MS PB site and then runs. It then does something for a long time , probably downloading some parts of PB 5.0 over internet, but then fails with the following error : --- Please wait while setup Wizard installs Macallan. This may take several minutes ... [progress bar here...] D:\WinCE500\public\voip\oak\lib\arm4i\retail\rtccore.lib --- Error 1335. The downloaded cabinet file CE_7[1].CAB required for this installation cannot be used. Click Rtetry to try Again or Cancel to Cancel setup. Retry does not help at all :( Cancel means it will start over for 1.5 days of downloading something with the same result. Anybody have seen this error ? What would be the suggestion - just gave up on this beta version of Macllan ? Redards Sergei Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51509
  - 15
    - Load customized driver dll file failed Hi,MVPs What is the meaning of the following message? (debugging message) 4294768681 PID:83fc6072 TID:83fca4e2 0x83fca118: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\SIS7018) entered 4294768699 PID:83fc6072 TID:83fca4e2 0x83fca118: >>> Loading module sis7018.dll at address 0x01E00000-0x01E07000 Loaded 'D:\WINCE420\PUBLIC\CEPC_DEMO\RELDIR\CEPC_X86DEBUG\SIS7018.DLL', no matching symbolic information found. 4294770430 PID:83fc6072 TID:83fca4e2 0x83fca118: Deleting an uninitialized critical section, ignored! 4294770430 PID:83fc6072 TID:83fca4e2 0x83fca118: Deleting an uninitialized critical section, ignored! 4294770430 PID:83fc6072 TID:83fca4e2 0x83fca118: <<< Unloading module sis7018.dll at address 0x01E00000-0x01E07000 Unloaded symbols for 'D:\WINCE420\PUBLIC\CEPC_DEMO\RELDIR\CEPC_X86DEBUG\SIS7018.DLL' 4294770432 PID:83fc6072 TID:83fca4e2 0x83fca118: DEVICE!StartOneDriver RegisterDevice(WAV, 1, sis7018.dll, 0x802ee5c) failed Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51508
  - 16
    - StrongARM with 64MB RAM This is a multi-part message in MIME format. ------=_NextPart_000_0084_01C42D75.E22278B0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Hi All, I got a very odd problem on my StrongARM CPU based WinCE 4.1 system. = Originally the platform has 32MB RAM and the physical starting address = of the RAM is 0xC000000 and it works fine. Later we changed the RAM chip = to 64MB one, I have modified the config.bib and OEMAddressTable to = reflect the changes, but the image that I build can't startup! For the 32MB RAM , the physical address region is : = 0xC0000000~0xC1FFFFFF; For the 64MB RAM, the physical address region is : = 0xC0000000~0xC3FFFFFF; In the OEMAddressTable, I do mapped whole 64MB RAM, and in config.bib I = changed RAM setting=20 from: RAM 8C140000 01EC0000 RAM=20 To: RAM 8C140000 03EC0000 RAM =20 But it just not works. I can't imagine why that happened.=20 I can guarantee in the OEMAddressTable, there's no overlapping after I = do the 64MB RAM mapping. And the hardware also don't have a problem. = Because if I only modified OEMAddressTable and not made any change to = config.bib , the image will still running, just we can only see 32MB RAM = available. And if at this time we are using following code to map = additional 32MB RAM to a virtual address, we can do read/write with the = additional 32MB RAM without a problem. void* pRAMBase =3D (void*)VirtualAlloc(0, 0x01000000, MEM_RESERVE, = PAGE_NOACCESS); VirtualCopy((PVOID)pRAMBase , (LPVOID)(0xC2000000>>8), = 0x01000000,PAGE_READWRITE|PAGE_NOCACHE|PAGE_PHYSICAL)=20 BTW. I've ever do the similar thing on a XScale platform and everything = works fine after I extented the memory setting. Anyone can tell me which part that I missed regarding this issue? Thanks a lot! Xu Jun ------=_NextPart_000_0084_01C42D75.E22278B0 Content-Type: text/html; charset="gb2312" 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=3Dgb2312"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV><FONT face=3DVerdana size=3D2>Hi All,<BR><BR>I got a very odd = problem on my=20 StrongARM CPU based WinCE 4.1 system. Originally the platform has 32MB = RAM and=20 the physical starting address of the RAM is 0xC000000 and it works fine. = Later=20 we changed the RAM chip to 64MB one, I have modified the config.bib and=20 OEMAddressTable to reflect the changes, but the image that I build can't = startup!</FONT></DIV> <DIV><FONT face=3DVerdana size=3D2></FONT> </DIV> <DIV><FONT face=3DVerdana size=3D2>For the 32MB RAM , the physical = address region is=20 : 0xC0000000~0xC1FFFFFF;</FONT></DIV> <DIV><FONT face=3DVerdana size=3D2>For the 64MB RAM,  the physical = address=20 region is : 0xC0000000~0xC3FFFFFF;</FONT></DIV> <DIV><FONT face=3DVerdana size=3D2></FONT> </DIV> <DIV><FONT face=3DVerdana size=3D2>In the OEMAddressTable, I do mapped = whole 64MB=20 RAM, and in config.bib I changed RAM setting </FONT></DIV> <DIV><FONT face=3DVerdana size=3D2>from:</FONT></DIV> <DIV><FONT face=3DVerdana = size=3D2>   RAM  8C140000 =20 01EC0000 RAM </FONT></DIV> <DIV><FONT face=3DVerdana size=3D2>To:</FONT></DIV> <DIV><FONT face=3DVerdana = size=3D2>   RAM  8C140000 =20 03EC0000 RAM  <BR></FONT></DIV> <DIV><FONT face=3DVerdana size=3D2>But it just not works. I can't = imagine why that=20 happened. </FONT></DIV> <DIV><FONT face=3DVerdana size=3D2></FONT> </DIV> <DIV><FONT face=3DVerdana size=3D2>I can guarantee in the = OEMAddressTable, there's=20 no overlapping after I do the  64MB RAM mapping. And the hardware = also=20 don't have a problem. Because if I only modified OEMAddressTable and not = made=20 any change to config.bib , the image will still running, just we = can only=20 see 32MB RAM available. And if at this time  we are using = following=20 code to map additional 32MB RAM  to a virtual address, we can = do=20 read/write with the additional 32MB RAM without a = problem.</FONT></DIV> <DIV><FONT face=3DVerdana size=3D2></FONT> </DIV> <DIV><FONT face=3DVerdana size=3D2>void* pRAMBase  =3D = (void*)VirtualAlloc(0,=20 0x01000000, MEM_RESERVE, = PAGE_NOACCESS);<BR>VirtualCopy((PVOID)pRAMBase  ,=20 (LPVOID)(0xC2000000>>8),=20 0x01000000,PAGE_READWRITE|PAGE_NOCACHE|PAGE_PHYSICAL) <BR></FONT></DIV> <DIV><FONT face=3DVerdana size=3D2>BTW. I've ever do the similar thing = on a XScale=20 platform and everything works fine after I extented the memory=20 setting.</FONT></DIV> <DIV><FONT face=3DVerdana size=3D2> </DIV></FONT> <DIV><FONT face=3DVerdana size=3D2>Anyone can tell me which part that I = missed=20 regarding this issue?</FONT></DIV> <DIV><FONT face=3DVerdana size=3D2></FONT> </DIV> <DIV><FONT face=3DVerdana size=3D2>Thanks a lot!</FONT></DIV> <DIV><FONT face=3DVerdana size=3D2>Xu Jun</DIV></FONT> <DIV><FONT face=3DVerdana size=3D2></FONT> </DIV></BODY></HTML> ------=_NextPart_000_0084_01C42D75.E22278B0-- Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51505
  - 17
    - Capture unhandled exception How can I capture any unhandled exceptions that occur when the system is running? Thanks Rodger Higgins Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51500
  - 18
    - debugging web server with lmemdebug Hi, I'm trying to debug the Windows CE 4.2 web server in order to find potential memory leaks, using lmemdebug and httpdexe. Only problem is, there's no way of gracefully terminating httpdexe, so I can't get accurate results...Any suggestions? Emil. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51498
  - 19
    - Intel PSM on Assabet-like board Hi all I am using a custom board based on SA1110, which is very similar to Assabet. The PB Document says that Intel PSM is supported for Assabet board. As my board is very same as far as flash interface is concerned, I want to make use of Intel PSM for my board, but I am unable to do it. I was told earlier that I have to buy PSM from Intel. I am not fully convinced, as I could not get reason for that. Can you please help me out in this? If necessary, I can write the Flash MTD level driver for my flash chips (which is again 28F160). How should I proceed. Can I be able to make use of PSM? Can anyone point to me some source for any flash file system Regards Hari. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51497
  - 20
    - OID_802_11_SSID:Indicating success for SetInfo I have a driver for an 802.11 device that works on PocketPC2003 and I am trying to make it support windows 802.11 OIDs. Scanning works fine and Wireless properties panel displays all APs, and when I select one, OID_802_11_SSID comes to the driver correctly. I return NDIS_STATUS_PENDING, get the MAC to associate succesfully and in the assoc confirm indication I do NDisMSetInformationComplete, followed by NdisMIndicateStatus with NDIS_STATUS_MEDIA_CONNECT. OID_GEN_MEDIA_CONNECT_STATUS also returns connected state. But wireless properties does not show that I am connected to the AP. DHCP also does not happen. If I set a static IP ping pkts dont come to the driver. Why is this happening? Ndis goes on trying to associate with the other APs in the list, with the same result in each case. What else do I need to do to inform NDIS that the card is associated? I tried doing the connect indicate as soon as I get the set SSID request, to eliminate any timing problems, but there is no difference. I also tried to serially complete the association and return NDIS_STATUS_SUCCESS to set SSID request, with NDIS_STATUS_MEDIA_CONNECT being indicated from a different context within 2 secs - this also did not help. My driver ndis version is 4.0 - when I tried building as 5.1 the driver did not load. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51495
  - 21
    - L2TP/IPSec in Windows CE .NET 4.2 Does Windows CE .NET 4.2 support L2TP/IPSec server, or just client? Will the client (or server if it exists) work with other vendors implementations of L2TP/IPSec (ie sonicwall, cisco, etc)? Is there any good documentation covering how to actually use L2TP/IPSec in Windows CE .NET 4.2? Finally, how taxing is a single L2TP/IPSec connection (using good security)? Do you think it will be possible to maintain 64kbps, 128kbps, or 256kbps (or higher) of continuous data with a 66mhz CPU and no crypto hardware? If so, will it be able to do anything else at the same time? Thanks, George McCollister NovaTech LLC Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51492
  - 22
    - FAT in CE.NET 4.2 CE File system experts, CE.NET 4.2 with GEODE based Tiny platform. I added all the necessary storage and file system features and can access ATA devices as well as ATAPI devices. I have a CF card that I formatted in a digital camera. This card is viewable/accessible/readable/writable in every OS I have tried -- Win9x, NT, 2k, XP, various Linuxes, other digital cameras, printers with CF slots, etc. -- However in CE (through the PCMCIA slot and a PCMCIA->CF adapter), it is deemed invalid and the OS formats the CF as FAT32, destroying its content. I have modified ther registry to not auto format but when the OS boots, it won't mount the device. A comparison between the format from this camera and what I'll call a "standard" FAT shows the FAT created by the camera has the first 12 bytes as 00 00 00 00 00 00 00 00 FF FF FF FF while the "standard" format has FF F8 FF FF FF FF FF FF FF FF FF FF. If I use a hex editor to change the CF card to have the FF F8 FF FF FF FF FF FF instead of all zeros, CE accepts the card as valid and all is well. I have found nothing in my research (MS, www.ntfs.com, www.ata-atapi.com) to indicate that the camera formatted CF is incorrect. All the 0s mean is that those clusters are not used. This is further backed by all the other OSes that do recognize this FAT as valid. Why does CE not recognize this FAT as valid? Thanks, Nick. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51491
  - 23
    - Flash Memory Hang Hi Guys, When the registry is bothered frequently, the flash memory driver does not respond. After several dozens of iterations - each iteration has 2 reads and 1 write of registry, the terminal hangs. Is there any QFE about this? Here's a call stack of that situation. Cheers, Shane ================== call stack of services.exe ======================== NK!SC_WaitForMultiple(unsigned long 0x00000000, void * const * 0x00000001, int 0x00000041, unsigned long 0x00000001) line 4429 + 20 bytes NK!UB_WaitForMultiple(unsigned long 0x00000000, void * const * 0x00000001, int 0x00000041, unsigned long 0x00000001) line 4478 COREDLL!xxx_WaitForSingleObject(void * 0x00000000, unsigned long 0x00000001) line 107 + 56 bytes MSFMD!CP_StartCompactor(unsigned long 0x00000000, unsigned long 0x00000001, int 0x00000041) line 302 + 12 bytes MSFMD!SM_GetNextFreeSector(unsigned long * 0x00000000, int 0x00000001) line 377 MSFMD!InternalWriteToMedia(_SG_REQ * 0x00000000, int 0x00000001) line 978 + 12 bytes MSFMD!WriteToMedia(_SG_REQ * 0x00000000) line 1202 + 12 bytes MSFMD!DSK_IOControl(unsigned long 0x00000000, unsigned long 0x00000001, unsigned char * 0x00000041, unsigned long 0x00000001, unsigned char * 0x00000000, unsigned long 0x00000000, unsigned long * 0x0c11f354) line 533 + 8 bytes DEVICE!FS_DevDeviceIoControl(fsopendev_t * 0x00000000, unsigned long 0x00000001, void * 0x00000041, unsigned long 0x00000001, void * 0x00000000, unsigned long 0x0c11f354, unsigned long * 0x00034e30, _OVERLAPPED * 0x00000000) line 1252 + 44 bytes NK!SC_DeviceIoControl(void * 0x00000000, unsigned long 0x00000001, void * 0x00000041, unsigned long 0x00000001, void * 0x00000000, unsigned long 0x00000000, unsigned long * 0x0c11f52c, _OVERLAPPED * 0x00000000) line 3649 + 64 bytes COREDLL!xxx_DeviceIoControl(void * 0x00000000, unsigned long 0x00000001, void * 0x00000041, unsigned long 0x00000001, void * 0x00000000, unsigned long 0x00000000, unsigned long * 0x0c11f354, _OVERLAPPED * 0x00000000) line 27 + 92 bytes MSPART!WritePartition(unsigned long 0x00000000, unsigned char * 0x00000001, unsigned long 0x00000041, unsigned char * 0x00000001, unsigned long 0x00000000, unsigned long * 0x0c11f354) line 608 + 56 bytes MSPART!PD_DeviceIoControl(unsigned long 0x00000000, unsigned long 0x00000001, unsigned char * 0x00000041, unsigned long 0x00000001, unsigned char * 0x00000000, unsigned long 0x00000000, unsigned long * 0x0c11f354) line 658 FSDMGR!CPartDriver::DeviceIoControl(CPartDriver * const 0x00000000, unsigned long 0x00000001, unsigned long 0x00000041, void * 0x00000001, unsigned long 0x00000000, void * 0x00000000, unsigned long 0x0c11f354, unsigned long * 0x0000001c) line 245 + 48 bytes FSDMGR!PartitionIoControl(CPartition * 0x00000000, unsigned long 0x00000001, void * 0x00000041, unsigned long 0x00000001, void * 0x00000000, unsigned long 0x00000000, unsigned long * 0x0c11f354, _OVERLAPPED * 0x00000000) line 28 + 40 bytes FSDMGR!FSDMGR_DiskIoControl(_DSK * 0x00000000, unsigned long 0x00000001, void * 0x00000041, unsigned long 0x00000001, void * 0x00000000, unsigned long 0x00000000, unsigned long * 0x0c11f354, _OVERLAPPED * 0x00000000) line 586 + 60 bytes FATFSD!ReadWriteDisk2(_VOLUME * 0x00000000, void * 0x00000001, unsigned long 0x00000041, _DISK_INFO * 0x00000001, unsigned long 0x00000000, int 0x00064a80, void * 0x00065d90) line 450 + 48 bytes FATFSD!ReadWriteDisk(_VOLUME * 0x00000000, void * 0x00000001, unsigned long 0x00000041, _DISK_INFO * 0x00000001, unsigned long 0x000000e9, int 0x00000007, void * 0x460071f0, int 0x00000001) line 267 FATFSD!WriteVolume(_VOLUME * 0x00000000, unsigned long 0x00000001, int 0x00000041, void * 0x00000001) line 239 FATFSD!WriteStreamData(_DSTREAM * 0x00000000, unsigned long 0x00000001, const void * 0x00000041, unsigned long 0x00000001, unsigned long * 0x00000000, int 0x00000000) line 942 + 24 bytes FATFSD!FATFSWriteFile(_FHANDLE * 0x00000000, const void * 0x00000001, unsigned long 0x00000041, unsigned long * 0x00000001, _OVERLAPPED * 0x0c11f584, unsigned long * 0x00000001, unsigned long * 0x00063c40) line 496 + 20 bytes FATFSD!FAT_WriteFileWithSeek(_FHANDLE * 0x00000000, const void * 0x00000001, unsigned long 0x00000041, unsigned long * 0x00000001, _OVERLAPPED * 0x00000000, unsigned long 0x00015010, unsigned long 0x00000000) line 838 + 44 bytes FSDMGR!FSDMGR_WriteFileWithSeek(_HDL * 0x00000000, const void * 0x00000001, unsigned long 0x00000041, unsigned long * 0x00000001, _OVERLAPPED * 0x00015010, unsigned long 0x00000000, unsigned long 0x00000000) line 857 + 64 bytes NK!SC_WriteFileWithSeek(void * 0x00000000, const void * 0x00000001, unsigned long 0x00000041, unsigned long * 0x00000001, _OVERLAPPED * 0x8287ad60 VAcs, unsigned long 0x807786d0, unsigned long 0x00000000) line 3534 + 56 bytes NK!FlushMapBuffersLogged(FSMAP * 0x00000000, unsigned long 0x00000001, unsigned long 0x00000041, unsigned long 0x00000001) line 2434 + 44 bytes NK!SC_FlushViewOfFile(const void * 0x00000000, unsigned long 0x00000001) line 1021 + 32 bytes COREDLL!xxx_FlushViewOfFile(const void * 0x00000000, unsigned long 0x00000001) line 515 + 52 bytes FILESYS!FSVolFlush(_CEGUID * 0x00000000, SharedVolInfo_t * 0x00000001, long * 0x00000041) line 153 FILESYS!RegFlushHive(heap_t * 0x00000000) line 170 + 20 bytes FILESYS!prgRegFlushKey(HKEY__ * 0x00000000) line 1279 + 24 bytes COREDLL!xxx_RegFlushKey(HKEY__ * 0x00000000) line 28 ACME!RegWrapper::CloseRegKey() line 601 ACME!RegWrapper::~RegWrapper() line 68 ACME!WindowProc(HWND__ * 0x000000f6, unsigned int 0x00000000, unsigned int 0x00000000, long 0x00000000) line 1120 + 20 bytes COREDLL!xxx_PerformCallBack4(_CALLBACKINFO * 0x00000000, void * 0x00000001) line 32 GWES!WindowProcCallback(void * 0x00000000, long (HWND__ *, unsigned int, unsigned int, long)* 0x00000001, CWindow * 0x00000041, unsigned int 0x00000001, unsigned int 0x806c1002, long 0x02738ffc, unsigned char * 0x000f33d0) line 2329 + 24 bytes GWES!CWindow::CallWindowProcWInternal(CePtr_t<long (__cdecl*)(HWND__ *,unsigned int,unsigned int,long)> {...}, HWND__ * 0x00000000, unsigned int 0x00000001, unsigned int 0x00000041, long 0x00000001, SendMsgEntry_t * 0x0c11fc00) line 2501 + 40 bytes GWES!MsgQueue::DispatchReceivedMsg(MsgQueue * const 0x00000000) line 2751 + 28 bytes GWES!MsgQueue::GetEvent(MsgQueue * const 0x00000000, MsgqGetEventFlag mgefNull, HWND__ * 0x00000041, unsigned int 0x00000001, unsigned int 0x03f8c9a0, tagMSG * 0x0a0ef518) line 2966 GWES!MsgQueue::PeekMessageW_I(tagMSG * 0x00000000, HWND__ * 0x00000001, unsigned int 0x00000041, unsigned int 0x00000001, unsigned int 0x00000001) line 4928 COREDLL!xxx_PeekMessageW(tagMSG * 0x00000000, HWND__ * 0x00000001, unsigned int 0x00000041, unsigned int 0x00000001, unsigned int 0x00000001) line 2786 + 68 bytes ACME!ThreadMessagePump(void * 0x0c02f3ec) line 398 + 28 bytes COREDLL!ThreadBaseFunc(void * 0x00000000, unsigned long 0x00000001) line 419 Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51490
  - 24
    - Ethernet driver problems Hello, I am currently booting CE .NET 5.0 off the hard drive in a Pentium4 machine. I compiled my own NK.bin using the platform builder and added the RTL8139 Ethernet driver to my build but when I boot up, the ethernet card simply does not show up When I boot through Ethernet however, it works just fine (using the VMini) Is there some small (or large) step I've overlooked Thanks in advance Cris. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51488
  - 25
    - FATFS bogus Directory This is a multi-part message in MIME format. ------=_NextPart_000_0078_01C42D55.E0612730 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, We are using WinCE 4.2 and having problems with the flash file system. = We use stratad.dll, mspart.dll to get a FATFS file system running. It = still runs but sometimes we got a bogus directory after startup. We = still work on, but if I try to save a dataset the CreateFile function = does not give a invalid handle. So the dataset is not saved on disk but = Create file returned with a valid handle. (see example below) Also we use ScanVolumeEx and DefragVolumeEx functions from Fatutil.dll = to check our file system. Those function tells no problem. But we still = have. Also is the return value from DefragVolumeEx (DEFRAG_RESULTS = including only SCAN_RESULTS)not actual. The values from dr.sr are the = same as from a scan before doing defrag. So what could I do with that = result? Is there any example code how to use the FATUTIL functions?=20 Before we power off the system we dismount all flash partitions and = dismount the flash volume.=20 Then we do a hard power off, because we start our system always new(no = changing registry) Now my questions: What went wrong that I get bogus directories?=20 How could I detect the bogus directory problem and how could I repair my = files? Why could ScanVolume not detect the bogus directories? What happens if power fall down without dismounting all the Flash stuff = and what could I do to prevent that? Must I use the TFAT format, and when yes could I use the "old" formatted = Volume without data lost? Is it enough to dismount all flash stuff or must I do more than this? A lot of question with the hope for a helpful answer Johannes Heusel Thanks!! Debug trace: 906317 PID:edbb6efe TID:edbb62c2 0x8dbb7000: +SetMeasData (tsDATA_PARAM) = 906320 PID:cdfe35a2 TID:edbb62c2 0x8dbb7000: FATFS!FindNext: bogus = directory!=20 906320 PID:cdfe35a2 TID:edbb62c2 0x8dbb7000: = FATFS!FAT_GetFileAttributesW(\000\040422142439-01.dat) returned = 0xffffffff (13)=20 906321 PID:cdfe35a2 TID:edbb62c2 0x8dbb7000: FATFS!FindNext: bogus = directory!=20 906356 PID:edbb6efe TID:edbb62c2 0x8dbb7000: -SetMeasData:eNO_ERR Source code example: // create a new file. hFile =3D CreateFile(strFilePath, GENERIC_WRITE, 0,NULL, CREATE_NEW, = FILE_ATTRIBUTE_NORMAL, NULL);=20 if (hFile =3D=3D INVALID_HANDLE_VALUE) { =20 nErr =3D GetLastError(); if (nErr !=3D ERROR_FILE_EXISTS) { RETAILMSG(DEBUG_MEAS_API, (_T("-SetMeasData:eERR_ACCESS = %d=3DGetLastError()\n"),nErr)); return eERR_ACCESS; } } //...rest of code ------=_NextPart_000_0078_01C42D55.E0612730 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.1400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV> <DIV><FONT face=3DArial size=3D2>We are using WinCE 4.2 and having = problems with the=20 flash file system. We use stratad.dll, mspart.dll to get a FATFS file = system=20 running. It still runs but sometimes we got a bogus directory after = startup. We=20 still work on, but if I try to save a dataset the CreateFile function = does not=20 give a invalid handle. So the dataset is not saved on disk but Create = file=20 returned with a valid handle. (see example below)</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Also we use ScanVolumeEx and = DefragVolumeEx=20 functions from Fatutil.dll to check our file system. Those function = tells no=20 problem. But we still have. Also is the return value from DefragVolumeEx = (DEFRAG_RESULTS including only SCAN_RESULTS)not actual. The values from = dr.sr=20 are the same as from a scan before doing defrag. So what could I do with = that=20 result? Is there any example code how to use the FATUTIL functions?=20 </FONT></DIV> <DIV><FONT face=3DArial size=3D2>Before we power off the system we = dismount all=20 flash partitions and dismount the flash volume. </FONT></DIV> <DIV><FONT face=3DArial size=3D2>Then we do a hard power off, because we = start our=20 system always new(no changing registry)</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Now my questions:</FONT></DIV> <DIV><FONT face=3DArial size=3D2>What went wrong that I get bogus = directories?=20 </FONT></DIV> <DIV><FONT face=3DArial size=3D2>How could I detect the bogus directory = problem and=20 how could I repair my files?</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Why could ScanVolume not detect the = bogus=20 directories?</FONT></DIV> <DIV><FONT face=3DArial size=3D2>What happens if power fall down without = dismounting=20 all the Flash stuff and what could I do to prevent that?</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Must I use the TFAT format, and when = yes could I=20 use the "old" formatted Volume without data lost?</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Is it enough to dismount all flash = stuff or must I=20 do more than this?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>A lot of question with the hope for a = helpful=20 answer</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Johannes Heusel</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Thanks!!</FONT></DIV> <DIV><FONT face=3DArial><FONT size=3D2><FONT face=3DArial=20 size=3D2></FONT></FONT></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Debug trace:</FONT></DIV> <DIV><FONT face=3DArial><FONT size=3D2><FONT face=3DArial=20 size=3D2></FONT></FONT></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>906317 PID:edbb6efe TID:edbb62c2 = 0x8dbb7000:=20 +SetMeasData (tsDATA_PARAM) </FONT></DIV> <DIV><FONT face=3DArial size=3D2>906320 PID:cdfe35a2 TID:edbb62c2 = 0x8dbb7000:=20 FATFS!FindNext: bogus directory! </FONT></DIV> <DIV><FONT face=3DArial size=3D2>906320 PID:cdfe35a2 TID:edbb62c2 = 0x8dbb7000:=20 FATFS!FAT_GetFileAttributesW(\000\040422142439-01.dat) returned = 0xffffffff (13)=20 </FONT></DIV> <DIV><FONT face=3DArial size=3D2>906321 PID:cdfe35a2 TID:edbb62c2 = 0x8dbb7000:=20 FATFS!FindNext: bogus directory! </FONT></DIV> <DIV><FONT face=3DArial size=3D2>906356 PID:edbb6efe TID:edbb62c2 = 0x8dbb7000:=20 -SetMeasData:eNO_ERR</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Source code example:</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>  // create a new = file.</FONT></DIV> <DIV><FONT face=3DArial size=3D2>  hFile =3D = CreateFile(strFilePath,</FONT><FONT=20 face=3DArial size=3D2>  GENERIC_WRITE, </FONT><FONT face=3DArial=20 size=3D2>0,</FONT><FONT face=3DArial size=3D2>NULL, </FONT><FONT = face=3DArial=20 size=3D2>CREATE_NEW, </FONT><FONT face=3DArial = size=3D2>FILE_ATTRIBUTE_NORMAL,=20 </FONT><FONT face=3DArial size=3D2>NULL); </FONT></DIV> <DIV><FONT face=3DArial><FONT size=3D2><FONT face=3DArial=20 size=3D2></FONT></FONT></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>  if (hFile =3D=3D=20 INVALID_HANDLE_VALUE)</FONT></DIV> <DIV><FONT face=3DArial size=3D2>  {  </FONT></DIV> <DIV><FONT face=3DArial size=3D2>    nErr =3D=20 GetLastError();</FONT></DIV> <DIV><FONT face=3DArial size=3D2>    if (nErr !=3D=20 ERROR_FILE_EXISTS)</FONT></DIV> <DIV><FONT face=3DArial size=3D2>    {</FONT></DIV> <DIV><FONT face=3DArial size=3D2>     =20 RETAILMSG(DEBUG_MEAS_API, (_T("-SetMeasData:eERR_ACCESS=20 %d=3DGetLastError()\n"),nErr));</FONT></DIV> <DIV><FONT face=3DArial size=3D2>      return=20 eERR_ACCESS;</FONT></DIV> <DIV><FONT face=3DArial size=3D2>    }</FONT></DIV> <DIV><FONT face=3DArial size=3D2>  }</FONT></DIV> <DIV><FONT face=3DArial><FONT size=3D2><FONT face=3DArial = size=3D2>//...rest of=20 code</FONT></FONT></FONT></DIV></BODY></HTML> ------=_NextPart_000_0078_01C42D55.E0612730-- Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51487
- Next
  - 1
    - Misaligned accesses with MS ARM compiler Does anyone know of a way to tell the ARM compiler that a WORD or DWORD pointer addresses an object that is not (or might not be) aligned on a 16 or 32 bit boundary? Effectively what I want to do is this: BYTE *pBuffer = malloc(something); WORD *pWord = (WORD *) &pBuffer[arbitrary_offset]; DWORD *pDWord = (DWORD *) &pBuffer[another_arbitrary_offset]; *pWord = word_value; /* May be misaligned */ *pDWord = dword_value; /* May be misaligned */ I have tried various versions of #pragma pack() without success. I could, of course, use WORD and DWORD temporaries and memcpy() into the array but that is messy. There are other, equally messy, workarounds involving byte manipulation. The problem arises because I am porting a large amount of code that was written for the ARM ADS compiler, which has such a facility. Thanks, --Alan Gillespie. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51481
  - 2
    - Newbie question Where can I download platform builder. On the microsoft site the link is out of date. Thanks. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnce30/html/cefinditfast.asp Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51477
  - 3
    - DDI flat driver and power managment/Bios routines call I'm tring to implement power managment capabilities on vga flat driver. My board is an x86 based board and my kernel is based on CEPC. My goal is to switch off and on the monitor on application request. I've decided to implement the power managment code in GPEFlat::DrvEscape in order to give applications the ability to send power management commands to the driver. I've also decided to use Vesa VBE/PM extensions to set/get power states. My question is: How can I call from WinCE (Protected Mode) the VESA VBE bios functions? In order to set power states I've to invoke INT 10h function 4F10h(AX)/01h(BL). But I cant call INT instruction directly from proteced mode. So my final question is, How can I call bios routines from WindowsCE? Thanks Claudio Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51465
  - 4
    - Fonts and desktop shortcuts Hi! How can I add fonts to my platform? I would like to create a shortcut to my application in the desktop too. Thanks Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51461
  - 5
    - PB 4.2 Where to get error codes for GetAdaptersInfo() Good morning experts, we have been successfully using in our CE 4.1 images the function GetAdaptersInfo() as described in header file iphlpapi.h. However, in PB 4.2 it dosn't work under the same conditions (part of the code is transferred from CE 4.1 into CE 4.2 as an evaluation step for potential future migration). I have tried to find detailed information on this function return values and there is nothing except ........ Return Values If the function succeeds, the return value is NO_ERROR. If the function fails, an error code is returned. .............. Where one can obtain error codes and their meanings for this function when used in PB 4.2 ? On one of our devices it returns error code 232 under PB 4.2 and works fine under PB 4.1. Any help on this GetAdaptersInfo() function return vlues is appreciated. Sincerely Sergei Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51460
  - 6
    - display driver quiery hello all We have developed our own configuration related Display driver for Window-CE. But after including our Display Driver with the ARM BSP we are able to made the NK.nb0(kernel image) but unable to port on to the board. The booting of kernel is getting aborted in between due to missing GWES.exe . I know the error is due to gwes.exe.but i am unable to include the gwes.exe in kernel image.Initially without including our Display Driver we are getting kernel image and it was perfectly getting loaded on to the board but after including our display driver using New Project tab in platform builder and modifing Platform.bib file(replaced video.dll with our own driver dll and making another entry for dll location) please suggest me how to include GWES.exe in the kernel image. Thanks & Regards George Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51457
  - 7
    - How to view debug information? In retail or debug , RETAILMSG(1,(TEXT("PDD_AudioInitialize1\r\n"))); DEBUGMSG(1,(TEXT("PDD_AudioInitialize2\r\n"))); there isnt debug messages occuring. I have no idea about it!If I need to do something? Thanks! Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51453
  - 8
    - Problem with Property Sheet Hi all Running an evc application that creates a propertysheet with 2 propertypages, I get this debug output in PB4.2: 1674978 0x8db69400: Menus in dialogs are not supported! 1676651 0x8db69400: ERROR: d:\mckendric\private\winceos\coreos\gwe\winmgr\wmbase\wmbase.cpp line 581: 1676651 0x8db69400: CreateWindow failed: Could not find class=K6ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ 1676653 0x8db69400: ERROR: d:\mckendric\private\winceos\coreos\gwe\dlgmgr\main\cmncore\loaddlg.cpp line 511: 1676653 0x8db69400: CreateDialog() failed: couldn't create dialog 1676693 0x8db69400: Menus in dialogs are not supported! 1678357 0x8db69400: ERROR: d:\mckendric\private\winceos\coreos\gwe\winmgr\wmbase\wmbase.cpp line 581: 1678358 0x8db69400: CreateWindow failed: Could not find class=K6ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ 1678359 0x8db69400: ERROR: d:\mckendric\private\winceos\coreos\gwe\dlgmgr\main\cmncore\loaddlg.cpp line 511: 1678360 0x8db69400: CreateDialog() failed: couldn't create dialog What does that mean? TIA -- Michael Reim reim AT helmut-fischer DOT de Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51451
  - 9
    - Question about IMGNODEBUGGER hello, If I change the "Kernel Debugger" setting from the project in platform builder, is that equivalent with changing IMGNODEBUGGER from a build window? What exactly does IMGNODEBUGGER affect? What I would like to know is what I need to rebuild. If I change IMGNODEBUGGER, do I need a rebuild all, or is makeimg enough? Loren. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51448
  - 10
    - how to use microsoft bluetooth sample Hi all i want to build a bluetooth application which can receive/send data (string or character) via bluetooth And I got Windows CE .NET 4.2 platform builder SDK, which has some sample codes in it They are located in %_WINCEROOT%\Public\Common\Oak\Drivers\Bluetooth\Sample But I dont know exactly how to use "build" command to build them Is there anyone tell me how to do it? I will be highly appreciated! Wilson Wang Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51444
  - 11
    - Cant see Persistent Memory Manager Directory The Persistent Memory Manager is loaded but I do not see the directory in explorer OS : winCE 4. PXA25 Process Viewer filesys.exe is running with modules : psmfsd.dll, fsdmgr.dll, relfsd.dll, coredll.dl Do not see any errors when winCE loads winCE runs directly from Flas Flash = Intel RC28F256K 64megs SDRA Registry entries are per the Intel doc and are verified through the remote registry reader [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\PSM "Dll"="PSMFSD.dll "Paging"=dword: [HKEY_LOCAL_MACHINE\System\StorageManager "Dll"="fsdmgr.dll ;To change the PSM folder name from the default of IPSM, you must add the following additional Registry Entry ;'flashDrv is the new name of the PSM folder [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\FlshDrv "FolderName"="flashDrv" Has anyone else encountered this problem Thanks in advance for any hel Bob S. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51442
  - 12
    - Accelent USB drivers; modify and compile for iPaq 4155 I'm part of a senior design team at Drexel University and we are wanting to communicate to the iPaq 4155 over USB using a Cypress CY7C67300 microcontroller. The microcontroller is an embedded USB host Cypress provides the source code to the driver for Windows CE.Net - but the source needs to be modified slightly to be used on the iPaq since the driver is designed for the Accelent USB development platform. Also, I do not have access to Platform Builder 4.2 URL to the source code http://www.cypress.com/cfuploads/support/reference_design/OTG-Host_WinCE_Host_driver_v1_0.zi Cypress has included a lot of documentation to modifying the source code to suit a given device. If I manage to correctly modify the source, would it be possible for a kind soul to compile it for me so that I can use it with eVC++ 4.0 SP Maybe someone already has done that and could share it I only have 2 weeks to go until the presentation for the design... so I'm getting nervous about completing it.. thankyou for any help. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51430
  - 13
    - 4.2: IR Printing? We're trying to print through the IrDA port, but we haven't even been able to get the transmit line on the IR port to activate at all. IrDA shows up as a printer port, but when we try to print from WordPad or IE, we get a "printer not attached or available" type error, and sometimes WordPad crashes. We have an Advantech PCM5820 board with Geode (x86) processor. Under platform builder 4.2 I have the following in my project: Under GEODEPAD features\Enterprise Web Pad (Display-based devices) I have: Applications and Services Development: Object Exchange Protocol (OBEX) (I think this relates to IR beaming?) Communication Services and Networking: Networking - Personal Area Network (PAN): IrDA Under GEODEPAD features\Device Drivers I have: Networking\Personal Area Networking (PAN) devices: Serial Infrared (SIR) Devices Printer Devices: Printing Port Library (irprint.c, prnport.c, prnerr.c) PCL Printer Driver (I've had this in and out to no effect) We've checked our BIOS, and enabled the IR port. The other BIOS settings are address=2E8H, mode=IrDA, Transmittion (sic) delay=Enabled, IRQ=IRQ11. I don't see any other IR related components in the Catalog to add. What am I missing? Michael Schwab Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51429
  - 14
    - Wince.net 4.2 USB Hi I am faced with a rather odd problem, I have a .exe file (driver for GSM card) I manage to connect to our hardware via USB, run the .exe on the PC and it starts to install the driver onto our hardware, it get through the process but I find that some of the files (those that go into \windows directory are present) but part of the installation is that it creates some sub directories in the Program Files directory and I find that these directories haven't been created and the files are not there. Now heres the interesting bit, I create another project (exactly same environment variables), only this time I tick the include Inbox component and again try to install the driver and this time the directories are created and all the files (.exe, dlls) are in place. This is all repeatable. Another thing is that when it installs correctly the process takes about 20 seconds, when it doesn't install correctly it takes a couple of minutes, very strange. I also find that with the image that doesn't let me installl the driver correctly also (70% of the time) falls over when trying to copy large files across (9 MB ish) I would have suspected the .exe running on the PC but this doesn't happen on our wince300 platform, I can run other .exe on the PC and they seem to install correctly, its such a horrible bug, I have also tried builds witout QFEs and with QFEs but alas get the same result. Any ideas would be very much appreciateed, I'm at the end of my teather with this one (well almost). Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51423
  - 15
    - Emulator Support for an SDK Hi All I want to create an SDK for my CE.NET4.2 image with emulator support. During the configuration of an SDK, when i click on emulation tab i see NONE in emulation image field. Can some body tell me why Thanks in Advanc Ashish Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51414
  - 16
    - WinCe420 hangs at boot in filesys Hi I'm downloading WinCE420 the first time on a new Hardware with the PXA255 CPU This Hardware is similar than the Sandgate Board We have 64MByte SDRAM and 64MByte Strata Flash The Strata Flash is a synchrounous one but at powerup its asynch, s for the moment we leave it asynch I've set also "set BSP_NOPM=1" Now during the download phase its hangs in the filesys Depending the debug zones, its seems not to hang a the exactl same position What happens, or what may cause this behave --> Debug output without [HCU\Pegasus\Zones\FilesSys] set 4294767342 PID:3cb7002 TID:3cb7262 0x83cb7024: >>> Loading module coredll.dll at address 0x03F20000-0x03FFA000 (RW data at 0x01FFF000-0x01FFFC50 4294767371 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: >>> Loading module filesys.exe at address 0x04010000-0x0409000 4294767384 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FileSystem Starting - starting with clean file syste 4294767393 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Opening existing volum 4294767395 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Volume heap already initialize 4294767396 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Initializing volume hea 4294767430 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Opening existing volum 4294767432 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Volume heap already initialize 4294767433 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSREG: Mounting clean system hiv 4294767435 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Creating new volum --> Debug output with [HCU\Pegasus\Zones\FilesSys=dword:20] set 4294767306 PID:3cb7002 TID:3cb7262 0x83cb7024: first = 01f30000, last = 02000000, SharedDllBase = 02e5000 4294767342 PID:3cb7002 TID:3cb7262 0x83cb7024: >>> Loading module coredll.dll at address 0x03F20000-0x03FFA000 (RW data at 0x01FFF000-0x01FFFC50 4294767371 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: >>> Loading module filesys.exe at address 0x04010000-0x0409000 4294767384 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FileSystem Starting - starting with clean file syste 4294767393 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Opening existing volum 4294767395 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Volume heap already initialize 4294767396 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSREG: Mounted ROM portion of boot registr 4294767396 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Creating clean virtual volum 4294767397 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSVOL: Initializing volume hea 4294767417 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FSREG: Mounted RAM portion of boot registr 4294767425 PID:c3c9e23e TID:c3ca3fb6 0x83c9e000: FS: Creating signal event SYSTEM/PowerManagerRead Many thanks in advanc George Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51412
  - 17
    - How to build an image that works with VS.2003 Hi All, Can anyone please tell me how can I build an OS image in platform builder that will work with Visual Studio 2003? So I can debug from Visual Studio? Thanks, Praveen Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51411
  - 18
    - Help with pOEMCalcFSPages Thanks in advance for any help implementing this callback. Platform is a proprietary x86 board, with a cloned CEPC BSP. I have copied the OAL from the common code into the platform, and as per "Cloaning the Microsoft Public Common Code" I seem to be successfully generating $(_TARGETPLATROOT)\lib\$(_CPUINDPATH)\i486oal.lib, and have updated the three KERN varieties in KERNEL\BUILDEXE to reflect this. I would like to dynamically pre-set the object store percentage before the OS has booted. I have verified that I can successfully do this statically by manually setting FSRAMPERCENT in the config.bib for the platform. However, no matter what I return from my implementation of pOEMCalcFSPages, the memory slider applet stays firmly at 50%, reflecting the default value. 1.) Is <MyBSP>/KERNEL/OAL/cfwpc.c a correct place to implement this callback function (of course, you can implement it wherever you want as long as you are linked correctly, so a better question is "is this the "best" place)? 2.) Is the updated OAL being built into my image? From the PB IDE, my proceedure is: A.) Open the build release directory and move to %_TARGETPLATROOT% B.) build -cf to rebuild the BSP. C.) sysgen i486oal. D.) back in PB IDE, choose "build" platform (not rebuild platform, and not enable deptree build). Thank you again, - Paul Cameron P.S. My impl' of pOEMCalcFSPages in cfwpc.c (of course, replace "return dwDefaultFSPages;" with return anything): typedef DWORD (*OEMCalcFSPagesPtr)(DWORD dwMemPages, DWORD dwDefaultFSPages); DWORD OEMCalcFSPages( DWORD dwMemPages, DWORD dwDefaultFSPages); extern OEMCalcFSPagesPtr pOEMCalcFSPagesPtr=&OEMCalcFSPages; DWORD OEMCalcFSPages(DWORD dwMemPages, DWORD dwDefaultFSPages) { return dwDefaultFSPages; } Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51410
  - 19
    - Problem with isochronous USB transfer Hi all, We are trying to develop a driver for a USB camera under Windows CE 4.2 (our board is based on a PXA255 and we have it running at 400 MHz.) The camera send the data using isochronous transfers and we are having serious problems to make it work. Let's see: to do the driver, we have make use of the ideas contained in http://support.microsoft.com/default.aspx?scid=kb;en-us;317434. The parameters we are using with IssueIsochTransfer are USB_NO_WAIT | USB_IN_TRANSFER | USB_SHORT_TRANSFER_OK | USB_START_ISOCH_ASAP. The size of the USB frames is 384, every transfer is composed of 6 frames. We know, based in what happens in a PC, that the camera returns, before sending the info corresponding to a picture, some USB frames with length 16; however, when in the CALLBACK function we try to see the bytes transferred using GetIsochResults, all the results are divided in two sets: frames with error code = 0 and with size = 384, and frames with error code = 14 (USB_NOT_ACCESSED_ERROR) and size = 0 (most of the frames fall in this second category). By what i know, USB frames are time-driven, so i suppose that the USB driver cannot take those 16 bytes-length chunks and add them to form a 384 frame... or am i wrong? Even the frames with error code = 14 seems to have some data on it, but i cannot know if it's valid data or only trash without knowing what is the length of the returned data... There is another way to know this? There are alternatives to use GetIsochResults or maybe i'm doing something wrong? Somebody understands what is happening here? I would apprecciate whatever help you could give me. Thanks in advance. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51408
  - 20
    - DiskOnChip as Persistent Storage Media Hi everybody, I'm using Windows CE .NET 4.2 and I'd like to use M-Systems DiskOnChip 2000 as persistent storage media. I added the TrueFFS driver from third party device drivers to my platform. I also added FAT File System feature to my platform. I put the following registry settings in my platform.reg file: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS] "Dll" = "TrueFFS.dll" "Prefix" = "DSK" "Order" = dword:1 "Ioctl" = dword:4 "FSD" = "FATFS.DLL" "WindowBase" = dword:E000 "DocBase" = dword:C8000 "DeviceArrayIndex"=dword:0 "DocAccessType" = dword:10 "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC] "Name"="DiskOnChip M-Systems" "Folder"="DiskOnChip" I did a clean build and checked the ce.bib file in my releasedir to see that trueFFS.dll entry exists. However I can't see diskonchip folder on my device or on the storage manager list when I load my image to target (via ethernet download). I changed WindowBase address as DC000, C8000, D0000, E000 and the result was the same. I used Dinfo.exe to get the following information: DiskOnChip 2000(R) found at E000:0000 ---------------------------------------------- Disk statistics: Drive letter : C Disk size : 64,144 Kbytes Software version : 1.23 TrueFFS Compatibility : 3.3.02 Firmware size : 48 Kbytes Actually, I don't know how to determine WindowBase and DocBase address value. Dinfo output doesn't give me any clues. I will appreciate if someone can tell me what the problem might be or what my fault is. Thanks already, Selin Metin Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51402
  - 21
    - Add a driver to Wince .net 4.2 Hi, there I get a set of files which are the SIS630 drivers for Wince. Files: sis7018.dll, sis900.dll, ddi_sis.dll, siside.dll, registry.txt and config.bib. Now what are the steps to add them to my CEPC(x86) BSP? Best regards, David Liu Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51401
  - 22
    - Getting INCBIN to work in windows CE 4.1 Hi, I am using windows CE 4.1, and I am building for an ARMV4I processor. I wish to use ARMASM's INCBIN directive. (The INCBIN directive of armasm includes a file into an assembler file. The file is included as it is, without being assembled). When I include a file using the above directive, the assembler works. However the linking stage fails and I get an error "invalid or corrupt file". What should I do to get it working? Is there anyway I can include a file without any interpretation? Thank you, Mariam. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51400
  - 23
    - Memory Mapping in PCI Driver Development question. Hi to all, I'm developing my own PCI driver for a custom made I/O card and I've got some easy questions about memory mapping, I'm used to work with microcontroller based platforms, and I'm a little bit lost in WCE memory mapping. I hope you can help me. First: There is any difference between using HalTranslateBusAddress + MmMapIoSpace or directly use TransBusAddrToVirtual ?? What is the better solution? In PB Helps says that you can use either but I don't know why in examples usually appears the first solution. Second: TransBusAddrToStatic is used typically to let the ISR manipulate hardware, Can I use it in a process instead of TransBusAddrToVirtual? Thanks in advance. Juan. Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51392
  - 24
    - how to add ROM image size? Hi: My board has 64MB Flash,but i only used 32MB,I want used 64MB,what's i do? My systerm information: OEMAddressTable ;;;------------------------------------------------------------- ;;; Virtual(cached) Phys Addr MB ;;;------------------------------------------------------------- ..... DCD 0x98300000, 0x00000000, 32 ; ..... config.bib MEMORY NK 800B8000 02000000 RAMIMAGE ; RAM 820B8000 01C00000 RAM ; EDBG 83F8D000 00020000 RESERVED AUD_DMA 83CB8000 0000A000 RESERVED SLEEP_SAV 83CC2000 00001000 RESERVED DRV_GLB 83CC3000 00001000 RESERVED CACHE_FLG 83CC4000 0003C000 RESERVED ; DISPLAY 83D00000 00130000 RESERVED ; UNUSED_BUF 83E30000 0015D000 RESERVED ZBANK 86000000 00100000 RESERVED CONFIG ...... ROMSTART=800B8000 ROMWIDTH=32 ROMSIZE=01E00000 ....... Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51388
  - 25
    - how to make winCE.net 4.2 support 240*320 LCD hi,everyon I have seen the source codes of wince.net 4.2 and find that the LCDs it suports are all 320*240(LQ039Q2DS54),not 240*320 LCD(LQ035Q7DB02). My target device's LCD is LQ035Q7DB02 and controlling chip is LZ9FC22. Does anybody know what should I modify Thanks Fred Tag: Dose the WInce 4.2 support the AGP display driver? Tag: 51387

Top