application note: booting windows xp embedded from … · 2015. 10. 29. · booting windows xp...

Booting Windows XP Embedded from uDiskOnChip

Application Note, December 2004 Aki Bleyer ([email protected])

1. INTRODUCTION 1.1 Scope This document provides guidelines for configuring uDiskOnChip to boot Windows XP Embedded. The reader should be familiar with building a Windows XP Embedded image.

1.2 uDiskOnChip uDiskOnChip can be partitioned into up to four drives, each with full read/write functionality and its own file system. The first drive can be designated as bootable, to support booting the operating system (OS) from uDiskOnChip.

1.3 Terminology The terminology defined in Table 1 is important for understanding the procedures described in this application note.

Table 1: Terminology Definitions

Term Description TAP.exe Target Analyzer Program. This program, run on Windows XP, enables producing a

comprehensive hardware inventory. The file generated by this program is one of the required setup files for building a Windows XP Embedded image.

TA.exe Target Analyzer. This is a 16-bit version of the TAP, and can be run on DOS or whenever TAP cannot be used.

FBA First Boot Agent. An agent for Windows XP Embedded that is used in the last stage of creating a boot image.

1 AP-DOC-1304, Rev. 1.0 94-AP-1204-10

mailto:[email protected]

Entdecken Sie weitere interessante Artikel und News zum Thema auf all-electronics.de!

Hier klicken & informieren!

http://www.all-electronics.de


1.4 Required Software Tools In addition to knowing how to build a Windows XP Embedded image, you must be familiar with the Microsoft Windows Embedded Studio suite of development tools. These tools must be installed on your host computer.

Note: If you use Windows XP Embedded with Service Pack 1, you must add the following Microsoft Update hot fixes: Q811279: http://www.microsoft.com/downloads/details.aspx?FamilyId=5C1C0AE5-8285-4AB2-B753-C624C6B622DD&displaylang=enQ822603: http://www.microsoft.com/downloads/details.aspx?FamilyID=ef6c21b9-ebe1-4c5b-9dd4-5c0eb387311e&DisplayLang=en

A tutorial for building a Windows XP Embedded image using Target Designer (one of the development tools in the Embedded Studio suite) is available at the following URL: http://www.acrosser.com/winEOS/tutorial-xp.htm

1.5 Overview of Topics Preparing a uDiskOnChip device to boot the OS involves the following workflow:

1. Creating a Windows XP Embedded image, described in Section 2 2. Configuring uDiskOnChip using the uDOC Partitioning Utility, described in Section 3.1 3. Finalizing the uDiskOnChip boot functionality, described in Section 3.2

2 AP-DOC-1304, Rev. 1.0 94-AP-1204-10

http://www.microsoft.com/downloads/details.aspx?FamilyId=5C1C0AE5-8285-4AB2-B753-C624C6B622DD&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=5C1C0AE5-8285-4AB2-B753-C624C6B622DD&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=ef6c21b9-ebe1-4c5b-9dd4-5c0eb387311e&DisplayLang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyID=ef6c21b9-ebe1-4c5b-9dd4-5c0eb387311e&DisplayLang=enhttp://www.acrosser.com/winEOS/tutorial-xp.htm


2. BUILDING A WINDOWS XP EMBEDDED IMAGE 2.1 Setting Up the Required Files (on Host) Building an image for booting Windows XP Embedded from uDiskOnChip is a two-stage process. The first stage is the setup process, where various files are placed on the host in preparation for building the actual master image in the second stage.

The setup process is independent of the image-building process and is performed only once. After the setup files have been placed on the host, they can be used each time you build a new image.

2.1.1 Adding uDiskOnChip Components to the Microsoft Component Database

Before you create a Windows XP Embedded image for uDiskOnChip, you must add the necessary uDiskOnChip components to the Microsoft Component Database, a tool in the Embedded Studio suite of applications. This step should be done only once in the host. If you are updating an existing image, continue below. If you are adding new uDiskOnChip components for the first time, skip to page 4.

