IMXWNR

i.MX Windows 10 IoT Release Notes

Rev. W1.3.0 — 20 December 2022 Release notes

Document information
Information Content
Keywords i.MX, Windows 10 IoT
Abstract This document contains important information about the package contents,
supported features, known issues and limitations in this release.
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

1 Overview
i.MX Windows 10 IoT 1.3.0 release includes all necessary code, documents, and tools to
assist users in building and running Windows 10 IoT on the i.MX boards from scratch.
Pre-built images are also included for a quick trial on the following platforms:
• i.MX 8M Mini EVK
• i.MX 8M Nano EVK
• i.MX 8M Plus EVK
• i.MX 8M Quad EVK
• i.MX 8QuadXPlus MEK (Silicon Revision C0)

1.1 References
For more information about Windows 10 IoT Enterprise, see Microsoft online
documentation.
The following quick start guides available on the NXP website contain basic information
on the board and setting it up:
• i.MX 8M Quad Evaluation Kit
• i.MX 8M Mini Evaluation Kit
• i.MX 8M Nano Evaluation Kit
• i.MX 8M Plus Evaluation Kit
• i.MX 8QuadXPlus Multisensory Enablement Kit
Documentation is available online at nxp.com

1.2 BSP change history

This chapter lists changes in releases including new features and defect fixes.
• 12/2022: W1.3.0
– Supported boards:
– MCIMX8M-EVK Evaluation Kit
– 8MMINILPD4-EVK Evaluation Kit
– 8MNANOLPD4-EVK Evaluation Kit
– 8MPLUSLPD4-EVK Evaluation Kit
– MCIM8QXP-MEK (Silicon Revision C0)
– New features:
– General
– UEFI.fit image is merged to U-Boot FIT image on 8M platforms.
– UEFI binary is compressed before inserted to uefi.fit on 8M platforms.
– The firmware name is suffixed with "_uuu" if it is compiled with UUU tools.
– Removed "-t signed". The firmware is always signed when using "-t
secured_efi".

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

2 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

– Custom HAB/AHAB signing keys can be now used by defining the

"KEY_ROOT" path.
– Audio driver:
– Driver imxaud.sys has been split into imxaud.sys using multi-channel
SAI peripheral for i.MX 8M and imxaudsc.sys using single-channel SAI
peripheral for i.MX 8QXP.
– I2C driver:
– A new imxlpi2c driver for the LPI2C peripheral is included. Interrupt and polling
modes have been supported.
– A new iMXLpi2cLib driver for the LPI2C peripheral in UEFI is included.
– ENET driver:
– QoS driver is supported on i.MX 8M Plus.
– I2C sensor drivers:
– e-Compass FXOS8700 - Accelerometer and Magnetometer is supported on
the i.MX 8QXP MEK board.
– Gyroscope FXAS2100 is supported on the i.MX 8QXP MEK board.
– Ambient Light Sensor ISL29023 is supported on i.MX 8QXP MEK board.
– GPU/display driver:
– GPU driver is added for i.MX 8QXP.
– HDMI display interface is supported for i.MX 8M Plus.
– GPU driver version is increased to 1.4.
– GPU driver support for video processing is added for i.MX 8M Nano/Plus.
– The source code for the GPU driver kernel part (galcore) is included in the
BSP.
– UART driver:
– LPUART is supported for i.MX 8QXP in interrupt mode. No flow control is
available for LPUART0 and LPUART2. LPUART1 (m2 slot) has RTS, CTS pins
wired.
– Fixes:
– GPU/display driver:
– Unsupported resolution and pixel clock (for example 1280x800, pclk=68.9
MHz) display an error message. As a workaround, the algorithm was changed
to set the closest possible pixel clock and display a warning message.
– i.MX 8M: Resolution 720p is set by default when a display is not connected or
it does not support EDID.
– USBC:
– i.MX 8M Plus: USB 3.0 devices were incorrectly detected as USB 2.0. USB
Type-C multiplex/demultiplexer switch "Selection control" pin polarity setting
has been added to the ACPI table.
• 10/2022: W1.2.1
– New features:
– Wi-Fi and Bluetooth driver:
– Wi-Fi AzureWave AW-CB178NF board based on 88W8897 SoC has been
supported. Wi-Fi and Bluetooth functionality has been enabled.
– 8/2022: W1.2.0
– Supported boards:
– MCIMX8M-EVK evaluation kit
– 8MMINILPD4-EVK evaluation kit
– 8MNANOD4-EVK evaluation kit
IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

