NXP IMXWQSG i.MX Windows 10 IoT User Guide

NXP IMXWQSG i.MX Windows 10 IoT

Document information

running this release package. It only explains how to download and run the default release image with the default configuration. For details on using the release package, see the Windows 10 IoT User’s Guide (IMXWUG) included in this release package.

Overview

This document guides you through the process of downloading and running this release package. It only explains how to download and run the default release image with the default configuration. For details on using the release package, see the Windows 10 IoT User’s Guide (IMXWUG) included in this release package.

Hardware requirements

The hardware requirements for using this release package are as follows: Supported evaluation boards (see Release Notes about supported board revisions):

• i.MX 8M Mini EVK
• i.MX 8M Nano EVK
• i.MX 8M Plus EVK
• i.MX 8M Quad EVK

Additional equipment:

• microSD card (minimum 8 GB)
• i.MX Mini SAS cable with IMX-MIPI-HDMI adapter (MIPI-DSI to HDMI converter) or IMX-LVDS-HDMI adapter (LVDS to HDMI converter), depending on the evaluation board/SoC capability. For more information, see the specific board chapter.

Software requirements

• Binary drivers and firmware (either downloaded from nxp.com or built locally)
• Windows IoT operating system. There are two options:
• Recommended: Windows 10 IoT Enterprise LTSC 2021 for Arm64
• Preview available on Microsoft Collaborate. Contact Microsoft at WinIoT-onNXP@microsoft.com for access.
• Windows 10 IoT Enterprise 21H2 GAC for Arm64
• Contact a Windows IoT distributor for access
• Windows ADK for Windows 10 and Windows PE add-on for ADK, version 2004.

Serial logging setup
To help troubleshoot issues during boot, use the USB micro-B port on i. MX EVK boards to output U-Boot and UEFI firmware serial debug logs to a host PC. The USB micro-B port on the EVK presents a virtual serial port to the host PC, which can be read by common Windows serial terminal applications such as HyperTerminal, Tera Term, or PuTTY.

1. Connect the target and the PC using the cable mentioned above.
2. Open Device Manager on the PC and locate the Enhanced Virtual serial device and note the COM port number.
3. Open the terminal on the PC. Configure the Enhanced Virtual serial/COM port to 921600 baud/s, an 8-bit, one-stop bit.

For the Host PC to recognize the i.MX device’s virtual serial port, you might need to download and install drivers for the i.MX’s USB to serial converter. The i.MX 8M EVK uses the CP210x USB to serial bridge. The CP210x driver can be found here. The i.MX 8M Mini EVK uses the FT2232D USB to serial bridge. The FT2232D driver can be found here. Note: The order in which serial/COM ports appear in Windows can differ depending on the board and Windows host.

References

For more information about Windows 10 IoT Enterprise, see Microsoft online documentation.

http://windowsondevices.com

The following Quick Start Guides contain basic information on the board and setting it up. They are available on the NXP website.

• i.MX 8M Quad Evaluation Kit Quick Start Guide
• i.MX 8M Mini Evaluation Kit Quick Start Guide
• i.MX 8M Nano Evaluation Kit Quick Start Guide
• i.MX 8M Plus Evaluation Kit Quick Start Guide
• Documentation is available online at nxp.com
• .MX 8 information is at http://www.nxp.com/imx8
• For more information about Windows 10 IoT Enterprise, see Microsoft’s online documentation.

Working with the i.MX 8M Mini EVK Board

Board hardware

The figures below show different components of the i.MX 8M Mini EVK LPDDR4 board.

Note:

• Tested on 8MMINILPD4-EVK, 700-31407 REV A3 (base board), SCH-3140 REV C4 (base board), 700-45699 REV X3 (CPU board), SCH-45699 REV A1 (CPU board) board revision.
• For i.MX 8M Mini EVK board, BT and Wi-Fi functions are not supported.
• USB(s) Device mode is not supported.

Display interface support

MIPI-DSI to HDMI converter IMX-MIPI-HDMI is supported. The converter is connected to the MIPI-DSI display interface on the EVK board (see Figure 1) with a mini-SAS cable (see Figure 2). Use a standard HDMI cable to connect an HDMI-compatible display.