Deleting Old uDiskOnChip Components To delete old USB Boot Solution components from an earlier version/update the USB Boot Solution component package in the Microsoft Component Database:

1. Launch the Component Database Manager in exclusive mode through Start>Programs>Microsoft Windows Embedded Studio menu, NOT through the Target Designer (Target Designer should remain closed).

2. Select the Package tab. The following window is displayed:

Figure 1: Microsoft Component Database Manager – Package Tab

3 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


3. Select the USB Boot Solution package. 4. Click Delete Package (this button is located in the lower right-hand area of the window). 5. Click Close to end the program.

Adding New uDiskOnChip Components

To add new uDiskOnChip components to the Microsoft Component Database:

1. Launch the Component Database Manager through Start>Programs>Microsoft Windows Embedded Studio menu. (This option can also be performed from within Target Designer.) The following window is displayed:

Figure 2: Microsoft Component Database Manager – Database Tab

4 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


2. Click Import. The following window is displayed:

Figure 3: Import SLD Window

Note: If the import process fails, make sure that the Copy repository files to repository root checkbox is not checked.

3. Browse to the location where the uDiskOnChip component resides, and click Import to import the uDOCBoot.sld uDiskOnChip component into the Microsoft Component Database.

Note: The uDOCBoot.sld file can be downloaded from http://www.m-systems.com within the XPeBoot.zip package.

4. Click Close to exit Microsoft Database Manager.

2.1.2 Preparing the Target Information File (.PMQ) (on Target)

In addition to preparing the custom XP embedded image, you should prepare target information file in .PMQ format on the target. This is accomplished by running Microsoft’s Target Analysis Program (TAP.exe) for Windows or Target Analysis (TA.exe) for DOS on your target board and saving the resulting .PMQ file on the host.

More information on how to use TA and/or TAP is available at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xetskSavingTargetAnalyzerOutputToFloppyDisk.asp

5 AP-DOC-1304, Rev. 1.0 94-AP-1204-10

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xetskSavingTargetAnalyzerOutputToFloppyDisk.asphttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/xpehelp/html/xetskSavingTargetAnalyzerOutputToFloppyDisk.asp


2.2 Creating the Windows XP Embedded Image (on Host) In this stage, the master uDiskOnChip image is created. This image will be copied to target uDiskOnChip devices, and will enable booting Windows XP Embedded.

Use Target Designer to create a boot image that will run on uDiskOnChip. This section describes two possible image types:

• WinLogon image: A Microsoft-standard template that is software- and hardware-agnostic. This example applies to any standard image that is built. M-Systems strongly recommends starting with a WinLogon base image to verify that uDiskOnChip can boot from your hardware.

• Custom image: This example is relevant if you have to build a custom image based on customer requests.

2.2.1 Building a WinLogon Boot Image

To build a standard WinLogon boot image:

1. Launch Target Designer and open a new image. 2. In the Target Designer configuration tree, add the USB uDiskOnChip WinLogon Macro to

the image through Software>Test & Development>USB uDiskOnChip WinLogon Macro, as shown in Figure 4.

Figure 4: USB uDiskOnChip WinLogon Macro in the Configuration Tree

3. Select Check Dependencies in the Configuration menu, or press F5 on your keyboard. In the window that is displayed, select the option that suits your system requirements.

6 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


4. After all dependencies are solved, select Build Target Image in the Configuration menu or press F7 on your keyboard to build the image. Select a path for the image files, and a path for the log file.

5. When the image is ready, close Target Designer. After you have completed the task of building the boot image, the next step is partitioning uDiskOnChip using the uDOC Partitioning Utility, as described in Section 3.

2.2.2 Building a Custom Boot Image

To build a custom boot image:

1. Launch Target Designer and open a new image. 2. Import your custom .PMQ file or open your custom .SLX file from Microsoft Target

Designer using the File>Import option in the menu.

