NXP Semiconductors Document Number: IMXLXRN

Release Notes Rev. L4.9.88_2.0.0-ga, 05/2018

i.MX Linux® Release Notes

Contents

1 Overview 1 Overview....................................................................1

This document contains important information about the 2 What's New?............................................................10

package contents, supported features, known issues and 3 BSP Supported Features.................. ....................... 11
limitations in this release.
4 Kernel Boot Parameters...........................................20
For information on changes in this release, see the manifest
Readme at index: imx-manifest.git and the Change Logs at 5 Known Issues/Limitations................ .......................24
index: imx-manifest.git. 6 Multimedia...............................................................32
Supported hardware SoC/board 7 Revision History......................... ............................ 40
• i.MX 6QuadPlus SABRE-SD Board and Platform
• i.MX 6QuadPlus SABRE-AI Board
• i.MX 6Quad SABRE-SD Board and Platform
• i.MX 6DualLite SDP SABRE-SD Platform
• i.MX 6Quad SABRE-AI Board
• i.MX 6DualLite SABRE-AI Board
• i.MX 6SoloLite EVK Board
• i.MX 6SoloX SABRE-SD Board
• i.MX 6SoloX SABRE-AI Board
• i.MX 7Dual SABRE-SD Board
• i.MX 6UltraLite EVK Board
• i.MX 6ULL EVK Board
Overview

• i.MX 8MQuad EVK Board (Beta Quality)

• i.MX 6SLL EVK Board
• i.MX 7ULP EVK Board

NOTE
In this document, the following notation is used:
• 6SABRE-SD stands for the i.MX 6Quad, i.MX 6QuadPlus, i.MX 6DualLite, and i.MX 6DualPlus
SABRE-SD Platforms.
• 6SABRE-AI stands for the i.MX 6Quad, i.MX 6QuadPlus, and i.MX 6DualLite SABRE-AI
Platforms.
• 6SoloLite stands for the i.MX 6SoloLite EVK
• 6SoloX-SD stands for the i.MX 6SoloX SABRE-SD Platform.
• 6SoloX-AI stands for the i.MX 6SoloX SABRE-AI Platform.
• 7D-SABRE-SD stands for the i.MX 7Dual SABRE-SD Platform.
• 6UltraLite stands for the i.MX 6UltraLite EVK Platform.
• 6ULL stands for the i.MX 6ULL EVK Platform.
• 7ULP stands for the i.MX 7 Ultra Low Power Platform.
• 8MQuad stands for the i.MX 8MQuad EVK Platform.

1.1 Release contents

This release consists of the following package files:
• L4.9.88_2.0.0_images_MX6QPDLSOLOX.tar.gz
• L4.9.88_2.0.0_images_MX6SLEVK.tar.gz
• L4.9.88_2.0.0_images_MX6SLLEVK.tar.gz
• L4.9.88_2.0.0_images_MX6UL7D.tar.gz
• L4.9.88_2.0.0_images_MX8MQ.tar.gz
• L4.9.88_images_MX7ULPEVK.tar.gz
• L4.9.88_2.0.0_mfg-tool.tar.gz
• L4.9.88_2.0.0_mfg-tool_MX8MQ.tar.gz
• imx-yocto-L4.9.88_2.0.0.tar.gz

The GA releases are named "L<Kernel_version>_<x.y.z>".

"<Kernel_version>": BSP Kernel version. (For example, "L4.9.88 indicates that this BSP release is based on the kernel
version 4.9.88)
"<x.y.z>": Semantic versioning specification, where X is the major version, Y is the minor version, and Z is the patch
version.
The following tables list the contents included in each package.
Table 1. Release contents
Component Description
Linux® OS Kernel and Device Trees 4.9.88
U-Boot v2017.03
SD Card images Pre-built images for download, and image files with a selection of packages and
libraries needed for the common tests.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

2 NXP Semiconductors
 Overview

Table 1. Release contents (continued)

Component Description
Manufacturing Tools for i.MX 6, i.MX 7, MFGTools is a program used to burn a production image into the board using a set
i.MX 8MQuad. of predefined parameters, such as the target memory to be used.
USB recognition may fail in serial download mode. You can use SD boot mode
without an SD card in socket to force ROM to enter serial download mode, and
then the MFGTools can work.

In the following table, the U-Boot configurations are listed for each machine configuration. The machine configurations are
provided through the Yocto Project layers in the meta-freescale and meta-fsl-bsp-release layers in the conf/machine sub-
directory.
Table 2. U-Boot configurations
U-Boot configuration for Description Supported machine configuration
Boot device
sd This supports booting from the SD imx6qsabresd, imx6qpsabresd, imx6dlsabresd
card. This is the default U-Boot
imx6qsabreauto, imx6qpsabreauto,
configuration.
imx6dlsabreauto
imx6qsabresd, imx6qpsabresd,
imx6slevk
imx6dlsabresd could be used for
eMMC boot on i.MX 6QuadPlus/Quad imx6sllevk
SDB board and i.MX 6Quad/DualLite
imx6sxsabresd
SDP.
imx6sxsabreauto
imx7dsabresd
imx6ulevk
imx6ull14x14evk
imx7ulpevk
imx8mqevk
spi-nor This supports booting from SPI-NOR. imx6qsabreauto, imx6dlsabreauto
imx6qpsabreauto
imx6slevk
eim-nor This supports booting from Parallel imx6qsabreauto, imx6dlsabreauto,
NOR. imx6solosabreauto imx6qpsabreauto
nand This supports booting from NAND. imx6qsabreauto, imx6dlsabreauto,
imx6solosabreauto imx6qpsabreauto
Note that NAND is not populated on the
i.MX 7Dual SABRE-SD board. Users imx6sxsabreauto
need to populate it if needed.
imx7dsabresd
imx6ull14x14evk
sata This supports booting from SATA. imx6qsabresd, imx6qpsabresd
imx6qsabreauto, imx6qpsabreauto
qspi2 This supports booting from QSPI2. imx6sxsabresd
Booting from the ARM® Cortex®-M4
processor is supported through QSPI2.
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 3
Overview

Table 2. U-Boot configurations (continued)

U-Boot configuration for Description Supported machine configuration
Boot device
Use U-Boot command “bootaux” to
boot the ARM Cortex-M4 processor.
The booting address is 0x78000000.
qspi1 This supports booting from QSPI1. imx6sxsabreauto
Booting from the ARM Cortex-M4
imx7dsabresd
processor is supported through QSPI1.
Use U-Boot command “bootaux” to imx6ulevk
boot the ARM Cortex-M4 processor.
The booting address is changed to
0x68000000.
emmc This supports booting from EMMC. imx6sxsabresd
Note that eMMC is not populated on
imx7dsabresd
the i.MX 7Dual, i.MX 6SoloX SABRE-
SD, or i.MX 7ULP board. Users need to imx6ull14x14evk
populate it if needed.
imx7ulpevk
m4fastup This supports booting from ARM imx6sxsabresd
Cortex-M4 processor by disabling
QSPI2 from using ARM Cortex-M4
processor.
epdc This supports EPDC splash screen in imx6slevk
U-Boot.
imx7dsabresd

The following table describes the kernel and device trees included in this release. A list of several device tree files are
provided for each board to offer examples on how to handle different pin conflicts due to pin muxing.
Table 3. Kernel and device tree configurations
Kernel and device tree configuration Description
zImage for i.MX 6 and i.MX 7 Binary kernel image for the 4.9.88 kernel. This kernel is built with the
imx_v7_defconfig for any i.MX 6 or i.MX 7 boards.
Kernel image for i.MX 8MQuad
Binary kernel image for i.MX 8MQuad kernel is built using defconfig in
arch/arm64/configs/.
Kernel image: Image
Default DTB Each reference board has a standard device tree as follows:
• zImage-imx6q-sabresd.dtb, zImage-imx6qp-sabresd.dtb
• zImage-imx6dl-sabresd.dtb
• zImage-imx6q-sabreauto.dtb, zImage-imx6qp-sabreauto.dtb
• zImage-imx6dl-sabreauto.dtb
• zImage-imx6sl-evk.dtb
• zImage-imx6sx-sdb.dtb, zImage-imx6sx-sdb-reva.dtb
• zImage-imx6sx-sabreauto.dtb
• zImage-imx7d-sdb.dtb
• zImage-imx6ul-14x14-evk.dtb, zImage-imx6ul-9x9-evk.dtb
• zImage-imx6ull-14x14-evk.dtb
• zImage-imx7ulp-evk.dtb
• Image-fsl-imx8mq-evk.dtb
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

4 NXP Semiconductors
 Overview

Table 3. Kernel and device tree configurations (continued)

Kernel and device tree configuration Description
Note: zImage-imx6sx-sdb.dtb is used for supporting the i.MX 6SoloX
SABRE-SDB Rev. B board, and imx6sx-sdb-reva.dtb is used for
supporting the legacy SABRE-SDB Rev. A board.
zImage-imx7d-sdb.dtb is used for supporting the i.MX 7Dual SABRE-SDB
Rev. C and Rev. D boards, and zImage-imx7d-sdb-reva.dtb is used for
supporting the legacy SABRE-SDB Rev. A board.
i.MX 8MQuad DTB Board DTB files:
• fsl-imx8mq-evk.dtb: for HDMI output
• fsl-imx8mq-evk-lcdif-adv7535.dts: for MIPI-DSI output with the MIPI-
to-HDMI adapter by using the LCDIF display controller
• fsl-imx8mq-evk-dcss-adv7535.dtb: for MIPI-DSI output with the
MIPI-to-HDMI adapter by using the DCSS display controller
• fsl-imx8mq-evk-dcss-rm67191.dtb: for MIPI-DSI output with the MIPI
panel by using the DCSS display controller
• fsl-imx8mq-evk-dual-display.dtb: for dual-dispaly-to-HDMI and MIPI-
to-HDMI adapter
• fsl-imx8mq-ddr4-arm2.dtb: for DDR4 validation board booting from
SD
• fsl-imx8mq-ddr4-arm2-gpmi-nand.dtb: for DDR4 validation board
booting from NAND
• fsl-imx8mq-ddr3l-arm2.dtb: for DDR3L validation board
GPMI and EIM_NOR Enables the GPMI and EIM-NOR. Due to pin conflicts, the GPMI and EIM-
NOR are disabled by default. See the device tree file for more details:
• zImage-imx6dl-sabreauto-gpmi-weim.dtb
• zImage-imx6q-sabreauto-gpmi-weim.dtb
• zImage-imx6qp-sabreauto-gpmi-weim.dtb
• zImage-imx7d-sdb-gpmi-weim.dtb and zImage-imx7d-sdb-reva-
gpmi-weim.dtb
ldo In standard DTB file, the LDO bypass is enabled. Therefore, to use LDO
device trees on configurations with [email protected], which does not
support LDO bypass mode, it is important to enable LDO. The LDO is
enabled in the following DTB files:
• zImage-imx6q-sabresd-ldo.dtb
• zImage-imx6qp-sabresd-ldo.dtb
• zImage-imx6ul-9x9-evk-ldo.dtb
• zImage-imx6dl-sabresd-ldo.dtb
• zImage-imx6sl-evk-ldo.dtb
• zImage-imx6sx-sdb-ldo .dtb, zImage-imx6sx-sdb-reva-ldo.dtb
hdcp Enables the HDMI-HDCP feature. This avoids the pin conflict between the
I2C2 and HDCP-DDC pins.
• zImage-imx6q-sabresd-hdcp.dtb
• zImage-imx6dl-sabresd-hdcp.dtb
• zImage-imx6qp-sabresd-hdcp.dtb
ecspi Enables eCSPI, which is disabled in the default DTB.
• zImage-imx6dl-sabreauto-ecspi.dtb
• zImage-imx6q-sabreauto-ecspi.dtb
• zImage-imx6qp-sabreauto-ecspi.dtb
flexcan1 Enables flexcan1, which is disabled by default in standard DTB file due to
pin conflicts with FEC.
• zImage-imx6q-sabreauto-flexcan1.dtb
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 5
Overview

