JTAG Debugger for Windows CE

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - 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: JTAG Debugger for Windows CE Tag: 78784
  - 2
    - 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: JTAG Debugger for Windows CE Tag: 78776
  - 3
    - 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: JTAG Debugger for Windows CE Tag: 78775
  - 4
    - 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: JTAG Debugger for Windows CE Tag: 78773
  - 5
    - 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: JTAG Debugger for Windows CE Tag: 78772
  - 6
    - 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: JTAG Debugger for Windows CE Tag: 78770
  - 7
    - 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: JTAG Debugger for Windows CE Tag: 78764
  - 8
    - 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: JTAG Debugger for Windows CE Tag: 78755
  - 9
    - 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: JTAG Debugger for Windows CE Tag: 78750
  - 10
    - 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: JTAG Debugger for Windows CE Tag: 78745
  - 11
    - 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: JTAG Debugger for Windows CE Tag: 78738
  - 12
    - =?Utf-8?Q?How_to_add_USB_Device_to_AU1200_?= How to add USB Device to AU1200 Bootloaderï¼?Who knowï¼?Please help me. Tag: JTAG Debugger for Windows CE Tag: 78735
  - 13
    - 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: JTAG Debugger for Windows CE Tag: 78733
  - 14
    - 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: JTAG Debugger for Windows CE Tag: 78732
  - 15
    - 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: JTAG Debugger for Windows CE Tag: 78727
  - 16
    - 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: JTAG Debugger for Windows CE Tag: 78725
  - 17
    - 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: JTAG Debugger for Windows CE Tag: 78707
  - 18
    - 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: JTAG Debugger for Windows CE Tag: 78696
  - 19
    - 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: JTAG Debugger for Windows CE Tag: 78694
  - 20
    - 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: JTAG Debugger for Windows CE Tag: 78686
  - 21
    - 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: JTAG Debugger for Windows CE Tag: 78674
  - 22
    - 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: JTAG Debugger for Windows CE Tag: 78666
  - 23
    - 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: JTAG Debugger for Windows CE Tag: 78662
  - 24
    - 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: JTAG Debugger for Windows CE Tag: 78655
  - 25
    - 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: JTAG Debugger for Windows CE Tag: 78650
