The difference of startup.s

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - CeGetVolumeInfo() prototype incorrect in storemgr.h I think I have all the latest CE 5.0 updates installed, but I seem to be having the same issue reported earlier in this thread back in February 2005: http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/2637189935d939c9/705cac02b72948bb?lnk=st&q=cegetvolumeinfo&rnum=1&hl=en#705cac02b72948bb The header defines a "wide" version of CeGetVolumeInfoW(), but coredll.lib only has CeGetVolumeInfo(). Also, as mentioned in the thread, the API seems to require an extern "C" to compile. Is there a CE 5.0 update with an official "fixed" storemgr.h? Or is there some other way to work around the issue? Thanks! David Holcomb Tag: The difference of startup.s Tag: 78836
  - 2
    - USB Keyboard Notification Dear Greats, We are writting one application that should detect the presence of USB keyboard and change its GUI accordingly. My application is an MFC Dialog based application. OS is Windows CE 5.0 with USBHID support. I tried to capture the WM_DEVICECHANGE notification message from my application. If I connect / remove this message is not received by my application. I saw some Notification registration for USB device attach/detach. Will this work for the keyboard as well. My other idea is, we can broadcast a attach message in the USB driver Init and broadcast a detach message in the USB driver DeInit. Greats, kindly advice me on what approach can I proceed. avkumar Tag: The difference of startup.s Tag: 78834
  - 3
    - RTC problem? Time change not regular. Hi all. On my device( wince4.2 ) there is RTC. The OEMGetRealTime(), OEMSetRealTime(),OEMSetAlarmTime() have been implemented using the RTC hardware. The problem is, on the control panel's date/time property. I observe the second time beat is not regular. What 's function this panel's date/time call? How do it to change the time? It is relate to the CurMSec. Because I wonder there some problem in the system timer setting. thanks in advance. Tag: The difference of startup.s Tag: 78833
  - 4
    - Why nobody answer my question about exception 004 MIPS platform? Is it because I did not provide enough information or someghing else? Please give some suggestion. Thanks you very much. Tag: The difference of startup.s Tag: 78830
  - 5
    - system timer, dwReschedTime problem? I have some question on the system timer. 1.The global scheduling variables, dwReschedTime in PB4.2. Is the kenel set the dwReschedTime value and keep it change by the thread scheduling algorithm ? For I cannot find in serval impelement OAL sample ? 2. The system timer's interupt period time, If in the OAL it is not set by one milisecond and other value such as 10 ms, what's the effect? Tag: The difference of startup.s Tag: 78829
  - 6
    - CE 4.2 build fails after installing QFE updates I'm having problems building an image after installing the 4.2 QFE updates. This happens on both the evaluation and the full version which I recently purchased. If no updates are installed, the image builds fine. This is the output in build.txt: C:\WINCE420\PUBLIC\Samsung\WINCE420\smdk2410\cesysgen\sdk\lib\ARMV4\retail\coredll.lib C:\WINCE420\public\common\sdk\lib\ARMV4\retail\corelibc.lib C:\WINCE420\public\common\sdk\lib\ARMV4\retail\corelibc.lib C:\WINCE420\PUBLIC\Samsung\WINCE420\smdk2410\cesysgen\oak\lib\ARMV4\retail\fsdmgr.exp fsdmgr_ALL.lib(fsdserv.obj) : error LNK2001: unresolved external symbol dlVOLList fsdmgr_ALL.lib(fsdapis.obj) : error LNK2001: unresolved external symbol dlVOLList C:\WINCE420\PUBLIC\Samsung\WINCE420\smdk2410\cesysgen\oak\target\ARMV4\retail\fsdmgr.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'link' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\WINCE420\sdk\bin\i386\nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\WINCE420\sdk\bin\i386\nmake.exe' : return code '0x2' The host pc OS is XP Pro with service pack 2. The processor is an Intel Pentium D. Any ideas what could cause this problem? I'm going to try installing on my old PC to see if I still have this problem. Any help would be appreciated. Thanks, Tony Tag: The difference of startup.s Tag: 78826
  - 7
    - Output file name / location? I'm trying to figure out how PB projects choose where the output files go and are named. For example if I create my own project named TEST it outputs as TEST.exe. Fine... but I'm using the Emulator and it uses ddi.dll as its display driver. The source code for that (from what I understand) comes from the vgaflat project located in PLATFORM/EMULATOR/src/drivers/display. How does the vgaflat project goes from that to outputting ddi.dll? Where are the bib files for vgaflat? Also... what are the differences between the projects under PLATFORM and public/common...? It seems like there is duplicate projects? Thanks! Tag: The difference of startup.s Tag: 78822
  - 8
    - Newbie getting networking going Hi. I've got an x86 (i.e an old pc) booting into CE 5.0 with an os image that I boot from the hard-drive. All seems good. However I can't get any networking going. I've tried putting in a range of different ne2000 pci network cards but the card does not show up, in the list of adapters in the control panel. Im sure its something obvious, but would apreciate if anyone has any advice on how to get networking up and running. Thanks RIchard Tag: The difference of startup.s Tag: 78819
  - 9
    - Sysgen errors (Fiber API ?) I did have a perfectly working PB platform to which I added various things from the Catalog, now when I Sysgen it I get errors (see below a snippet from build.log). It seems to be requiring the Fibre API which I also added from the catalog. What am I missing? 0 Please add _COMMONPUBROOT and __PROJROOT to your tree's cesysgen\sources file. Directory: C:\WINCE500\PUBLIC\COMMON\CESYSGEN TARGETNAME: coredll_ALL makefile.def: Including C:\WINCE500\public\common\oak\misc\sources.ReleaseType_OAK 'C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\lib\ARMV4I\debug\coredll_ALL.lib' is up-to-date cefilter C:\WINCE500\public\common\oak\lib\ARMV4I\debug\coredll.def C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\lib\ARMV4I\debug Cefilter for Windows CE (Release) (Built on May 11 2004 16:51:41) nmake /NOLOGO C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\target\ARMV4I\debug\coredll.dll makefile.def: Invoked with predefined settings: TARGETNAME: coredll TARGETTYPE: DYNLINK RELEASETYPE: SDK TARGETLIBS: C:\WINCE500\public\common\oak\lib\ARMV4I\debug\corestub.lib C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\target\ARMV4I\debug\0409\coredll.res C:\WINCE500\public\common\sdk\lib\ARMV4I\debug\corelibc.lib SOURCELIBS: C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\lib\ARMV4I\debug\coredll_ALL.lib DEFFILE: C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\lib\ARMV4I\debug\coredll.def DLLENTRY: CoreDllInit makefile.def: BUILDROOT is C:\WINCE500\public\common\cesysgen 0 Please add _COMMONPUBROOT and __PROJROOT to your tree's cesysgen\sources file. Directory: C:\WINCE500\PUBLIC\COMMON\CESYSGEN TARGETNAME: coredll makefile.def: Including C:\WINCE500\public\common\oak\misc\sources.ReleaseType_SDK BUILD_MARKER:LINK_DLL_START Linking C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\sdk\lib\ARMV4I\debug\coredll.lib link -lib -out:C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\sdk\lib\ARMV4I\debug\coredll.lib -def:C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\lib\ARMV4I\debug\coredll.def -machine:thumb @C:\DOCUME~1\Martin\LOCALS~1\Temp\nm8B9.tmpMicrosoft (R) Library Manager Version 7.10.4017Copyright (C) Microsoft Corporation. All rights reserved.-nodefaultlib-ignore:4001-subsystem:windowsce,5.00C:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\oak\lib\ARMV4I\debug\coredll_ALL.libcoredll.def : error LNK2001: unresolved external symbol ConvertThreadToFibercoredll.def : error LNK2001: unresolved external symbol CreateFibercoredll.def : error LNK2001: unresolved external symbol DeleteFibercoredll.def : error LNK2001: unresolved external symbol GetCurrentFibercoredll.def : error LNK2001: unresolved external symbol GetFiberDatacoredll.def : error LNK2001: unresolved external symbol SwitchToFiberC:\WINCE500\PBWorkspaces\VRM270Thin\WINCE500\VRM270_ARMV4I\cesysgen\sdk\lib\ARMV4I\debug\coredll.lib : fatal error LNK1120: 6 unresolved externalsNMAKE : fatal error U1077: 'link' : return code '0x460'Stop.NMAKE : fatal error U1077: 'C:\WINCE500\sdk\bin\i386\nmake.exe' : returncode '0x2'Stop.NMAKE : fatal error U1077: 'C:\WINCE500\sdk\bin\i386\nmake.exe' : returncode '0x2'Stop. Tag: The difference of startup.s Tag: 78818
  - 10
    - DMA Interrupts Has anyone already programmed DMA Interrupts on PXA270? It's been a while since I started doing that. I could easily transfer data In or Out, With or Without the use of descriptors, but when i wanted to enable some interrupt (I am mostly interested in DCSR_ENDINTR) the system crashed at some point. The following steps summarize the test procedure i use: 1) Allocate N descriptors and buffers 2) Set up the Descriptors 3) Start the transfer 4) Poll a global variable until the IST flags it or until the loop times out. 5) Stop the transfer (it hopefully should be over anyway) 6) Deallocate everything The IST simply counts the times and ENDINTR is fired. Now if i don't enable the IRQs (and poll the STOPINTR flag instead) everything works fine. BUT! most of the time when i enable some IRQ the system crashes. I tried BTUART and SPI. BTUART really can't help itself but on rare occasions, SPI succeeded every now and then when it felt like it, instead. It all seems so aleatory. Besides, when a DMA IRQ is enabled the OS crashes even when i don't set up an IST. So i guess it doesn't depend on the IST (unless DMA needs the IST to reset the IRQ in any case) Have any clue? Tag: The difference of startup.s Tag: 78815
  - 11
    - WZC reporting RSSI incorrectly on Windows CE 5? All of the commercial devices we have sitting around are still Windows Mobile 2003 (or earlier), so I can't immediately verify this outside of our own WinCE 5 platform on our own hardware -- is anyone else using CE 5 and any 802.11 radio, and able to look at the RSSI as reported by the WZC api? With multiple different vendors' radios/drivers, I'm seeing the RSSI reported for any given access point apparently not getting updated. Even looking at the output of 'wzctool -q', the RSSI never changes from the initial value reported, as I move from right on top of the AP to completely out to the edge of its cell. It's "stuck". :( Can anyone confirm/refute this? It _looks_ like a bug in the WZC service or api (I don't believe it's a driver issue, as I'm (almost) positive this worked right under WinCE4.2 with those same radios/drivers)... Thanks, - Brian -- Brian Bender Vocollect, Inc. Pittsburgh, PA, USA [Apologies for the following "disclaimer" -- it's corporate policy.] -CONFIDENTIAL, PRIVILEGED COMMUNICATION- This e-mail transmission is private and intended for the addressee(s) only. It may contain information that is privileged and/or confidential. If you have received this transmission in error, you are not authorized to read, copy, disclose or disseminate it in any manner. If you have received it in error, please delete it and all copies (including backup copies) that have been made, and transmit a reply message informing the sender that it was misdirected. Tag: The difference of startup.s Tag: 78812
  - 12
    - TFAT issue Hi , I am trying to use TFAT for my Pesistent-Store partition in my NOR flash. I have used following registry settings. [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash_NORFMD\FATFS] "FormatTfat"=dword:1 "CheckForFormat"=dword:1 "Flags"=dword:14 [ FATFS_ENABLE_BACKUP_FAT | FATFS_DISABLE_AUTOSCAN] but this doesn't seem to work, It looks like "FormatTfat" value is not having any effect. So to force TFAT format on my Persistent Store as suggested by microsoft document I have modified my registry settings as given below (Just added FATFS_FORCE_TFAT) . [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash_NORFMD\FATFS] "FormatTfat"=dword:0 "CheckForFormat"=dword:1 "Flags"=dword:400014 [FATFS_FORCE_TFAT | FATFS_ENABLE_BACKUP_FAT |FATFS_DISABLE_AUTOSCAN] But these settings are causing the device to hang. Do you know why these settings are not working ? Can you tell me any other method to force TFAT for Persistent store ? Thanks in advance for the help. Regards, ~Mike Tag: The difference of startup.s Tag: 78800
  - 13
    - How to call Assembly code from C program Hi All, I have created a new project where i have to call some of Assembly functions (Instructions x86 processor related) please note that the assembly file is a separate .asm file and i dont want to use inline assembly program in my C code. I want to know that how can i link my .asm file with my C program code under Win CE Platform builder environment. I also want to know how i can access variables defined in C code in assembly program and is it possible to call C functions with in .asm file? Regards Roshan Tag: The difference of startup.s Tag: 78799
  - 14
    - ActiveSync + WM5 Hi, I am trying to convince WIndows Mobile 5 to use USB Serial Function driver. The best I could get is Guest connection. It does not give me an option to create a partnership at all. The registry settings I have for this works fine on Windows CE 4.2, 5.0 & WM2003 but does not want to properly work under WIndows Mobile 5. Here are my registry settings: [-HKEY_LOCAL_MACHINE\Drivers\USB] [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\USB] "Dll"="sa_usb_ser.Dll" "Irq"=dword:0 ; 11 - "IoLen"=dword:1000 ; UDC Register space 0x1000 (4K) "Tsp"="Unimodem.dll" "DeviceArrayIndex"=dword:0 "Prefix"="COM" "Order"=dword:12 "DeviceType"=dword:0 ; "FriendlyName"=LOC_FRIENDLYNAME_USB "FriendlyName"="USB Cable:" ; Eliminate flow control bit "DevConfig"=hex: 10,00,00,00,05,00,00,00,00,01,00,00,00,4B,00,00,00,00,08,00,00,00,00,00,00 [HKEY_LOCAL_MACHINE\Comm\SAUSB] ; "DisplayName"=LOC_DISPLAYNAME_SAUSB "DisplayName"="ISP1362 USB Function Driver" "Group"="Serial" "ImagePath"="sa_usb_ser.dll" [HKEY_LOCAL_MACHINE\Comm\SAUSB\Linkage] "Route"=multi_sz:"SAUSB1" [HKEY_LOCAL_MACHINE\Comm\SAUSB1] [HKEY_LOCAL_MACHINE\Comm\SAUSB1\Parms] [HKEY_LOCAL_MACHINE\Comm\USB] [HKEY_LOCAL_MACHINE\Comm\USB\Linkage] "Bind"=multi_sz:"SAUSB1" [HKEY_LOCAL_MACHINE\Comm\USB Cable:] [HKEY_LOCAL_MACHINE\Comm\USB Cable:\Parms] [HKEY_LOCAL_MACHINE\Comm\USB Cable:\Parms\TcpIp] "DNS"=multi_sz:"127.0.0.1" "DefaultGateway"=multi_sz:"192.168.55.100" "Subnetmask"=multi_sz:"255.255.255.0" "IpAddress"=multi_sz:"192.168.55.101" "DontAddDefaultGateway"=dword:00000000 "UseZeroBroadcast"=dword:00000000 "EnableDHCP"=dword:00000000 ;Connectoids [HKEY_LOCAL_MACHINE\Comm\DefaultConnections] IF BSP_NOUSBSER ! "`USB Default"=multi_sz:"USB Cable:","115200" ENDIF "`19200 Default"=multi_sz:"Serial Cable on COM1:","19200" "`38400 Default"=multi_sz:"Serial Cable on COM1:","38400" "`Infrared Port"=multi_sz:"Infrared Port","115200" "`115200 Default"=multi_sz:"Serial Cable on COM1:","115200" "`57600 Default"=multi_sz:"Serial Cable on COM1:","57600" ;Default Connectoid [HKEY_CURRENT_USER\ControlPanel\Comm] IF BSP_NOUSBSER ! "Cnct"="`USB Default" ELSE "Cnct"="`Com1 @ 115200`" ENDIF "AutoCnct"=dword:1 IF BSP_NOUSBSER ! ************************************************************************************************ It seems that WIndows Mobile 5 uses different registry settings and defaults to RNDIS. But I delete those registry by this: [-HKEY_LOCAL_MACHINE\Drivers\USB] and try to use my old driver the way it works in CE4.2, CE5.0 & WM2003. It does not work. Any suggestions? Thank you in advance. PK Tag: The difference of startup.s Tag: 78798
  - 15
    - how to install the second audio driver? I have built the x86 platform of WinCE 4.2 with default Ensoniq 1371 audio driver. I can put 2 kind of audio driver when I build x86 platform, but it is not my requirement. If I want to install another audio driver on run-time (Ensoniq 1371 has been exist), how can I do? Thanks! Nelson Tag: The difference of startup.s Tag: 78797
  - 16
    - Test mail Merry Chritmas n happy new year to everybody.. ~Mike Tag: The difference of startup.s Tag: 78796
  - 17
    - Network data corruption problem ! Hi all, I have written a socket application like echo server to test my NDIS miniport driver. I have TCP client runs on Windows XP and echo server running on WinCE. TCP client application continuously sends some known pattern. On echo server, I compare this pattern with expected pattern. It ran for 30 min - 1hr, and after that I see some data corruption in received data. Strangely it is some 4 bytes chunks in 4-5 places in the entire packet (1460 packet data size). I have debugged my NDIS miniport driver, but the data in my driver buffer is correct!!! I have used "NdisMIndicateReceivePacket" call to indicate the reception of data to NDIS. And in my "MiniportReturnPacket" function I reuse the packets as suggested in documentations. I wounder if anybody have experienced this problem... Any body has any clue on what is happening here ? One more doubt, I use my local buffer in my echo server application for "recvfrom" call. Do the TCPIP stack directly use this buffer to copy the data from my miniport driver buffer or is it uses some temporary buffer to do this copy operation? Thanks in advance, Raghav Tag: The difference of startup.s Tag: 78794
  - 18
    - JTAG Debugger for Windows CE Hi all, We are starting a new platform development. We are planning to use WinCE 5.0, and we will like to know what is the most recommended JTAG probe for real hardware debugging via the microprocessor JTAG interface. We Know the ARM Multi-ICE and the EPI Majic probe, and they say they are compatible with the Platform Builder. Do you know what is the best option for debugging a new implementation? Do you know any other manufacturer of JTAG probes? Do you think it is OK to use only the kernel debug option ( intrusive debug via WInCE kernel options )? Thanks a lot for your help. Best regards. Jose Manuel. Tag: The difference of startup.s Tag: 78785
  - 19
    - Do Windows ce can support K9F (K9F1G08U0M nand flash) ?thanks! Hi all! I have a big trouble about K9F flash use in wince , Can you tell me if windows ce can support K9F flash? how to find the proper driver for it ? I can't find it . thanks! K9F reference : http://www.samsung.com/Products/Semiconductor/Flash/NAND/1Gbit/K9F1G08U0M/K9F1G08U0M.htm thanks! calvin Tag: The difference of startup.s Tag: 78784
  - 20
    - connectivity options problem Hi, I am very very new to winCE.NET.I have Installed winCE 5.0 licensed version. I have followed proper installation steps and i have installed only the x86 emulator. As per the tutorials given in the MSDN i have followed the steps to build and OS Image.When I was trying to open the connectivity options Its giving an dilog "platform builder was unable to read the device setting from the database"... I have tried to install and un install again..but still the problem exist...:-( I don't know its an installation error or settings problem. Kindly help me Regards Murali Tag: The difference of startup.s Tag: 78776
  - 21
    - How to expend the SDRAM size from 64M bytes to 128MBytes. Platform:samsung2410 SDRAM 64M now I will expand my SDRAM from 64 Mbytes to 128M bytes , how can i do it? I searched the SDRAM from my platform, there has two points : kernel\arm\power.c After I replaced the sDRAM , my device display has some mistake, the screen is discorrect. Tag: The difference of startup.s Tag: 78775
  - 22
    - coreconnectivity error PB5.0 I have previously installed EV of PB5.0.After updating with lisenced version of PB5.0, when I select the coreconnectivity option its giving "unable to locate the database" I have tried installing again. Can any one help? Regards Murali Tag: The difference of startup.s Tag: 78773
  - 23
    - Purchase WinCe-5.0 Platform Builder Hi, We are Bangalore, India based product company. We are wanting to purchase the WinCE 5.0 for building custom target image for a TI OMAP platform. Could you please let me know who is the right person to contact in APAC sales for this. I understand that there is a qualifying process involved and we would like to get started on it. Tag: The difference of startup.s Tag: 78772
  - 24
    - Exception 004, MIPSII, WINCE5.0!!! Dear All, I met a big problem on my mips32 wince 5.0 tiny kernel platform, please help me! 1)When load filesys.exe, exception 004 occus. The following is the debug message: 0x87f72a88: Exception 004 Thread=87f72a88 Proc=07f72c9a 'filesys.exe' 0x87f72a88: AKY=00000003 PC=fffffb98(???+0xfffffb98) RA=03f71ae4(coredll.dll+0x00021ae4) BVA=fffffb98 0x87f72a88: NKDispatchException: returning failure. Flags=0 0x87f72a88: Unhandled exception c0000005: 0x87f72a88: Terminating thread 87f72a88 2)And after a while it occus again in nk.exe: Exception 004 Thread=87f74d30 Proc=07f7f002 'NK.EXE' 0x87f74d30: AKY=00000001 PC=fffffc00(???+0xfffffc00) RA=8085cd08(NK.EXE+0x0005cd08) BVA=fffffc00 0x87f74d30: NKDispatchException: returning failure. Flags=0 0x87f74d30: Unhandled exception 80000002: 0x87f74d30: Terminating thread 87f74d30 0x87f74d30: Secondary thread in proc 07f7f002 (NK.EXE) faulted! 0x87f74d30: Terminating process 07f7f002 (NK.EXE)! 0x87f74d30: Invalid handle: Set=1 Method=9 And then I can not see any debug message from kernel or file system. The OS does not work any more. But my timer interruupt handler still works because I can see it's debug message. The kernel(nk.exe) and file system(filesys.exe) do not work properly. I looked up in the CEPB help, exception 004 is: An address is unaligned. How to fighure out what code cause this kind of exception? How to location the error by the debug message above,such as (RVA:coredll.dll+0x00021ae4)? I have no idea about this. Any anyone help me? Thanks a lot!!! BTW: the following are the whole debug message: Windows CE Kernel for MIPS Built on Jun 24 2004 at 18:22:07 +OEMInit +g_oalCacheInfo.L1ISize=(65536) +g_oalCacheInfo.L1ILineSize=(32) +g_oalCacheInfo.L1INumWays=(4) +g_oalCacheInfo.L1ISetsPerWay=(1024) +g_oalCacheInfo.L1DSize=(65536) +g_oalCacheInfo.L1DLineSize=(32) +g_oalCacheInfo.L1DNumWays=(4) +g_oalCacheInfo.L1DSetsPerWay=(1024) +OALTimerInit(1, 100000, 200) +g_oalTimer.countsPerMSec=(100000) +g_oalTimer.countsMargin=(200) +g_oalTimer.msecPerSysTick=(1) +g_oalTimer.countsPerSysTick=(100000) +g_oalTimer.actualMSecPerSysTick=(1) +g_oalTimer.actualCountsPerSysTick=(100000) +++OALArgsQuery(4) -OALArgsQuery(pData = 0x00000000) +++OALTimerInitCount ---OALTimerInitCount -OEMInit Error Reporting Memory Reserved, dump size = 00020000 Booting Windows CE version 5.00 for (MIPS32) MIPS16 Instructions NOT Supported &pTOC = 8080109c, pTOC = 808a3c4c, pTOC->ulRamFree = 80c8a000, MemForPT = 00000000 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 29421, Secondary pages: 0, Filesystem pages = 14710 ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000004) ----OEMCacheRangeFlush(0x00000000, 0, 0x00000004) Booting kernel with clean memory configuration: Memory Sections: [0] : start: 80c8b000, extension: 00008000, length: 072ed000 Windows CE KernelInit ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000001) ----OEMCacheRangeFlush(0x00000000, 0, 0x00000001) Updated eptr->e32_vsize to = 000a4000 Scheduling the first thread. 0x87f7f028: KernelInit2: pCurThread=87f7f028 hCurThread=07f7f212 hCurProc=07f7f002, KernelInit = 8083370c 0x87f7f028: first = 01fb0000, last = 02000000, SharedDllBase = 03d20000 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000004) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000004) 0x87f7f028: +OALIoCtlHalPostinit Code=(0x10100B4) 0x87f7f028: +OEMGetRealTime 0x87f7f028: lining:: ticks = -2013794264 0x87f7f028: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.155) 0x87f7f028: +OEMGetRealTime 0x87f7f028: lining:: ticks = -2013794264 0x87f7f028: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.180) 0x87f7f028: +OEMGetRealTime 0x87f7f028: lining:: ticks = -2013794264 0x87f7f028: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.204) 0x87f74800: +OEMGetRealTime 0x87f74800: lining:: ticks = -2013837312 0x87f74800: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.228) 0x87f74800: +OEMGetRealTime 0x87f74800: lining:: ticks = -2013837312 0x87f74800: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.252) 0x87f74d30: +OEMGetRealTime 0x87f74d30: lining:: ticks = -2013835984 0x87f74d30: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.276) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x04080000, 4096, 0x00000003) 0x87f72a88: ----OEMCacheRangeFlush(0x04080000, 4096, 0x00000003) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: +OEMGetRealTime 0x87f72a88: lining:: ticks = -2013844856 0x87f72a88: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.477) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: CertMod.dll not found, using old OEM Trust Model 0x87f72a88: Exception 004 Thread=87f72a88 Proc=07f72c9a 'filesys.exe' 0x87f72a88: AKY=00000003 PC=fffffb98(???+0xfffffb98) RA=03f71ae4(coredll.dll+0x00021ae4) BVA=fffffb98 0x87f72a88: NKDispatchException: returning failure. Flags=0 0x87f72a88: Unhandled exception c0000005: 0x87f72a88: Terminating thread 87f72a88 0x87f72a88: +OEMGetRealTime 0x87f72a88: lining:: ticks = -2013844856 0x87f72a88: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.612) 0x87f74d30: Exception 004 Thread=87f74d30 Proc=07f7f002 'NK.EXE' 0x87f74d30: AKY=00000001 PC=fffffc00(???+0xfffffc00) RA=8085cd08(NK.EXE+0x0005cd08) BVA=fffffc00 0x87f74d30: NKDispatchException: returning failure. Flags=0 0x87f74d30: Unhandled exception 80000002: 0x87f74d30: Terminating thread 87f74d30 0x87f74d30: Secondary thread in proc 07f7f002 (NK.EXE) faulted! 0x87f74d30: Terminating process 07f7f002 (NK.EXE)! 0x87f74d30: Invalid handle: Set=1 Method=9 0x87f74d30: +OEMGetRealTime 0x87f74d30: lining:: ticks = -2013835984 0x87f74d30: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.716) 0x87f72828: Main thread in proc 07f72c9a faulted, Excpetion code = c0000005, Exception Address = fffffb98! 0x87f74d30: +OEMGetRealTime 0x87f72828: Main thread in proc 07f72c9a faulted, WMGR not on line! 0x87f74d30: lining:: ticks = -2013835984 0x87f72828: Main thread in proc 07f72c9a faulted - cleaning up! 0x87f74d30: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.759) 0x87f72828: +OEMGetRealTime 0x87f72828: lining:: ticks = -2013845464 0x87f72828: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.806) 0x87f72828: +OEMGetRealTime 0x87f72828: lining:: ticks = -2013845464 0x87f72828: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.830) 0x87f74800: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f74800: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f74800: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f74800: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f6fce0: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f6fce0: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f6fce0: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f6fce0: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate Tag: The difference of startup.s Tag: 78770
  - 25
    - SD card driver 2GB support Hi I'm developing a SD card driver for pxa255 on WinCE 4.2. Its working perfectly. But when I used 2GB SD cards, it detects only 1GB. What changes should I do to make my driver detect 2 GB size. Any help is appreciated. Thanks Anand Tag: The difference of startup.s Tag: 78764