Table 3. Kernel and device tree configurations (continued)

Kernel and device tree configuration Description
• zImage-imx6dl-sabreauto-flexcan1.dtb
• zImage-imx6qp-sabreauto-flexcan1.dtb
csi Enables CSI support for V4L2.
On i.MX 6UltraLite EVK, this device tree avoids the pin conflict between
SIM and CSI.
• zImage-imx6sl-evk-csi.dtb
• zImage-imx6ul-14x14-evk-csi.dtb
• zImage-imx6ul-9x9-evk-csi.dtb
enetirq An example to demonstrate GPIO6 workaround for the bug where
only the ENET wake-up interrupt request can
wake the system from Wait mode.
Since the pad GPIO6 is used by l2C3 on the board, these device trees
have I2C3 disabled to enable this workaround
• zImage-imx6q-sabresd-enetirq.dtb
• zImage-imx6dl-sabresd-enetirq.dtb
• zImage-imx6dl-sabreauto-enetirq.dtb
• zImage-imx6q-sabreauto-enetirq.dtb
emmc The eMMC chip is DNP by default. This requires hardware modifications
to burn the eMMC4.5 chip on the eMMC socket on uSDHC0 and connect
eMMC signals as well as disconnect BOOT SD CARD slot signals.
• zImage-imx6sx-sdb-emmc.dtb
• zImage-imx7ulp-evk-emmc.dtb
Cortex-M4 Disable the access of ADC 1 & 2, flexcan 1 & 2, I2C3, UART 2 and QSPI
2 from Cortex-A processor when ARM Cortex-M4 processor is running.
• zImage-imx6sx-sdb-m4.dtb
• zImage-imx6sx-sabreauto-m4.dtb
• zImage-imx7d-sdb-m4.dtb
• Image-fsl-imx8mq-evk-m4.dtb
epdc Pin conflict between HDMI and EPDC, disable HDMI for EPDC.
• zImage-imx7d-sdb-epdc.dtb
• zImage-imx7d-sdb-reva-epdc.dtb
qspi Enable DDR Quad mode for Macronix QSPI chip mx25l51245g by setting
Quad bit in status register.
• zImage-imx7-sdb-qspi.dtb zImage-imx7-sdb-reva-qspi.dtb
• zImage-imx7ulp-evk-qspi.dtb
Audio Enable WM8960 audio as the default one and disable HDMI audio.
• zImage-imx7ulp-evk-wm8960.dtb
HDMI Audio Enable HDMI audio as the default one and disable WM8960 audio.
• zImage-imx7d-sdb-reva-hdmi-audio.dtb
touch Add tsc2046 touch screen controller support. Because the pin PENIRQ of
tsc2046 conflicts with the interrupt pin of HDMI, this disables the HDMI.
• zImage-imx7-sdb-reva-touch.dtb
MIPI Display Enable MIPI-DSI.
• zImage-imx7d-sdb-mipi-dsi.dtb
• imx7ulp-evk-mipi.dtb
Bluetooth® wireless technology Wi-Fi Enable the Broadcom Bluetooth wireless technology and Wi-Fi hardware.
• zImage-imx6q-sabresd-btwifi.dtb
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

6 NXP Semiconductors
 Overview

Table 3. Kernel and device tree configurations (continued)

Kernel and device tree configuration Description
• zImage-imx6qp-sabresd-btwifi.dtb
• zImage-imx6dl-sabresd-btwifi.dtb
• zImage-imx6sl-evk-btwifi.dtb
• zImage-imx6sll-evk-btwifi.dtb
• zImage-imx6sx-sabresd-btwifi.dtb
• zImage-imx6ul-14x14-evk-btwifi.dtb
• zImage-imx6ul-9x9-evk-btwifi.dtb
• zImage-imx6ull-14x14-evk-btwifi.dtb
USB Enable USB certification for i.MX 6UltraLite.
• zImage-imx6ul-14x14-evk-usb-certi.dtb
LP UART Enable LPUART.
• zImage-imx7ulp-evk-lpuart.dtb
sd1 Enable sd1 on uSDHC1 on the base board.
• zImage-imx7ulp-sd1.dtb

The release package contains the following pre-built images.

Table 4. Pre-built images
Package Description
XWayland SDCard This release provides the following SD card images for i.MX 6 and i.MX 7.
These images include a GUI with XWayland backend. The imx6qpdlsolox
image works on all i.MX 6 boards GPU with U-Boot and device tree
changes. To change U-Boot and the device tree, see the i.MX Linux®
User's Guide (IMXLUG).
• fsl-image-validation-xwayland-imx6qpdlsolox.sdcard
• fsl-image-validation-xwayland-imx6ul7d.sdcard
• fsl-image-validation-xwayland-imx6sllevk.sdcard
• fsl-image-validation-xwayland-imx7ulpevk.sdcard
Kernel Kernel and device trees as specified in Table 3.
U-Boot U-Boot files as specified in Table 2.
mfgtools_with_rootfs.tar.gz Manufacturing tools with the rootfs support.
M4-Demo i.MX 7ULP demo:
• imx7ulp_m4_demo.img

i.MX 8MQuad demo:

• imx8mq_m4_hello_world.bin
• imx8mq_m4_TCM_hello_world.bin
• imx8mq_m4_TCM_rpmsg_lite_pingpong_rtos_linux_remote.bin
• imx8mq_m4_TCM_rpmsg_lite_str_echo_rtos.bin
i.MX 8 Combined Boot Image Boot image that combines HDMI Firmware, DDR Firmware, U-Boot, and
Arm Trusted Firmware.

Table 5. imx-yocto-L4.9.88_2.0.0-ga.tar.gz content

File name Description
README README for L4.9.88_2.0.0-ga.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 7
Overview

Table 5. imx-yocto-L4.9.88_2.0.0-ga.tar.gz content (continued)

File name Description
/doc The following docs are provided: i.MX Linux® Release Notes, User's Guide,
Porting Guide, Graphics Guide,VPU API Reference Manual, Yocto Project
User's Guide, and Reference Manual.

Table 6. Multimedia standard packages

File name Description Comment
imx-codec-4.3.5.bin i.MX codecs i.MX optimized A/V core codec
imx-parser-4.3.5.bin i.MX parser i.MX optimized core parser
imx-vpuwrap-4.3.5.bin i.MX VPU wrapper i.MX VPU wrapper for VPU library

Contact a marketing representative to get access to the following controlled packages.

Table 7. Controlled access packages
File name Description Comment
imx-aacpcodec-4.3.5.bin AACplus decoder i.MX optimized AACplus decoder
imx-mscodec-4.3.5.bin Microsoft codecs i.MX optimized Microsoft codecs
imx-msparser-4.3.5.bin Microsoft parser i.MX optimized Microsoft ASF parser
imx-ac3codec-4.3.5.bin AC3 decoder i.MX optimized Dolby audio AC3 decoder
imx-ddpcodec-4.3.5.bin DDplus decoder i.MX optimized Dolby audio DDplus decoder
imx-real-4.3.5.bin Real Networks codecs and parser i.MX optimized Real Networks real audio
decoder, real media parser. i.MX 6 also provides
real video firmware
eink-waveform-firmware-1.0.2.bin E Ink E Ink REGAL/-D waveform for associated E Ink
panels.
firmware-bcmdhd-1.363.22.bin Broadcom Bluetooth® firmware and Broadcom Firmware for Wi-Fi and Bluetooth
Wi-Fi firmware wireless technology.

1.2 License
The Board Support Package (BSP) is composed of a set of packages and metadata (for Yocto Project Recipes) and each one
has its own licensing. Verify the license of the target package before developing. The license can be found at the top of a
recipe or a source file (such as *.c or *.h). For details, contact your NXP representative.
The following components are released as binary files on the Yocto Project Mirror and have NXP Proprietary Licenses.
During the Yocto Project setup, to set up an i.MX build, accept the NXP license. This acceptance is recorded in the build
configuration files so that the following proprietary binaries can be extracted during the build process. The NXP proprietary
packages contain a Software Content Register (SCR) file that lists information about the package: imx-gpu-viv, imx-codec,
and imx-parser.

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

8 NXP Semiconductors
 Overview

1.3 Proprietary Licensing Packages

i.MX packages can be found in two locations:
• Standard packages are provided on the NXP mirror. They are accessed automatically by the Yocto Project scripts as
needed.
• Limited Access packages listed in the following table are provided on nxp.com with controlled access. Contact your
sales representative for access. These include codecs to support WMA, WMV, RMVB, AAC+, AC3, DD+ decoding,
encoding, WMA, Broadcom firmware, and E Ink firmware. Each package has its own Readme file with instructions on
how to build, install, and run.

Table 8. Limited access packages for Yocto project releases

Name Package Comment
AACPlus Decoder imx-aacpcodec-4.3.5.bin i.MX AACplus core decoder
Microsoft Codec imx-mscodec-4.3.5.bin i.MX optimized MS codec
Microsoft Parser imx-msparser-4.3.5.bin i.MX optimized ASF parser
AC3 Decoder imx-ac3codec-4.3.5.bin i.MX AC3 core decoder
DDplus Decoder imx-ddpcodec-4.3.5.bin i.MX DD-plus decoder
RMVB Decoders and Parser imx-real-4.3.5.bin i.MX Real Networks
E Ink Waveform firmware-eink-1.363.22.bin E Ink REGAL/-D waveform for i.MX 7D
SABRE-SD
Broadcom Firmware firmware-bcmd-1.363.22.bin Broadcom Bluetooth wireless
technology and Wi-Fi firmware
Broadcom Bluetooth Applications BSA- Broadcom Bluetooth wireless
ServerAndClientsApps-0107.00.16.bin technology applications

1.4 References
This release includes the following references and additional information.
• i.MX Linux® Release Notes (IMXLXRN) - Provides the release information.
• i.MX Linux® User's Guide (IMXLUG) - Contains the information on installing U-Boot and Linux OS and using i.MX-
specific features.
• i.MX Yocto Project User's Guide (IMXLXYOCTOUG) - Contains the instructions for setting up and building Linux
OS in the Yocto Project.
• i.MX Reference Manual (IMXLXRM) - Contains the information on Linux drivers for i.MX.
• i.MX Graphics User's Guide (IMXGRAPHICUG) - Describes the graphics features.
• i.MX BSP Porting Guide (IMXXBSPPG) - Contains the instructions on porting the BSP to a new board.
• i.MX VPU Application Programming Interface Linux® Reference Manual (IMXVPUAPI) - Provides the reference
information on the VPU API.

The quick start guides contain basic information on the board and setting it up. They are on the NXP website.
• SABRE Platform Quick Start Guide (IMX6QSDPQSG)
• SABRE Board Quick Start Guide (IMX6QSDBQSG)
• i.MX 6UltraLite EVK Quick Start Guide (IMX6ULTRALITEQSG)
• i.MX 6ULL EVK Quick Start Guide (IMX6ULLQSG)
• SABRE Automotive Infotainment Quick Start Guide (IMX6SABREINFOQSG)
• i.MX 6SoloLite Evaluation Kit Quick Start Guide (IMX6SLEVKQSG)

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 9
What's New?

• i.MX 7Dual SABRE-SD Quick Start Guide (SABRESDBIMX7DUALQSG)

• i.MX 8MQuad Evaluation Kit Quick Start Guide (IMX8MQUADEVKQSG)

Documentation is available online at nxp.com.

• i.MX 6 information is at nxp.com/iMX6series
• i.MX SABRE information is at nxp.com/imxSABRE
• i.MX 6SoloLite EVK information is at nxp.com/6SLEVK
• i.MX 6UltraLite information is at nxp.com/iMX6UL
• i.MX 6ULL information is at nxp.com/iMX6ULL
• i.MX 7Dual information is at nxp.com/iMX7D
• i.MX 7ULP information is at nxp.com/imx7ulp
• i.MX 8 information is at nxp.com/imx8

2 What's New?
This section describes the changes in this release, including new features and defect fixes.

2.1 New features