- Next
  - 1
    - 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: JTAG Debugger for Windows CE Tag: 78637
  - 2
    - 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: JTAG Debugger for Windows CE Tag: 78628
  - 3
    - 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: JTAG Debugger for Windows CE Tag: 78624
  - 4
    - 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: JTAG Debugger for Windows CE Tag: 78622
  - 5
    - 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: JTAG Debugger for Windows CE Tag: 78621
  - 6
    - 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: JTAG Debugger for Windows CE Tag: 78610
  - 7
    - 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: JTAG Debugger for Windows CE Tag: 78607
  - 8
    - Is there a way for a PB debug shell extension to access the host machine's filesystem? I am curious if it is possible for a ceshell debug extension loaded with the loadext command to access files on the desktop, or host machine? Or execute code on the desktop? I'm using PB 5.0. I'm not sure if there might be some interface available to the target device that allows an application, or shell extension, running in the address space of the CE device to interact with the desktop host machine in this way. I know corecon allows you to do some operations going from the desktop to the target CE device, but since I am looking at a shell extension I am going the other way. I'm not certain yet if corecon has an interface that is intended to run on the target device that goes back out to the host machine. For example, say I wanted to read the registry or read a file from the desktop or get the COMPUTERNAME of the desktop using a shell extension... Are there any interfaces available to a shell extension that allow for these type of operations? Since the shell extension is loaded into the debug shell, which is loaded by Platform Builder, I thought just maybe there is some way exposed that allows you to cross the device boundaries in this way without having to write some sort of socket-based solution to talk between the CE device and a service or application running on the desktop. Thanks! David Holcomb Tag: JTAG Debugger for Windows CE Tag: 78603
  - 9
    - How to complete RNDIS on WinCE50? Dear all: I am newbie in RNDIS. Lately, I have to complet RNDIS on WinCE50. I try to read some MSDN about RNDIS and USB Spec. 2.0. But I have no sense to build it. Somebody could give me some hints and reference? Or where is the sample code? Because I saw some folders and they are all named "RNDIS". Which one is true? Thanks for your help. Tag: JTAG Debugger for Windows CE Tag: 78598
  - 10
    - Installing Windows CE 5.0 Crashes XP and Windows 2000 Using Windows 2000 with all the latest service packs and hotfixes (Service Pack 4), I tried to install the 120-day trial version of Windows CE 5.0 from the CD's. On installing the 3rd disk...disk number 5, while "Registering Platform Manager Components", my Lan Manager License Requester popped up briefly and then the system crashed into blue screen without much detail. Upon recovery I had lost my network connectivity. This prompted my department to give me a brand new PC with Windows XP service pack 2 and every critical update installed. It was overdue ;-) This is a 3.2 GHZ Pentium Dell Precision Workstation with 2 120GB hard drives in a mirrored RAID configuration. During installation of CE 5.0, in the same exact spot while registering the platform manager components, my Lan Manager License Requester popped up briefly and crashed the system again. This time I was able to get the minidump and xml files created. The problem seems to be with either TCPIP.SYS or NDIS.SYS. I've reverted back to previous good settings and reinstalled (after the suspended install of CE 5.0 reversed all changes). Each time it crashed in pretty much the same way. BTW, each time it boots after this crash, if I let it sit at the login prompt, it will crash again after a couple of minutes. I have to revert back to last known good config and back out the install each time. I did this 4 times. Now for the kicker...I finally decided to disable my network connection (through network properties) so as to prevent the license manager from trying to reconnect. I installed successfully! However, when I reenabled the network, it crashed exactly as before during the license request. This time, though, it rebooted and did not crash again. However, there is definitely something not right. Everything runs perfectly until I disable the network connection (through network properties) and then simply re-enable it. At that time I get the blue screen (DRIVER_NOT_LESS_OR_EQUAL). -----update---- OK...This time it booted up with the network in a disabled state. After I logged in, I re-enabled the network and it didn't crash. I unplugged the cable 3 times. Each time I reconnected it, the License manager popped up and everthing was fine. I disabled again through network properties, then re-enabled, and it didn't crash. I've done this twice now. Everything seems to be ok now. If ANYONE knows what has been happening and why it works now after what I described, I'd like to know. This is a work PC with PATHWORKS 32 V7.2. It's a Broadcom NetXtreme 57xx Gigabit Controller. Thanks Tag: JTAG Debugger for Windows CE Tag: 78595
  - 11
    - Headless device hi, i am creating mp3 player(headless device) based on SMDK2440 bsp. in my system i dont use display driver so i am not able create window to receive keyboard inputs for player. i want to create interactive player i checked the code samples using IMediaControl. problem is either it needs window for interative player to receive key inputs or it plays without user interacation. can anyone sugest me. warm regards Himanth Tag: JTAG Debugger for Windows CE Tag: 78594
  - 12
    - Which OemIOControl is it I would like to know which OEMIOControl code these belong to. How can I find out?? OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 Tag: JTAG Debugger for Windows CE Tag: 78586
  - 13
    - Exception 0e0 in NDIS (device.exe) on SH3 in WinCE 4.1 I have a SH3 device in CE 4.1 that shows a failure (very hard to reproduce) during an FTP download. My test scenario involves a busy network, constant pinging of the device (several ping sessions) and FTP download of 177 files continuously (7.7MB total). I can run this test many times without failure, but when it fails, I get no response from NDIS, it is dead. All other peripherals and interfaces are good yet. (Other note, we have the same ethernet driver running on ARM9 and SH4 systems and have not found this issue to date) Questions: 1) Has anyone seen this issue before? 2) Is the only way to get into the ndisMCompleteSend() function through using NdisMSendComplete()? 3) What could cause the ndisMCompleteSend() function to fail in this way? CALL STACK: #################################################### Process: device.exe Thread: 0xADF91C92 NDIS!ndisMCompleteSend(_NDIS_MINIPORT_BLOCK * 0x00031278, _NDIS_PACKET * 0x0003d78c, _NDIS_STACK_RESERVED * 0x0003d73c, int 0x00000000, unsigned char 0x01, unsigned long 0x00000004) line 64 + 18 bytes NDIS!ndisMStartSends(_NDIS_MINIPORT_BLOCK * 0x00031278) line 1195 + 20 bytes NDIS!ndisMProcessDeferred(_NDIS_MINIPORT_BLOCK * 0x00031278) line 2946 NDIS!ndisMDpc(void * 0x00031278, void * 0x0003d78c, void * 0x0003d73c, void * 0x00000000) line 1508 NDIS!CeKeDpcQueueThread(void * 0x00031278) line 63 + 10 bytes COREDLL!ThreadBaseFunc(void * 0x00031278, unsigned long 0x0003d78c) line 419 EXCEPTION: #################################################### 874427 PID:2dfab9a6 TID:adf91c92 Exception 0e0 Thread=8df8b5e8 Proc=2dfab9a6 'device.exe' 874427 PID:2dfab9a6 TID:adf91c92 AKY=ffffffff PC=03d4d8d0 RA=03d4e62e TEA=4d4f43b1 Tag: JTAG Debugger for Windows CE Tag: 78579
  - 14
    - shell Some months ago I coaxed PB 5.0 into using a different shell look-n-feel. It's outlined in all but the first screen shot on this site: http://www.hpcfactor.com/support/windowsce/wince50/ I have now been told to resurrect this change and I can't figure out how I did it!! :( Can anyone tell me what needs to be tweaked in PB 5.0 to build an OS with this look-n-feel? Thanks. eamonn Tag: JTAG Debugger for Windows CE Tag: 78577
  - 15
    - CE Support for USB to RS232 adapters Numerous vendors sell inexpensive USB to RS232 adapter/cables for the desktop environment and supply Windows drivers with them. We would like to use an adapter like this with Windows CE 5.0 but have been unable to find one with CE support. Are any newsgroup readers aware of a vendor or other solution? Tag: JTAG Debugger for Windows CE Tag: 78566
  - 16
    - Problem with RTL8139 on Geode with CE.NET 5.0 Hi, I've a very freaky problem with the RTL8139 driver on Geode: I connect my RTL8139 over cross cable to an XP machine. On XP, the network adapter has 2 IP Address in different networks. I start a flood ping from XP to the RTL8139 (5000 bytes), the RTL8139 is responding well! During the flood ping, I make a small ping from the second IP address (RTL8139 doesn't know the network ID). After the small ping (not answered) and ~12 fping (answered!) the RTL8139 is dead! A thread with prio ~115 doen't give any CPU time anymore! (should be the ISR in NDIS...). The CheckForHang function is still running, but doesn't care about the hanging state of the network.... I can reproduce this problem with a RTL8139 PCI Card on the Geode to! I can not reproduce it on the CEPC with the same PCI card... It seems like it's a synchronization problem in the RTL8139 driver, which appear on the Geode platform... Does anybody have a similar problem with the RTL8139 driver? Any workaround? I'm looking for the source code of the driver... Thank you for reply!! Tag: JTAG Debugger for Windows CE Tag: 78563
  - 17
    - usb client suspend resume on pxa270 Mainstone PXA270 WinCE5.0 I'm trying to resume usb serial function after suspend. I have done these modifications: 1) correct bul_usbfn.cpp BulUsbDevice::ReInit() with inserting parenthesis in for cycle (to correct Reinit skipping) 2) correct BulUsbDevice::PowerDown in order to call always PowerMgr function 3) call Reinit in BulUsbDevice::PowerMgr function in case of Powerup But it still does not work. I have no more ideas. Any help ? Thanks Piero Tag: JTAG Debugger for Windows CE Tag: 78562
  - 18
    - BSP What does BSP stand for? Mhaxx Tag: JTAG Debugger for Windows CE Tag: 78558
  - 19
    - When will MS fix the WinCE USB Mass Storage Problems? I have searched through many of the postings regarding problems associated with USB memory stick devices and have found that others in the community have been experiencing the same troubles. We have recently tested about 9 different USB memory stick devices from various vendors and have found that 4 simply do not work on WinCE 4.2, although they work fine when plugged into an XP desktop. These sticks are popular brands, too, and telling our customers they cannot use these devices will be quite unpopular. To summarize what I have gleaned from the postings, the USB mass storage driver/SCSI disk drivers in WinCE 4.2 and 5.0 are not capable of supporting the full gamut of devices. We (the community) have been told that there are QFEs to fix some of these issues, and we have been told to fix the drivers ourselves or purchase a 3rd party driver. This issue has been open for more than a year; many of the postings started around this time in 2004. Which QFEs fix this problem? This has already been asked but I could not find a response posting. I have looked through this years QFE summaries but nothing seems to have been done. If no QFEs have been issued, when can we get MS to address the issue? I submit that this kind of problem gives WinCE a "black eye", supplying the naysayers with extra ammunition to oppose its use for a new project. Moreover, we would like to move one of our existing products from 4.1 to 5.0, but we don't want to invite more trouble than we already have by doing so. Does anybody have a list of those devices that work vs. non-working? This would be helpful until the true "production-quality" driver for 5.0 becomes available. I would like to believe that the embedded group at MS has enough of a budget to purchase the most popular brands and compile a list, both for our benefit and to help the developers address the driver issues. If MS intends to ignore the issue, then who out there has a 3rd party solution? Thanks in advance. Tag: JTAG Debugger for Windows CE Tag: 78556
  - 20
    - an eboot problem About Au1200 BSP Hi,all I am working on Au1200. I don't want to use YAMON to start Eboot.What would I modify the source file and eboot.bib in the eboot of the Au1200 BSP provided by Bsquare company. I know that the start physical address after resetting au1200 is 0x1fc00000,I have attempted to set some macro variable which are "BOOTJUMP=BFC000000" in eboot.bib file and "EXEBASE=0xbfc00000" in Source file, but failed! please, share some clue with me. does Au1200 have to use YAMON to start eboot? or Platform Builder doesn't support Au1200 starts eboot directly? Thanks a lot. Tag: JTAG Debugger for Windows CE Tag: 78553
  - 21
    - driver unload not called........... hello, We are porting a Ndis intermediate driver from NT to wince4.2 .we are using platformbuilder's emulator for testing...we are able to load the driver and also send and receive packets successfully. however when we unload the driver using emulators softreset the protocol unbind handler and driver unload handler does not get called.....we are using NdisMRegisterUnloadHandler for registering our drivers unload handler.....is the soft reset on the emulator sufficient to unload the driver and load it again? we are using a self registering dll for installing the registry entries for the driver.....can anyone please help me out.....any kind of help would be really appreciated...........thankyou Tag: JTAG Debugger for Windows CE Tag: 78550
  - 22
    - How to get the registry location of a driver Hi, How do I get the registry location of a driver? Whether if I can use device name "USB:" to get device driver's registry location? "HKEY_LOCAL_MACHINE\Drivers\BuiltIn\USB" Jemmy Tag: JTAG Debugger for Windows CE Tag: 78546
  - 23
    - Third party loader & BSP development Hello all! I would like to get some explanation for my situation. I develop BSP for S3C2410-based board with 64M NAND-flash and 128M SDRAM. We use third-party bootloader. That bootloader just initializes NAND controller and copies NANDflash contents into SDRAM and then jumps at the beginning of SDRAM (0x30000000). No MMU, no IRQ, nothing. We use JTAG for initial copying of bootloader and OS-image into NANDflash (therefore image must be stored in nb0-format). How I shall develop BSP in this case? As far as I have understood I don't need to develop Bootloader because all sequence from StartUp(bootloader) to OEMLaunch is already present in third-party bootloader. I should start to develop BSP from OAL-step? I.e : 1 create StartUp (how can I order to make my StartUp the first instruction in image? Place EXEENTRY=StartUp in \KERNEL\BUILDEXE\KERN\sources ? What address I need to specify in this file and all another configuration files - real or virtual? (In my case MMU is disabled at this step) ) 2 from StartUp call KernelStart. 3 From KernelStart create MMU table and initialize MMU (how can I make it? Just like in example for SMDK2410? But, in this example MMU was initialized before copying image to SDRAM. In my case image is already placed in SDRAM and MMU is off... Here there are any dirty tricks?) 4 In example for SMDK2410 KernelStart calls main(). What finction should I call? Who calls OEMARMCacheMode, OEMInit, OEMDebugInit and all other OAL-functions? I don't understand it... I need to "switch" from my own code to code that executed by OS (if it is possible so to be expressed). In case of Bootloader I can make it by calling BootloaderMain() from main(). How can I make it in my case? Perhaps, I have not correctly understood OEMLaunch behavior? And maybe in my case I don't need to place StartUp (OAL) at beginning of image? But then what?... Perhaps, I don't need to call KernelStart manually?... But who calls KernelStart?.. So, main problem is: how to "switch" from my own code to code that executed by OS. And how to initialize MMU correctly in my case. Thank you all very much! And excuse for my very bad English... Regards, Sergey. Tag: JTAG Debugger for Windows CE Tag: 78545
  - 24
    - Sampling GPIO 1 ms Dear Greats, I am starting to develop on driver that should look for a the signal coming from a GPIO pin. My driver needs to sample that pin for 1ms. Is it possible for me to sample the GPIO pin for 1ms. I have a GUI to display this data after processing. Kindly help me finding out a reliable design to get this performance in Windows CE 5.0, X86 hardware, 800 MHz. What my idea, I searched some of the previous threads for getting a reliable 1ms timer, Is it possible to share the timer interrupt for my driver to get a 1ms sampling. Kindly pass on you ideas. Thanks in advance. avkumar Tag: JTAG Debugger for Windows CE Tag: 78544
  - 25
    - usb problem in cepc pls help me, I am using 945 mother board. When i try to load usb driver. It is not getting loaded. When i see the debug window it shows uhci.dll is getting loaded. But i have support for USB2.0 which is ehci.dll. I want to cepc to ehci.dll instead of uhci. I have included platform.bib to include ehci. I feel the pci enumerator is creating this problem. Even i set the noconfig value to 1. To stop loading this. But it is still loading uhci. Can any tell me how to solve this issue. Thanks in advance Jim Tag: JTAG Debugger for Windows CE Tag: 78536

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.