Working with the i.MX 8M Nano EVK Board

Board hardware

The figures below show different components of the i.MX 8M Nano EVK board .

Note:

• Tested on 8MNANOD4-EVK, 700-31407 REV A3 (base board), SCH 31407 REV C3 (base board) board revision.
• For i.MX 8M Nano EVK board, Bluetooth/Wi-Fi functions are not supported.
• USB(s) Device mode is not supported.

Display interface support

The MIPI-DSI to HDMI converter IMX-MIPI-HDMI is supported. The converter is connected to the MIPI-DSI display interface on the EVK board (see Figure 5) with a mini-SAS cable (see Figure 6). Use a standard HDMI cable to connect an HDMI-compatible display.

Working with the i.MX 8M Plus EVK Board

Board hardware

The figures below show different components of the i.MX 8M Plus EVK board .

Note:

• Tested on 700-46370 REV B1 (base board), SCH-46370 REV B1 (base board), 700- 46368 REV A (CPU board), SCH-46368 REV A3 (CPU board) board revision.
• Ethernet QoS peripheral/port is not supported yet
• USB(s) Device mode is not supported.

Display interface support

LVDS to HDMI converter IMX-LVDS-HDMI is supported. The converter is connected to the LVDS0 display interface on the EVK board (see Figure 9) with a mini-SAS cable (see Figure 10). Use a standard HDMI cable to connect an HDMI-compatible display.
Note: The HDMI display interface is not supported directly on the EVK board.
Optionally use a dual LVDS display (connected to both LVDS0 and LVDS1). It is necessary to update the Display0Interface parameter in the registry or galore. inf for the windows GPU driver and reboot/re-install the GPU driver.

Working with the i.MX 8M Quad EVK Board

Board hardware

The figures below show different components of the i.MX 8M Quad EVK board .

Note:

• Tested on MCIMX8M-EVK, 700-29615 REV A3, SCH-29615 REV B4 board revision.
• The NXP 88W8997 Wi-Fi&BT M.2 expansion card is not supported.
• USB(s) Device mode is not supported.

Display interface support

The HDMI interface is supported on the EVK board (see Figure 14). Use a standard HDMI cable to connect an HDMI-compatible display.

Flashing Windows IoT image

Windows 10 IoT must be installed on the eMMC from the SD card. Preparing the bootable SD card consists of two steps: flashing the Windows 10 IoT installer and flashing the firmware to an SD card.

Flashing Windows 10 IoT Installer to the SD card

Currently, the only way to deploy a Windows IoT Enterprise on the onboard eMMC is to use WinPE. OS (Windows Preinstallation Environment) to write the Windows IoT image to eMMC. Windows manufacturing OS that can be fully loaded and run from memory without using persistent storage. The following steps create an SD card with WinPE and a Windows IoT image that contains the BSP drivers. The boot firmware checks the SD card and boots WinPE, which then installs the Windows IoT image to the eMMC.

1. Decompress the W21H2-1-2-0-imx-windows-BSP-binaries.zip file. The package contains pre-built binaries and image files.

2. Open the elevated command prompt and navigate to the IoTEntOnNXP directory.

3. Mount the previously downloaded Windows IoT Enterprise ISO image file (see chapter Software requirements) and copy the install.wim file from the \sources\install.wim to the IoTEntOnNXP directory.

4. Execute the command:
   make-wine-enterprise.cmd /disable_updates /
   disable_transparency /patch_sdport /test_signing
   This command creates a copy of the selected install.wim image with injected i.MX drivers.
   Note: Be sure to copy the whole command line

5. Execute the command:
   make-wine-enterprise.cmd /apply
   where is the physical number of the SD card disk on your PC. It can be obtained using the Disk Management tool (right-click the start menu icon and select Disk Management).
   This command deploys the WinPE image to the SD card.
   CAUTION: Make sure to select the correct disk number, as this step formats the selected disk! The WinPE-based Windows installer is now deployed on the SD card.

6. Continue with the firmware installation to the SD card.

Flashing Firmware to the SD card