A summary of the main new features is as follows.
New features added for all supported boards:
• Upgraded the kernel to 4.9.88 and includes Spectre and Meltdown patches.
• Updated EULA to v22 April 2018.
• New location at Code Aurora Forum at https://source.codeaurora.org/external/imx/ :
• New manifest imx-manifest for distributions
• New repos at Code Aurora Forum repo site
• Upgraded the Yocto Project to version 2.4 Rocko.
• Upgraded U-Boot to 2017.03.
• Supports the GCC 7.3 toolchain.
• Supports Optee, but it is not enabled by default. For how to enable it, see ReadMe.
• Graphics updates:
• GPU driver upgraded to 6.2.4.p1.
• GPU SDK upgraded to 5.0.2
• Chromium browser upgraded to v64.0.3282.186 for X11 and v64.0.3274.0 for XWayland.
• New multimedia features and changes:
• GStreamer upgraded to 1.12.2
• Qt upgraded to 5.9
• On SoCs without hardware graphics acceleration (GPU) for Frame Buffer, X11 or Wayland graphic backends
QT5 is handled only using mesa software graphics, and it is not supported by NXP.
• Supports Qualcomm Wi-Fi and Bluetooth.
• Supports CAN FD mode in FlexCAN.
• Supports suspending and resuming.
• Supports MIPI DSI panel.
• Supports USB3.0 device mode for i.MX 8.

Features on i.MX 8MQuad

• Engineering release for:
• supporting WIFI/BT with Qulcomm Driver integration new GPU fixes.

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

10 NXP Semiconductors
 BSP Supported Features

2.2 Power management supported features

The following common power management features are supported on i.MX 6 and i.MX 7:
• CPU/GPU frequency throttle for SoCs with GPU
• GPU dynamic power management for SoCs with GPU
• CPU idle framework with two working levels: pure WFI and WFI with wait mode enabled
• Low power mode: standby and dormant (mem) mode
• Thermal temperature

Power management features supported on 6SoloLite, 6SABRE-SD, and 6SABRE-AI:

• LDO bypass
• CPUFreq driver: CPU frequency adjusted based on the CPU loading and Interactive governor
• VPU/GPU dynamic power management for SoCs with VPU and GPU
• LDO bypass
• Bus frequency support
• SD3.0 dynamic clock management
• USB remote wake-up and USB charger

2.3 Graphics
This section describes new features and bug fixes for the graphics provided in this release.
Graphics Changes are now available in the following locations
• Changes for i.MX with GPU are documented on https://source.codeaurora.org/external/imx/imx-manifest.git/tree/
GraphicsChangeLogv6?h=imx-linux-rocko.

3 BSP Supported Features

The following table describes the features that are supported in this BSP release. In this table, if no board is explicitly stated,
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 9. Supported features
Feature Supported Comment
board
Kernel
Kernel All i.MX Kernel version: 4.9.88
File System All i.MX EXT2/EXT3/EXT4 are used as the file system in MMC/eMMC/SD card.
On i.MX 6SABRE-AI and 7D-SABRE-SD,
• UBIFS is used for NAND.
• JFFS2/UBIFS is used for Parallel NOR, QSPI NOR.
Bootloader
U-Boot All i.MX U-Boot delivery is based on U-Boot version v2017.03.
Clock, Anatop regulator, ENET, UART, MMC/SD, eMMC4.3/4.4/4.5.
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 11
BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
High-Assurance Boot, ROM Plug-in Mode.
SPI-NOR, Parallel NOR, SATA, NAND, FlexSPI-NOR, USB Mass Storage.
See Table 2 in Section 1.1 for U-Boot configurations supported on each board for
SPI_NOR, NAND, Parallel NOR, FlexSPI-NOR. These are not supported on all
boards.
i.MX 6QuadPlus/Quad/DualLite SABRE-SD and SABRE-AI support DDR3 528 MHz @
64 bit.
i.MX 6SoloX SABRE-SD and SABRE-AI support LDDR3 400 MHz @ 32 bit.
i.MX 6SoloLite EVK supports LPDDR2 400 MHz @ 32 bit and boot using L2Cache as
OCRAM.
i.MX 6SoloLite EVK supports LPDDR.
i.MX 7Dual SABRE-SD supports DDR3 533 MHz @ 32 bit and boot using L2Cache as
OCRAM.
i.MX 6UltraLite EVK supports DDR3 400 Mhz @ 16 bit.
i.MX 6ULL supports DDR3 400 Mhz @ 16 bit.
i.MX 7ULP supports Clock, UART, MMC/SD, eMMC4.3/4.4/4.5, High-Assurance Boot,
ROM Plug-in Mode QuadSPI-NOR, USB Mass Storage I2C, and SPI.
i.MX 8 uses imx-mkimage to produce the flash.bin file that contains the i.MX 8 system
controller firmware and U-Boot, and the flash.bin file that can be flashed to the SD
cards with the command: dd if=flash.bin of=/dev/sd<x> seek=33 bs=1K.
8MQuad, 8QuadMax, and 8QuadXPlus use seek=33 bs=1k.
Machine-specific layer
Arm® Core All i.MX 6SABRE-SD, 6SABRE-AI, 6SoloLite, 6SLL, 6SoloX-SD, and 6SoloX-AI support the
Arm Cortex-A9 processor.
7D-SABRE-SD supports the Arm Cortex-A7 processor.
7ULP EVK supports the Arm Cortex-A7 processor.
6UltraLite EVK supports the Arm Cortex-A7 processor.
6ULL EVK, 6UltraLite EVK, and 7D-SABRE-SD support the Arm Cortex-A7 processor.
i.MX 8MQuad supports four Cortex-A53 cores.
Memory All i.MX On i.MX 6 and i.MX 7 SoC, the user/kernel space is split 2G/2G.
On i.MX 8 with 64-bit configuration, the memory is not split.
Interrupt All i.MX GIC.
Clock All i.MX Controls the system frequency and clock tree distribution.
Timer (GPT) All i.MX System timer tick and broadcast timer support.
GPIO/EDIO All i.MX GPIO is initialized in earlier phase according to hardware design.
IOMUX All i.MX Provides the interfaces for I/O configuration. IOMUX-V3 version is used on i.MX 6 and
i.MX 7 boards.
DMA engine
SDMA All i.MX except Conforms to the DMA engine framework.
i.MX 7ULP
APBH-Bridge-DMA 6SABRE-AI Conforms to the DMA engine framework. This feature requires a NAND U-Boot.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

12 NXP Semiconductors
 BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
Character device drivers
MXC UART All i.MX i.MX 6 SABRE-SD, and SoloLite EVK support console through internal Debug UART1.
i.MX 6SoloX SABRE-SD and SABRE-AI support Cortex-A9 processor through UART1
and Cortex-M4 processor through UART2.
i.MX 7Dual SABRE-SD Cortex-A7 processor through UART1 and Cortex-M4
processor through UART2.
i.MX 6UltraLite EVK and i.MX 6ULL Cortex-A7 processor through UART1.
i.MX 6 SABRE-AI supports console through internal Debug UART 4.
i.MX 7ULP EVK supports through LPUART. There are two LPUARTs on the i.MX
7ULP EVK board. LPUART0 is connected to Arm Cortex-M4 domain and LPUART4 to
Arm Cortex-A7 domain.
i.MX 8 supports Cortex-A53 processor through UART0 and Cortex-M4 processor
through UART2.
Power Management Drivers
Anatop Regulator All i.MX Supports Anatop regulator management.
Lower Power mode All i.MX 6 and Supports standby mode and dormant (mem) mode on i.MX 6 and i.MX 7 boards.
7
CPUIdle All i.MX 6 and 2 levels CPUIdle supported: purely WFI and WFI with wait mode enabled.
7
CPUFreq All i.MX CPUFreq can be used for CPU frequency adjustment. The Interactive governor is
added and enabled by default.
BusFreq All i.MX 6 Supports the system bus clock frequency scaling on i.MX 6 and i.MX 7D boards.
7D-SABRE-SD
Battery charging All i.MX 6 and -
7
Networking drivers
ENET All i.MX 6 i.MX 6Quad/SoloX board supports AR8031 PHY, i.MX 6UltraLite EVK board supports
KSZ8081 PHY, and i.MX 7Dual SABRE-SD board supports BCM54220 PHY.
7D-SABRE-SD
i.MX 6SoloX SABRE-SD, SABRE-AI, and i.MX 7Dual SABRE-SD support AVB
8MQuad
features.
i.MX 8 supports Atheros AR8031 PHY with 10/100/1000 bps mode and AVB features.
IEEE® 1588 All i.MX 6 and Supports Linuxptp stack.
7
Features:
• Supports IPv4, IPv6, and IEEE 802.3 transport.
• Supports E2E, and P2P transparent clock.
• Supports IEEE802.1AS-2011 in the role of end station.

Note:
Linuxptp stack is open source.
Command instance:

ptp4l -A -4 -H -m -i eth0
PCIe All i.MX With the platform that supports the PCIe module.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 13
BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
PCIe EP/RC i.MX 6Quad Two of the same i.MX 6Quad SD boards, i.MX 7Dual SABRE-SD boards, or i.MX
validation system SD 6SoloX SDB boards. One is used as RC, and the other is used as EP.
• EP can be initialized/enumerated by RC.
i.MX 6SoloX-
• EP can access the memory of RC.
SD
• RC can access the memory of EP.
7D-SABRE-SD • EP can trigger MSI, and the triggered MSI can be captured by RC.
MediaLB 6SABRE-AI On i.MX 6SABRE-AI, CPU1 supports MLB 150 and MLB 25/50. On i.MX 6SABRE-AI,
CPU2 and i.MX 6QuadPlus SABRE-AI supports MLB 25/50 only.
6SoloX-AI
On i.MX 6SoloX-AI, it supports MLB 25/50.
FlexCAN All i.MX 6 Supports one CAN with the default device tree on i.MX 6SABRE-AI. Supports both
CANs using the FlexCAN device tree but has a pin conflict with FEC.
7D-SABRE-SD
Supports with the default device tree on i.MX 6SoloX-SD and i.MX 6SoloX-AI.
Supports with the default device tree on i.MX 7Dual SABRE-SD.
Supports with the default device tree on i.MX 6UltreLite EVK.
Supports with the default device tree on i.MX 6ULL EVK.
Security drivers
CAAM All i.MX 6 and Cryptographic Acceleration and Assurance Module.
7 except 6LL,
6SoloLite, and
6ULL
SNVS All i.MX 6 and Secure Non-Volatile Storage.
7
SIMv2 6UltraLite Smart Card Interface.
7D-SABRE-SD
Sound drivers
WM8962/SSI 6SABRE-SD Supports playback.
WM8960/SSI 6SoloLite
6SoloX-SD
7D-SABRE-SD
6UltraLite
6ULL
7ULP
S/PDIF 6SABRE-SD Supports 16 bit and 24 bit stereo playback from 32 KHz to 48 KHz sample rate.
6SABRE-AI Supports 24 bit stereo record from 16 KHz to 96 KHz.
6SoloX-AI
ASRC 6SABRE-AI Supports sample rates conversion from 5 KHz to 192 KHz and output sample rates
from 32 KHz to 192 KHz.
6SoloX-SD
Supports ALSA plug-in library playback.
6UltraLite
6ULL
ESAI/CS42888 6SABRE-AI Supports 16 bit, 24 bit PCM format, channel from 2 to 6, and sample rate from 8 KHz
to 192 KHz for playback with ASRC P2P.
6SoloX-AI
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

14 NXP Semiconductors
 BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
