Windows Embedded CE / Compact live chats

Windows Embedded CE / Compact live chats

  • Comments 8

If you are not aware, the Windows Embedded CE/Compact team regularly sets up live chats for you to come and ask questions about their product.

You can find the dates and info on this MSDN page or below. Next one will be on July 27th. No specific agenda, you just jump in and ask questions.

July 27, 2010
9:00 - 10:00 A.M. Pacific Time
Additional Time Zones

Enter Chat Room
Add to Calendar

August 31, 2010
9:00 - 10:00 A.M. Pacific Time
Additional Time Zones

Enter Chat Room
Add to Calendar

September 28, 2010
9:00 - 10:00 A.M. Pacific Time
Additional Time Zones

Enter Chat Room
Add to Calendar

October 26, 2010
9:00 - 10:00 A.M. Pacific Time
Additional Time Zones

Enter Chat Room
Add to Calendar

November 30, 2010
9:00 - 10:00 A.M. Pacific Time
Additional Time Zones

Enter Chat Room
Add to Calendar

December 28, 2010
9:00 - 10:00 A.M. Pacific Time
Additional Time Zones

Enter Chat Room
Add to Calendar

Leave a Comment
  • Please add 4 and 6 and type the answer here:
  • Post
  • Hello,

    I have development board with intel atom z5xx processor . I have built X86 BSP for my board.

    I want to bring windows ce 6.0 on my board. I have made bootable floppy disk using makeimagedisk.exe utility. Problem is after execution of loadcepc.exe, i'm getting a message- Jumping to address 0Xdddddddd; and after this nothing happening. so WinCe is not booting up.

    Help me to bring Windows Ce on this.

    Regards

    AGG    

  • @AGG

    Hi, for an Atom processor, I would recommend to use the ATOM BSP rather than the basic CEPC one. You can find it on Adeneo's Web site: www.adeneo-embedded.com/.../show

    - Olivier

  • I'm confused, can you tell me the steps to bring up wince 6.0 on my X86  based device with Atom processor.

    I'm very new to this.. Please help me to port WINCE6 on X86 based device.

    Thanks  

  • @AGG

    Well let me point you to some online training material, as explaining the full process would make for a full article :-).

    So take a look at MSDN, there you will find all the training material you need to get started with CE: msdn.microsoft.com/.../default.aspx

    -Olivier

  • Hi Olivier Bloch ,

    Thanks for your replay, Now i'm running  Nk.bin directly on my x86 device using USB. I want to use CF card on my device,  but not able generate  correct eboot.bin,

    This is spec of my Device

      - X86 platform

      - atom Z5xx processor

      - RTL E100

    when i run my eboot.bin, this is the display on hyperterminal.

    Microsoft Windows CE Bootloader Common Library Version 1.4 Built Oct 19 2010 11:

    11:41

    Microsoft Windows CE Ethernet Bootloader 3.7 for CE/PC (Oct 21 2010)

    Boot Args @ 0x201F6 and  ucLoaderFlags is 1

    PCI Device Configurations (4 PCI bus(es) present)...

    ========================================================

    Bus, Device, Function = 0, 2, 0

    Vendor ID, Device ID  = 0x8086, 0x8108

    Base Class, Subclass  = 3, 0 => DISPLAY_CTLR

    Interrupt             = 4

    BaseAddress[0]        = 0xF0080000 (Memory)

    BaseAddress[1]        = 0x1800 (I/O)

    BaseAddress[2]        = 0xE0000000 (Memory)

    BaseAddress[3]        = 0xF0040000 (Memory)

    ========================================================

    Bus, Device, Function = 0, 27, 0

    Vendor ID, Device ID  = 0x8086, 0x811B

    Base Class, Subclass  = 4, 3 => MULTIMEDIA_DEV

    Interrupt             = 10

    BaseAddress[0]        = 0xC8020000 (Memory)

    ========================================================

    Bus, Device, Function = 0, 29, 0

    Vendor ID, Device ID  = 0x8086, 0x8114

    Base Class, Subclass  = 12, 3 => SERIAL_BUS_CTLR

    Interrupt             = 10

    BaseAddress[4]        = 0x1820 (I/O)

    ========================================================

    Bus, Device, Function = 0, 29, 1

    Vendor ID, Device ID  = 0x8086, 0x8115

    Base Class, Subclass  = 12, 3 => SERIAL_BUS_CTLR

    Interrupt             = 7

    BaseAddress[4]        = 0x1840 (I/O)

    ========================================================

    Bus, Device, Function = 0, 29, 2

    Vendor ID, Device ID  = 0x8086, 0x8116

    Base Class, Subclass  = 12, 3 => SERIAL_BUS_CTLR

    Interrupt             = 4

    BaseAddress[4]        = 0x1860 (I/O)

    ========================================================

    Bus, Device, Function = 0, 30, 0

    Vendor ID, Device ID  = 0x8086, 0x811C

    Base Class, Subclass  = 8, 5 => BASE_SYSTEM_DEV

    Interrupt             = 10

    BaseAddress[0]        = 0xF0004400 (Memory)

    ========================================================

    Bus, Device, Function = 3, 0, 0

    Vendor ID, Device ID  = 0x10EC, 0x8136

    Base Class, Subclass  = 2, 0 => NETWORK_CTLR

    Interrupt             = 11

    BaseAddress[0]        = 0x2000 (I/O)

    BaseAddress[2]        = 0xF0100000 (Memory)

    BaseAddress[4]        = 0xF0400000 (Memory)

    ========================================================

    InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = B, dwIoBase = 2000, dwDfltT

    ype = 4) ...

    InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=11, IOBase=0x2000).

    RTL8139InitDMABuffer():: Start[0x200000]-[0x200000] - Size[0x20000]

    Tx[0x200000] - Rx[0x201800] - RxLength[0x10000] - RxLengthBit[0x1800]

    RTL8139:: built on [Sep  6 2006] [19:21:34]

    RTL8139Init():: BaseIO[0x2000] : MemOffset[0x1]

    RTL8139Init():: TxBuff[0x200000] - RxBuff[0x201800] - LastRx[0x2117FF]

    RTL8139Init:: MAC = 00-0F-02-02-00-11

    RTL8139 ethdbg library: perform auto negotiate.

    RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00

    Returned MAC Address:00:0F:02:02:00:11

    System ready!

    Preparing for download...

    OEMPreDownload  ucLoaderFlags is 0

    x86KitlCreateName: Using Device Name 'IA3217'

    Using device name: IA3217

    Using static IP address: 5002A8C0

    Duplicate IP Address Detected:

    -IP address 192.168.2.80 in use by device with MAC address 00:0F:02:02:00:11.

    -Requesting new IP address via DHCP...

  • @AGG

    It seems your eboot is configured to use fixed IP address (it seems to be using an IP address already used on your Network) and also seems to be confiured to boot an image from the Network, not from local storage.

    usually the CF card is seen as an IDE drive from which you can boot. You can setup the BIOs of the x86 machine to boot from this IDE drive.

    Let me recommend you to prepare your CF card using the tool diskprep referenced in this previous blog post, it will allow you to prepare the CF card to boot your nk.bin file: blogs.msdn.com/.../how-to-setup-a-virtual-machine-to-run-windows-embedded-compact-7.aspx

    -Olivier

  • Hi Oliver,

    Now i'm booting my nk.bin from USB successfully. Now i want to boot that nk.bin from CF card. can you tell me how to proceed.

    And another problem is i'm not able to enable Ethernet driver, i have RTL8139 ethernet card. Please help me.

    Best Regards

    Akash G

  • @Akash follow the instructions in my previous comment for CF boot, you should be good.

    For the Ethernet driver, the RTL driver should be available in the catalog. you might need to change the regitry settings for it.

    -Olivier

Page 1 of 1 (8 items)