3 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

– 8MPLUSLPD4-EVK evaluation kit

– New features:
– General
– Visual Studio 2019 has been supported, but version 2017 is no
longer supported.
– Firmware update: buildme64.sh switch –cap added to build
Firmware capsule. Capsule update working from Uefi shell
with capsule stored on SD card: fs0: CapsuleApp.efi fs3:
FirmwareCapsuleIMX.cap
– make-winpe-enterprise.cmd parameters have been updated, see
User's Guide for details.
– i.MX 8M CPU frequency changed from 1 GHz to 1.5 GHz
– GPU driver:
– GPU driver has been updated to v1.3.
– GPU driver added for i.MX 8M Plus and i.MX 8M Nano SOCs.
– GPU driver support for video processing has been added for i.MX
8M.
– Camera driver:
– OV5640 camera has been supported for all EVK boards.
– OV10635 camera has been supported for all EVK boards.
– YUV422 YUY2 and YUV420 NV12 camera color formats have
been supported. The i.MX 8M EVK does not support YUV420
NV12 format.
– Display driver:
– Windows driver with fixed display mode supported for LVDS
display interface for i.MX 8M Plus.
– Windows driver with fixed display mode supported for MIPI-DSI
display interface for i.MX 8M Nano.
– VPU driver:
– VPU decoder has been supported for i.MX 8M Quad, i.MX 8M
Mini, and i.MX 8M Plus EVK boards.
– Fixes:
– WM8960 driver: I2C is correctly released when the WM8960 device
is removed.
– 8/2022: W1.2.0
– Supported boards:
– MCIMX8M-EVK evaluation kit
– 8MMINILPD4-EVK evaluation kit
– 8MNANOD4-EVK evaluation kit
– 8MPLUSLPD4-EVK evaluation kit
– New features:
– General
– Visual Studio 2019 has been supported, but version 2017 is no
longer supported.
– Firmware update: buildme64.sh switch –cap added to build
Firmware capsule. Capsule update working from Uefi shell
with capsule stored on SD card: fs0: CapsuleApp.efi fs3:
FirmwareCapsuleIMX.cap

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

4 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

– make-winpe-enterprise.cmd parameters have been updated, see

User's Guide for details.
– i.MX 8M CPU frequency changed from 1 GHz to 1.5 GHz
– GPU driver:
– GPU driver has been updated to v1.3.
– GPU driver added for i.MX 8M Plus and i.MX 8M Nano SOCs.
– GPU driver support for video processing has been added for i.MX
8M.
– Camera driver:
– OV5640 camera has been supported for all EVK boards.
– OV10635 camera has been supported for all EVK boards.
– YUV422 YUY2 and YUV420 NV12 camera color formats have
been supported. The i.MX 8M EVK does not support YUV420
NV12 format.
– Display driver:
– Windows driver with fixed display mode supported for LVDS
display interface for i.MX 8M Plus.
– Windows driver with fixed display mode supported for MIPI-DSI
display interface for i.MX 8M Nano.
– VPU driver:
– VPU decoder has been supported for i.MX 8M Quad, i.MX 8M
Mini, and i.MX 8M Plus EVK boards.
– Fixes:
– WM8960 driver: I2C is correctly released when the WM8960 device
is removed.
– 8/2022: W1.2.0
– Supported boards:
– MCIMX8M-EVK evaluation kit
– 8MMINILPD4-EVK evaluation kit
– 8MNANOD4-EVK evaluation kit
– 8MPLUSLPD4-EVK evaluation kit
– New features:
– General
– Visual Studio 2019 has been supported, but version 2017 is no
longer supported.
– Firmware update: buildme64.sh switch –cap added to build
Firmware capsule. Capsule update working from Uefi shell
with capsule stored on SD card: fs0: CapsuleApp.efi fs3:
FirmwareCapsuleIMX.cap
– make-winpe-enterprise.cmd parameters have been updated, see
User's Guide for details.
– i.MX 8M CPU frequency changed from 1 GHz to 1.5 GHz
– GPU driver:
– GPU driver has been updated to v1.3.
– GPU driver added for i.MX 8M Plus and i.MX 8M Nano SOCs.
– GPU driver support for video processing has been added for i.MX
8M.
– Camera driver:
– OV5640 camera has been supported for all EVK boards.
IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