Top

Re: JTAG Debugger for Windows CE by Marco

Marco
Wed Dec 28 10:23:53 CST 2005

> 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.

ARM Multi-ICE eXDI don't support PB 5.0 but only 4.2

IMHO
the best (and most expensive) choice is Lauterbach
second place to EPI Majic probe.

Best regards
happy new year

-- Marco Cavallini
=====================================================
Koan s.a.s. - Software Engineering
Linux and WinCE solutions for Embedded and Real-Time Software
Klinux : the embedded distribution for industrial applications
- Atmel AT91 ARM Third Party Consultant
- Intel PCA Developer Network Member
- Microsoft Windows Embedded Partner
Via Pascoli, 3 - 24121 Bergamo - ITALIA
Tel. +39-(0)35-255.235 - Fax +39-178-223.9748
http://www.koansoftware.com - http://www.klinux.org
=====================================================

Top

Re: JTAG Debugger for Windows CE by Steve

Steve
Wed Dec 28 10:35:21 CST 2005

We use the EPI Majic and have had great success with it. It is certainly
possible to build systems without it. But that depends entirely on the
quality and flexibility of the BSP provided with the hardware. If you are
starting completely from scratch then there is no better an investment than
an eXDI JTAG debugger. The amount of time and money it will save you is far
exceeds its cost.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Top