Supports sample rate from 8 KHz to 96 KHz for record and playback without ASRC.
Supports 4 channels input and 8 channels output.
Supports full duplex operations.
Supports amixer alsamixer control from user space.
SAI/MQS 6SoloX-SD Supports 16 bit, 24 bit, and 32 bit PCM format.
7D-SABRE-SD Supports sample rate from 8 KHz to 96 KHz for record and playback .
6UltraLite Supports full duplex operations.
6ULL Supports amixer alsamixer control from user space.
7ULP Supports clock control.
8MQuad
HDMI Audio 6SABRE-SD Supported on the i.MX 6Dual/Quad and i.MX 6DualLite for SABRE-SD and SABRE-AI.
6SABRE-AI Supported on the i.MX 7Dual SABRE-SD board.
7D-SABRE-SD
Input device drivers
USB devices All i.MX Supports USB mouse and USB keypad through USB ports.
Touch panel All i.MX 6SABRE-SD, 6SABRE-AI. Supports EGalaxy capacitive touch screen.
6SoloLite supports E Ink® touch screen on DC2/DC3 add-on card.
7Dual SABRE-SD supports E Ink® touch screen with a separate package download.
6SoloX SABRE-SD and SABRE-AI support LVDS panel.
7ULP EVK supports touch through DSI panel
Keypad 6SoloLite 6SoloLite supports 4x4 keypads on DC2/DC3 add-on card.
6UltraLite 6UltraLite EVK , 7ULP EVK and 7D SABRE-SD support the resistive touch panel.
7D-SABRE-SD
7ULP
MTD driver
FlexSPI-NOR 6SoloX-SD i.MX 6SoloX SABRE-AI supports QSPI1. i.MX 6SoloX SABRE-SD supports QSPI2.
6SoloX-AI i.MX 6UltraLite EVK supports QSPI1.
7D-SABRE-SD i.MX 7Dual SABRE-SD supports QSPI1.
6UltraLite
6ULL
8MQuad
SPI-NOR 6SABRE-AI Supports M25P32
6SoloLite On i.MX 6SABRE-SD DualQuad/DualLite there is a pin conflict for supporting SPI-
NOR
NAND 6SABRE-AI Normal NAND and ONFI NAND asynchronous mode with BCH40/BCH62.
6SoloX-AI
7D-SABRE-SD
Parallel NOR 6SABRE-AI Supports Parallel NOR by using the EIM interface on i.MX 6 SABRE-AI.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 15
BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
SATA 6SABRE-SD Serial ATA 2.0 supports only i.MX 6DualQuad SABRE-SD and SABRE-AI and i.MX 6
QuadPlus SABRE_SD and SABRE-AI and 8QuadMax.
6SABRE-AI
USB drivers
USB Host 6SABRE-AI Supports USB HOST1 and USB OTG host.
6SoloLite
6SoloX-SD
6SoloX-AI
7D-SABRE-SD
6UltraLite
6ULL
7ULP
8MQuad
USB Device All i.MX Supports USB OTG device mode.
USB All i.MX Supports USB OTG2.0, USB Host2.0, USB 3.0, and Type-C ports. USB 3.0 is only
supported by i.MX 8.
USB Host mode: MSC, HID, UVC, and USB audio.
USB device mode: MSC, Ethernet, and Serial.
USB OTG pin detect support for Dual-role switch at USB2.
Graphics drivers
GPU 6SABRE-SD Graphics Chips Details
6SABRE-AI One GC7000-Lite on 8MQuad.
6SoloX GC2000, GC355, and GC320 on 6Dual/6Quad
6SoloLite GC2000+, GC355, and GC320 on 6QuadPlus
7ULP GC880 and GC320 on 6Solo/DualLite
8MQuad GC400T on 6SoloX
The GPU on the chips listed above supports these features that include 2D and 3D
hardware acceleration:
• Supports EGL 1.5 for fbdev, X11, XWayland
• Supports OpenGL ES1.1
• Supports OpenGL ES2.0 (WebGL 1.0.1 compatible on X11)
• Supports OpenGL ES3.0
• Supports OpenVG1.1
• Supports OpenCL1.1 on GC2000 and GC2000+.
• Supports OpenGL2.1

GC355 and GC320 on 6SoloLite, which includes only 2D hardware acceleration

• Supports EGL 1.5 for fbdev, X, Wayland
• Supports OpenVG1.1
Frame Buffer Driver All i.MX MXC Frame buffer driver for IPU V3 on i.MX 6SABRE-SD and i.MX 6SABRE-AI.
MXC Frame buffer driver for PXP on i.MX 6SoloLite, i.MX 6SoloX SABRE-SD/SABRE-
AI, i.MX 6UltraLite EVK i.MX 6ULL EVK and i.MX 7Dual SABRE-SD.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

16 NXP Semiconductors
 BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
VDOA 6SABRE-SD Supports Video Data Order Adapter.
6SABRE-AI
LVDS 6SABRE-SD Supports HannStar LVDS panel. It is the default display if no other video option is
setup.
6SABRE-AI
On the SABRE-AI there are 2 ports. Port 0 is the default.
6SoloX-SD
6SoloX-AI
HDMI 6SABRE-SD i.MX 6SABRE-SD and SABRE-AI support on-chip DesignWare HDMI hardware
module.
6SABRE-AI
i.MX 7D-SABRE-SD supports on-chip DesignWare HDMI hardware module.
6SoloLite
i.MX 6SoloLite and i.MX 6SoloX SABRE-SD and SABRE-AI support external HDMI.
6SoloX-SD
i.MX 7ULP EVK supports HDMI through the MIPI pins.
6SoloX-AI
i.MX DCSS is used for i.MX 8MQuad.
7D-SABRE-SD
7ULP
8MQuad
HDCP 6SABRE-SD Supports HDCP v1.2 specifications.
WVGA panel All i.MX 6 and Supports SEIKO WVGA panel.
7
For i.MX 6UltraLite, i.MX 6ULL and i.MX 7Dual SABRE-SD, it supports Embest
LCD8000-43T LCD panel.
PxP 6DualLite-SD Enables PXP Driver for EPDC on i.MX 6SoloLite , i.MX 6SLL and i.MX 6DualLite
SABRE-SD.
6SoloLite
Enables PXP driver for EPDC on i.MX 7Dual SABRE-SD i.MX 6UltaLite EVK and i.MX
6SLL
6ULL EVK.
6SoloX-SD
Conforms to DMA engine framework.
6SoloX-AI
7D-SABRE-SD
6UltraLite
6ULL
MIPI Display 6SABRE-SD Supports MIPI DSI driver through MIPI daughter card on i.MX 6 and i.MX 7-SABRE-
SD.
7D-SABRE-SD
Support MIPI DSI with direct connection on i.MX 7ULP
7ULP
Supports MIPI display drived by LCDIF with up to 720p60.
8MQuad
Supports MIPI display driven by DCSS with up to 1080p60.
Framebuffer 8MQuad Supports graphic framebuffer compression with DEC400.
compression
Supports video framebuffer compression with DTRC.
EPDC 6DualLite-SD Supports RGB565 frame buffer format.
6SoloLite Supports Y8 frame buffer format.
6SLL Supports full and partial EPD screen updates.
7D-SABRE-SD Supports up to 256 panel-specific waveform modes.
Supports automatic optimal waveform selection for a given update.
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 17
BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
Supports synchronization by waiting for a specific update request to complete.
Supports screen updates from an alternate (overlay) buffer.
Supports automated collision handling.
Supports 64 simultaneous update regions.
Supports pixel inversion in a Y8 frame buffer format.
Supports posterization of the update contents (driving all pixels to either solid black or
white).
Supports use of a color map to remap Y8 frame buffer contents.
Supports 90, 180, and 270 degree HW-accelerated frame buffer rotation.
Supports panning (y-direction only).
Supports three EPDC driver display update schemes: Snapshot, Queue, and Queue
and Merge.
Supports user control of the delay between completing all updates and powering down
the EPDC.
Supports dithering.
i.MX 7Dual supports E Ink® but requires a separate download. Contact Marketing
representative.
Multimedia Drivers
IPU V3 driver 6SABRE-SD On i.MX 6SABRE-SD and i.MX 6SABRE-AI provides interfaces to access IPU V3
modules.
6SABRE-AI
PRE/PRG driver 6QuadPlus-SD On i.MX 6QuadPlus provides interfaces to support prefetch linear frames or resolve
tiled frames for display.
6QuadPlus-AI
V4L2 Output All i.MX i.MX 6SABRE-SD and i.MX 6SABRE-AI use the IPU post-processing functions for
video output.
i.MX 6SoloLite, i.MX 6SoloX SABRE-SD and SABRE-AI, i.MX 6UltraLite EVK and i.MX
7D SABRE-SD use the PXP post-processing functions for video output.
i.MX 7ULP EVK uses MIPI connection for V4L2 output.
V4L2 Capture All i.MX 6 and Supports dual cameras on i.MX 6SABRE-SD and SABRE-AI.
7-SABRE-SD
Supports single camera on i.MX 6SoloLite and i.MX 6SoloX SABRE-SD, i.MX
6UltraLite EVK, i.MX 6ULL EVK, and 7D-SABRE-SD.
VPU 6SABRE-SD i.MX 6 Encoder: MPEG-4, H.263, H.264 (AVC/MVC), MJPEG
6SABRE-AI i.MX 6 Decoder: MPEG-4, H.263, H.264 (AVC/MVC), VC-1,MPEG-2, MJPEG, AVS,
VP8.
8MQuad
i.MX 8MQuad Decoder: HEVC, VP9, H.264, MPEG-2, MPEG-4p2, VC-1, VP8, RV9,
AVS, MJPEG, H.263.
MIPI Camera 8MQuad Supports MIPI camera OV5640 with 720p30, 1080p30, 2592x1944@15.
MIPI 6SABRE-SD Supports 2 lanes CSI and DSI. Supports OV5640 camera sensor.
7D-SABRE-SD
7ULP
Parallel CSI 6SABRE-SD i.MX 6 Supports OV5640 camera sensor.
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

18 NXP Semiconductors
 BSP Supported Features

Table 9. Supported features (continued)

Feature Supported Comment
board
6SoloLite
6SoloX-SD
6UltraLite
6ULL
TV-IN 6SABRE-AI Supports TV-IN through ADV7180 on the 6SABRE-AI with bt656, NTSC, and PAL.
General drivers
uSDHC All i.MX Supports SD2.0 and SDXC.
Supports SD3.0 on all i.MX except 6SABRE-SD.
Supports eMMC 1bit/4bit/8bit SDR/DDR mode. i.MX 6SABRE-SD is soldered, i.MX
6SABRE-AI uses the daughter card, and i.MX 6SoloX-SD is not soldered.
Supports eMMC4.5 on i.MX 6SoloLite and i.MX 6SoloX-SD.
Supports eMMC5.0 on i.MX 7Dual SABRE-SD.
Watchdog All i.MX Supports Watchdog reset.
I2C All i.MX Supports I2C master.
SPI All i.MX Supports SPI master mode.
PWM All i.MX Supports the backlight driver through PWM.
ADC 6SoloX-SD Supports the ADC driver.
6SoloX-AI
7D-SABRE-SD
6UltraLite
6ULL
7ULP
Temperature All i.MX Pre-calibrated. See the "Thermal Driver" chapter in i.MX Linux® Reference Manual
monitor (IMXLXRM) for more information.
Accelerometer 6SABRE-SD Supports the MMA8451 sensor on i.MX 6SABRE-SD, i.MX 6SoloX-SABRE-SD, and
SABRE-AI.
6SoloLite
Supports the MMA8450 sensor on i.MX 6SoloLite.
6SoloX-SD
Supports the FXLS8471Q sensor on 6UltraLite EVK and 6ULL EVK.
6SoloX-AI
Supports the FXOS8700CQR1 sensor on the i.MX 7.
6UltraLite
6ULL
7D-SABRE-SD
7ULP
Wi-Fi/Bluetooth 6SABRE-SD Supports Murata 1CQ (QCA6174A) Wi-Fi/Bluetooth.
wireless technology
6SoloLite Supports the WL_HOST_WAKE (OOB) feature for all the listed boards except i.MX
6UL/ULL EVK, which requires hardware rework.
6SoloX-SD
The CONFIG_BCM4339 performance optimization option is not enabled by the default
6UltraLite
kernel. Users can enable it manually to gain big performance improvement.
6ULL
7D-SABRE-SD
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 19
Kernel Boot Parameters

Table 9. Supported features (continued)