During active development of the boot firmware, it can be time-consuming and error-prone to repeatedly change the dip switches between UUU download mode and eMMC boot mode. To simplify this process, the i. MX EVK boards support SD Card boot mode that allows you to keep the boot firmware on an SD card. To deploy boot firmware to an SD card from Windows, we recommend using the Cfimager tool from https://www.nxp.com/webapp/Download?colCode=CF_IMAGER.
Perform the following steps to flash the firmware to the SD card:

1. Download the NXP cfimager tool and install it into the firmware directory or a directory listed in the system environment variable %PATH%.

2. Navigate to the firmware directory.

3. Plug the SD card into the host PC and execute the following board-specific command:
   For i.MX 8M Mini EVK board:
   flash_bootloader.cmd /device <device_name, for example, MX8M_MINI_EVK> /target_drive <SD card driver letter, for example, f:>
   For i.MX 8M Quad EVK board:
   flash_bootloader.cmd /device <device_name, for example, MX8M_EVK> /target_drive <SD card driver letter, for example, f:>
   For i.MX 8M Nano EVK board:
   flash_bootloader.cmd /device <device_name, for example, MX8M_NANO_EVK> /target_drive <SD card driver letter, for example, f:>
   For i.MX 8M Plus EVK board:
   flash_bootloader.cmd /device <device_name, for example, MX8M_PLUS_EVK> /target_drive <SD card driver letter, for example, f:>

4. Power off the board.

5. Insert the SD card into the board

6. Change the boot device to the SD card.

Table 1. Boot DIPs configuration

Installing Windows 10 IoT on eMMC and Booting Windows 10 IoT

1. Power on the board and let the Windows installer install Windows IoT Enterprise to the eMMC, then reboot into installed Windows. Installing Windows IoT Enterprise from the SD card can take around 30 minutes, so get some coffee while you wait!Note: The WinPE installer renames the EFI folder at the root of the SD card to _efi, which causes UEFI to skip the SD card at boot time. This allows you to keep the SD card inserted across reboots without having Windows IoT reinstalled on each reboot. If you wish to boot into the WinPE installer again, you can rename _efi back to EFI.
2. Make sure to disable sleep in “Power & sleep” settings after Windows OS boots up to avoid unexpected system hangs.

Working with cameras

1. OV5640 is the default camera in the BSP. To start video capturing, plug the OV5640 camera into the default MIPI CSI-2 input. The board must be powered off. The following tab table shows labels of the MIPI CSI 2 connectors to be used by default.

Table 2. Default MIPI CSI-2 inputs

1. Power up the board.
2. After Windows boots up, run the Camera app and check the video preview, take a picture and record the video.

Revision history

Legal information

Definitions
Draft — A draft status on a document indicates that the content is still under internal review and subject to formal approval, which may result
in modifications or additions. NXP Semiconductors does not give any representations or warranties as to the accuracy or completeness of information included in a draft version of a document and shall have no liability for the consequences of use of such information.
Disclaimers
Limited warranty and liability — Information in this document is believed to be accurate and reliable. However, NXP Semiconductors does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such information. NXP Semiconductors takes no responsibility for the content in this document if provided by an information source outside of NXP Semiconductors. In no event shall NXP Semiconductors be liable for any indirect, incidental, punitive, special or consequential damages (including – without limitation -lost profits, lost savings, business interruption, costs related to the removal or replacement of any products or rework charges) whether or not such damages are based on tort (including negligence), warranty, breach of contract or any other legal theory. Notwithstanding any damages that customer might incur for any reason whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms and conditions of commercial sale of NXP Semiconductors.
Right to make changes — NXP Semiconductors reserves the right to make changes to information published in this document, including without limitation specifications and product descriptions, at any time and without notice. This document supersedes and replaces all information supplied prior to the publication hereof.
Suitability for use — NXP Semiconductors products are not designed, authorized or warranted to be suitable for use in life support, life-critical or safety-critical systems or equipment, nor in applications where failure or malfunction of an NXP Semiconductors product can reasonably be expected to result in personal injury, death or severe property or environmental damage. NXP Semiconductors and its suppliers accept no liability for inclusion and/or use of NXP Semiconductors products in such equipment or applications and therefore such inclusion and/or use is at the customer’s own risk.
Ap plications — Applications that are described herein for any of these products are for illustrative purposes only. NXP Semiconductors makes no representation or warranty that such applications will be suitable for the specified use without further testing or modification. Customers are responsible for the design and operation of their applications and products using NXP Semiconductors products, and NXP Semiconductors accepts no liability for any assistance with applications or customer product design. It is the customer’s sole responsibility to determine whether the NXP Semiconductors product is suitable and fit for the customer’s applications and products planned, as well as for the planned application and use of the customer’s third-party customer(s). Customers should provide appropriate design and operating safeguards to minimize the risks associated with their applications and products. NXP Semiconductors does not accept any liability related to any default, damage, costs, or problem which is based on any weakness or default in the customer’s applications or products, or the application or use by the customer’s third-party customer(s). The customer is responsible for doing all necessary testing for the customer’s applications and products using NXP Semiconductors products in order to avoid a default of the applications and the products or of the application or use by the customer’s third-party customer(s). NXP does not accept any liability in this respect.