5 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

– OV10635 camera has been supported for all EVK boards.

– YUV422 YUY2 and YUV420 NV12 camera color formats have
been supported. The i.MX 8M EVK does not support YUV420
NV12 format.
– Display driver:
– Windows driver with fixed display mode supported for LVDS
display interface for i.MX 8M Plus.
– Windows driver with fixed display mode supported for MIPI-DSI
display interface for i.MX 8M Nano.
– VPU driver:
– VPU decoder has been supported for i.MX 8M Quad, i.MX 8M
Mini, and i.MX 8M Plus EVK boards.
– Fixes:
– WM8960 driver: I2C is correctly released when the WM8960 device
is removed.
• 8/2022: W1.2.0
– Supported boards:
– MCIMX8M-EVK evaluation kit
– 8MMINILPD4-EVK evaluation kit
– 8MNANOD4-EVK evaluation kit
– 8MPLUSLPD4-EVK evaluation kit
– New features:
– General
– Visual Studio 2019 has been supported, but version 2017 is no longer
supported.
– Firmware update: buildme64.sh switch –cap added to build Firmware capsule.
Capsule update working from Uefi shell with capsule stored on SD card: fs0:
CapsuleApp.efi fs3: FirmwareCapsuleIMX.cap
– make-winpe-enterprise.cmd parameters have been updated, see User's Guide
for details.
– i.MX 8M CPU frequency changed from 1 GHz to 1.5 GHz
– GPU driver:
– GPU driver has been updated to v1.3.
– GPU driver added for i.MX 8M Plus and i.MX 8M Nano SOCs.
– GPU driver support for video processing has been added for i.MX 8M.
– Camera driver:
– OV5640 camera has been supported for all EVK boards.
– OV10635 camera has been supported for all EVK boards.
– YUV422 YUY2 and YUV420 NV12 camera color formats have been supported.
The i.MX 8M EVK does not support YUV420 NV12 format.
– Display driver:
– Windows driver with fixed display mode supported for LVDS display interface
for i.MX 8M Plus.

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

6 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

– Windows driver with fixed display mode supported for MIPI-DSI display
interface for i.MX 8M Nano.
– VPU driver:
– VPU decoder has been supported for i.MX 8M Quad, i.MX 8M Mini, and i.MX
8M Plus EVK boards.
– Fixes:
– WM8960 driver: I2C is correctly released when the WM8960 device is removed.
• 6/2022: W1.1.0
Public release for i.MX 8M Nano and i.MX 8M Plus platforms.
– Supported boards:
– MCIMX8M-EVK evaluation kit
– 8MMINILPD4-EVK evaluation kit
– 8MNANOD4-EVK evaluation kit
– 8MPLUSLPD4-EVK evaluation kit
– New features:
– Camera driver: OV5640 camera in J1502 connector has been supported on i.MX
8M EVK board.
– FlexCAN driver: FlexCAN device has been supported on i.MX 8M Plus EVK by
the imxcan.sys driver.
– I2C driver: I2C expander (PCA6416) has been supported in
iMX8BoardInit module and options SelectCAN1InsteadOfI2C5 and
SelectCAN2InsteadOfPDMStream3 allow configuring corresponding selectors
on the Base Board.
– GPU driver: GPU driver has been updated to v1.1.
– Debug drivers: WinDbg over Ethernet has been supported. WinDbg over
ethernet requires the kd_8003_1fc9.dll library which is not distributed as a
part of the BSP. To get this library, contact Microsoft.
– ENET driver: HW checksum offload has been supported in the NDIS miniport
driver.
– Fixes:
– Audio driver: A failure during uninstallation in the Device manager has been
fixed.
– Display driver: IMX-LVDS-HDMI and IMX-MIPI-HDMI converters: If a native
HDMI display resolution exceeds the upper limit, the fixed maximum available
resolution is set instead. 1920x1080@60 Hz in case of IMX-MIPI-HDMI and
1280x720@60 Hz in case of IMX-LVDS-HDMI.
– SD driver: Configuration “fixed device” has been changed to “removable device”,
which allows you to safely remove the SD card by the "Eject" option.
• 4/2022: W1.0.0
Public release for i.MX 8M and i.MX 8M Mini platforms.
– Supported boards: MCIMX8M-EVK evaluation kit 8MMINILPD4-EVK evaluation kit
– New features:
– VPU driver: Supported codecs HEVC, VP9, H.264, VP8. MPEG-2 and MPEG-4
codecs supported on i.MX 8M only.
– Fixes:
– UART driver: The UART driver failure during uninstallation in the Device manager
has been fixed.
– I2C driver: The issue in iMXI2cRead function (when ReadBufferSize == 1) in
UEFI has been fixed.

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