Feature Supported Comment
board
7ULP NOTE: i.MX 6SoloLite EVK does not support enabling CONFIG_BCM4339 due to the
known Wi-Fi driver limitation. For i.MX 8MQuad, it needs to add kernel parameter
8MQuad
"pci=nomsi" to support Murata 1CQ Wi-Fi.
Bluetooth wireless 6SABRE-SD Supports Qualcomm QCA9377-3 Bluetooth module on i.MX 7ULP. Supports
technology Qualcomm QCA6174A Bluetooth module on i.MX 8QuadMax/8QuadXPlus/8MQuad.
6SoloX-SD
The default Bluetooth software stack is BlueZ, but Broadcom provides a Bluetooth
6UltraLite stack that supports additional Bluetooth profiles if using Broadcom hardware.
6ULL For Bluetooth A2DP, if Yocto project has no frame buffer, for example, the 6UltraLite
G1 part chip has no LCDIF, run the pulseaudio manually with the command:
7D-SABRE-SD
7ULP /usr/bin/pulseaudio --start --log-target=syslog
GPIO Expander 6SABRE-SD Supports the MAX7310 GPIO expander on i.MX 6 SABRE-SD and SABRE-AI.
6SABRE-AI Supports the 74LV595 GPIO expander on i.MX 7Dual SABRE-SD.
7D-SABRE-SD Supports PCA9557 on i.MX 8.
SNVS RTC All i.MX 6 and SNVS is a block that interfaces with CAAM and SRTC.
7
Ambient Light 6SABRE-SD Supports the ISL29023 sensor on i.MX 6 boards.
Sensor
6SABRE-AI Supports the ISL29023 sensor on i.MX 8 boards
6SoloX-SD
6SoloX-AI
Pressure and 6SABRE-SD Supports the MAG3110FCR2 sensor on i.MX 6 boards.
Gyroscope
6SABRE-AI Supports the FXLS8471 sensor on i.MX 6UltraLite EVK board.
Magnetometer
Sensor 6SoloX-SD Supports MPL3115A2, FXOS8700CQR1, and FXAS21002CQR1 sensors on all the
i.MX 7 boards.
6SoloX-AI
6UltraLite
7D-SABRE-SD
7ULP-EVK
AM/FM module 6SABRE-AI Supports the SI4763 AM/FM module. Supports FM by using the SSI interface.

4 Kernel Boot Parameters

Depending on the booting or usage scenario, you may need different kernel boot parameters.
The following table describes different boot parameters.
To force the i.MX 6SABRE-AI board to disable SMP to remove overhead, add boot parameters "nosmp". Disabling
CONFIG_SMP configuration can remove further overhead for single core.

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

20 NXP Semiconductors
 Kernel Boot Parameters

Table 10. Common kernel boot parameters

Kernel Description Typical value Used when
parameter
console Where to output the console=ttymxc0,115200 All use cases
kernel logging by
For 6SABRE-AI, console=ttymxc3,115200
printk.
For 6SoloX-AI, console=ttymxc0,115200
For 7ULP, console=ttyLP0, 115200
console=ttymxc0, 115200
nosmp A command-line nosmp CONFIG_SMP is defined. Use this to
option of 'nosmp' disable SMP activation. SMP is
disables SMP activated by default through the
activation entirely. CONFIG_SMP configuration.
ip Tells the kernel how ip=none "ip=dhcp" or
or whether to get an
ip=dhcp "ip=static_ip_address" is mandatory in
IP address.
"boot from TFTP/NFS."
ip=static_ip_address
nfsroot Location of the NFS nfsroot=<ip_address>:<rootfs path> Used in "boot from tftp/NFS" together
server/directory. with "root=/dev/nfs."
root Location of the root root=/dev/nfs Used in "boot from tftp/NFS" (that is,
file system. root=/dev/nfs);
or
Used in "boot from SD" (that is,
root=/dev/mmcblk0p2
root=/dev/mmcblk0p2).
root is set by default by U-Boot to the
SD/MMC slot that U-Boot is booting
from.
rootfstype Indicates the file rootfstype=ext4 Used in "boot from SD" together with
system type of the "root=/dev/mmcblkXpY" (X is the MMC
root file system. device number while Y is the rootfs
partition number.)
rootwait Waits (indefinitely) for rootwait Used when mounting SD root file
the root device to system.
show up.
mem Tells the kernel how None or Note: MemTotal-<mem> -
much memory can be <gpu_memory> is reserved.
mem=864M
used.
max17135 Configures the max17135:pass=[pass_num],vcom=[vcom Used when enabling EPDC. pass_num
maximum of 17135 _uV] should equal 2 for all IMXEBOOKDC2
EPD PMIC pass cards. vcom_uV, in microvolts, should
For 7D-SABRE-SD (EPDC panel upgrade
number and VCOM be equal to the value printed on the
to DC4):
voltage. cable connector that is attached the E
max17135:pass=2,vcom=-2370000
Ink panel being used.
fec.macaddr Tells the Ethernet fec.macaddr=0x00,0x04,0x9f, Changes the FEC MAC address.
MAC address. 0x01,0x30,0x05
maxcpus [SMP] Maximum maxcpus=1 maxcpus=n : n >= 0 limits the kernel to
number of processors using 'n' processors. n=0 is a special
that SMP kernel situation. It is equivalent to "nosmp".
should use.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 21
Kernel Boot Parameters

Table 10. Common kernel boot parameters (continued)

Kernel Description Typical value Used when
parameter
epdc Enables EPDC video=mxcepdcfb:E060SCM,bpp=16 Adds to kernel options only if E Ink is
the primary display panel. If other
For 7D-SABRE-SD (EPDC panel upgrade
display panel is primary, this option
to DC4): video=mxcepdcfb:ED060XC8
may result in a pixel clock conflict and
improper display function.
video on Tells the kernel/driver 1. video=mxcfb0:dev=hdmi, 1. Used when primarily displaying
6SABRE-SD which resolution/ 1920x1080M@60,if=RGB24 on HDMI with 1080P60 mode.
depth and refresh video=mxcfb1:dev=ldb,if=RGB666 Secondarily displaying on LVDS
rate should be used 2. video=mxcfb0:dev=ldb,if=RGB666 with XGA mode.
for display port 0 or 1. video=mxcfb1:dev=hdmi, 2. Used when primarily displaying
1920x1080M@60,if=RGB24 on LVDS with XGA mode.
See the parameter
3. video=mxcfb0:dev=hdmi, Secondarily displaying on HDMI
information under
1920x1080M@60,if=RGB24 with 1080P60 mode.
Documentation/fb/
4. video=mxcfb0:dev=ldb,if=RGB666 3. Used when primary displaying on
modedb.txt
5. video=mxcfb0:dev=lcd,CLAA- HDMI with 1080P60 mode.
Tells the kernel/driver WVGA,if=RGB656 4. Used when primary displaying on
which IPU display 6. video=mxcfb0:dev=mipi_dsi,TRULY- the HannStar LVDS1.
interface format WVGA,if=RGB24 5. Used when primary displaying on
should be used. the CLAA-WVGA dumb parallel
LCD panel.
6. Used when primary displaying on
the TRULY-WVGA MIPI DSI
LCD panel.

NOTE: GBR24/RGB565/YUV444
represents the display HW interface
format. Typical values for certain
different display devices are as follows:
TVOUT: YUV444
VGA: GBR24
HDMI&DVI: RGB24
CLAA WVGA LCD: RGB565
Typical values for dev= are shown as
follows:
lcd: LCD interface
ldb: LVDS
hdmi: HDMI on chip or sii902x
dvi: DVI port
vga: VGA through TVE
tve: TVOUT
video on Tells the kernel/driver 1. video=mxcfb0:dev=hdmi, 1. Used when primarily displaying
6SABRE-AI which resolution/ 1920x1080M@60,if=RGB24video=m on HDMI with 1080P60 mode.
depth and refresh xcfb1:dev=ldb,if=RGB666 Secondarily displaying on LVDS
rate should be used 2. video=mxcfb0:dev=ldb,if=RGB666vi with XGA mode.
for display port 0 or 1. deo=mxcfb1:dev=hdmi, 2. Used when primarily displaying
1920x1080M@60,if=RGB24 on LVDS with XGA mode.
3. video=mxcfb0:dev=hdmi, Secondarily displaying on HDMI
1920x1080M@60,if=RGB24 with 1080P60 mode.
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

22 NXP Semiconductors
 Kernel Boot Parameters

Table 10. Common kernel boot parameters (continued)

Kernel Description Typical value Used when
parameter
See the parameter 4. video=mxcfb0:dev=ldb,if=RGB666 3. Used when primary displaying on
information under 5. video=mxcfb0:dev=hdmi, HDMI with 1080P60 mode.
Documentation/fb/ 1920x1080M@60,if=RGB24 4. Used when primary displaying on
modedb.txt the HannStar LVDS0.
5. Used when enabling HDMI
Tells the kernel/driver
1080P60 mode and LVDS0. To
which IPU display
enable second display, run "echo
interface format
0 > /sys/class/graphics/fb2/blank"
should be used.
NOTE: GBR24/RGB565/YUV444
represents the display HW interface
format. Typical values for certain
different display devices are shown as
follows:
TVOUT: YUV444
VGA: GBR24
HDMI&DVI: RGB24
CLAA WVGA LCD: RGB565
Typical values for dev= are shown
below:
lcd: LCD interface
ldb: LVDS
hdmi: HDMI on chip or sii902x
dvi: DVI port
vga: VGA through TVE
tve: TVOUT
video on Tells the EPDC FB video=mxcepdcfb:E060SCM,bpp=16 Used when enabling EPDC to select
6SoloLite driver which E Ink the correct E Ink panel parameters to
panel is in use and use.
what bpp should be
bpp=16 selects RGB565 FB pix format
used for the Frame
Buffer. bpp=8 selects Y8 FB pixel format
video on Tells the ELCDIF FB video=mxc_elcdif_fb:SEIKO- Used when enabling LCDIF to select
6SoloLite driver which LCD WVGA,bpp=16 the correct panel parameters to use.
panel is in use and
bpp=16 selects RGB565 FB pix format
which bpp should be
used for the Frame Note: if only use EPDC FB, then turn
Buffer. off ELCDIF FB by
"video=mxc_elcdif_fb:off"
video on 7D Tells the ELCDIF FB video=mxcfb0:dev=mipi_dsi,TRULY- Used when primary displaying on the
SABRE-SD driver which LCD WVGA,if=RGB24 TRULY-WVGA MIPI DSI LCD panel.
panel is in use and
which bpp should be
used for the Frame
Buffer.
dmfc Tells the kernel/driver None "dmfc=1" means
how to set the IPU DMFC_HIGH_RESOLUTION_DC.
Or
DMFC segment size.
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 23
Known Issues/Limitations

Table 10. Common kernel boot parameters (continued)

Kernel Description Typical value Used when
parameter
dmfc=3 "dmfc=2" means
DMFC_HIGH_RESOLUTION_DP.
"dmfc=3" means
DMFC_HIGH_RESOLUTION_ONLY_
DP.
DMFC_HIGH_RESOLUTION_ONLY_
DP can only be set by the command
line. It is recommended to set this
when no IPU connects the two panels.
When it is set, each IPU can only
connect one panel.
mtdparts on Tells the kernel mtd mtdparts=gpmi-nand:16m(boot), When to enable NAND. The partition:
6SABRE-AI partition information. 16m(kernel),1024m(rootfs),-(user) 16m (boot),16m (kernel),1024m (rootfs)
is an example, you can change it
according to your needs.
uart clock from Chooses the UART's uart_from_osc This is necessary for low power idle
osc for 6SoloX clock parent. and all use cases with the FreeRTOS
low power idle running on ARM Cortex-M4 processor.
and scenario of When setting this parameter, UART
Linux OS and sources clock from OSC instead of
FreeRTOS PLL3_80M, and then all PLLs can be
running together off in low power idle.

NOTE
For full command line list, see kernel source tree Documentation/Kernel-parameter.txt.