Terms and conditions of commercial sale — NXP Semiconductors products are sold subject to the general terms and conditions of commercial sale, as published at http://www.nxp.com/profile/terms unless otherwise agreed in a valid written individual agreement. In case an individual agreement is concluded only the terms and conditions of the respective agreement shall apply. NXP Semiconductors hereby expressly objects to applying the customer’s general terms and conditions with regard to the purchase of NXP Semiconductors products by the customer.
Export control — This document as well as the item(s) described herein may be subject to export control regulations. Export might require a prior authorization from competent authorities.
Suitability for use in non-automotive qualified products — Unless
this data sheet expressly states that this specific NXP Semiconductors product is automotive qualified, the product is not suitable for automotive use. It is neither qualified nor tested in accordance with automotive testing or application requirements. NXP Semiconductors accepts no liability for inclusion and/or use of non-automotive qualified products in automotive equipment or applications. In the event that the customer uses the product for design-in and use in automotive applications to automotive specifications and standards, customer (a) shall use the product without NXP Semiconductors’ warranty of the product for such automotive applications, use and specifications, and (b) whenever customer uses the product for automotive applications beyond NXP Semiconductors’ specifications such use shall be solely at customer’s own risk, and (c) customer fully indemnifies NXP Semiconductors for any liability, damages or failed product claims resulting from customer design and use of the product for automotive applications beyond NXP Semiconductors’ standard warranty and NXP Semiconductors’ product specifications.
Translations — A non-English (translated) version of a document, including the legal information in that document, is for reference only. The English version shall prevail in case of any discrepancy between the translated and English versions.
Security — Customer understands that all NXP products may be subject to unidentified vulnerabilities or may support established security standards or specifications with known limitations. Customer is responsible for the design and operation of its applications and products throughout their lifecycles to reduce the effect of these vulnerabilities on customer’s applications and products. Customer’s responsibility also extends to other open and/or proprietary technologies supported by NXP products for use in customer’s applications. NXP accepts no liability for any vulnerability. Customer should regularly check security updates from NXP and follow up appropriately. Customer shall select products with security features that best meet rules, regulations, and standards of the intended application and make the ultimate design decisions regarding its products and is solely responsible for compliance with all legal, regulatory, and security related requirements concerning its products, regardless of any information or support that may be provided by NXP. NXP has a Product Security Incident Response Team (PSIRT) (reachable at PSIRT@nxp.com) that manages the investigation, reporting, and solution release to security vulnerabilities of NXP products.
Trademarks
Notice: All referenced brands, product names, service names, and trademarks are the property of their respective owners.
NXP — wordmark and logo are trademarks of NXP B.V.

Please be aware that important notices concerning this document and the product(s) described herein, have been included in the section ‘Legal information.

• © 2022 NXP B.V.
• For more information, please visit:http://www.nxp.com
• All rights reserved.
• Date of release: 20 September 2022
• Document identifier: IMXWQSG

Documents / Resources

| NXP IMXWQSG i.MX Windows 10 IoT [pdf] User Guide
IMXWQSG, i.MX Windows 10 IoT, IMXWQSG i.MX Windows 10 IoT
---|---

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>