Programación de Sistemas Empotrados y Móviles (PSEM)

Transcription

1 Introduction to Windows Embedded Programación de Sistemas Empotrados y Móviles (PSEM) Marco A. Peña marcoa@ac.upc.edu Table of contents Windows XP Embedded vs. Windows CE Windows XP Embedded Windows CE 2 1

2 Embedded systems and Appliances Devices are getting smarter Washing Machines VCRs, Digital Cameras Alarm Systems They have more to do More processing Communicate with other devices Communicate with your PC What s required is a general purpose OS that could be used for all computing appliances DSEM: Diseño de Sistemas Empotrados y Móviles 3 Windows XP Embedded vs Windows CE Processor Support Win32 API Compatibility WINDOWS XP EMBEDDED Supports x86 CPUs only - brings the PC model and benefits to embedded Provides full Win32 API compatibility enabling users to leverage DTOS work WINDOWS CE.NET Supports multiple processors SuperH, ARM, MIPS, x86 Requires additional effort to run DTOS apps Footprint Provides for basic images from 8MB ( Hello World ) Provides for basic images from 200 KB Real-time With 3 rd party extensions Native 4 2

3 Windows XP Embedded 5 What is Windows XP Embedded? Componentized version of Windows XP Professional Approx 10,000 Components 8,000+ components are drivers Same binary components as XP SP1 Additional OS features for Embedded specific scenarios Remote Boot Device Update Agent Headless Support R/O Boot Media (CD, Flash) 6 3

4 XPe Development Tools Target Analyzer Simplifies configuring OS image for target hardware Generates XML definition of target hardware Component Designer GUI tool used to create components for use on embedded devices Developer specifies the files, resources and dependencies required by the component 7 XPe Development Tools Target Designer GUI tool used to build runtime images End-user selection and configuration of OS, App or macro components Automatic inclusion of required Windows components Build ; assembles the bootable OS image Component-based documentation 8 4

5 XPe Development Overview Target Analyzer Component Designer Target Designer Hardware Definition App, OS and EEF Components OS Image Application Binaries XPe Component Database 9 Application and Hardware Development XPe applications are Windows applications Target Win32 or.net Framework Visual Studio PC based development and test Component based installation Author components, not setup Components are unit of servicing, distribution XPe devices are built on commodity PC hardware X86 CPU Standard or reduced motherboards PC devices and drivers 10 5

6 Componentization Windows NT Embedded 4.0 (Impala) Post product ship 18 months effort Minimal componentization -<20 major components Minimal driver support Large amount of effort to build and ship devices Windows 2000 (Skipped to align with XP) Skipped align development with Windows XP Windows XP Embedded (Mantis) Windows Feature Teams owned componentization and o/s dependencies, such as: Shell needs Internet Explorer Internet Explorer adds Outlook Express RDP Client needed DirectX (this is fixed in SP1) 11 Componentization Next steps Componentization is core to Longhorn release Componentization enables SKU Agility for Longhorn Client Reduce cost of new SKUs, increase ability to respond Home, Professional, Media Center, Tablet, Embedded Windows teams running atomic testing of components against minwin and full operating system images Deliver Component Database for Longhorn Embedded Reduce footprint for targeted embedded scenarios Aiming i for < 32MB bootable bl images 12 6

7 Windows CE (.NET) 13 Goals Create an OS suitable for building intelligent appliances Focused function (not general purpose) Broad range of hardware Smaller systems Resources typically limited Often portable, battery operated Should still be easy to use, with rich functionality Allow OEMs to customize OS Rapidly configure OS to meet precise functional requirements Minimal memory footprint 14 7

8 Some history Started life as an object-oriented OS for two products: Set-top-Box (Interactive TV) Pulsar (Handheld Personal Digital Assistant) However, needs of the different products quickly diverged: Pulsar had tight memory constraints ITV required large amounts of memory Pulsar team tried porting WinNT (to maintain Win32 compatibility), but result was simply too big for devices 15 Some history Fall of 1994 Bill Gats reviewed of Pulsar, plus another handheld product being worked on at Microsoft: WinPad Ran a different OS known as Microsoft At Work, based on Windows 3.1 Designed for office equipment (Copiers and Fax Machines) Result: Scrapped both WinPad and Pulsar! 16 8