5 Known Issues/Limitations
Read through all hardware-related reference material and ensure that the necessary hardware modifications are made before
using the software.
The following tables list some key known issues.
Table 11. Known issues and workarounds for i.MX 7ULP
Module Source Description Workaround
GPU Software Chromium crashes on Xwayland graphics. No workaround.
DTB Software The imx7ulp-evk-sd1.dtb in the release image Delete the “no-1-8-v” property.
does not support 3.0 SD Card, because it has
the property of “no-1-8-v”.
DTB Software The display coordinates under the touch panel Change the display-coords to <0, 0, 480, 854>.
node in imx7ulp-evk.dts is configured
incorreclty, which may cause the touch point to
be inaccurate.
GPU Software 16 test cases of webgl1.0.2 CTS failed with The issue is related with chromium v64 version,
the error of timeout. and it can be fixed with a new version of
chromium.

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

24 NXP Semiconductors
 Known Issues/Limitations

Table 12. Common known issues and workarounds for i.MX 6 and i.MX 7
Module Source Description Workaround
Thermal Hardware The Temperature Monitor should only be Ensure proper temperature calibration before
enabled for chips that have undergone proper using the temperature monitor. See the
thermal sensor calibration. MC marked "Thermal Driver" Chapter in the i.MX Linux®
devices have undergone temperature Reference Manual (IMXLXRM).
calibration.
Ethernet Software When booting an image from the local storage, To solve this problem, unmask connman and
the network connection over Ethernet is not start:
established automatically. This is because
connman is masked. $ systemctl unmask connman
$ systemctl enable connman
$ systemctl start connman
Otherwise, udhcpc can be used to establish a
network connection:

$ udhcpc

Table 13. Known issues and workarounds for i.MX 8MQuad

Module Source Description Workaround
GPU Software OpenCL 1.2FP and ES31 conformance No workaround.
test random fails.
DTRC Software The display turns to green sometimes Disable the playback video with
when playback video with DTRC enabled. DTRC.
NAND Boot Hardware Fails to boot up from NAND when the Boot up from NAND with the boot
boot file is integrated with the HDMI file that does not have the HDMI
firmware. firmware.
MIPI CSI Hardware MIPI CSI: prompts lots of "Rx fifo Use different DDR and NoC
overflow" when running capture and configuration from Errata.
video playback simultaneously.
MIPI DSI Software When using DCSS to drive the MIPI Do not perform system
display, after resuming from system suspending or resuming.
suspending, the display is black.
QCA6174 PCIE Wi-Fi Software The QCA CLD driver of the release It needs to add kernel parameter
doeso not support PCIe MSI. pci=nomsi to support Wi-Fi.

Table 14. Known issues and workarounds for i.MX 6 SABRE-SD and i.MX 6 SABRE-AI
Module Source Description Workaround
ARM core Software smp_wmb performance is very low. This is the common side-effect of
SMP. No fix plan.
IPU Software The framebuffer driver and V4L2 output Frame Buffer operations should
driver share the same fb device.For be banned during video playback
example, /dev/video16 also uses on the same FB device.
the /dev/fb0 to do video playback.
IPU Hardware Currently, only supports 4-stripe and 2- No workaround.
stripe split mode. When doing large ratio
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 25
 Known Issues/Limitations

Table 14. Known issues and workarounds for i.MX 6 SABRE-SD and i.MX 6 SABRE-AI
(continued)
Module Source Description Workaround
up-scaling from low resolution frames to
high resolution frames, for example,
64x64 to 1920x1080, the requirement
cannot be covered by the current split
mode solution, that is, each stripe would
exceed 1024 pixels for width. Therefore,
the video cannot display a full screen.
IPU Hardware CSI_SMFC_MEM capture channel The current workaround is to
cannot support 32 pixel IDMAC burst size change 32 pixel burst size to 16
for non-interleaved and partial-interleaved pixel burst size, which would
YUV pixel formats with non-16byte- bring considerable capture
aligned UV stride line. Little horizontal performance penalty.
stripes can be seen on the capture
frames.
LVDS Hardware HannStar HSD100PXN1 panel, backlight No workaround.
brightness does not change from 0 to 2.
This is limitation that comes from the
panel itself. This is also a limitation for all
the i.MX 6Quad/QuadPlus/DualLite/SoloX
platforms, which use this HannStar
HSD100PXN1 panel.
PRE Hardware When the software write No workaround.
(hw_pre_ctrl_pio_write) and the hardware
write (hw_pre_ctrl_enable_enable ) are in
the same clock cycle, the hardware write
is ignored, because the software write
has a higher priority. It causes the PRE to
stop working unless the whole PRE+PRG
+ IPU corresponding channel is restarted.
This issue is tracked by the PDM ticket
TKT275991. The relevant framebuffer
pan display or set par operations may
cause the PRE to stop working due to
accidentally triggering the hardware bug.
GPU Software There are some errors with the webgl Upgrade the Chrome application
conformance test. This is a Chrome to the stable version with V52.
application problem, which does not pass
down the correct parameters to the GPU
driver, and does not handle the
application error correctly.
GPU Software Xwayland is not displayed when running Apply the new GPU patch
the VDK ES11 application with the release after 5.0.11.p8.6.
retrace tool. This is not a GPU driver
problem. It only has impact on the ES11
VDK use case on the Xwayland platform,
no impact on the typical usage in general.
PCIe Hardware/Software To pass the PCIe compliance tests, Add one extra DTB file to support
external OSC should be used as the PCIe to pass the compliance
PCIe REF clock. Therefore, to import the tests. For example, "imx6qp-
external OSC to PCIe, the PLL6_ENET sabresd-ldo-pcie-cert.dtb" used
should be set to bypass mode. Then, the
ENET/SATA cannot work simultaneously.
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

26 NXP Semiconductors
 Known Issues/Limitations

Table 14. Known issues and workarounds for i.MX 6 SABRE-SD and i.MX 6 SABRE-AI
(continued)
Module Source Description Workaround
by iMX 6QuadPlus SABRE-SD
board to pass the PCIe
compliance tests.
Memory Management Software The system reports page allocation This may be caused by the
failure: order:9, mode:0xd0 when the kernel page reclaiming issue.
system does not have sufficient physical One workaround for this: echo 1
continuous memory to allocate. > /proc/sys/vm/drop_caches
before you run the application.
HDMI Software HDMI cannot be set to 1080p@60hz with Use the xrandr application to
kernel configuration settings. configure the HDMI resolution
from user-space.
ASRC Hardware Two ASRC M2M instances and one P2P When there are three instances,
instance conversion simultaneously meet the total MIPS consumption
serious noise on 176 KHz and 192 KHz should not exceed the ASRC
sampling rates. master clock (132 MHz). In this
situation, the total MIPS
consumption is more than 120
MHz, and it is close to the
threshold (132 MHz) in theory.
Therefore, this is a capability
issue of ASRC, and the noise is
expected.

Table 15. Known issues and workarounds for i.MX 6 SABRE-SD

Module Source Description Workaround
SPI NOR Hardware SPI NOR boot is not supported by the SABRE- Current SD board uses KEY relative PINs as
boot SD board. SPI interface. However, this set of PINs are not
supported by ROM. Therefore, SPI NOR boot is
not supported by the SABRE-SD board.
CPU hotplug Software System hangs after conducting CPU hot plug Known ARM Linux OS limitation. No
many times during heavy interrupt. workaround as of yet.
VPU Software Cannot support the "-x 1" option for unit test To avoid this issue, do not use "-x 1", since "-x
program mxc_vpu_test.out, because the IPU 1" means enable for IPU library.
library is removed.
IPU Hardware Currently, the IPU only supports 4-stripe and No workaround.
2-stripe split mode. When doing large ratio up-
scaling from low resolution frames to high
resolution frames, for example, 64x64 to
1920x1080, the requirement cannot be
covered by the current split mode solution, that
is, each stripe would exceed 1024 pixels for
width. Therefore, the video cannot display a
full screen.

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 27
Known Issues/Limitations

Table 16. Known issues and workarounds specifically for i.MX 6Dual/6Quad SABRE-SD
Module Source Description Workaround
SATA Boot Hardware The system cannot boot from SATA on the Rev.B Remove R7.
board.
Boot Hardware The system cannot boot sometimes when it ist Add 2.2M ohm resistor to 24M OSC.
powered on the Rev. B board for the first time.
Suspend/ Hardware/ Suspend/Resume failure if board rework "Add Remove rework.
Resume Software 2.2M ohm resistor to 24M OSC".

Table 17. Known issues and workarounds specifically for i.MX 6Solo/6DualLite SABRE-SD
Module Source Description Workaround
PMIC Hardware The i.MX 6DualLite SD board depopulates the i.MX 6DualLite uses dumb mode by default.
resistor R30 and takes away the ability of the
processor to turn off the PMIC in hardware.
EPDC Software Enabling E Ink Auto-update mode (Device Disable the E Ink Auto-update Mode feature in
Drivers > Graphics Support > E Ink Auto- the menuconfig.
update Mode Support) causes E Ink panel
updates to be distorted and flaky.
EPDC Hardware The three boards cannot boot with EPDC DC2 This occurs when the SW3 (KEYPAD_LOCK)
attached while they boot normally without DC2 switch on the EBOOK DC2 board is switched
daughter cards. "ON", which affects the boot bin "EIM_DA7"
(BT_CFG1_7). You need to set the SW3 in DC2
board to "OFF."

Table 18. Known issues and workarounds for i.MX 6Dual/6Quad SABRE-AI
Module Source Description Workaround
ARM core Software CONFIG_SMP should be disabled for the i.MX To remove overhead caused by SMP for better
6Solo chip. performance, CONFIG_SMP is expected to be
disabled for single core. Complete support with
SMP disabled is provided with future Linux BSP
release.
IPU Hardware Default 24bpp on the second display used by No workaround.
HDMI. IPU keeps printing error for hardware
bandwidth limitation as described in CR
ENGR00293432.
eCompass Hardware eCompass cannot work after EIM-NOR or SPI- No workaround.
NOR are enabled on the kernel.
USB Software USB OTG and USB host cannot work after No workaround.
EIM-NOR or SPI-NOR are enabled on kernel.
TV-IN Software Error messages may be expected along with No workaround.
bad quality at first frames on the TV-IN
interface. This may occur on a hot plug
connection.
U-Boot Hardware ENGR00236878: eMMC 4.4 fails to boot on No workaround.
SABRE-AI boards.
MLB Software The SYNC mode cannot work stably in the No workaround.
test.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

28 NXP Semiconductors
 Known Issues/Limitations

Table 18. Known issues and workarounds for i.MX 6Dual/6Quad SABRE-AI (continued)
Module Source Description Workaround
SDIO3.0 Software No available device to do the SDIO 3.0 test. No workaround.
SPI-NOR Software Fail to erase NOR memory. Will be fixed in the next release.

Table 19. Known issues and workarounds specifically for i.MX 6QuadPlus
Module Source Description Workaround
PRE Hardware When the software write(hw_pre_ctrl_pio_write) and the hardware No workaround.
write(hw_pre_ctrl_enable_enable ) are in the same clock cycle, the
hardware write is ignored, because the software write has a higher
priority. It causes the PRE to stop working unless the whole PRE
+PRG + IPU corresponding channel is restarted.
This issue is tracked by the PDM ticket TKT275991. The relevant
framebuffer pan display or set par operations are likely to cause the
PRE to stop working due to accidentally triggering the hardware
bug.

Table 20. Known issues and workarounds specifically for i.MX 6Solo/6DualLite SABRE-AI
Module Source Description Workaround
Hardware Hardware HDMI, SD3 card detection, and eGalax This is because some PINs are not soldered well.
manufacture touch screens are found to fail on some If any basic feature, which is announced to be
boards. supported, does not work on your board, check
the board.
CPU hotplug Software System hangs after conducting CPU hot Known ARM Linux OS limitation. No workaround
plug many times during heavy interrupt. as of yet.
VPU Software Cannot support "-x 1" option for unit test To avoid this issue, do not use "-x 1", because "-x
program mxc_vpu_test.out, because 1" means enabled for IPU library.
IPU library is removed.

