This chapter addresses the Windows Embedded CE 6.0 R2 unified build system for OS images. The Windows Embedded CE tools use a unified build system. An operating system can be built by using the Microsoft Visual Studio 2005 integrated environment or by using the command line. The build tools are composed of batch files and console utilities. IXP4xx (IXP425, 422, 421, 420) BSP for Windows CE (wince/Windows Embedded Compact) 4.2/5.0/6.0/7.0 Downloads: 4 This Week Last Update: 2018-01-22 See Project 18. Technical information about “Windows Embedded CE 6.0 R2” available from MSDN Subscriber Downloads. Currently, you can find here information about 2 files. If you want to search for a specific file in the “Windows Embedded CE 6.0 R2” section, enter the file name, MSDN code, SHA-1 hash, or any keyword from the title or file description in. Windows Embedded CE 6.0 is a set of tools and technologies that you can use to create real-time operating system for a wide range of small-footprint consumer and enterprise connected devices. You can use Windows Embedded Compact to create operating systems for devices based on X86, ARM, MIPS, and SH4 architectures.

Windows Embedded Ce 6.0 Tools Free
Windows Embedded Ce 6.0 Tools Tutorial
Windows Embedded Ce 6.0 Tools Harbor Freight

Description

Building an embedded operating system image is only part of the process for releasing a final product - Testing and diagnosis tools should also be an integral part of the release process - an operating system image may appear to be running just fine, but how do you really know that there aren't any issues lurking unseen within the operating system image - it's possible that your processes could corrupt heaps, orphan CriticalSections and do other nasty things, but how do you find out this has happened ?
This video shows the use of CEDebugX, a new (and extremely cool tool) that ships with the Windows Embedded CE 6.0 SP1 update.
Note that in the video I'm creating a KDump file, if you are running a debug image (or have the kernel debugger in your release image) you can run CEDebugX directly from the Windows CE Command Prompt against the operating system image without needing to create a kdump file.
- Mike

Embed

Download

Right click or Alt+Enter to download this episode

Low Quality MP4 (43.3 MB)
High Quality MP4 (115.1 MB)
Mid Quality MP4 (74.1 MB)

-->

Mobilize

Explore The New Features In Windows Embedded CE 6.0

Paul Yao

This article is based on a prerelease version of Windows Embedded CE 6.0. All information herein is subject to change.

This article discusses:

Windows Embedded CE 6.0
Embedded development
Kernel innovations
Shared source implementation

This article uses the following technologies:
Windows CE

Contents

Overview of Windows Embedded CE 6.0
API Deployment Scheme
Kernel-Mode Operation
Memory Architecture
Device Emulator
Cell Technologies for CE 6.0
Location-Based Programming
Security Enhancements
Development Tools
Cool Tools
Registry File Editor
Runtime Image Viewer
Shared Source and Windows CE Development
Conclusion

The first version of Windows CE shipped in 1996. Since then, many new types of portable and embedded products have emerged-enabled by myriad advances in semiconductor components. In 1994, worldwide semiconductor sales hit the $100 billion mark, according to the Semiconductor Industry Association (SIA), and that number is expected to hit $250 billion for 2006. Along the way, the Windows® CE team has kept its fingers on the pulse of developers working in the embedded space, pushing the boundaries in each generation.

Overview of Windows Embedded CE 6.0

For each of its previous five versions, Windows CE has served as the foundation for a wide range of embedded devices. The newest version, Windows Embedded CE 6.0, continues the push forward, providing a whole new set of features-some of which you need to understand, and others you may just want to be aware of. (See the sidebar 'Inside Embedded Innovation at Microsoft'.)

Inside Embedded Innovation at Microsoft

The process of conceiving, planning, developing, and delivering a new version of a successful product is a huge undertaking—especially when that product is an operating system, albeit a small one. In the case of Windows CE, it involves a development team with upwards of 700 individuals. When planning new features, Microsoft solicits customer feedback in several ways. The best known feedback mechanism is the beta software program, whereby prerelease software is shipped to customers. But beta programs are not the only way to get input. The design and planning phases are bolstered with customer visits and design reviews to inject customer insights into the product development process.

At the start of the product planning process, the Windows CE planning team hits the road to visit customers around the world to learn about their current and anticipated product development needs. These visits occur shortly after the previous product version ships, because innovation is an ongoing process. On the basis of these visits, a draft development plan is created and reviewed internally.

With a draft development plan in place, the next step involves validating the plan at a design review where hundreds of people from outside Microsoft gather to provide input. I participated in a design review in June of 2005 for the CE 6.0 plan. This week-long event started with participants signing non-disclosure agreements (NDA) to facilitate open and honest discussion on both sides. The actual mechanics of a design review are pretty interesting. Major feature areas are first described by members of a development team. Each presentation ends with a question and answer period, and each participant uses a wireless voting box that was provided at registration. Immediately after each vote, the results are displayed for everyone to view and discuss.

By the end of the week, each participant may have provided hundreds of opinions on how the development team should set priorities. The value of the exercise can best be measured by the new insights that development teams have gotten when they put their tough questions in front of customers who are relying on the presence of some feature in a future product version.

The specific features of interest to you will depend on the type of gadgets you are working with. If you're a designer of headless industrial controllers, it's likely you have a different set of needs from a software developer creating the next generation of sewing machine applications. Both are likely to define what's interesting in ways that might not make sense to a developer of mobile phone applications. You get the point.

While Windows CE is the foundation for many types of gadgets, you often get the impression that it's split into two camps: Windows Mobile®-powered devices and custom embedded devices (in other words, everything else). But can one platform support both standard and custom devices? Yes, Windows Mobile and custom embedded devices are linked by a vast technology portfolio that includes a small but capable multithreaded kernel, a rich family of programming APIs-Win32, MFC, and the .NET Compact Framework-and a powerful, extensible set of development tools.

Windows Embedded CE 6.0 (CE 6.0) introduces a new kernel that overcomes limitations of earlier kernels, while squeezing more performance out of those tiny CPUs. In this article I'll describe the new CE 6.0 operating system capabilities beginning with those that pertain to the new kernel: a new API deployment scheme, new use of kernel mode, and the memory architecture. I'll then cover other new features of CE 6.0.

Finally, I'll go over the new tools for configuring, building, and testing the myriad Windows CE configurations. The discussion of tools is aimed squarely at developers of embedded applications who create custom Windows CE configurations. But if you're a Windows Mobile developer and are tempted to skip this second half, I urge you to keep reading, paying special attention to the discussion of Windows CE shared source. It's a mandatory resource for anyone who wants the inside scoop on Windows CE that only the source code can provide.

API Deployment Scheme

One of the strengths of Windows CE is that its development benefitted from the features and optimizations of the desktop versions of Windows. Starting with the first version of Windows CE and including ever

Windows Embedded Ce 6.0 Tools