3. Add the USB uDiskOnChip component to the configuration tree through Hardware>Devices>Hard Disks> USB uDiskOnChip Secure Component, as shown in Figure 5.

Figure 5: USB uDiskOnChip Component in the Configuration Tree

4. Add any other components that may be required by your custom image. 5. Select Check Dependencies from the Configuration menu or press F5 on your keyboard. 6. After all dependencies have been solved, select Build Image File from the Configuration

menu or press F7 on your keyboard to build the boot image. Select a path for the image, and a path for the log file.

7. When the boot image is ready, close Target Designer. After you have completed the task of building the boot image, the next step is partitioning uDiskOnChip using the uDOC Partitioning Utility, as described in Section 3.

7 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


3. CONFIGURING UDISKONCHIP FOR BOOT FUNCTIONALITY The uDOC Partitioning Utility enables configuring uDiskOnChip with up to four drives. The first drive on uDiskOnChip can be flagged as the boot partition. This enables booting the OS from DiskOnChip.

3.1 Partitioning uDiskOnChip (on Host)

Figure 6: uDOC Partitioning Utility Main Window

1. Insert a uDiskOnChip device into a USB port on the host. 2. Launch the uDOC Partitioning Utility by double-clicking the uDOCPart.exe icon in

Windows Explorer.

3. In the Main Window, click Partition a Device or press F6 on your keyboard to begin configuring the media as a standard hard drive in the system.

8 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


Figure 7: Step 1 – Defining the Size of the Partition(s)

4. In step 1 of the utility, assign up to four partitions to the public area by defining the size of each. Partition 0 is the active boot partition, and it should be large enough to hold the OS image. The default file is FAT16/32, according to the partition size. If you want to assign a different file system, check the Show Advanced Options checkbox under the Partition Graph area. Click Next.

Figure 8: Step 2 – Defining Advanced Partition Properties

5. If you did not check the Show Advanced Options checkbox, skip to the next step of the written procedure. Otherwise, assign a custom volume name to each partition (optional) and select the required file system type from the dropdown lists. Click Next.

9 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


Figure 9: Step 3 – Confirming Partition Properties

6. In step 3 of the utility, you can review the partition properties. If the settings are correct, click Next to partition the uDiskOnChip into the defined drive. If the settings need to be modified, click Back.

Figure 10: Confirmation Window – Successfully Configured the Public Area

7. A progress indicator is displayed while the uDiskOnChip device is partitioned into the assigned drives. After the device is formatted, a Windows Explorer window is displayed with the first formatted drive.

8. Close the Explorer window and click Exit in the uDOC Partitioning Utility to return to the Main Window. Do NOT close the uDOC Partitioning Utility.

10 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


9. Copy the Windows XP Embedded image to the first drive on uDiskOnChip. 10. Press F9 to mount and view (one at a time) any additional drives you may have partitioned.

You can copy other applications and files to these drives based on your requirements.

11. Click Eject uDiskOnChip or press F8 in the Main Window to safely eject the uDiskOnChip device.

12. Close the uDiskOnChip Partitioning Utility. The uDiskOnChip device is now ready for the final stage of preparing boot functionality.

3.2 Activating the First Boot Agent (on Target) Before booting from uDiskOnChip for the first time, you must access the target board BIOS options and set the BIOS to boot from uDiskOnChip by applying the setting for USB HDD. The first boot stage on the target platform is the First Boot Agent (FBA). The FBA runs automatically on the first boot from uDiskOnChip. After the FBA finishes configuring the system, it automatically reboots the system.

After the FBA reboots the system, you should see the uDiskOnChip drives created with the uDOC Partitioning Utility arranged as follows:

• [C:]: The first drive on uDiskOnChip, which contains the OS image and necessary files for booting the system.

• [D-F:]: The rest of the drives (depending on the uDiskOnChip settings) The uDiskOnChip is now ready for use as a boot and data storage device.

