It is when CE and other full-featured embedded systems. Use the corresponding higher levels of integration, lower cost to reduce tasks, and increased performance makes a new application possible. Windows Ce running on the PDA has been launched for nearly two years, and with some large electronic manufacturers, like Matsushita (Panasonic) and Hitachi, it has also been selected as some set-top device design and other consumer electrical operations. system. Although these consumer applications are the most visible applications for Windows, Microsoft and their partners are busy developing hundreds of other applications for a wide range of traditional or non-consumer embedded systems. The embedded design is CE to win industrial control, data collection, sales point, rugged handheld products, and network devices and other industries. As the manufacturer puts these products in the next three to nine months, the broad scope of the CE program will increase significantly. What is WindowsCE Windowsce is the latest member of the Windows operating system family. But it is not a part or reduced version of WindowsNT or Windows9x. Windows Cels have its own system structure, with independently developed kernels and unique device driver models. CE is different from its desktop, it is originally designed to take up less memory applications, that is, the use of operation, microprocessor portability, and power conservation. In terms of application development and functional characteristics, CE also enjoys a key section of WindowsNT and Windows9x. WindowsCE supports a subset of more than 600 WIN32 applications (ApplicationProgramInterface, APIs) for desktop operating systems, including built-in networking technology, and provides the same component technology (including COM / OLE and dynamic link libraries). In addition, CE supports the same desktop development tools Visualc , VisualBasic, and VisualJava and supports Microsoft Extended C , including structured exception handling. Why is WINDOWSCE? It is when CE and other full-featured embedded systems. Use the corresponding higher levels of integration, lower cost to reduce tasks, and increased performance makes new applications, which makes it possible to increase interconnects and richer features in existing applications. The complexity and differences of embedded systems are gradually transferring from hardware to software. If a software platform is based on a suitable software platform, software-oriented systems will provide greater flexibility to adapt to market demand, so that all production lines tend to be general, and reduce the time of launching market. CE focuses on software and software developers more than its competitors. WindowsCE provides the following significant advantages for embedded system developers: 1.Win32API. WindowsCE uses the same basic API with WindowsNT and Windows 9x. These are the same APIs used by more than 2 million software developers worldwide. The universal dissemination of the API enables development team to balance developers' skills to reduce the time of repeated training and increase access to existing developers. Increased demand analysis for software part of embedded systems means that software developers are the key to reducing development costs and speeding up market time. 2. Development tools. Used for WIN-sending tools and technologies with the same use in WindowsNT and Windows 9X. Existing tools for CE include Visualc , VisualBasic, and Visualjava; these are running on a WindowsNT system, and most software developers can generally get them. This again, the developer's production capacity is direct by the versatility of tools, technology and development systems. 3. Software integration. WindowsCE is an integrated operating system that includes graphics, window management, and networking technologies, as well as basic operating system support, such as timers, interrupt processing, and synchronous primitives. Microsoft has integrated these components and tested this integrated software system.
With Windowsce, embedded system developers do not have to look for these components from a number of suppliers, then integrate them together and test the entire system. 4. Processor support. Although Windowsce is a young operating system, it has supported a wide range of microprocessor architecture, including CISC and RISC. Currently, WindowsCE supports Hitachi's SH, MIPS, PowerPC, ARM, and X86 architectures. Usually there are multiple variants per structured series. The CE embedded designer has a wide range of microprocessors to choose from to optimize the performance, power consumption, component size, cost, and integrated peripherals. Development tools and operating system components are consistent in all architectures, so this provides flexibility for balancing software between systems, even when the base microprocessor is not the same. 5. Third Party support. The focus is placed on the software and encourages the third-party independent software vendor (ISV, Independentsoftware "to develop and sell software that can balance between various design. Microsoft has a huge interest in the CE platform through its market share, existing ISV relationships and sales efforts. ISV software has become increasing, developing tools, device drivers, applications, and components. This shows that the embedded designer has an opportunity to balance the existing work, reduce project risk, development costs, and market time. WindowsCE is a software-centric embedded development model. This model-based model produces a large number of components and applications, and developers have time to increase the role of each development project. Microsoft supports its existing developers, tools, and technical bases means that Windowsce will continue to enjoy its competitors no significant advantages. EmbeddedToolkit (ETK, Embedded Toolbox) for CEs is a software development box for embedded WindowsCE development boxes that support system-level and applications. ETK consists of Visualc (VC ) development environment, programming tools, and two-way WindowsCE operating system components. The toolbox includes a cross-compiler, assembler, and a remote debugger, which are used to integrate all supported microprocessors integrated into VC IDE (IntegratedDevelopmenvironment, integrated development environment). Target compilation and debugging for a particular microprocessor structure is just to change a setting on a VC menu. Developed on a WindowsNT host system connected to a separate WindowsCE target device with a separate Windows Ce Target device. Write and compile the code on the host and then download the code to the target by interconnect. Debugging is remote and through interconnection. The CE operating system for embedded design is established from the components provided by Microsoft and the components developed by the designer. Basic components are provided in the form of a library or a dynamic link library (DLL, DynamiLinkLibrary). In some cases, an executable image and a DLL are formed by a component (device driver and system function) specified by the link system to the base base part. In an index file, select the program part included in the final operating system creation, then perform a compile image program to create a WindowscerOm image. This program performs many functions, which are like typical desktop load functions, such as image repositioning and collection of DLLs. The final ROM image is suitable for XIP (ExecuteInplace, on-site execution) or RAM execution. ETK also includes an extension simulation environment for application development. The emulator performs WindowsCE virtual versions on a desktop computer, allowing to run compilation-commissioning cycles locally in the absence of a WindowsCE target device. The simulation environment accelerates the development cycle by reducing program download time and remote debugging.
Moreover, the simulation program can also be used to develop application software before obtaining a working prototype hardware, reducing the sequentialization of the development process. BSquare estimates that the development of 90 can be done in the simulation environment for typical applications. The remaining 10 (debugging and testing) is done on the actual target hardware. The development cycle is the step of successfully developing a WindowsCe embedded system (Ignore the main steps for definition and sales products): Design WindowsCE hardware system; transplant Windowsce to target hardware; create user interface; write software application layer . OEM also needs to collaborate with Microsoft or Like a salesman, such Microsoft, to get WindowsCE licenses for WINDOWSCE licenses. Most of the hardware design is determined by the product demand. But some requirements and considerations of CE will affect the design of the hardware system. For example, the designer chooses a microprocessor supported by Microsoft in the WindowsCE version of the desired WindowsCe. Designers must consider some requirements for CE, including one interval timer and the annual clock. The memory requirements for XIPROM, RAM, and non-volatile memory are for applications, to a large extent, depending on the required operating system components and software applications. Designers need to consider memory persistence or non-volatile memory requirements, as CE is not a disk operating system; instead, it stores data in a target storage area that may be located in RAM or non-missing memory. For devices with direct user interface, the designer can select the touch screen indicator or finger input, or select the mouse input. (CE supports both.) In addition, CE allows you to select LCD or display. Transplanting Windowsce transplays Windowsce into the hardware include the following steps: Writing the boot program Write an OEM adaptory layer (OAL) Write the device driver. Guide program. The boot process is a piece of code executed when the system is powered up (or after restart). The boot program is responsible for initializing the hardware system, loading Windowsce, and then start execution. It can be a medium complex extent, depending on the required system configuration and the number of debugged supports. The boot program will establish an initial microprocessor configuration, configure any system board ASIC, and may define the size of the cache and memory (e.g., DRAM timer) and configure them, and execute bus configurations (eg, PCI bus configuration). Many functions of the bootstrap are similar to the initialization function of the BIOS on the desktop PC. 2.oal.oal is a small part of the code dedicated to the system and microprocessor, its abstraction system-level hardware function (such as interrupt processing, cache control, hardware timer, and kernel clock). 3. Device driver. The device driver provides an abstract concept between peripherals and operating systems. The WindowsCE driver supports a wide range of devices, including input devices, display devices, sound generators, network interfaces, and communication devices. The working range required by the development of the driver depends on the complexity of the device itself, whether the existing driver is used, and the number of drivers required. If you want to create a fully debugged device driver for the platform, you need a certain amount of effective job. The designer has a variety of options to shorten the development cycle of the WindowsCE port. Third-party ISV provides source code tools to design a supply boot program, OAL, and device driver for a particular microprocessor. BSquare is currently providing tools for Amdelansc400, CyrixMediagx series, Strongarm1100, MotorolappC821, AMD-K6, NEC4300, and Hitachism7709. Extra tools will be developed as long as the processor is launched and the market is mature. User interface, desktop or peripheral is a key decision for CE embedded design.
