Want to play around with Windows Embedded Compact 7 and the latest BeagleBoard from TI?

Want to play around with Windows Embedded Compact 7 and the latest BeagleBoard from TI?

  • Comments 2

This year at ESC Boston, the now well-known Build Your Own Embedded System (a.k.a. BYOES) program will give you a chance to learn how to design a Windows Embedded Compact 7 OS and deploy it on a BeagleBoard-xm, the cool tiny inexpensive board from Texas Instruments. You can also purchase the kit and walk away with your own device at the end of the 2 days of training.

Windows Embedded Compact 7 is the next generation of Windows CE embedded real time operating system. During this 2 days training that will take place in Boston during the Embedded System Conference, you will learn how to use the new tools to build an embedded OS, deploy it on a real hardware, debug and test it before developing applications for it. You will also be given a chance to play around with Silverlight for Windows Embedded, the latest and greatest XAML based technology enabling developing high end user interfaces for devices (you can read more about Silverlight for Windows Embedded here).

This training will be delivered by MPC Data, long time Windows Embedded partner and active developers of a BSP for the Beagleboard.

You can register for ESC on this page, I look forward to see you there!

Leave a Comment
  • Please add 1 and 8 and type the answer here:
  • Post
  • From what I have been able to see so far, WEC7 is basically CE6 + a new UI, networking stack and graphics stack.

    Is there a URL to something providing a deeper look at the kernel?

    Some things I'm still trying to find out:

    * Is WEC7 based on a new kernel or is it still a CE6 kernel?

    * Has the driver and FSD model changed from CE6 to WEC7? How much effort is involved in changing from CE6 to WEC7?

    * Do the same fundamental CE6 limitations apply? Single CPU etc.

  • @Charles

    For now we don't have public material covering this level of details, but I can answer to most of your questions here:

    Compact 7 kernel has not much changed from CE 6.

    Some of the fundamental limits have been changed, like the RAM supported (up to 3GB now vs. 512MB in CE 6).

    Compact 7 will support SMP on ARM.

    The port of a BSP from CE 6 to Compact 7 will not be as important as it was from CE 5 to CE 6.

    Here are some of the things that will need to be taken of when porting a BSP from CE 6 to Compact 7:

     - Sources paths have slightly been resturctured (nothing big, just a few environment variables will need to be changed in sources.cmn file and some makefile.inc files

     - RNE_MDD has been relocated

     - vbridge has been moved into oal_kitl (vs. being a standalone library)

     - Dependencies to DEBUGZONEs were added when generating a debug version of CEDDK. As a result ddk_main.lib needs to be linked against for a successful debug build

     - DEFINE_GUID macro has been fixed, so static declaration in the soruce file should be deleted and the DEFINE_GUID macro should be used

     - Some PFN_EDBG_XXXX_EEPROM function typedefs' have been removed

     - ENABLE_OAL_TIMING has been removed

     - Some other minor changes in the Installable ISR, some language dlls removed, location of SystemHive needing to be enforced and some profiler API prototyp changes will require some attention

    This list is not exhaustive and some things might change by RTM time, but this gives you a rough idea on where changes occured.

    A full document on porting from CE 5 or CE 6  to Compact 7 will be publised at RTM time.

    -Olivier

Page 1 of 1 (2 items)