9 Some history Started a new project Windows Companion Device Initially used the same object-oriented oriented OS, but OS team were slow at fixing bugs, adding new features Also found it difficult to build applications (not Win32 compatible) So secretly started writing a brand new OS from scratch Preserved Win32 API using new, optimized code: Carefully selected subset of the Win32 APIs Took the What do we need? approach 17 Family of Operating Systems Windows Mobile Platform Builder Windows CE 18 9

10 Overview of Windows CE Developed from the ground up, specifically for the embedded system and appliance market Features include Small Footprint Highly Modular Architecture Componentization Quick/easy to customise OS for a particular system Wide range of hardware support Runs on lots of processor architectures Real-time Support Crucial for time-critical embedded systems Aggressive Power Management 19 Overview of Windows CE Embedded 32-bit, real-time, preemptive multitasking operating system Win32 based API Familiar software development tools & SDKs Highly componentized & scalable OS is delivered as a granular set of OS components Hundreds of components provided in catalog OS image is configured via Platform Builder tools Footprint scales with Functionality Selected Minimum OS footprint: 200kB Maximum OS functionality: IE, WMP, WM, etc... Supports a wide variety of CPUs 20 10

11 Modular Architecture OS is divided into 202 modules (EXE/DLL) Modules can be divided into many components Each component is a.lib file Components are ROMable, Compressable (can execute from ROM or Flash) OEM s can make decisions about features, performance and size: Smallest about 400K Networking (no graphics) about 800K GWE, Shell and Apps about 4MB Internet Explorer for Windows CE about 3MB 21 Hardware Support Windows CE is designed to be portable Supports five processor architectures ARM/StrongARM, MIPS, PPC, SuperH, X86 OEM adapts OS to specific hardware configuration Drivers for interrupt services, etc. OEMs also provide power management functions OS uses these for instant-on, battery management 22 11

12 Real-time support Real-time support is essential when dealing with time-critical applications! Windows CE provides bounded, deterministic response times Low Interrupt Service Routines and Interrupt Service Threads (ISR/IST) latencies 23 Power Management Windows CE designed to work on battery-powered devices Advanced power management features intended to minimize power usage Functions include: Instant On Allows Windows CE devices to be powered off and then turned on instantly if the device has non-volatile RAM OAL allow OEMs to turn off unnecessary hardware components 24 12

13 Tools: Operating System Development Platform Builder Integrated Development Environment for all aspects of OS configuration, build, debug and test. Graphical UI for adding / removing components Drag and drop component features Dependencies automatically handled Emulator Target Emulator like any hardware platform Runs in a desktop window Distributable with your SDK to 3rd parties Skinnable to reflect your product (w/ hw buttons) Source Code Viewable Source Access for debugging. 1.5 Millions lines 25 Tools: Application Development Visual Studio.NET for managed code Developers productivity #1 goal Platform interoperability is important Preview ships with Windows CE.NET embedded Visual C++ (based on VC++ 6.0) for native code Performance is #1 goal Lowest level of control Smallest working set 26 13

14 Debug Support KITL Debug over any communications channel Kernel Independent Transport Layer Device side and host side code. Abstracts the protocol from the communications USB, Ethernet, and Serial transports included Use the same net card for application and debug Extensible add additional debug support. 27 Board Support Packages Available for a Selection of CPUs Design flexibility 4 Major CPU architecture families ARM/SA/XScale, MIPS, SH, x86 Over 2000 CPU types 10 integrated Board Support Packages (plus emulator) Extensible CPU/BSP plug-in model for 3rd party BSPs BSP Wizard, Export Wizard and other PB tools avail Third parties can install BSPs for their hardware into Platform Builder 28 14

15 Windows CE Architecture 29 Preguntas y respuestas 30 15