Table 21. Known issues and workarounds for i.MX 6SoloLite

Module Source Description Workaround
EPDC Software Enabling E Ink Auto-update mode (Device Disable the E Ink Auto-update Mode feature
Drivers > Graphics Support > E Ink Auto- in the menuconfig.
update Mode Support) causes E Ink panel
updates to be distorted and flaky.
System Hardware Reboot may not work on the EVK board. Reboot function should be always okay if
the hardware can trigger PMIC reset, which
ensures RESET key and watchdog reset
can control PMIC_ON_REQ pin.
CSI/EPDC Hardware Cannot be used simultaneously, because The board file in BSP configures these pins
these two modules share the same pins on for proper function through DTS. Use
the EVK board. imx6sl-evk.dts for EPDC, and imx6sl-evk-
csi.dts for CSI.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 29
Known Issues/Limitations

Table 21. Known issues and workarounds for i.MX 6SoloLite (continued)
Module Source Description Workaround
X-Acceleration Hardware/ Out of memory error during the x11perf It is a system limitation since the x11perf
Software test. needs a lot of memory. No work-around on
the EVK board (only with LPDDR2 memory
of 512 MB). Users may use a larger memory
to work around this issue.
Mfgtool2 Software Mfgtool2 may fail to execute the frf Remove the frf command from ucl2.xml to
command if there is no send or pipe fix this issue.
command executed prior to it.
FUSE for RTC Hardware SEC_CONFIG[0] fuse bit is not burned, In U-Boot prompt, run the command "imxotp
which leads the RTC not to be functional. blow --force 4 0x2". This action is
irreversible.
SDIO3.0 Software No available device to do the SDIO 3.0 No workaround.
test.
HDMI Software ENGR00298771, i.MX 6SoloLite EVK: on No workaround. Only found on 1400x1050
some special resolutions, such as mode until now.
1400x1050, the Yocto Project GUI display
on HDMI is distorted. This is caused by
xrandr and tries to expand the frame buffer
size to 1408x1050 to align with 16 bytes.
However, i.MX 6SoloLite ELCDIF does not
support stride buffer and cannot crop
1400x1050 from the buffer 1408x1050,
which then causes distortion.
WiFi/BCMDHD Software i.MX 6SoloLite EVK does not support This relese does not support
enabling CONFIG_BCM4339 to optimize CONFIG_BCM4339.
performance due to known Wi-Fi driver
limitation.

Table 22. Known issues and workarounds for i.MX 6SoloX

Module Source Description Workaround
Video Software The video display has a green line at No workaround.
bottom during gplay.
CAAM Software The system reboots after the CAAM There is hardware function conflict between the
RNG test is suspended and resumed. Mega/Fast mix off feature and CAAM. To use
CAAM after kernel bootup, the user should
enable the CAAM wakeup function to avoid
Mega mix off in DSM. Workaround: echo
enabled > /sys/bus/platform/devices/
2100000.aips-bus/2100000.caam/2101000.jr0/
power/wakeup
VADC Software Sometimes VADC cannot correctly The VADC auto standard detect function is not
detect the video standard. CSI works in required. VADC input device does not change in
NTSC mode but the VADC input is PAL. product. Hard code VADC input standard in the
VADC driver.
MLB Software SYNC mode is not stable. No workaround.
QSPI-NOR Hardware PMIC needs to be reset to reset the Connect NOR chip pin 3 to U6 pin 15.
QSPI-NOR flash on the board to the
default 3 bytes mode.

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

30 NXP Semiconductors
 Known Issues/Limitations

Table 22. Known issues and workarounds for i.MX 6SoloX (continued)
Module Source Description Workaround
PCIe Hardware/ When the extremely power save mode is No workaround.
Software enabled on i.MX 6SoloX PCIe, the i.MX
6 SoloX PCIe phy/controller would be
powered off completely, all the TLPs on
the PCIe link would be discarded, and
link would be down in suspend. The i.MX
6 SoloX PCIe and the PCIe link would be
re-initialized completely during resume
operations. There is one known issue
when the pcie2usb device is used during
suspend/resume. The development node
of the pcie2usb device maybe changed,
since the pcie2usb device is reset when
the i.MX 6SoloX PCIe is re-initialized
during resume.
MMC Software Hynix eMMC times out when the rootfs Rootfs should not automatically mount the
automatically mounts the RPMB partition RPMB partition, because it is a secure partition.
on i.MX 6SoloX SD.
CSI/LCD Hardware CSI and LCD cannot be used No workaround.
simultaneously since the two modules
share the same pins on the i.MX 6SoloX
SABRE-SD board.
UART Hardware UART cannot wake up with the RTS pin No workaround.
programmed with hard flow control
enabled. And there is limitation of the
framesize to about 16.

Table 23. Known issues and workarounds for i.MX 6UltraLite and 6ULL EVKs
Module Source Description Workaround
EMMC/SD/ Hardware For i.MX 6ULL, the existing errata No workaround.
SDIO ERR010450, EMMC HS200, and SD/SDIO
3.0 SDR104 at 1.8 V can only work below
or equal to 150 MHz. EMMC DDR52 and
SD/SDIO DDR50 at 1.8 V can only work
below or equal to 45 MHz.

Table 24. Known issues and workarounds for i.MX 7Dual SABRE-SD
Module Source Description Workaround
EPDC Software EPDC does not function for REGAL/-D The upper-layer application or framework needs
due to license issue. to check the correct touch driver.
HDMI Software HDMI supports only one startup Cannot port Vivante or NXP EXA driver to the
resolution mode 1280x720 when i.MX 7Dual board, because the EXA driver
booting to X backend rootfs. depends on Vivante's 2D library and there is no
GPU hardware on i.MX 7Dual. Therefore, a
default software version driver (FBDEV) is used
for i.MX 7Dual. The FB video mode is changed
by FB command, but the UI cannot get the
Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 31
Multimedia

Table 24. Known issues and workarounds for i.MX 7Dual SABRE-SD (continued)
Module Source Description Workaround
video mode changed event, because i.MX
7Dual has no GPU hardware and still draws the
UI to original video mode. No workaround.
HDMI Software After booting up, it connects to the Cannot port Vivante or NXP EXA driver to the
HDMI cable. The X backend desktop i.MX 7Dual board, because the EXA driver
cannot display. depends on Vivante's 2D library and there is no
GPU hardware on i.MX 7Dual. Therefore, a
default software version driver (FBDEV) is used
for i.MX 7Dual. It is expected, because FB video
mode is changed after the HDMI cable is
plugged in, and the UI cannot handle the HDMI
cable plugin event or change the UI to new
video mode. No workaround.
Wi-Fi Software Wi-Fi does not support suspend/ BroadCom Wi-Fi is not supported.
resume when doing IPERF.
PCIe Hardware Cannot probe up PCIe devices on Hardware rework is required. Rework: Change
Rev. C board. C459&C458 caps to 0 ohm resistors.
eMMC Software eMMC fast boot fails with plug-in U- 1. Use U-Boot SPL to replace the plug-in
Boot. boot, which supports the uSDHC driver.
SPL can read the remaining U-Boot from
eMMC by itself without using ROM's API.
2. Plug-in implements its own eMMC read
routine to read the remaining U-Boot.
Low power Hardware TKT291710 low-power idle stress test No workaround.
fails in the Linux OS kernel, with
identical hardware settings. CPU #0
runs into exception, and CPU #1 is
successful.

6 Multimedia
This chapter contains the information on the 4.3.5 multimedia component of the BSP.
The GStreamer version in this release is 1.12.2.

6.1 i.MX GStreamer plugins

Table 25. i.MX GStreamer 1.0 plugins
Plugin Features
Audio decoder beepdec: unified audio decoder plugin
Supports MP3, AAC, AAC+, WMA, AC3, Vorbis, DD+, AMR, RA
Audio encoder avenc_mp2: MP3 encoder plugin from gst-libav
Video decoder • vpudec: VPU-based video decoder plugin
• Software video decoder plugins: use gst-libav plugins

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

32 NXP Semiconductors
 Multimedia

Table 25. i.MX GStreamer 1.0 plugins (continued)

Plugin Features
Video encoder • vpuenc_h264: VPU-based AVC/H264 video encoder
• vpuenc_h263: VPU-based H263 video encoder
• vpuenc_mpeg4: VPU-based MPEG4 video encoder
• vpuenc_jpeg: VPU-based JPEG video encoder
Demux aiurdemux: aiur universal demuxer plugin supporting
Supports AVI, MKV, MP4, MPEG2, ASF, OGG, FLV, WebM, RMVB
Video Decoder vpudec: video decoder plugin based on the hardware video decoder
Video render • imxv4l2sink: V4L2-based video sink plugin
• overlaysink : G2D-based video sink plugin
• kmssink: video sink based on the DCSS KMS driver
• glimagesink: video sink based on EGL
Video source • v4l2src: V4L2 based camera source plugin
Video convert • imxvideoconvert_g2d: GPU2D-based video convert plugin, to perform video color
space conversion, resize, rotate
• imxvideoconvert_ipu: IPU-based video convert plugin, to perform video color space
conversion, resize, rotate, deinterlacing
• imxvideoconvert_pxp: PXP-based video convert plugin, to perform video color
space conversion, resizing, and rotation
OpenGL (ES) Plugins • glimagesink: OpenGL (ES)-based video sink plugin, supported in Wayland and FB
backends
• gleffects: GL Shading Language effects plugin
• gldeinterlace: video deinterlacing based on shaders
• glvideomixer: compositing multiple videos together
• glcolorconvert: video color space convert based on shaders
• glcolorbalance: adjusting brightness, contrast, hue, and saturation on a video
stream
Video compositor • imxcompositor_g2d: GPU2D-based video compositor plugin
• imxcompositor_ipu: IPU-based video compositor plugin
• imxcompositor_pxp: PXP-based video compositor plugin
• Video compositor plugins can compose multiple videos into one, support color
space conversion, resize, rotate, alpha, z-order and keep aspect ratio feature at the
same time while composition

NOTE
• To support WMA, AAC+, AC3, DD+, and RA decoding, install separate packages.
• vpudec plugins are only for SoCs with the VPU hardware.
• OpenGL (ES) plugins are from the gst-plugins-bad package, accelerated with
Vivante private APIs.
• Enable video framebuffer compression (DTRC) by using: kmssink force-
hantrotile=true.

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 33
Multimedia

6.2 i.MX playback example

i.MX provides an example gplay-1.0 application based on GStreamer's high-level API GstPlayer. The example provides the
following functions.
Table 26. i.MX playback engine example
Function Feature
Playback • Play, Stop
• Pause, Resume
• Fast seek, Accurate seek
• Playback rate control (fast forward, fast rewind, slow forward)
Media Info • Media meta data (artist, year, etc.)
• Video Thumbnail
• Audio Album Art
Subtitle • Supports internal and external subtitle
Track Selection • Audio Track Selection
• Video Track Selection
• Subtitle Selection
Display Control • Resize

6.3 i.MX recording engine API

i.MX provides a high-level API set for easier-making camera-related applications based on the GStreamer framework. This
API set is based on the camerabin, which is from the gst-plugins-bad package.
This API can be found at gst1.0-fsl-plugin/tools/grecorder/recorder_engine.h.
This API set can provide the following functions.

Table 27. Recording engine functions

Function Feature
Image capture Captures images from the camera with different resolutions and saves them to JPEG files.
Video recording Records audio and video into various file formats, supporting (MP3) x (H264, MPEG4, H263,
MJPEG) x (MP4, MKV, AVI, FLV, TS)
Meta data Adds the time and date information to the captured image or recorded video.
Endless recording Records to multiple file segments and specifies the total file segment count and each file's
maximum size. It can record a file endlessly, saving to file segments in a loop.
This function can only work with the TS file format.
Web camera Records audio and video and sends them out through RTP.
This function can only work with the TS file format.
Graphic effect Supports adding the graphic effect in the video and record into the file.
Device selection Supports selecting different camera and audio sources.