7 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

– buildme 64.sh: The script has been updated. Updates in UEFI source code were
included in firmware.bin only if firmware was built with -c parameter (clean build).
– PCIe: PCIE ATU (Address Translation Unit) setup for PCIE BAR memory-mapped
registers in UEFI drivers has been fixed. After this fix, the system works as
expected in UEFI and relevant Storage drivers appear in Windows.
• 3/2022: W0.9.1
Public preview release for i.MX 8M platform.
– Fixes:
– eMMC driver: eMMC tuning parameters add to the Dsdt-Sdhc.asl.
– BSP deployment: Removed invalid characters from make-winpe-enterprise.cmd.
• 1/2022: W0.9.0
Private preview release for i.MX 8M platform.
– Supported boards: The existing BSP with support for the MCIMX8M-EVK NXP
board.

2 BSP supported features

The following table displays the features supported in this BSP release. If no board is
explicitly mentioned, the feature is shared across all boards listed in Supported Hardware
in the Release contents section; otherwise, the feature is only supported on the boards
listed.

Table 1.  Supported boards

Board name Board revision Schema revision BSP name
MCIMX8M-EVK 700-29615 REV A3 SCH-29615 REV B4 MX8M_EVK
8MMINILPD4- 700-31407 REV A3 SCH-3140 REV C4 MX8M_MINI_EVK
EVK
700-47712REV X2 SCH-47712 REV A2
8MNANOLPD4- 700-31407 REV X5 SCH-31407 REV C2 MX8M_NANO_EVK
EVK (base (base
board) board)
700-38823 REV A (cpu SCH-38823 REV A2
board) (cpu
board)
8MPLUSLPD4- 700-46370 REV B (base SCH-46370 REV B1 MX8M_PLUS_EVK
EVK board) (base
board)
700-46368 REV A (cpu SCH-46368 REV A3
board) (cpu
board)
MCIM8QXP- 700-29683 REV C2 (cpu SCH-29683 REV D4 MX8QXP_MEK
MEK board) (cpu board)
700-29918 REV C1 SCH-29918 REV C1
(base board) (base board)

Table 2. Supported features

Feature Supported board Comment
Boot Image

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

8 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

Table 2. Supported features...continued

Feature Supported board Comment
U-Boot All i.MX • Clock, Anatop regulator,
ENET, UART, MMC/SD, e
MMC4.3/4.4/4.5.

OP-TEE All i.MX • OP-TEE OS is required

