Find all the test info that you need at the Windows CE Testing Tools web portal!
Building strong, reliable embedded devices is critical in today's market. Testing a device or driver can involve assessing many different elements from security, to usability, to performance. This is why Microsoft is working to provide the following tools and resources that will work in conjunction with your testing efforts.
Tutorials
Documentation from MSDN
Windows CE Test Kit
Test device drivers or a platform that you created with Windows CE by using the Windows CE Test Kit (CETK) tool. |
Windows CE Test Kit Tests
Explore the variety of pre-defined tests that are included in the CETK to quickly test a driver or the stability of a platform. |
MSDN Technical Articles
Tools and Resources
Download the Windows CE 5.0 Standalone Test Kit
This kit is a collection of tests and tools that can be used to help verify the stability, reliability, and quality of a platform or device running Windows CE 5.0. This download is intended to be used on systems where Windows CE 5.0 is not installed; however, it is the same kit as the one included in the Windows CE 5.0 product and is used in the same way. |
Windows CE Testing Newsgroup
Exchange information with other Windows Embedded systems and application developers about Windows CE test tools. This is also available through a newsreader. |
CODESNITCH
Get information about this code analysis tool for Windows CE. |
Programs
Windows CE Driver Validation Program (DVP)
DVP is designed to give developers, Independent Hardware Vendors (IHVs), or original equipment manufacturer (OEM) licensees of Microsoft Windows CE the opportunity to validate their drivers for use with Windows CE operating systems. |
I've been asked why we used the name "Yamazaki" as a codename for CE 6.0 - There's some history behind the naming of Windows CE versions, here's the short version...
Before the Windows CE product was released we had an internal set of tools known as the Oem Adaptation Kit also known as the OAK - an OAK of course is a type of tree.
The initial releases of Windows CE were therefore named after trees, as follows.
- Windows CE 1.0 - Alder (Nov 1996)
- Windows CE 2.0 - Birch (Nov 1997)
- Windows CE 3.0 - Cedar (Apr 2000)
Interestingly, there was a second team within the Windows CE group that worked on the tools, I guess you could consider tools to be something that makes a job easier, or cuts the job down to size - therefore the tools releases were named after things that cut down trees - as follows...
- Windows CE 1.0 - Alder - Tools: Axe
- Windows CE 2.0 - Birch - Tools: Buzzsaw
- Windows CE 3.0 - Cedar - Tools: Chainsaw
For Windows CE 4.0 the original plan was to call the O/S DougFir (DouglasFir), the thing that cuts down DougFir trees was going to be Dozer (BullDozer) - interestingly, at Windows CE 4.0 the o/s team and tools teams merged together to form a new, combined team - the codenames for the operating system and tools also changed at this time from trees/tools to <drumroll>Whiskeys</drumroll> - so the codenames for Windows CE 4.0 onwards are as follows.
- Windows CE 4.0 - Talisker (Jan 2002)
- Windows CE 4.1 - Jameson (Jun 2002)
- Windows CE 4.2 - McKendric (Apr 2003)
- Windows CE 5.0 - Macallan (Aug 2004)
- Windows CE 5.0 Network Device Feature Pack - Tomatin (Apr 2006)
- Windows CE 6.0 - Yamazaki (Sep 2006)
Don
*originally posted on Mike Hall's Weblog
The contest, which ran from May 23 through July 28, challenged developers to create an exciting Windows CE-based real-world project. The official theme of the contest, co-sponsored by Microsoft's Mobile and Embedded Devices (MED) group and WindowsForDevices.com, was "Show-It-Off at the Shared Source Project Competition." Contest participants were encouraged to create cool, practical projects combining Windows CE 5.0 along with either or both of two Shared Source components -- the Windows CE WebCam driver and/or the Windows CE DVR engine.
|
|
Virtual Labs for Windows CE 6.0
Register for the Windows CE 6.0 virtual lab "Introduction to Building/Debugging Operating System Images." The objective of this virtual lab is to provide an overview of Windows CE 6 platform builder features. To achieve this you will create, customize, build, download and debug a Windows CE image on the Microsoft Device Emulator. Visit MSDN Virtual Labs for more information. |
|
|
Two Windows XP Embedded Sessions to Be Presented in TechEd China in September
Two sessions on Windows XP Embedded will be presented in TechEd China to be held in 3 cities Beijing, Shanghai and Guangzhou in late September. The two sessions are:
Session 1: Quick Introduction to XPe. It covers the basics of the Tools, Components and Enabled Embedded Features, explains benefits of XPe over XP-Pro and a basic comparison of XPe to CE. It will also cover how to use XPe to bring your devices to the market in the Embedded Ecosystem. It's a 100 level presentation. Target audience would be people not familiar with the platform at all. It's also good for CTOs to IT Pros and developers familiar with other embedded platform, such as Windows CE.
Session 2: Discussion of XPe's Tools, Components and Enabled Embedded Features in length with demos. It will also cover the work we're doing in the Feature Pack due to RTM this fall. It is a 200 level presentation that builds on the first presentation above. The session will demo building a runtime using CHS MUI to show the benefits of XPe over XP Pro. It will also demo other key features of the latest release XPe SP2, plus some new features from the Feature Pack to be released.
If you are going to the conference, be sure to check out the sessions. For more information on TechEd China, please check the website: http://www.microsoft.com/china/technet/TechEd/default.asp. |
|
|
Windows XP Embedded Feature Pack 2007 Community Technology Preview Released
We are excited to announce that on July 31st we released the first Community Tech Preview (CTP) download for Windows XP Embedded Service Pack 2 Feature Pack 2007!
Among our biggest goals in this Feature Pack are to improve the developer's experience and to enable new capabilities and Microsoft technologies on your embedded device. The most interesting aspects of this Feature Pack are:
|
• |
New EEFs! Such as File Based Write Filter and Registry Filter. |
|
• |
USB Boot! Yes, this is native USB Boot capability in XPe! |
|
• |
Enhancements to EWF and Hibernate Once Resume Many |
|
• |
Many of the bug fixes you've been asking for in the Tools (such as Target Designer, CMI, Import Framework, SLX/XML usability) |
|
• |
New command line tool that replicates Target Designer, enables you to script your builds and much much more! |
|
• |
Tons of work on component dependencies to reduce footprint (including removing dependencies to the full "Internet Explorer" component!) |
|
• |
We've added new configurable UI to common components to simplify your offline configuration of images |
|
• |
New components added to the database to address more Application Compatibility challenges |
|
• |
New macro components to allow installation of other Microsoft technologies in your runtime |
|
• |
All security patches for XPe-SP2 rolled up to the Feature Pack repository |
|
For detailed instructions on how to join the program and participate in early testing, please visit the article on the Embedded Windows team blog site: http://blogs.msdn.com/embedded/archive/2006/07/10/660998.aspx
So far we have close to 1000 downloads and 35+ customer logged bugs from the Connect site. The Feature Pack is scheduled to RTM later this year.
|
|
Developers Needed to Participate in Microsoft Usability Research
Microsoft Usability Research has an ongoing need for professional developers to take part in Usability research studies. We need real feedback from real users to make the next generation of server products and developer tools better than ever. Usability studies typically take 2 hours or less and are scheduled at your convenience. You'll get to take a look at products under development, give us your honest feedback, and have a direct impact on the development of those products! In addition, each study participant will receive a hardware or software gratuity. Choices include several of our software packages such as Visual Studio Professional, Office 2003 Professional. Xbox games, wireless keyboard/mouse combinations and much more! Interested? Sign up today. |
Posted by Jason Hoobler
Jeff Han
Jeff Han is a research scientist for New York University's Courant Institute of Mathematical Sciences. Here, he demonstrates—for the first time publicly—his intuitive, "interface-free," touch-driven computer screen, which can be manipulated intuitively with the fingertips, and responds to varying levels of pressure. (Recorded February 2006 in Monterey, CA. Duration: 09:32)
http://ted.com/tedtalks/tedtalksplayer.cfm?key=j_han
Posted by Don Gambrell
Windows CE Device Emulator Goes Shared Source
Microsoft has released the source code to the Windows CE device emulator 1.0 that ships with Visual Studio 2005 under a shared source "academic" license. This makes the code available for "non-commercial teaching, research, and personal experimentation while attending or employed by an accredited educational institution," according to the license.
Windows XP Embedded SP2 Feature Pack 2007 Community Tech Preview Available in August!
In early August, Microsoft will release a Community Technology Preview (CTP) of its upcoming release of Feature Pack 2007 for Windows XP Embedded SP2. Feature Pack 2007 is designed to improve the developer's experience, and to enable new capabilities and Microsoft technologies for embedded devices. It provides new features, such as USB Boot, and enhancements to existing features and tools, such as Footprint Reduction and Console Application. You can sign up to participate in the CTP on the Microsoft Connect site and automatically be notified when downloads of Feature Pack 2007 are available. For more information and detailed instructions on how to sign up visit the Windows XP Embedded Team blog.
Visual Studio 2005
Visual Studio 2005 will introduce a wave of productivity enhancements designed to assist all members of the software development team. These virtual labs are based on pre-release versions of Visual Studio 2005, and deliver a sneak-peak of what's coming! It's simple -- no complex setup or installation is required to try out Visual Studio 2005 running in the full-featured MSDN Virtual Lab.
New Windows CE Community Projects!
Windows CE Driver for Phidgets: Using the Windows CE Shared Source Webcam driver and the Windows CE Sample Shared Source, Phidgets Inc. developed a Windows CE Driver for its USB sensors and controllers better known as phidgets. You will not only be able to use phidgets like servos or RFIDs on Windows CE, but you will also be able to access the source code to the driver, access phidgets and other Windows Embedded community projects here.
LSP Samples: With this community project, you can access the code necessary to create LSPs (Lightweight Streaming Protocol) on Windows CE and Windows Mobile, access LSP Samples and other Windows Embedded community projects here.
-----------------------
********* All the preceeding information was just a portion of August's newsletter made available by Window Embedded DevWire. To sign up to recieve DevWire E-mail click here.
- Jason Hoobler
Legal Information
Have you heard about the Windows CE Shared Source program?
===== If YES -->
If you are already familiar with this resource and have used it to help your development work, then Microsoft wants to here from *you*. Skip to the bottom of this email, click on the link, and take the survey. Your input will help with work going on right now to improve this important program.
===== If NO -->
If you are not familiar with this program, or have heard about it but want to learn more, then read on. Most mobile and embedded developers, it seems, have not accessed the CE source code. For example, many Windows Mobile application developers that I speak with do not know about it. Or they know about it, but have not tried to find it -- perhaps thinking that it is too expensive, or only available with some onerous licensing agreement.
===== What Is CE Shared Source Program??
Microsoft introduced the Windows CE shared source program back with Windows CE 3.0. It was introduced to help developers in debugging Windows CE projects, and also in learning about this OS. It was such a success that Microsoft has continued to expand the program. Today, you can use this source code to see how the Windows CE kernel allocates memory, opens files, and creates processes and threads. You can see the exact steps involved in system startup, as well as learn about the inner workings of web servers, message queues, and much, much more. (Why do I feel the sudden need to say that "this offer is not available in any store?... ;-)
===== To Obtain Eval Versions of Platform Builder If you want to get your hands on it, you can download and install an evaluation version of Windows CE 5.0 Platform Builder. During installation, you have to click the option to install the source code and then click the license agreement. After that, you will find the source code in the following location: the \wince500\private subdirectory.
Download (or order a CD) the eval version of PB for CE 5.0 at this URL: http://msdn.microsoft.com/embedded/getstart/evaluate/default.aspx
===== Take the Survey - Help Yourself Out For those of you who have used the shared source code, Microsoft wants to hear from you! Nic Sagez, the program manager in charge of the Windows CE source code, has asked me to invite you to participate in a survey. If CE share source has been helpful to you in the past, then you will want to click on the survey link right away and make sure that Nic and his team know about other source code that you might need.
Here is the link for the survey:
https://live.datstat.com/MED-Collector/Survey.ashx?Name=Shared_Source_Survey
On behalf of Nic's team, thank you for taking the survey and helping make the CE shared source programs be the very useful resource that it is.
Best,
Paul Yao
WE-DIG (http://www.we-dig.org/)
The Puget Sound Handheld Users Group (PSHUG) holds a meeting on the fourth Tuesday of each month at Microsoft's Redmond campus to discuss mobile software, services and new devices. Here is a summary of what was discussed at this month's meeting:
Xbox Live Anywhere - http://www.microsoft.com/presspass/press/2006/may06/05-09E32006BriefingPR.mspx
- The new service announced at E3 to integrate Xbox Live into mobile devices and PCs was discussed.
- A video of Bill Gates’ announcement was shown as well as screenshots of the communication working between a Tornado and Xbox 360 (on a private Xbox Live server).
- The HTC STARTRK (Flip-phone style Smartphone similar in size to the RAZR) was shown and Xbox Live Anywhere was demonstrated on the device with features such as looking at what other players are doing, their rankings, etc.
Digital Cameras
- Discussed new dual-lens cameras that offer up to 10x zoom without a big lens.
Office Live - http://officelive.microsoft.com/
- Web-hosting and simple design service offered by Microsoft for small businesses.
- Services are all free during Beta and post-beta they will still have a free hosting service.
- Includes domain, e-mail accounts (at your domain) and a simple way to design a basic website.
URGE – http://www.urge.com/
- Demo of the music service offered with Windows Media Player 11 through MTV and Microsoft.
- Challenged members to name a band with an album not available, all artists were found!
- Showed that downloaded content can be used on “Plays for Sure” devices with DRM support.
Look for details on the June meeting to be announced soon, we hope to see you there!
-Phil
The Windows CE 5.0 Networked Media Device Feature Pack gives you the ability to create a device that can stream content from PC's around your home network and 'play' that content on your TV set (photos, music, video) - the Network Media Device Feature Pack ships with a Sample User Interface which can easily be updated.
Here's how the standard user interface looks (pretty cool, eh!)
And here's how the user interface looks after dropping some new images into the Networked Media Device UI folder (even cooler, right?).
The Networked Media Device user interface can be updated in a number of ways, the simplest is to replace the existing bitmaps (after backing them up!) with new bitmaps - simply replace the bitaps in this folder C:\WINCE500\PUBLIC\FP_NMD\OAK\NMD_UI with new bitmaps, rebuild and you're done - the alternative is to modify and rebuild some of the source code that ships with the Networked Media Device Feature Pack.
Here's a link to sample bitmaps displayed above.
- Mike
Here is a heads up from one of our Developer's Tools Devs, Marty Larson:
This is something I discovered yesterday, and thought you all might
appreciate a heads up. If you try to build tux tests with VS 2005, you'll
run into this problem.
The default build settings in VS 2005 do not match the settings that the OS
was built with. VS tries to be C++ compliant, and treats wchar_t as a native
type. The OS tries to be backward compatible, and turns off that behavior.
This is only a problem when a dll exports a C++ interface (like kato does).
You'll see the following errors:
error LNK2019: unresolved external symbol "__declspec(dllimport) public: int
__cdecl CKato::EndLevel(wchar_t const *,...)"
(__imp_?EndLevel@CKato@@QAAHPB_WZZ) referenced in function ShellProc
error LNK2019: unresolved external symbol "__declspec(dllimport) public: int
__cdecl CKato::BeginLevel(unsigned long,wchar_t const *,...)"
(__imp_?BeginLevel@CKato@@QAAHKPB_WZZ) referenced in function ShellProc
error LNK2019: unresolved external symbol "__declspec(dllimport) public: int
__cdecl CKato::Log(unsigned long,wchar_t const *,...)"
(__imp_?Log@CKato@@QAAHKPB_WZZ) referenced in function ShellProc
To fix this, go to Project --> Properties --> Configuration Properties -->
C/C++ --> Language, and set 'Treat wchar_t as Built-in Type' to No.
--
Marty Larson [MS]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Posted by Don Gambrell
Want to advise development projects where the creators actually listen to your input?
Want to show off your own code binaries, code source, rough ideas and position papers with others?
Want to find, download, evaluate, and discuss the best of what’s next in .NET or other platforms...?
If you like the idea of your feedback driving the project... then CodeGallery is for you
Download the Windows CE 5.0 Standalone Test Kit
This kit is a collection of tests and tools that can be used to help verify the stability, reliability, and quality of a platform or device running Windows CE 5.0. This download is intended to be used on systems where Windows CE 5.0 is not installed; however, it is the same kit as the one included in the Windows CE 5.0 product and is used in the same way.
Do you spend too much time trying to figure out what's new on your favorite web sites and Blogs? RSS/Atom aggregators track it all and bring the web pages to you. Now you can read more and search less. These RSS/Atom aggregators take a diverse spectrum of Community, technical and news resources such as Blogs, Newsgroups, etc. and put them in one place.
No more wandering around looking for Mike Hall’s blog (http://blogs.msdn.com/mikehall/) , that great CE Test blog, Test Embedded (http://blogs.msdn.com/TestEmbedded/), or trying to keep up with Microsoft Windows MED Community Goings-On (http://blogs.msdn.com/nwhite/), tech news like Wired News or Slashdot, Newsgroups like microsoft.beta.yamazaki.tools, on and on.
Below are just a few suggestions of these types of aggregators:
- NewsGator: NewsGator Online also includes synchronization with Outlook Edition, viewing content on TV with Media Center Edition, as well as the publication of blogrolls and headlines. http://www.newsgator.com/ngs/default.aspx
- RSS Bandit: an RSS/Atom aggregator (also known as an RSS Reader) for your desktop written with the .NET Framework. http://www.rssbandit.org/
- SharpReader is an RSS/Atom Aggregator for Windows. http://www.sharpreader.net/
And if one of those does not fit your needs, here is a huge list of news aggregators From Wikipedia - http://en.wikipedia.org/wiki/List_of_news_aggregators
Don Gambrell
Got NetLog?
The creativity and knowledge of our team never ceases to amaze me. When I was having issues sniffing across a switch in our network (doesn't allow for capturing broadcast packets) someone on the CE Core Network team suggested that I use Netlog on the CE device.
What? You can catch packets from a CE device with a utility that is shipped with Platform Builder? And PPP connectivty? Oh yeah... with one catch: there is no CE Netmon UI to display the captures. You have to use the desktop version of Netmon.
See msdn article http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcecomm5/html/wce50grfnetlog.asp for more details ....
Netlog is a sample tool that logs network traffic. It produces files that can be read by using the Microsoft Windows Network Monitor (NetMon) .Netlog has no arguments of its own, but is controlled by the Netlogctl sample command-line tool. For more information, see Netlogctl.
Don Gambrell
When you use the Windows CE Test Kit (CETK) to run tests on a Microsoft® Windows® CE–based device, you might want to analyze an unexpected result to determine the cause of the result. You begin your analysis by verifying that the OS design and hardware platform adequately support the CETK test. You might then need to debug the source code for the CETK test to find the reason for the unexpected result. By debugging the source code for the CETK test, you narrow the cause of the unexpected result to the line of code that exhibits unexpected behavior. You can use that information to debug your driver.
Investigation of a single test case result might yield insight into multiple test case results. A single condition might cause several related test cases to fail. For information about the test cases for each CETK test, see CETK Tests.
Information that a CETK test writes to the log can be a valuable source of information about a test. Careful inspection of the log might preempt the need for further investigation. For information about viewing a CETK test log, see Viewing the Results of a Test.
Hardware and Software Assumptions
- You have connected the CETK to a target device.
For information, see Connecting the CETK to a Target Device by Using Platform Manager.
- You are familiar with running CETK tests on a target device.
To learn how to run a CETK test, see How to Use the CETK to Test a Driver.
- You have installed Windows CE Shared Source. For more information, see Installing Windows CE with Shared Source Code.
- You have source code for the CETK test that returned a result that you want to analyze.
Microsoft provides source code for some CETK tests to assist you in debugging your device drivers and to assist you in creating custom tests for the CETK. You cannot build some of the source files, and source files for certain tests are not provided.
To track your progress in the following table, select the check box next to each step.
| |
Step |
Topic |
|
1. Familiarize yourself with the test result codes for a CETK test case.
|
Test Result Codes for a CETK Test Case |
|
2. If a test case skipped, aborted, or failed, verify that the OS design and hardware platform adequately support the CETK test. |
Investigating a Skipped CETK Test Case
Investigating a Failed or Aborted CETK Test Case |
|
3. Display a list of test cases for the CETK test by editing the command line for the test.
Inspect the log, and note the ordinal and name of the test case that previously aborted, failed, or skipped. |
Displaying a List of Test Cases for a CETK Test |
|
4. Edit the command line for the CETK test to run only the test case that returned the result that you want to analyze. |
Running a Single Test Case From a CETK Test |
|
5. Determine the value of the %_PRIVATEROOT% environment variable.
In this procedure, for <variable name>, type _privateroot. |
Determining the Value of an Environment Variable |
|
6. Find sources files related to the CETK test.
A sources file is a text file that sets the macro definitions for the source code in a directory. Platform Builder uses sources and dirs files to build projects. |
Finding Files for a CETK Test |
|
7. In each directory that contains a sources file that specifies as TARGETNAME the name of the Tux DLL for the CETK test, search for the test case name in the source code.
Search until you find an occurrence of the test case name within the definition of a FUNCTION_TABLE_ENTRY structure. Note the function name associated with the test case name. |
Finding a Test Case in the Source Code for a CETK Test |
|
8. In each directory that contains a sources file that specifies as TARGETNAME the name of the Tux DLL for the CETK test, search for the function name associated with the test case.
Open the file that contains each search result until you find the implementation of the function. |
Finding the Function for a Test Case in the Source Code for a CETK Test |
|
9. In the implementation of the function that corresponds to the test case, set a breakpoint at the entry point and at each exit point. |
Setting a Breakpoint at a Source Code Line |
|
10. Edit the command-line for the CETK test to run only the test case that returned the result that you want to analyze.
Confirm that the breakpoint at the function entry point activates, and then confirm that a breakpoint at an exit point activates.
If a breakpoint at an exit point does not activate, an exception might have occurred. Use stepping, breakpoints, and other debugger functionality to narrow the cause to the line of code that exhibits unexpected behavior. For information about debugger functionality, see System Debugging. |
Running a Single Test Case From a CETK Test |
See Also
How-to Topics | Windows CE Test Kit | CETK Setup | System Debugging
Don Gambrell