NOTE
This recording engine is only available in platforms with VPU.

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

34 NXP Semiconductors
 Multimedia

6.4 i.MX Qt Applications

The following applications based on Qt demonstrate the multimedia features on the X11 backend.

Table 28. Qt applications

Application Feature
IMXPlayer Based on the playback engine, it provides all the features supported in the playback engine.
IMXCamera Based on the recording engine, it provides all the features supported in the recording engine.

NOTE
The demo applications are only available in platforms with VPU and in an X11
environment.

6.5 Multimedia feature matrix

This section provides feature matrix details of various codecs used for playback.

6.5.1 Parser/Demuxer specifications

The demuxer support of a particular audio or video type requires the availability of the codec.
Table 29. Parser/Demuxer supported audio/video
Demuxer ASF AVI MP4 OGG FLV MPG2 MKV RMVB
feature
Video H264 - Y Y - Y Y Y -
MPEG2 - Y - - - Y Y -
MPEG4 Y Y Y - - - Y -
H263 - Y Y - Y - Y -
MJPEG - Y Y - - - Y -
VC1 Y Y - - - - Y -
DivX Y Y Y - - - Y -
Xvid - Y - - - - Y -
VP8 - - - - - - Y -
VP6 - - - - Y - Y -
Theora - - - Y - - - -
RV - - - - - - Y Y
Audio AAC - Y Y - Y Y Y Y
MP3 Y Y Y - Y Y Y -
WMA Y Y - - - - Y -
AC3 - Y Y - - Y Y -

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 35
Multimedia

Table 29. Parser/Demuxer supported audio/video (continued)

Demuxer ASF AVI MP4 OGG FLV MPG2 MKV RMVB
feature
PCM/ADPCM Y Y Y - Y Y Y -
AMR - - Y - - - Y -
Vorbis - Y Y Y - - Y -
SPEEX - - - Y Y - Y -
DTS - - - - - Y Y -
FLAC - - - Y - - Y -
DD+ Y - Y - - Y Y -
RA - - - - - - - Y

6.5.2 Video codec specifications

The tables in this section show the video codec specifications with and without VPU acceleration. Check Section BSP
Supported Features to determine if your board supports VPU.
Table 30. Video codec specification for hardware with VPU acceleration
Feature Profile Max. Min. Max. H/W or S/W Bitrate Comment
resolution resolution framerate
Video MPEG2 MP 1920 * 1080 64 * 64 30 fps H/W 50 -
decoder Mbps
MPEG4 SP 1920 * 1080 64 * 64 30 fps H/W 40 -
Mbps
MPEG4 ASP 1920 * 1080 64 * 64 30 fps H/W 40 -
Mbps
H.263 P3 1920 * 1080 64 * 64 30 fps H/W 20 -
Mbps
H.264 BP 3840 * 2160 64 * 64 30 fps H/W 50 -
Mbps
H.264 MP 3840 * 2160 64 * 64 30 fps H/W 50 -
Mbps
H.264 HP 3840 * 2160 64 * 64 30 fps H/W 50 -
Mbps
VC-1 SP 1920 * 1080 64 * 64 30 fps H/W 45 -
Mbps
VC-1 MP 1920 * 1080 64 * 64 30 fps H/W 45 -
Mbps
VC-1 AP 1920 * 1080 64 * 64 30 fps H/W 45 -
Mbps
VP8 - 1280 * 720 64 * 64 30 fps H/W 20 i.MX 6DualLite
Mbps
VP8 - 1920 * 1080 64 * 64 30 fps H/W 20 -
Mbps

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

36 NXP Semiconductors
 Multimedia

Table 30. Video codec specification for hardware with VPU acceleration (continued)
Feature Profile Max. Min. Max. H/W or S/W Bitrate Comment
resolution resolution framerate
MJPEG - 1920 * 1080 64 * 64 30 fps H/W 120 -
Mpixl
RV 8/9/10 1920 * 1080 64 * 64 30 fps H/W 40 -
Mbps
HEVC main, main 3840 * 2160 64 * 64 60 fps H/W 160 -
10 Mbps
VP9 profile 0, 2 3840 * 2160 64 * 64 60 fps H/W 160 -
Mbps

6.5.3 Audio codec specification

Table 31. Audio codec specification
Decoder Feature/Profile Channel Sample rate Bit rate (kbps) H/W or S/W Comment
(KHz)
MP3 MPEG-1 (Layer-1/ stereo/mono <= 48 8 - 448 8QuadXPlus -
Layer-2/Layer-3) supports
H/W.
MPEG-2 (Layer-1/
Layer-2/Layer-3) 8QuadMax
does not
MPEG-2.5 (Layer-3)
support H/W
audio
decoder.
AACLC MPEG-2 AACLC <= 5.1 8 - 96 8 - 256 8QuadXPlus For H/W, it
supports only supports
MPEG-4 AACLC
H/W. mono and
stereo
8QuadMax
channels.
does not
support H/W
audio
decoder.
HE-AAC HE-AAC V1 stereo/mono 8 - 96 Mono: 8 - 384 S/W -
HE-AAC V2 stereo: 16 - 768
WMA10 Std L1 @ QL1 stereo/mono 44.1 64 - 161 S/W -
L2 @ QL1 stereo/mono <= 48 <= 161 S/W -
L3 @ QL1 stereo/mono <= 48 <= 385 S/W -
WMA10 Pro M0a @ QL2 stereo/mono <= 48 48 - 192 S/W -
M0b @ QL2 stereo/mono <= 48 <= 192 S/W -
M1 @ QL2 <= 5.1 <= 48 <= 384 S/W -
M2 @ QL2 <= 5.1 <= 96 <= 768 S/W -
M3 @ QL2 <= 7.1 <= 96 <= 1500 S/W -
WMA 9 N1 stereo/mono <= 48 <= 3000 S/W -
Lossless

Table continues on the next page...

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 37
Multimedia

Table 31. Audio codec specification (continued)

Decoder Feature/Profile Channel Sample rate Bit rate (kbps) H/W or S/W Comment
(KHz)
N2 <=5.1 <= 96 <= 3000 S/W -
N3 <=7.1 <= 96 <= 3000 S/W -
AC-3 - <=5.1 <= 48 32 - 640 S/W -
FLAC - <=7.1 8 - 192 - N/A -
BSAC - <=5.1 <= 48 64 per channel N/A Core codec
only
Ogg Vorbis q1 - q10 Stereo 8 - 192 <= 500 S/W -
DD-plus - <=7.1 32, 44.1, 48 <= 6.144 Mbps S/W -
64, 88.2, 96
RA cook stero/mono 8k, 11.025k, - S/W -
22.05k, 44.1k

NOTE
• The bitrate (bps) supported for MP3 encoder: 32 k, 48 k, 56 k, 64 k, 80 k, 96 k, 112
k, 128 k, 160 k, 192 k, 224 k, 256 k, 320 k
• The sample and supported bitrate (bps) combinations for WMA8 encoder:
• For mono output:
• 22050 Hz: 20 k, 16 k, 22 k, 17.6 k
• 32000 Hz: 20 k, 22 k
• 44100 Hz: 32 k, 35.2 k, 48 k, 52.8 k
• For Stereo output:
• 22050 Hz: 35.2 k, 32 k, 22 k, 20 k
• 32000 Hz: 52.8 k, 48 k, 44 k, 40 k, 35.2 k, 32 k
• 44100 Hz: 211.2 k, 192 k, 176 k, 160 k, 140.8 k, 128 k, 105.6 k, 96 k,
88 k, 80 k, 70.4 k, 64 k
• 48000 Hz: 211.2 k, 192 k, 176 k, 160 k, 140.8 k, 128 k

6.5.4 Image codec specification

Table 32. Image codec specification
Feature Profile Max. resolution H/W or S/W
Image decoder JPEG Baseline Memory-related S/W
PNG N/A Memory-related S/W
GIF N/A Memory-related S/W
BMP N/A Memory-related S/W
Image encoder JPEG Baseline Memory-related S/W

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

38 NXP Semiconductors
 Multimedia

6.5.5 Speech codec specification

Table 33. Speech codec specification
Feature Sample rate Bit rate (kbps) H/W or S/W
Speech codec G.711 8 KHz 64 S/W
G.723.1 8 KHz 5.3, 6.3 S/W
G.726 8 KHz 16, 24, 32, 40 S/W
G.729ab 8 KHz 8 S/W
AMR_NB 8 KHz 12.2, 10.2, 7.9, 7.4, 6.7, S/W
5.9, 5.15, 4.75
AMR_WB 16 KHz 23.85, 23.05, 19.85, S/W
18.25, 15.85, 14.25,
12.65, 8.85, 6.6

6.5.6 Streaming protocol specification

Table 34. Streaming protocol specification
Protocol Feature
HTTP HTTP progressive streaming
RTSP RTP, SDP
RTP/UDP RTP/UDP MPEGTS streaming

6.5.7 RTSP streaming server specification

To support the RTSP server, the gst-rtsp-server open source package needs to be installed. See Section “RTSP Streaming
Server” in the i.MX Linux® User’s Guide (IMXLUG) for information on how to build and install it.
Table 35. RTSP streaming server specification
Demux feature AVI MP4 FLV MKV MP3 AAC
Video H264 Y Y Y Y - -
MPEG4 Y Y - Y - -
Audio MP3 Y Y Y Y Y -
AAC Y Y Y Y - Y

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

NXP Semiconductors 39
Revision History

6.5.8 Subtitle specification

Table 36. Subtitle specification
Internal/External Subtitle format
Internal SRT, SSA, ASS
External SRT

6.6 Known issues and limitations for multimedia

None.

7 Revision History
This table provides the revision history.

Table 37. Revision history

Revision number Date Substantive changes
L4.9.51_imx8qxp-alpha 11/2017 Initial release
L4.9.51_imx8qm-beta1 12/2017 Added i.MX 8QuadMax
L4.9.51_imx8mq-beta 12/2017 Added i.MX 8MQuad
L4.9.51_8qm-beta2/8qxp-beta 02/2018 Added i.MX 8QuadMax Beta2 and i.MX
8QuadXPlus Beta
L4.9.51_imx8mq-ga 03/2018 Added i.MX 8MQuad GA
L4.9.88_2.0.0-ga 05/2018 i.MX 7ULP and i.MX 8MQuad GA
release

i.MX Linux® Release Notes, Rev. L4.9.88_2.0.0-ga, 05/2018

40 NXP Semiconductors
How to Reach Us: Information in this document is provided solely to enable system and software implementers to
use NXP products. There are no express or implied copyright licenses granted hereunder to
Home Page:
nxp.com design or fabricate any integrated circuits based on the information in this document. NXP

Web Support: reserves the right to make changes without further notice to any products herein.
nxp.com/support NXP makes no warranty, representation, or guarantee regarding the suitability of its products for
any particular purpose, nor does NXP assume any liability arising out of the application or use
of any product or circuit, and specifically disclaims any and all liability, including without
limitation consequential or incidental damages. “Typical” parameters that may be provided in
NXP data sheets and/or specifications can and do vary in different applications, and actual
performance may vary over time. All operating parameters, including “typicals”, must be
validated for each customer application by customer’s technical experts. NXP does not convey
any license under its patent rights nor the rights of others. NXP sells products pursuant to
standard terms and conditions of sale, which can be found at the following address:
nxp.com/SalesTermsandConditions.

NXP, the NXP logo, Freescale, and the Freescale logo are trademarks of NXP B.V. All other
product or service names are the property of their respective owners.

Arm, the Arm logo, and Cortex are registered trademarks of Arm Limited (or its subsidiaries)
in the EU and/or elsewhere. IEEE 1588 and 802 are registered trademarks of the Institute of
Electrical and Electronics Engineers, Inc. (IEEE). This product is not endorsed or approved by
the IEEE. The Bluetooth word mark and logos are registered trademarks owned by Bluetooth
SIG, Inc. and any use of such marks by NXP is under license. All rights reserved.
© 2018 NXP B.V.

Document Number: IMXLXRN

Rev. L4.9.88_2.0.0-ga
05/2018