on the boot partition with
the TEE file for OP-TEE
enablement.
Machine-specific layer
Interrupt All i.MX • GIC
Clock All i.MX • Controls the system
frequency and clock tree
distribution.
Timer All i.MX • System timer tick and
broadcast timer support.
GPIO All i.MX • GPIO is initialized in earlier
phase according to hardware
design.
IOMUX All i.MX • Provides the interfaces for I/
O configuration.
SCFW i.MX8QXP • Clock/Power/Security is
controlled by the “System
Control Firmware”. The
“imxscfw” driver controls
communication channel with
this firmware.
DMA engine
SDMA i.MX 8M • SDMA HAL
Character device drivers
UART i.MX 8M/Mini/Nano/Plus • DMA(default) and Interrupt
mode configurable in ACPI
• UART2 is not available
in Windows, used by the
Cortex-M4 processor.
LPUART i.MX 8QXP • Interrupt mode
Networking drivers
ENET All i.MX • i.MX 8 supports Atheros
AR8031 PHY with
10/100/1000 bps mode
ENET QOS i.MX 8M Plus • ENET QOS is available on
i.MX 8M Plus.
• RTL8211 PHY is supported.
PCIe All i.MX • i.MX 8 supports M.2
interface.
Sound drivers

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

9 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

Table 2. Supported features...continued

Feature Supported board Comment
SAI All i.MX • Supports both transmit to
and receive from the audio
codec.
WM8524 codec i.MX 8M/Mini/Nano • Supports playback
WM8960 codec i.MX 8M Plus/i.MX 8QXP • Supports playback and
record.
USB drivers
USB Host All i.MX • Supports USB-A and USB-C
connectors.
Display/GPU
HDMI i.MX 8M • Up to 1080p
i.MX 8M Plus
LVDS display interface i.MX 8M Plus • i.MX 8M Plus:
i.MX 8QXP – Single-channel mode up to
720p
– Dual-channel mode up to
1080p (or 1920x1200@60
Hz)
– Default mode set to 720p
• i.MX 8QXP
– Single-channel mode up to
1080p
– Default mode set to 1080p
IMX-LVDS-HDMI (LVDS to i.MX 8M Plus • Single-channel mode.
HDMI converter) i.MX 8QXP Default resolution – see
above.
MIPI-DSI display interface i.MX 8M Mini/Nano • i.MX 8M Nano: supports
Windows GPU driver up to
1080p (or 1920x1200@60
Hz). Default resolution set to
720p.
• i.MX 8M Mini: no Windows
driver, only firmware support
up to 1080p. Default
resolution with IMX-MIPI-
HDMI converter depends on
the monitor native mode –
1080p in most cases.
IMX-MIPI-HDMI (MIPI-DSI to i.MX 8M Mini/Nano • Default resolution – see
HDMI converter) above.
GPU i.MX 8M /Plus/Nano • HW acceleration for 3D
i.MX 8QXP rendering through D3D11
API, therefore accelerates
D2D, XAML, UWP, WinUI,
Windows desktop UI, and
D3D11 apps.
Camera

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

10 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

Table 2. Supported features...continued

Feature Supported board Comment
Camera (SoCs with CSI i.MX 8M/Mini • Video preview at 720p 30 fps
Bridge) YUYV.
Camera (SoCs with ISI) i.MX 8M Plus/Nano • Video preview at 720p 30 fps
YUYV and NV12
OV5640 All i.MX • Second camera configurable
camera in UEFI in <BOARD>.dsc file.

OV10635 camera All i.MX • Selectable in UEFI in

<BOARD>.dsc file.
• i.MX 8M/Mini/Nano/Plus
requires an external 12 V
PSU and a manual reset
every time Windows OS is
rebooted.
• i.MX 8QXP powers camera
via mini SAS connector.
Video
VPU full feature i.MX 8M • Supported codecs HEVC,
VP9, H.264, VP8, MPEG-2,
and MPEG-4 codecs
VPU limited feature i.MX 8 Mini/Plus • Supported codecs HEVC,
VP9, H.264, VP8.
General drivers
uSDHC All i.MX • Supports SD, SDXC, eMMC.
I2C All i.MX • Supports I2C master mode.
SPI All i.MX • Supports SPI master mode.
FlexCAN i.MX 8M • FlexCAN low-level driver.
Power management
Device power management All i.MX • Sample PoFx callbacks are
implemented in i2c and pwm
drivers. Devices entering
D3 (power down) and D0
(active) states, WakeUp
sample callbacks in i2c
driver.
Processor power management All i.MX • PEP (Power Engine Plugin)
driver is included in this
release. Set usePpm
to 1 in imxpep.cpp to
enable processor power
management, and contact
NXP for the latest Pep
version.

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