- Next
  - 1
    - Windows CE 5.0 Platform Builder Update List ?? Dear Sir, I have been installed WINCE5.0 and update 4004-QFE/2005-Q1/2005-Q2/2005-Q3 QFE. (http://msdn.microsoft.com/embedded/downloads/ce/wince/default.aspx) Could anyone kindly tell me where can download other QFE ? PS. In Microsoft download center, search "Windows CE 5.0 Platform Builder Update", I can find QFE (ex : Windows CE 5.0 Platform Builder Update 051027_KB904260. Do Microsoft have web site to list all of QFE for WINCE 5.0 ? BR, Wiles Tag: The difference of startup.s Tag: 78755
  - 2
    - Whether MSFlash FMD support partition for Nand flash Dear all, We want to know Whether MSFlash FMD driver support partition for Nan flash. Anybody giving the solution for the above issue it would b appreciable. Thanks in advance,Jalvat Tag: The difference of startup.s Tag: 78750
  - 3
    - VS 2005 and PB 5 incompatibility Some background: My build environment: Visual Studio 2005 and Platform Builder 5.0. This article: http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/300736069a29e32e/c222adca0bd2d313 The problem mentioned in the above article is triggered when Visual Studio 2005 creates subdirectories in the app dir, and those subdirectories have spaces in their names. The specific directory I'm seeing is named "SDK (PROCESSOR)", where SDK and PROCESSOR are the names of the OS design SDK and processor VS 2005 is building for. Note that there is a space between SDK and the left parenthesis. Build.exe likes to create and update a build.dat [1] file in the application directory when it's building my application. This file seems to be some kind of whitespace-delimited cache file containing dependency information and file timestamps. Because it's whitespace-delimited and it doesn't do whitespace escaping, space-containing filenames break build.exe's ability to read the file later on. This is a problem, because the following procedure breaks the application build and anything that depends on on it: - Start with a working project in Platform Builder. - Create a corresponding project in VS 2005. - Build the app or parent OS design in PB. It should work. - Build the app in VS 2005. It should work. - Build the app in PB again. The build should break. The obvious workaround is to avoid VS 2005, but I don't want to give up variable argument macros and the unified dev environment. [1] This doesn't seem to be documented in the "Build Tool" topic in the Platform Builder docs. In fact, it doesn't seem to be mentioned anywhere in the docs. Why? What does it do? Was the build tool somehow exempt from Microsoft's internal documentation procedures? Tag: The difference of startup.s Tag: 78745
  - 4
    - building an OS Image Hi, I am trying to build an Multi Lingual Image on Windows CE.Net 4.2 supporting European languages i.e., Chinese(simplified) , Japanese and Korean (CJK)in a single platform where default locale is English (Unites States). I tried downloading the image to the target and tested. I made changesin the regional settings by changing UI language to Korean and Your Locale to Korean, but whereever the text has to be there,im getting it as boxes.even the date and time is not displayed properly in Korean. I have included font Gulim_subset_1_60 for korean.Do I have to do any modifications anywhere.I have tried all methods as specified in the PB 4.2. Plz suggest on this . Thanking u in anticipation, Div Tag: The difference of startup.s Tag: 78738
  - 5
    - =?Utf-8?Q?How_to_add_USB_Device_to_AU1200_?= How to add USB Device to AU1200 Bootloaderï¼?Who knowï¼?Please help me. Tag: The difference of startup.s Tag: 78735
  - 6
    - block driver registry IOCTL help? Hi, all. In my device, there is one build in nand flash. The registry of the driver is below: [HKEY_LOCAL_MACHINE\Drivers\BlockDevice\FlashDrv] "Prefix"="DSK" "Dll"="FLASHDRV.dll" "Order"=dword:0 "Ioctl"=dword:4 "Profile"="FlashDrv" "FriendlyName"="MS Flash Driver" "MountFlags"=dword:11 "BootPhase"=dword:0 "flags"=dword:1000 My question is the when CE call the Ioctl. What's meaning of the key value (4). I find in the source code: #define CTL_CODE( DeviceType, Function, Method, Access ) .... Is the key value(4) for the 'Function' of the CTL_CODE, or others. In the debug info, there print the IOCTRL value in the drvier's FMD_OEMIoControl, which is: FMD_OEMIoControl = 0x71c24. How to interpret this value 0x71c24. Hope to get some help. Thanks in advance. Tag: The difference of startup.s Tag: 78733
  - 7
    - SD Driver migration: 4.2 to 5.0 Hi, I have migrated a PXA 255 BSP and few drivers to 5.0. SD card driver is giving me trouble: I see that the loader is able to detect the card and make registry settings for the driver, however I do not see the SD?MMC folder show up! It also appears that the sysgen variable SYSGEN_SDMMC is missing in the 5.0 catalog items. Do i need to insert any other sysgen variable?... or is that my old driver will not work in 5.0, considering the changes in the architecture SD drivers in 5.0? It seems a lot of people in this grp faced similar problems with their SD drivers earlier, it would be nice if they shared how they got over this.. Please help... thanx in advance. -T@N Tag: The difference of startup.s Tag: 78732
  - 8
    - EbootCheckUDP Problem Dear All: I have modified WinCE5.0 MAINSTONEII bootloader eBoot code to my emulation board, that ethernet chip is SMSC91C1111. When I try to connect to the PB, it can't get response. static ip host PB ip: 192.168.1.10 emu-board: 192.168.1.11 submask: 255.255.255.0 I can see the device name (which I decided) show up in the: [Target]->[Connectivity Options]->[Setting] In "Ethernet Download Settings dialog window", the IP Address is correct, the Bootloader version default is 1.7 in MAINSTONEII (I have searched group, some one say that this version should not modified), but I also try to use 2.5 and 3.5, it is still not work. !!! Is the network communication OK, if I can get device in "Settings dialog" ??? I trace the source code, it get error at: EbootCheckUDP() if( !fPromiscuousIP && pIPHeader->dwDestIP != pMyAddr->dwIP ) { EdbgOutputDebugString( "!CheckUDP: Not our IP (0x%X)\n",pIPHeader->dwDestIP); return( 1 ); } I heve dumped the Frame Data to check but still can't found the problem, !!! Why the PB is no response ??? I stuck here for a week. please get me any suggestion.... message list below: Starting auto download ... INFO: Trying to initialize the built-in SMSC NIC... LAN91Cxxx: Chip Id 9 Revision 1 INFO: SMSC LAN91C111 Ethernet controller initialized. INFO: MAC address: 0-1-2-3-4-5 System ready! Preparing for download... INFO: Using device name: 'VT33001029' INFO: Using static IP address 192.168.1.11. INFO: Using subnet mask 255.255.255.0. ... +EbootSendBootmeAndWaitForTftp OEMDumpFrame send: 0000: FF FF FF FF FF FF 00 01-02 03 04 05 08 00 45 00 0010: 00 5C 00 00 00 00 40 11-B8 DE C0 A8 01 0B FF FF 0020: FF FF 03 D4 03 D4 00 48-C6 DC 45 44 42 47 FF 01 0030: 00 00 03 05 00 01 02 03-04 05 C0 A8 01 0B 56 54 0040: 33 33 30 30 00 00 00 00-00 00 00 00 00 00 00 56 0050: 54 33 33 30 30 31 30 32-39 00 00 00 00 00 00 00 0060: 41 02 01 00 01 00 00 00-00 00 Sent BOOTME to 255.255.255.255 OEMDumpFrame get: 0000: FF FF FF FF FF FF 00 80-1E 15 5E 10 08 00 45 00 0010: 00 8C 08 9D 00 00 80 11-AD 6A C0 A8 01 0A C0 A8 0020: 01 FF 0F 66 99 2D 00 78-42 3D 04 D3 A9 00 01 00 0030: 00 00 0C 00 10 01 2C 00-00 00 44 00 00 00 C0 A8 0040: 01 0A C0 A8 01 0A 00 00-00 00 00 00 00 00 00 00 0050: 00 00 00 00 00 00 4A 49-55 4E 31 00 00 00 00 00 0060: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 0070: 00 00 00 00 00 00 FF FF-FF 00 00 00 00 00 00 00 0080: 00 00 01 00 00 00 01 00-00 00 00 00 00 00 00 00 0090: 00 00 00 00 00 00 00 00-00 00 !CheckUDP: Not our IP (0xFF01A8C0) ... Thanks a lot, Jiun. PS: I also compare the frame data with PB<->CEPC, it is same, but why it is ok OEMDumpFrame send: 0000: FF FF FF FF FF FF 00 05-1C 0B B1 34 08 00 45 00 0010: 00 5C 00 00 00 00 40 11-B8 DD C0 A8 01 0C FF FF 0020: FF FF 03 D4 03 D4 00 48-63 BC 45 44 42 47 FF 01 0030: 00 00 03 05 00 05 1C 0B-B1 34 C0 A8 01 0C 43 45 0040: 50 43 00 00 00 00 00 00-00 00 00 00 00 00 00 43 0050: 45 50 43 34 35 33 36 34-00 00 00 00 00 00 00 00 0060: 30 02 01 00 01 00 00 00-00 00 Tag: The difference of startup.s Tag: 78727
  - 9
    - Exception 004 on Wince5.0 mips32 platform, hlep! Hi, All, I met a big problem on my mips32 wince 5.0 tiny kernel platform. 1)When load filesys.exe, exception 004 occus. The following is the debug message: 0x87f72a88: Exception 004 Thread=87f72a88 Proc=07f72c9a 'filesys.exe' 0x87f72a88: AKY=00000003 PC=fffffb98(???+0xfffffb98) RA=03f71ae4(coredll.dll+0x00021ae4) BVA=fffffb98 0x87f72a88: NKDispatchException: returning failure. Flags=0 0x87f72a88: Unhandled exception c0000005: 0x87f72a88: Terminating thread 87f72a88 2)And after a while it occus again in nk.exe: Exception 004 Thread=87f74d30 Proc=07f7f002 'NK.EXE' 0x87f74d30: AKY=00000001 PC=fffffc00(???+0xfffffc00) RA=8085cd08(NK.EXE+0x0005cd08) BVA=fffffc00 0x87f74d30: NKDispatchException: returning failure. Flags=0 0x87f74d30: Unhandled exception 80000002: 0x87f74d30: Terminating thread 87f74d30 0x87f74d30: Secondary thread in proc 07f7f002 (NK.EXE) faulted! 0x87f74d30: Terminating process 07f7f002 (NK.EXE)! 0x87f74d30: Invalid handle: Set=1 Method=9 And then I can not see any debug message from kernel or file system. The OS does not work any more. But my timer interruupt handler still works because I can see it's debug message. The kernel(nk.exe) and file system(filesys.exe) do not work properly. I looked up in the CEPB help, exception 004 is: An address is unaligned. How to fighure out what code cause this kind of exception? How to location the error by the debug message above,such as (RVA:coredll.dll+0x00021ae4)? I have no idea about this. Any anyone help me? Thanks a lot!!! BTW: the following are the whole debug message: Windows CE Kernel for MIPS Built on Jun 24 2004 at 18:22:07 +OEMInit +g_oalCacheInfo.L1ISize=(65536) +g_oalCacheInfo.L1ILineSize=(32) +g_oalCacheInfo.L1INumWays=(4) +g_oalCacheInfo.L1ISetsPerWay=(1024) +g_oalCacheInfo.L1DSize=(65536) +g_oalCacheInfo.L1DLineSize=(32) +g_oalCacheInfo.L1DNumWays=(4) +g_oalCacheInfo.L1DSetsPerWay=(1024) +OALTimerInit(1, 100000, 200) +g_oalTimer.countsPerMSec=(100000) +g_oalTimer.countsMargin=(200) +g_oalTimer.msecPerSysTick=(1) +g_oalTimer.countsPerSysTick=(100000) +g_oalTimer.actualMSecPerSysTick=(1) +g_oalTimer.actualCountsPerSysTick=(100000) +++OALArgsQuery(4) -OALArgsQuery(pData = 0x00000000) +++OALTimerInitCount ---OALTimerInitCount -OEMInit Error Reporting Memory Reserved, dump size = 00020000 Booting Windows CE version 5.00 for (MIPS32) MIPS16 Instructions NOT Supported &pTOC = 8080109c, pTOC = 808a3c4c, pTOC->ulRamFree = 80c8a000, MemForPT = 00000000 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 29421, Secondary pages: 0, Filesystem pages = 14710 ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000004) ----OEMCacheRangeFlush(0x00000000, 0, 0x00000004) Booting kernel with clean memory configuration: Memory Sections: [0] : start: 80c8b000, extension: 00008000, length: 072ed000 Windows CE KernelInit ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000001) ----OEMCacheRangeFlush(0x00000000, 0, 0x00000001) Updated eptr->e32_vsize to = 000a4000 Scheduling the first thread. 0x87f7f028: KernelInit2: pCurThread=87f7f028 hCurThread=07f7f212 hCurProc=07f7f002, KernelInit = 8083370c 0x87f7f028: first = 01fb0000, last = 02000000, SharedDllBase = 03d20000 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f7f028: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000004) 0x87f7f028: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000004) 0x87f7f028: +OALIoCtlHalPostinit Code=(0x10100B4) 0x87f7f028: +OEMGetRealTime 0x87f7f028: lining:: ticks = -2013794264 0x87f7f028: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.155) 0x87f7f028: +OEMGetRealTime 0x87f7f028: lining:: ticks = -2013794264 0x87f7f028: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.180) 0x87f7f028: +OEMGetRealTime 0x87f7f028: lining:: ticks = -2013794264 0x87f7f028: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.204) 0x87f74800: +OEMGetRealTime 0x87f74800: lining:: ticks = -2013837312 0x87f74800: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.228) 0x87f74800: +OEMGetRealTime 0x87f74800: lining:: ticks = -2013837312 0x87f74800: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.252) 0x87f74d30: +OEMGetRealTime 0x87f74d30: lining:: ticks = -2013835984 0x87f74d30: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.276) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x04080000, 4096, 0x00000003) 0x87f72a88: ----OEMCacheRangeFlush(0x04080000, 4096, 0x00000003) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: +OEMGetRealTime 0x87f72a88: lining:: ticks = -2013844856 0x87f72a88: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.477) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f72828: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72828: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f72a88: CertMod.dll not found, using old OEM Trust Model 0x87f72a88: Exception 004 Thread=87f72a88 Proc=07f72c9a 'filesys.exe' 0x87f72a88: AKY=00000003 PC=fffffb98(???+0xfffffb98) RA=03f71ae4(coredll.dll+0x00021ae4) BVA=fffffb98 0x87f72a88: NKDispatchException: returning failure. Flags=0 0x87f72a88: Unhandled exception c0000005: 0x87f72a88: Terminating thread 87f72a88 0x87f72a88: +OEMGetRealTime 0x87f72a88: lining:: ticks = -2013844856 0x87f72a88: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.612) 0x87f74d30: Exception 004 Thread=87f74d30 Proc=07f7f002 'NK.EXE' 0x87f74d30: AKY=00000001 PC=fffffc00(???+0xfffffc00) RA=8085cd08(NK.EXE+0x0005cd08) BVA=fffffc00 0x87f74d30: NKDispatchException: returning failure. Flags=0 0x87f74d30: Unhandled exception 80000002: 0x87f74d30: Terminating thread 87f74d30 0x87f74d30: Secondary thread in proc 07f7f002 (NK.EXE) faulted! 0x87f74d30: Terminating process 07f7f002 (NK.EXE)! 0x87f74d30: Invalid handle: Set=1 Method=9 0x87f74d30: +OEMGetRealTime 0x87f74d30: lining:: ticks = -2013835984 0x87f74d30: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.716) 0x87f72828: Main thread in proc 07f72c9a faulted, Excpetion code = c0000005, Exception Address = fffffb98! 0x87f74d30: +OEMGetRealTime 0x87f72828: Main thread in proc 07f72c9a faulted, WMGR not on line! 0x87f74d30: lining:: ticks = -2013835984 0x87f72828: Main thread in proc 07f72c9a faulted - cleaning up! 0x87f74d30: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.759) 0x87f72828: +OEMGetRealTime 0x87f72828: lining:: ticks = -2013845464 0x87f72828: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.806) 0x87f72828: +OEMGetRealTime 0x87f72828: lining:: ticks = -2013845464 0x87f72828: -OEMGetRealTime(rc = 1 2003/1/1 12:0:0.830) 0x87f74800: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f74800: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f74800: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f74800: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f6fce0: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f6fce0: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000003) 0x87f6fce0: ++++OEMCacheRangeFlush(0x00000000, 0, 0x00000018) 0x87f6fce0: ----OEMCacheRangeFlush(0x00000000, 0, 0x00000018) +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate +++OALTimerUpdate ---OALTimerUpdate Tag: The difference of startup.s Tag: 78725
  - 10
    - CEPC, boot from HD, does not see PCI Network Card! Hi everybody, I have built CE5 for CEPC (Pent.III), am able to boot nk.bin from harddrive, but for some reason it does not see the network card. The card is there and is OK, since if I create an image with KITL, I can eboot it without problem, yet when I use ldr to boot from HD, Windows start, but it does not see network (or does not install drivers?) I have spent last 3 days browsing Google and reading MS documentation, nothing works. I feel that I am missing some important piece of info. I have tried modifying Project.reg by adding the entries below - no effect. Any help would be greatly appreciated! Viktor [HKEY_LOCAL_MACHINE\Drivers\PCI\Template\NE2000] "Dll"="NDIS.dll" "ConfigDll"="NE2000cfg.dll" "ConfigEntry"="DeviceConfig" "Class"=dword:02 "SubClass"=dword:00 "ProgIF"=dword:00 "MiniPort"="NE2000" [HKEY_LOCAL_MACHINE\Comm\NE20001\Parms\TcpIp] "EnableDHCP"=dword:1 "DefaultGateway"="192.168.0.1" "UseZeroBroadcast"=dword:0 "IpAddress"="192.168.0.212" "Subnetmask"="255.255.255.0" "DNS"="xxx.xxx.xxx.11" [HKEY_LOCAL_MACHINE\Comm\NE20001\Parms] "BusNumber"=dword:0 "BusType"=dword:5 "InterruptNumber"=dword:0a "Sysintr"=dword:1a "Sysintr"=dword:1f "IoBaseAddress"=dword:300 "Transceiver"=dword:3 "CardType"=dword:0 [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage] "Bind"=multi_sz:"NE20001" All I see (through Serial), is this: Microsoft Windows CE BIOS Bootloader Version 2.2 (Built Dec 21 2005) Opening IniFile: 'boot.ini' INFO: code=0x4. Image File name from boot.ini: 'nk.bin' INFO: code=0x4. INFO: code=0x4. Jumping to image (address=0x224F98) Debug Serial Init SysInit: Mapping Extra RAM from 0x84000000 to 0x8f800000 GDTBase=81a990e8 IDTBase=81aba860 KData=81ac1800 Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42 g_pPageDir = 81ac5000 RTC - Status Reg B - 0x02 X86Init done, OEMAddressTable = 81ac6000. OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 OEMIoControl: Unsupported Code 0x10100d4 - device 0x0101 func 53 OEMIoControl: Unsupported Code 0x10100c4 - device 0x0101 func 49 OEMIoControl: Unsupported Code 0x10100c4 - device 0x0101 func 49 OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 Tag: The difference of startup.s Tag: 78707
  - 11
    - How to implement 18bpp display driver? i have to implement 18bpp display, and i know i should complete the following work items, but i dont know how many blitting code should be written, there seem to be many blitting code for every raster operation. Make LCD driver a standard 24bpp GPE driver DrvGetMasks has to return 24bpp masks (0x00RRGGBB usually) GPE::GetModeInfo override needs to report proper bpp and masks GPE::SetMode override needs to generate proper palette (containing masks using EngCreatePalette) Allocate 24 bpp (bit per pixel) primary surface Connect the 24-bit frame buffer to 18-bit LCD by dropping low order bits of each color Optimize blitting code Tag: The difference of startup.s Tag: 78696
  - 12
    - SD Card Query ... ? Hello All, I have some queries related to the SD-Card (Memory). Background Information :- Processor :- Intel PXA270. Reference BSP :- MainstoneII from PB 5.0 I have included the following items in my OS image :- 1. SDBUS driver. 2. SD Standard Host Controller Driver. 3. SD Memory Driver. When I download my OS image, I can oberve that the SDBUS driver is being loaded (i.e.SDBUS.dll) and I believe that the SDMemory driver is loaded after I insert the card in to slot, but at present no activity is happening when I insert the card ... So I am trying to locate where exactly could the problem be ... ? If anyone could provide me with any pointers in this regard it would be a great help ... ! Regards, Swapnil. Tag: The difference of startup.s Tag: 78694
  - 13
    - ActiveSync related We have a requirement in one of our projects where in we want an application running on a Windows Mobile 5.0 device ( i-mate JASJAR ) to receive IP packets on a UDP port and a server running in LAN to send the UDP packets to this application. The device is connected to one of the machines through USB (ActiveSync). Is this scenario possible?? As in one of the articles on Active Sync in MSDN it says that UDP is not supported on ActiveSync. If this is the case then is there any work around for the above scenario. Tag: The difference of startup.s Tag: 78686
  - 14
    - Ether boot Hai, I am planning develop a boot loader based on CE 5.0 x86 BIOS boot loader. Is it possible for me to include the etherboot source also along with this BIOS boot loader to download windows ce image. Essentially I need to download windows ce os image from platform builder with out DOS only with my boot loader. Kindly inform me is there any difficulty present in this approach. Before starting I wish take you greats idea. Thanks. avkumar Tag: The difference of startup.s Tag: 78674
  - 15
    - How to use PB5 to build application which supports ArmV4 ? Hi, How to use PB5 to build application which supports ArmV4 ? Applications which were built using "ArmV4I" can not run on ArmV4 device. Jemmy Tag: The difference of startup.s Tag: 78666
  - 16
    - How to debug driver only using PB Hi there, I have a device dopod818 which is not made by us. However, I want to wrote a driver and debug on it. How do I use PB to do such kind of thing? PB always ask me to download platform image to that device, but I dont have any platform. Another way is using eVC, however I found eVC cannot debug driver. thanks for any help Jemmy Tag: The difference of startup.s Tag: 78662
  - 17
    - PXA255 NSSP problem in SPI mode Dear all, I'm developing a WinCE driver for a peripheral attached to the NSSP port of a PXA255 processor. NSSP port is configured in SPI mode 0, SPI bus master (Clock and Frame master), data size = 8bit, and is used in PIO mode (so no DMA and no Interrupts just polling). I'm currently testing the port in Loopback mode (I've tried internal loopback or external loopback shorting RX and TX pins). I've encountered this problem: >From PXA developer's manual I thought that writing a byte to TxFifo and waiting for TxFifo to be empty would cause RxFifo to contain a byte (SPI is full-duplex so if I transmit a byte I also receive a byte). But after writing a byte to TxFifo and waiting for Tx completion, RxFifo is empty. What is really strange is that writing a second byte causes RxFifo to contain the first byte transmitted and so on. For example: 1) Write 0x01 -> RxFifo Empty 2) Write 0x02 -> RxFifo contains 1 byte with value 0x01 3) Write 0x03 -> RxFifo contains 1 byte with value 0x02 and so on. It seems that NSSP controller has an hidden Rx buffer where data is stored prior to putting it in RxFifo on the arrival of another byte. Is that behaviour correct or am I making some kind of error? Has anybody esperienced this kind of behaviour? Thanks for the kind reply Claudio Tag: The difference of startup.s Tag: 78655
  - 18
    - SD card mounting porblem Hi, I'm developing a SD card driver for platform PXA255 on WinCE 4.2. I can see SD card partition in Storage Manager control panel but its mounted. When I try to mount, it gives error unable to mount the partition. The following is the registry I'm using. [HKEY_LOCAL_MACHINE\Drivers\SDMMC] ;"FSD"="FATFS.DLL" "Prefix"="DSK" "Dll"="sdmmc.dll" "Index"=dword:1 "FriendlyName"="SDMMC Driver" "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\sdmmc] "Prefix"="SML" "Dll"="SDMMC_Loader.dll" "Order"=dword:2 "Ioctl"=dword:4 "FriendlyName"="SDCard/MMC Loader" [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\SDMMC] "Name"="SD/MMC Card" "Folder"="SD/MMC Card" Any help is appreciated. thanks Anand Tag: The difference of startup.s Tag: 78650
  - 19
    - How to do an IOCTL_NDISUIO_SET_OID_VALUE when WZC controls the UIO? We are using the WZC service to manage our network configuration and have found a way to do most things through that. However, this does not manage the radio specific settings such as power level. I can create a handle to the NDISUIO device, but can not OPEN_DEVICE without an error (ERROR_GEN_FAILURE). I'm assuming this is because the WZC service already owns this and so denies me access. I can still query the OID_802_11_TX_POWER_LEVEL to read the current setting, but get an ERROR_INVALID_USER_BUFFER error if I try to set the OID (which makes sense b/c I couldn't open!). In the help, I found the IOCTL_NDISUIO_OPEN_WRITE_DEVICE which is supposed to allow simultaneous access for multiple apps. By using this, you should be able to set and query OID values (among other things). I can successfully OPEN_WRITE_DEVICE, but still get the same results. The query still works and the set still returns the same error as above. Is there really a way to _set_ NDIS OIDs to an adapter that's owned by WZC? Am I just going about this wrong? I did try to open the ZCF1: device (WZC) and pass the SET_OID_VALUE, but this was an unsupported IOCTL. Any help would be appreciated! Thanks, Vanessa Sanchez Vocollect, Inc. Pittsburgh, PA, USA [Apologies for the following "disclaimer" -- it's corporate policy.] -CONFIDENTIAL, PRIVILEGED COMMUNICATION- This e-mail transmission is private and intended for the addressee(s) only. It may contain information that is privileged and/or confidential. If you have received this transmission in error, you are not authorized to read, copy, disclose or disseminate it in any manner. If you have received it in error, please delete it and all copies (including backup copies) that have been made, and transmit a reply message informing the sender that it was misdirected. Tag: The difference of startup.s Tag: 78637
  - 20
    - How can I excute my program when WinCE startUp I set a registe item ; [HKEY_LOCAL_MACHINE\init] "Launch90"="myapp.exe" "Depend90"=hex:50 but Myapp.exe is auto run the software on SD/CF( example \storage card\autorun.exe) when this file was found . everything looks ready, and normally it running good , but sometimes , when I did not insert the SD/CF card to socket during booting, after system had startup , I inserted the SD/CF , there will occured a confliction between WinCE File System and user software file searching ,so , myapp.exe normally can not find the \storage card\autorun.exe file or occured a Error. How can I avoid this error or exception ??? I changed the search way (FindFirstFile/fopen all can occure a error ). and how can I avoid a error occured after I remove the SD/CF card when the autorun.exe is running...... normally a Error/Exception dialog is showed. -- slyzhang Tag: The difference of startup.s Tag: 78628
  - 21
    - It's slow to recognise the SD card after I insert the sd card . samsung 2410 wince4.2 My device is slowly recognise the SD card after I insert the sd card . and <my Computer> explorer is slowly to update the Storage Card folder after I Insert/Remove sd card , how can i change the register to make it response quickly . -- slyzhang Tag: The difference of startup.s Tag: 78624
  - 22
    - my XP/2000 PC is blue-screen with using Samsung2410 USB to update kernel Platform samsung : 2410 WinCE4.2 my PC (windows XP/2000) occured a Blue-Screen when I pull-out the 2410 USB device . Why PC will be Blue-Screen After I poll-out my usb client? the USB driver has some BUGS?? -- slyzhang Tag: The difference of startup.s Tag: 78622
  - 23
    - Image CE 5.0 with CF2.0 Hello, I'd like to add CF2.0 to Platform Builder 5.0 Catalog. Is there some tutorial/doc? Thanks in advance Giuseppe Tag: The difference of startup.s Tag: 78621
  - 24
    - Cesys bug I think there is an error in cesys source code: The structure defining the partition table is declared as #pragma pack(1) typedef struct { unsigned char ActiveFlag; unsigned char SSector; unsigned char SHead; unsigned char SCylinder; //... } PARTTE, *PPARTTE; I think that SSector and SHead should be inverted Tag: The difference of startup.s Tag: 78610
  - 25
    - Who knows the best speed of transferring file through ActiveSync from Desktop PC to device, (via USB 2.0 bus.) Dear all: Who has ever made some device supporting Activesync connection by USB 2.0? And how about the speed? Microsoft should know this , I think, however, cannot get their response. Thanks a lot!! Best Regards!! Tag: The difference of startup.s Tag: 78607

I have one question on startup.s

I have ARM cored board. (ARM 922T).
Generally, you can find three startup.s for a ARM based board.
For example, In case of Samsung 2410x board, you can find one startup.s in
'eboot' directory of 2410x BSP.
another is in 'oal' of 2410x BSP.

The other is in \Platform\Common\SRC\ARM\Samsung\S3c2410x\Startup

I know the first 'startup.s' is for bootloader. But, now, I wonder what the
difference between the second and the third is.

And What should I do for XIP (excute in Place)?

Top