Note: The general functionality of the uDiskOnChip device should be tested before using this device as a master for creating new target devices with the uDOC Cloning Utility.

11 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


4. CLONING A NEW UDISKONCHIP DEVICE After using the uDOC Partitioning Utility to customize uDiskOnChip for the system design, the uDOC Cloning Utility is used to read the master image and copy it to the target uDiskOnChip devices. For instructions on how to use the uDOC Cloning Utility, please see the uDOC Cloning Utility user manual.

12 AP-DOC-1304, Rev. 1.0 94-AP-1204-10


HOW TO CONTACT US USA M-Systems, Inc. 555 North Mathilda Avenue, Suite 220 Sunnyvale, CA 94085 Phone: +1-408-470-4440 Fax: +1-408-470-4470

China M-Systems China Ltd. Room 121-122 Bldg. 2, International Commerce & Exhibition Ctr. Hong Hua Rd. Futian Free Trade Zone Shenzhen, China Phone: +86-755-8348-5218 Fax: +86-755-8348-5418

Europe M-Systems Ltd. 7 Atir Yeda St. Kfar Saba 44425, Israel Tel: +972-9-764-5000 Fax: +972-3-548-8666

Internet www.m-systems.com

General Information [email protected]

Japan M-Systems Japan Inc. Asahi Seimei Gotanda Bldg., 3F 5-25-16 Higashi-Gotanda Shinagawa-ku Tokyo, 141-0022 Phone: +81-3-5423-8101 Fax: +81-3-5423-8102

Taiwan M-Systems Asia Ltd. 14 F, No. 6, Sec. 3 Minquan East Road Taipei, Taiwan, 104 Tel: +886-2-2515-2522 Fax: +886-2-2515-2295

Sales and Technical Information [email protected]

This document is for information use only and is subject to change without prior notice. M-Systems Flash Disk Pioneers Ltd. assumes no responsibility for any errors that may appear in this document. No part of this document may be reproduced, transmitted, transcribed, stored in a retrievable manner or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without prior written consent of M-Systems.

M-Systems products are not warranted to operate without failure. Accordingly, in any use of the Product in life support systems or other applications where failure could cause injury or loss of life, the Product should only be incorporated in systems designed with appropriate and sufficient redundancy or backup features.

Contact your local M-Systems sales office or distributor, or visit our website at www.m-systems.com to obtain the latest specifications before placing your order.

© 2004 M-Systems Flash Disk Pioneers Ltd. All rights reserved.

M-Systems, DiskOnChip, DiskOnChip Millennium, DiskOnKey, DiskOnKey MyKey, FFD, Fly-By, iDiskOnChip, iDOC, mDiskOnChip, mDOC, Mobile DiskOnChip, Smart DiskOnKey, SmartCaps, SuperMAP, TrueFFS, uDiskOnChip, uDOC, and Xkey are trademarks or registered trademarks of M-Systems Flash Disk Pioneers, Ltd. Other product names or service marks mentioned herein may be trademarks or registered trademarks of their respective owners and are hereby acknowledged. All specifications are subject to change without prior notice.

13 AP-DOC-1304, Rev. 1.0 94-AP-1204-10

http://www.m-systems.com/mailto:[email protected]:[email protected]://www.m-systems.com/

IntroductionScopeuDiskOnChipTerminologyRequired Software ToolsOverview of Topics

Building a Windows XP Embedded ImageSetting Up the Required Files (on Host)Adding uDiskOnChip Components to the Microsoft Component DatPreparing the Target Information File (.PMQ) (on Target)

Creating the Windows XP Embedded Image (on Host)Building a WinLogon Boot ImageBuilding a Custom Boot Image

Configuring uDiskOnChip for Boot FunctionalityPartitioning uDiskOnChip (on Host)Activating the First Boot Agent (on Target)

Cloning a New uDiskOnChip DeviceHow to Contact Us

application note: booting windows xp embedded from … · 2015. 10. 29. · booting windows xp...

Documents