11 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

Table 2. Supported features...continued

Feature Supported board Comment
USB Power delivery All i.MX • The initial USB Power
delivery contract is
negotiated in Uboot. See
tcpc_port_config
structure initialization in
imx8mp_evk.c, imx8mq_
evk.c, imx8mm_evk.c, and
imx8mn_evk.c files for actual
setting of voltage and current
for given board.

3 Known issues/limitations
Read through all hardware-related reference material and ensure that you have made all
the necessary hardware modifications before using the software.

Table 3. Known issues/limitations

Limitation/Workaround SoC
Boot
Limitation: Supported boot media are SD and eMMC only. All
Workaround: No workaround.
Camera
Limitation: Only i.MX 8MQ EVK SCH-29615 rev. B4 is supported. Earlier board i.MX 8M
revisions use different I2C for the camera.
Workaround: For i.MX 8MQ EVK SCH-29615 rev. B3, choose I2C1 camera
device instead of I2C2 in mu_platform_nxp/NXP/<BOARD>/AcpiTables/
DsdtCamera_<CONFIGURATION>.asl.
Limitation: OV10635 requires an external 12V power source and cannot be i.MX 8M
reconfigured by software without a power cycle. i.MX 8M Mini
Workaround: After powering off the board, unplug the power supply from the i.MX 8M Nano
camera and wait a few seconds before powering the camera and EVK board i.MX 8M Plus
again.
Display/GPU
Limitation: Monitor power-off is emulated by displaying a blank image. All
Workaround:Monitor power-off support will be added in the next release.
Limitation: Video Processing of NV12 image format has limited performance on i.MX 8M Nano
GPU. A video stream from a camera or media player may lose frames or show i.MX 8M Plus
lag.
Workaround: Decrease resolution or change format used to YUY2. NV12
processing performance will be improved in the next release.
Limitation: Some monitors/displays may fail reading EDID using on board HDMI i.MX 8M Plus
interface because of incompatible voltage level shifter on 8MPLUSLPD4-EVK
revision A.
Workaround: Use 8MPLUSLPD4-EVK revision B1 or newer.

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

12 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

Table 3. Known issues/limitations...continued

Limitation/Workaround SoC
Limitation: GPU driver does not support D3D9 (used to accelerate Windows i.MX 8M
Presentation Foundation apps). i.MX 8M Plus
Workaround: GPU driver for D3D9 will be added in the upcoming release.
i.MX 8M Nano
i.MX 8QXP
Limitation: Using Remote Desktop to connect to the device results in black i.MX 8M
screen.
Workaround: Apply the following register value to run the older XDDM driver for
Remote Desktop.
reg add "HKLM\System\CurrentControlSet\Control\Terminal Server
\WinStations" /v "LoadWddmIDDDriver" /t REG_DWORD /d 0x0 /f
GPIO
Limitation: EXP_IO pins on EXP CN connector cannot be used as GPIOs i.MX 8M Mini
because they are connected to PCA6416 I/O expander for which there is no i.MX 8M Nano
driver implemented.
i.MX 8M Plus
Workaround: Use the GPIO pin on the EXP CN connector connected directly to
the SoC’s pin with GPIO functionality instead of connecting to the PCA6416 I/O
expander.
SPI

Limitation: The LPSPI peripheral is not supported. i.MX 8QXP

Workaround: LPSPI support will be added in the next release.
HAL Drivers
Limitation: The HAL Extensions must be signed by certificates provided by All
Microsoft. The required certificates that are included in WDK have expired.
Workaround: Download the Microsoft Kits Package from Collaborate and use
the “Windows OEM HAL Extension Test Cert 2017 (TEST ONLY)” and “Windows
OEM Intermediate 2017 (TEST ONLY)” found in the EWDK.iso file or contact
Microsoft for help.
SDHC
Limitation: The imxusdhc.sys in crash dump mode does not read HW- All
specific settings from ACPI so these values are hardcoded in the SdhcSlot
Initialize() method.
Workaround: Keep these values synchronized with values in Dsdt-Sdhc.asl
ACPI table.
Limitation: The sdport.sys in the recommended Windows build 19044. All
1288.2110060501.21h2 could cause the blue bug check screen. This could be
observed when encrypting volumes with Bitlocker or running Cfimager.
Workaround: Install KB5014023 or enable test signing (/test_signing) and patch
the operating system with the sdport.sys included in bsp (/patch_sdport) as
described in Installing Windows IOT Enterprise, eMMC. If test signature is not
enabled, /patch_sdport will cause a blue screen.
Limitation: SDCARD insertion/removal can cause a bug check if the delay All
between insertion/removal is too short.
Workaround: Wait a few seconds before insertion/removal.
UART/LPUART

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

13 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

Table 3. Known issues/limitations...continued

Limitation/Workaround SoC
Limitation: The RTS-CTS hardware flow control is not available. All
Workaround: No
USB
Limitation: The size of SDRAM is limited to 3 GB due to a USB host controller i.MX 8M Plus
issue.
Workaround: There is a plan to fix this issue at Microsoft provided USB stack
update. Contact Microsoft to obtain this fix. As soon as this fix is available, the
size of SDRAM can be increased to 6 GB in \mu_platform_nxp\NXP\EVK_
iMX8MP_6GB\EVK_iMX8MP_6GB.dsc by modifying giMX8TokenSpaceGuid.
PcdBank1MemorySize to 0x00000000C0000000.
VPU
Limitation: VPU not supported on i.MX 8QXP. i.MX 8QXP
Workaround: VPU will be added in the next release.

4 Revision history
Table 4. Revision history
Revision number Date Substantive changes
W0.9.0 1/2022 Private preview release for i.MX 8M platform.
W0.9.1 3/2022 Public preview release for i.MX 8M platform.
W1.0.0 4/2022 Public release for i.MX 8M and i.MX 8M Mini platforms.
W1.1.0 6/2022 Public release for i.MX 8M Nano and i.MX 8M Plus platforms.
W1.2.0 9/2022 Sections 1.2 and 3 are updated.
W1.2.1 10/2022 Section 1.2 is updated.
W1.3.0 12/2022 i.MX8 QuadXPlus MEK board support added

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

14 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

5 Legal information
5.1 Definitions 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
Draft — A draft status on a document indicates that the content is still agreed in a valid written individual agreement. In case an individual
under internal review and subject to formal approval, which may result agreement is concluded only the terms and conditions of the respective
in modifications or additions. NXP Semiconductors does not give any agreement shall apply. NXP Semiconductors hereby expressly objects to
representations or warranties as to the accuracy or completeness of applying the customer’s general terms and conditions with regard to the
information included in a draft version of a document and shall have no purchase of NXP Semiconductors products by customer.
liability for the consequences of use of such information.
Suitability for use in automotive applications — This NXP product has
been qualified for use in automotive applications. If this product is used
5.2 Disclaimers by customer in the development of, or for incorporation into, products or
services (a) used in safety critical applications or (b) in which failure could
lead to death, personal injury, or severe physical or environmental damage
Limited warranty and liability — Information in this document is believed
(such products and services hereinafter referred to as “Critical Applications”),
to be accurate and reliable. However, NXP Semiconductors does not give
then customer makes the ultimate design decisions regarding its products
any representations or warranties, expressed or implied, as to the accuracy
and is solely responsible for compliance with all legal, regulatory, safety,
or completeness of such information and shall have no liability for the
and security related requirements concerning its products, regardless of
consequences of use of such information. NXP Semiconductors takes no
any information or support that may be provided by NXP. As such, customer
responsibility for the content in this document if provided by an information
assumes all risk related to use of any products in Critical Applications and
source outside of NXP Semiconductors.
NXP and its suppliers shall not be liable for any such use by customer.
In no event shall NXP Semiconductors be liable for any indirect, incidental, Accordingly, customer will indemnify and hold NXP harmless from any
punitive, special or consequential damages (including - without limitation - claims, liabilities, damages and associated costs and expenses (including
lost profits, lost savings, business interruption, costs related to the removal attorneys’ fees) that NXP may incur related to customer’s incorporation of
or replacement of any products or rework charges) whether or not such any product in a Critical Application.
damages are based on tort (including negligence), warranty, breach of
contract or any other legal theory.
Export control — This document as well as the item(s) described herein
Notwithstanding any damages that customer might incur for any reason may be subject to export control regulations. Export might require a prior
whatsoever, NXP Semiconductors’ aggregate and cumulative liability authorization from competent authorities.
towards customer for the products described herein shall be limited in
accordance with the Terms and conditions of commercial sale of NXP Translations — A non-English (translated) version of a document, including
Semiconductors. the legal information in that document, is for reference only. The English
version shall prevail in case of any discrepancy between the translated and
Right to make changes — NXP Semiconductors reserves the right to English versions.
make changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without Security — Customer understands that all NXP products may be subject to
notice. This document supersedes and replaces all information supplied prior unidentified vulnerabilities or may support established security standards or
to the publication hereof. specifications with known limitations. Customer is responsible for the design
and operation of its applications and products throughout their lifecycles
Applications — Applications that are described herein for any of these to reduce the effect of these vulnerabilities on customer’s applications
products are for illustrative purposes only. NXP Semiconductors makes no and products. Customer’s responsibility also extends to other open and/or
representation or warranty that such applications will be suitable for the proprietary technologies supported by NXP products for use in customer’s
specified use without further testing or modification. applications. NXP accepts no liability for any vulnerability. Customer should
Customers are responsible for the design and operation of their regularly check security updates from NXP and follow up appropriately.
applications and products using NXP Semiconductors products, and NXP Customer shall select products with security features that best meet rules,
Semiconductors accepts no liability for any assistance with applications or regulations, and standards of the intended application and make the
customer product design. It is customer’s sole responsibility to determine ultimate design decisions regarding its products and is solely responsible
whether the NXP Semiconductors product is suitable and fit for the for compliance with all legal, regulatory, and security related requirements
customer’s applications and products planned, as well as for the planned concerning its products, regardless of any information or support that may be
application and use of customer’s third party customer(s). Customers should provided by NXP.
provide appropriate design and operating safeguards to minimize the risks
NXP has a Product Security Incident Response Team (PSIRT) (reachable
associated with their applications and products.
at PSIRT@nxp.com) that manages the investigation, reporting, and solution
NXP Semiconductors does not accept any liability related to any default, release to security vulnerabilities of NXP products.
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
customer’s third party customer(s). Customer is responsible for doing all
necessary testing for the customer’s applications and products using NXP 5.3 Trademarks
Semiconductors products in order to avoid a default of the applications
and the products or of the application or use by customer’s third party Notice: All referenced brands, product names, service names, and
customer(s). NXP does not accept any liability in this respect. trademarks are the property of their respective owners.
NXP — wordmark and logo are trademarks of NXP B.V.
Bluetooth — the Bluetooth wordmark and logos are registered trademarks
owned by Bluetooth SIG, Inc. and any use of such marks by NXP
Semiconductors is under license.

IMXWNR All information provided in this document is subject to legal disclaimers. © 2022 NXP B.V. All rights reserved.

Release notes Rev. W1.3.0 — 20 December 2022

15 / 16
NXP Semiconductors
IMXWNR
i.MX Windows 10 IoT Release Notes

Contents
1 Overview .............................................................. 2
1.1 References .........................................................2
1.2 BSP change history ...........................................2
2 BSP supported features ..................................... 8
3 Known issues/limitations ................................. 12
4 Revision history ................................................ 14
5 Legal information .............................................. 15

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

© 2022 NXP B.V. All rights reserved.

For more information, please visit: http://www.nxp.com
Date of release: 20 December 2022
Document identifier: IMXWNR