IMX8QPAEC
IMX8QPAEC
Rev. 3, 11/2021
Data Sheet: Technical Data
MIMX8QPnAVUxxAx
i.MX 8QuadPlus
Automotive and
Infotainment
Applications Processors Package Information
29 x 29 mm package case outline
Ordering Information
1 Introduction 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 System Controller Firmware (SCFW) Requirements5
The i.MX 8 Family consists of two processors: 1.3 Related resources . . . . . . . . . . . . . . . . . . . . . . . . . . 5
i.MX 8QuadMax and 8QuadPlus. This data sheet covers 2 Architectural Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
the i.MX 8QuadPlus processor, which is composed of 3 Modules List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
seven cores (one Arm® Cortex®-A72, four Arm 3.1 Special Signal Considerations. . . . . . . . . . . . . . . . 13
Cortex®-A53, and two Arm Cortex®-M4F), dual 32-bit 4
3.2 Recommended Connections for Unused Interfaces13
Electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 14
GPU subsystems, 4K H.265 capable VPU, and dual 4.1 Chip-level conditions . . . . . . . . . . . . . . . . . . . . . . . 14
failover-ready display controllers. This processor 4.2 Power supplies requirements and restrictions. . . . 26
4.3 PLL electrical characteristics . . . . . . . . . . . . . . . . . 29
supports a single 4K display (with multiple display 4.4 On-chip oscillators. . . . . . . . . . . . . . . . . . . . . . . . . 33
output options, including MIPI-DSI, HDMI, eDP/DP, 4.5 I/O DC Parameters . . . . . . . . . . . . . . . . . . . . . . . . 36
4.6 I/O AC Parameters . . . . . . . . . . . . . . . . . . . . . . . . 42
and LVDS), or multiple smaller displays. Memory 4.7 Output Buffer Impedance Parameters. . . . . . . . . . 45
interfaces supporting LPDDR4, Quad SPI/Octal SPI 4.8 System Modules Timing . . . . . . . . . . . . . . . . . . . . 49
(FlexSPI), eMMC 5.1, RAW NAND, SD 3.0, and a wide 4.9 General-Purpose Media Interface (GPMI) Timing . 53
4.10 External Peripheral Interface Parameters . . . . . . . 62
range of peripheral I/Os such as PCIe, provide wide 4.11 Analog-to-digital converter (ADC) . . . . . . . . . . . . 111
flexibility. Advanced multicore audio processing is 5 Boot mode configuration . . . . . . . . . . . . . . . . . . . . . . . . 115
5.1 Boot mode configuration inputs. . . . . . . . . . . . . . 115
supported by the Arm cores and a high performance 5.2 Boot devices interfaces allocation . . . . . . . . . . . . 115
Tensilica® HiFi 4 DSP for pre- and post-audio 6 Package information and contact assignments . . . . . . 117
processing as well as voice recognition. 6.1 FCPBGA, 29 x 29 mm, 0.75 mm pitch . . . . . . . . 117
7 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
NXP reserves the right to change the detail specifications as may be required to permit improvements in the design of
its products.
The i.MX 8QuadPlus processor offers numerous advanced features as shown in this table.
Function Feature
Multicore architecture provides AArch64 for 64-bit support and new architectural features
4× Cortex-A53, 1× Cortex-A72 cores,
and 2× Cortex-M4F cores AArch32 for full backward compatibility with ARMv7
Graphics Processing Unit (GPU) 16× Vec4 shaders with 64 execution units. Split GPU architecture allows for dual
independent 8-Vec4 shader GPUs or a combined 16-Vec4 shader GPU.
Supports OpenGL 3.0, 2.1,; OpenGL ES 3.2, 3.1 (with AEP), 3.0, 2.0, and 1.1;
OpenCL 1.2 Full Profile and 1.1; OpenVG 1.1; and Vulkan
AVS decode
2× Quad SPI or 1× Octal SPI (FlexSPI) for fast boot from SPI NOR flash
1× eMMC5.1/SD3.0
Function Feature
Display Controller Supports single UltraHD 4Kp60 display or up to 4 independent FullHD 1080p60
displays
Up to 18-layer composition
Integrated Failover Path (SafeAssure) to ensure display content stays valid even in
event of a software failure
This high performance serializer supports a pair of LVDS displays with 8 lanes each.
Each port can be configured for 2x Tx with 4 lanes each.
Camera I/O and video • 2× MIPI-CSI with 4-lanes each, MIPI DPHYSM v1.1
• 1× HDMI-RX (See restrictions in Section 4.10.8)
Security Advanced High Assurance Boot (AHAB) secure & encrypted boot
See the security reference manual for this chip for a full list of security features.
System Control • 2× I2C tightly coupled with Cortex-M4 cores (1× per Cortex M4F core)
• The tightly coupled M4 I2C ports cannot be used for general-purpose use
• System Control Unit (SCU):
• Power control, clocks, reset
• Boot ROMs
• PMIC interface
• Resource Domain Controller
Function Feature
I/O 1× PCIe 3.0 (2-lanes). Can be used as two PCIe 3.0 controllers with one-lane,
independent operation. PCIe 1.0 and 2.0 compliant. PCIe 3.0 capable, contact your
NXP representative.
1× SATA 3.0 can be used as PCIe one-lane. This is in addition to the standard PCIe
controller. PCIe 1.0 and 2.0 compliant. PCIe 3.0 capable, contact your NXP
representative.
2× 1Gb Ethernet with AVB (can be used as 10/100 Mbps ENET with AVB)
3× CAN/CAN-FD
8× UARTs:
• 5× UARTs (2× with hardware flow control)
• 2× UARTs tightly coupled with Cortex-M4F cores (1× per Cortex-M4F core)
• 1× UART tightly coupled with SCU
18× I2C:
• 5× General-Purpose I2C (full-speed with DMA support)
• Low-speed I2C without DMA support:
• 2× master I2C in MIPI-DSI (1× per instance)
• 4× master I2C in LVDS (2× per instance)
• 2× master I2C in HDMI-TX
• 2× master I2C in MIPI-CSI (1× per instance)
Note: Although low-speed I2Cs can be made available for general purpose use
which requires the associated PHY (for example, MIPI) to be powered on, it is not
recommended.
Note: I/O muxing constraints prevent using all I2Cs simultaneously.
• 2x I2C tightly coupled with Cortex-M4 cores (1x per Cortex M4F core)
Note: The tightly coupled M4 I2C ports cannot be used for general purpose use.
• 1× I2C tightly coupled with SCU for communication with the PMIC. Not general
purpose and not available for non-PMIC uses.
4× SAI (SAI0 and SAI1 are transmit/receive; SAI2 and SAI3 are receive only)
× ASRC (Asynchronous Sample Rate Converter) (note: no I/O signals are directly
connected to this module)
4× PWM channels
4× SPI
Qualification
Part Number Options Cortex-A72 Cortex-A53 Cortex-M4F GPU Package
Tier
Type Description
Reference manual The i.MX 8QuadMax Applications Processor Reference Manual (IMX8QMRM) contains a
comprehensive description of the structure and function (operation) of the QuadPlus SoC.
Data sheet This data sheet includes electrical characteristics and signal connections.
Chip Errata The chip mask set errata provides additional and/or corrective information for a particular
device mask set.
Package drawing Package dimensions are provided in Section 6, “Package information and contact
assignments".”
Hardware guide The i.MX 8QuadMax/8QuadPlus Hardware Developer’s Guide (IMX8HWDG) provides
system design guidelines.
2 Architectural Overview
The following subsections provide an architectural overview of the i.MX 8QuadPlus processor system.
PHY PHY
ESAI TX / RX
2x ESAI MQS 2x eDMA 2x PCIe 1 lane each
2x SAI TX / RX SATA 1x SATA 3.0 /
2x SAI RX
8x SAI 6x GPT Audio Mixer SSI Bus
1x PCIe
(1 lane)
RAW / Imaging
ONFI 3.2 Connectivity Subsystem VPU Subsystem 2x LVDS 1/2 LVDS TX
NAND Flash MJPEG MJPEG TX (4 lanes each)
Video Processing Unit ISI
NAND DEC ENC
1x eMMC LPI2C 1x I2C
5.1 / SD 3.0 VPU
2x SD 3.0 (UHS-I) 3x uSDHC
Display Controllers
1x USB 3.0 PHY
USB3 DSP Core LPI2C 1x I2C
1x USB 2.0 HIFI4 DSP
Host / HSIC 2x DPU (4x LCD) 2x MIPI 2x MIPI CSI2
32KB I$ 48KB D$ CSI2 (4-lanes)
2x USB2
1x USB 2.0 448KB OCRAM
OTG, PHY 64KB TCM LPI2C 1x I2C
Graphics Processing Unit
2x ENET 2x MIPI
10/100/1000M MIPI Display
2x GPU DSI (4-lanes)
Ethernet + AVB
3 Modules List
The i.MX 8QuadPlus processors contain a variety of digital and analog modules. This table describes the
processor modules in alphabetical order.
Block
Block Name Brief Description
Mnemonic
APBH-DMA NAND Flash and BCH The AHB-to-APBH bridge provides the chip with a peripheral attachment bus
ECC DMA Controller running on the AHB's HCLK, which includes the AHB-to-APB PIO bridge for a
memory-mapped I/O to the APB devices, as well as a central DMA facility for
devices on this bus and a vectored interrupt controller for the Arm core.
A53 Arm (CPU1) CPU cluster embedding 4x Cortex-A53 CPUs with a 32KB L1 instruction cache and
a 32KB data cache. The CPUs share a 1 MB L2 cache.
A72 Arm (CPU2) CPU cluster embedding 1x Cortex-A72 CPU with a 48 KB L1 instruction cache and
32 KB data cache. The CPU has a 1MB L2 cache.
ASRC Asynchronous Sample The Asynchronous Sample Rate Converter (ASRC) converts the sampling rate of
Rate Converter a signal associated to an input clock into a signal associated to a different output
clock. The ASRC supports concurrent sample rate conversion of up to 10 channels
of about -120dB THD+N. The sample rate conversion of each channel is
associated to a pair of incoming and outgoing sampling rates. The ASRC supports
up to three sampling rate pairs.
BCH-62 Binary-BCH ECC The BCH62 module provides up to 62-bit ECC for NAND Flash controller (GPMI2)
Processor
CAAM Cryptographic CAAM is a cryptographic accelerator and assurance module. CAAM implements
Accelerator and several encryption and hashing functions, a run-time integrity checker, and a
Assurance Module Pseudo Random Number Generator (PRNG).
CAAM also implements a Secure Memory mechanism. In this device the security
memory provided is 64 KB.
CTI Cross Trigger Interface CTI sends signals across the chip indicating that debug events have occurred. It is
used by features of the Coresight infrastructure.
CTM Cross Trigger Matrix Cross Trigger Matrix IP is used to route triggering events between CTIs.
DAP Debug Access Port The DAP provides real-time access for the debugger without halting the core to:
• System memory and peripheral registers
• All debug configuration registers
The DAP also provides debugger access to JTAG scan chains.
Block
Block Name Brief Description
Mnemonic
DPR Display/Prefetch/ The DPR prefetches data from memory and converts the data to raster format for
Resolve display output. Raster source buffers can also be prefetched unconverted. The
resolve process supports graphics and video formatted tile frame buffers and
converts them to raster format. Embedded display memory is used as temporary
storage for data which is sourced by the display controller to drive the display.
eDMA Enhanced Direct • 4× eDMA with a total of 128 channels (note: all channels are not assigned; see
Memory Access the product reference manual for more information):
• 4× instances with 32 channels each
• Programmable source, destination addresses, transfer size, plus support for
enhanced addressing modes
• Internal data buffer, used as temporary storage to support 64-byte burst
transfers, one outstanding transaction per DMA controller.
• Transfer control descriptor organized to support two-deep, nested transfer
operations
• Channel service request via one of three methods:
• Explicit software initiation
• Initiation via a channel-to-channel linking mechanism for continuous
transfers
• Peripheral-paced hardware requests (one per channel)
• Support for fixed-priority and round-robin channel arbitration
• Channel completion reported via interrupt requests
• Support for scatter/gather DMA processing
• Support for complex data structures via transfer descriptors
• Support to cancel transfers via software or hardware
• Each eDMA instance can be uniquely assigned to a different resource domain,
security (TZ) state, and virtual machine
• In scatter-gather mode, each transfer descriptor’s buffers can be assigned to
different SMMU translation
ENET Ethernet Controller 2× 1 Gbps Ethernet controllers supporting RGMII + AVB (Audio Video Bridging,
IEEE 802.1Qav)
ESAI Enhanced Serial Audio The Enhanced Serial Audio Interface (ESAI) provides a full-duplex serial port for
Interface serial communication with a variety of serial devices, including industry-standard
codecs, SPDIF transceivers, and other processors. The ESAI consists of
independent transmitter and receiver sections, each section with its own clock
generator. All serial transfers are synchronized to a clock. Additional
synchronization signals are used to delineate the word frames. The normal mode
of operation is used to transfer data at a periodic rate, one word per period. The
network mode is also intended for periodic transfers; however, it supports up to 32
words (time slots) per period. This mode can be used to build time division
multiplexed (TDM) networks. In contrast, the on-demand mode is intended for
non-periodic transfers of data and to transfer data serially at high speed when the
data becomes available.
The ESAI has 12 pins for data and clocking connection to external devices.
FlexCAN Flexible Controller Area Communication controller implementing the CAN with Flexible Data rate (CAN FD)
Network protocol and the CAN protocol according to the CAN 2.0B protocol specification.
Block
Block Name Brief Description
Mnemonic
FlexSpi (Quad Flexible Serial • Flexible sequence engine to support various flash vendor devices, including
SPI/Octal SPI) Peripheral Interface HyperBus™ devices:
• Support for FPGA interface
• Single, dual, quad, and octal mode of operation.
• DDR/DTR mode wherein the data is generated on every edge of the serial flash
clock.
• Support for flash data strobe signal for data sampling in DDR and SDR mode.
• Two identical serial flash devices can be connected and accessed in parallel for
data read operations, forming one (virtual) flash memory with doubled readout
bandwidth.
GIC Generic Interrupt The GIC-500 handles all interrupts from the various subsystems and is ready for
Controller virtualization.
GPIO General Purpose I/O Used for general purpose input/output to external devices. Each GPIO module
Modules supports 32 bits of I/O.
GPMI General Purpose Media The GPMI module supports up to 8× NAND devices. 62-bit ECC (BCH)
Interface encryption/decryption for NAND Flash controller (GPMI). The GPMI supports
separate DMA channels per NAND device.
GPT General Purpose Timer Each GPT is a 32-bit “free-running” or “set and forget” mode timer with
programmable prescaler and compare and capture register. A timer counter value
can be captured using an external event and can be configured to trigger a capture
event on either the leading or trailing edges of an input pulse. When the timer is
configured to operate in “set and forget” mode, it is capable of providing precise
interrupts at regular intervals with minimal processor intervention. The counter has
output compare logic to provide the status and interrupt at comparison. This timer
can be configured to run either on an external clock or on an internal clock.
GPU Graphics Processing 2× GC7000XSVX GPUs with 8 shaders each that can run either independently or
in “dual-mode” with 16 shaders.
HDMI Tx/ HDMI Tx interface HDMI transmitter, Display Port 1.3 and embedded Display Port 1.4
DP/eDP
HDMI Rx HDMI Rx interface HDMI 1.4b receiver (See restrictions in Section 4.10.8)
HiFi 4 DSP Audio Processor A highly optimized audio processor geared for efficient execution of audio and
voice codecs and pre- and post-processing modules to offload the Arm core.
I2C I2C Interface I2C provides serial interface for external devices.
IOMUXC IOMUX Control This module enables flexible I/O multiplexing. Each I/O pad has default and several
alternate functions. The alternate functions are software configurable.
Block
Block Name Brief Description
Mnemonic
KPP Key Pad Port The Keypad Port (KPP) is a 16-bit peripheral that can be used as a 6 x 8 keypad
matrix interface or as general purpose input/output (I/O).
LPIT-1 Low-Power Periodic Each LPIT is a 32-bit “set and forget” timer that starts counting after the LPIT is
LPIT-2 Interrupt Timer enabled by software. It is capable of providing precise interrupts at regular intervals
with minimal processor intervention. It has a 12-bit prescaler for division of input
clock frequency to get the required time setting for the interrupts to occur, and
counter value can be programmed on the fly.
LPSPI 0–3 Configurable SPI Full-duplex enhanced Synchronous Serial Interface. It is configurable to support
Master/Slave modes, four chip selects to support multiple peripherals.
LVDS LVDS Display Bridge This high performance serializer supports a pair of LVDS displays with 8 lanes
each. Each port can be configured for 2x Tx with 4 lanes each.
MIPI CSI-2 MIPI CSI-2 Interface The MIPI CSI-2 IP provides MIPI CSI-2 standard camera interface ports. The MIPI
CSI-2 interface supports up to 1.5 Gbps for up to 4 data lanes
MIPI-DSI MIPI DSI interface The MIPI DSI IP provides DSI standard display serial interface. The DSI interface
supports 80 Mbps to 1.5 Gbps speed per data lane.
MQS Medium Quality Sound Medium Quality Sound (MQS) is used to generate 2-channel medium quality
PWM-like audio via two standard digital GPIO pins.
OCOTP_CTRL OTP Controller The On-Chip OTP controller (OCOTP_CTRL) provides an interface for reading,
programming, and/or overriding identification and control information stored in
on-chip fuse elements. The module supports electrically-programmable poly fuses
(eFUSEs). The OCOTP_CTRL also provides a set of volatile software-accessible
signals that can be used for software control of hardware elements, not requiring
non-volatility. The OCOTP_CTRL provides the primary user-visible mechanism for
interfacing with on-chip fuse elements. Among the uses for the fuses are unique
chip identifiers, mask revision numbers, cryptographic keys, JTAG secure mode,
boot characteristics, and various control signals requiring permanent nonvolatility.
Block
Block Name Brief Description
Mnemonic
OCRAM On-Chip Memory The On-Chip Memory controller (OCRAM) module is designed as an interface
Controller between the system’s AXI bus and the internal (on-chip) SRAM memory module.
The OCRAM is used for controlling the 256 KB multimedia RAM through a 64-bit
AXI bus.
PCIe PCI Express 3.0 PCIe 1.0 and 2.0 compliant. PCIe 3.0 capable; contact your NXP representative.
PRG Prefetch/Resolve The PRG is a gasket which translates system memory accesses to local display
Gasket RTRAM accesses for display refresh. It works with the DPR to complete the
prefetch and resolving operations needed to drive the display.
PWM Pulse Width Modulation The pulse-width modulator (PWM) has a 16-bit counter and is optimized to
generate sound from stored sample audio images and it can also generate tones.
It uses 16-bit resolution and a 4×16 data FIFO to generate square waveforms.
RAM Internal RAM Internal RAM, which is accessed through OCRAM memory controllers.
256 KB
RNG Random Number The purpose of the RNG is to generate cryptographically strong random data. It
Generator uses a true random number generator (TRNG) and a pseudo-random number
generator (PRNG) to achieve true randomness and cryptographic strength. The
RNG generates random numbers for secret keys, per message secrets, random
challenges, and other similar quantities used in cryptographic algorithms.
SAI I2S/SSI/AC97 Interface The SAI module provides a synchronous audio interface that supports full duplex
serial interfaces with frame synchronization, such as I2S, AC97, TDM, and
codec/DSP interfaces.
SECO Security Controller Core and associated memory and hardware responsible for key management.
SJC Secure JTAG Controller The SJC provides the JTAG interface, which is compatible with JTAG TAP
standards, to internal logic. This device uses JTAG port for production, testing, and
system debugging. Additionally, the SJC provides BSR (Boundary Scan Register)
standard support, which is compatible with IEEE1149.1 and IEEE1149.6 standards.
The JTAG port must be accessible during platform initial laboratory bring-up, for
manufacturing tests and troubleshooting, as well as for software debugging by
authorized entities. The SJC incorporates three security modes for protecting
against unauthorized accesses. Modes are selected through eFUSE configuration.
sMMU System MMU The System MMU is an MMU-500 from Arm. It supports two-stage address
translation and multiple translation contexts.
SNVS Secure Non-Volatile Secure Non-Volatile Storage, including Secure Real Time Clock, Security State
Storage Machine, Master Key Control.
SPDIF Sony Philips Digital The Sony/Philips Digital Interface (SPDIF) audio block is a stereo transceiver that
Interconnect Format allows the processor to receive and transmit digital audio. The SPDIF transceiver
allows the handling of both SPDIF channel status (CS) and User (U) data and
includes a frequency measurement block that allows the precise measurement of
an incoming sampling frequency.
Block
Block Name Brief Description
Mnemonic
TEMPMON Temperature Monitor The temperature monitor/sensor IP module for detecting high temperature
conditions. The temperature read out does not reflect case or ambient temperature.
It reflects the temperature in proximity of the sensor location on the die.
Temperature distribution may not be uniformly distributed; therefore, the read-out
value may not be the reflection of the temperature value for the entire die.
USB3/USB2 The USB3/USB2 OTG module has been specified to perform USB 3.0 dual role and
USB 2.0 On-The-Go (OTG) compatible with the USB 3.0, and USB 2.0
specification with OTG supplementary specifications. This controller supports
twoindependent USB cores (1× USB3.0 dual-role, 1× USB2.0 OTG) and includes
the PHY and I/O interfaces to support this operation. The full pinout of the USB 3.0
controller includes the signaling for both USB 3.0 and USB 2.0. This does not
mean there is a separate USB 2.0 controller that can be used independently and
simultaneously with USB 3.0. This device has an additional separate,
independent USB 2.0 OTG controller which can be used simultaneously with this
USB 3.0. Specific features requested for this updated module:
• Super Speed (5 Gbps), High Speed (480 Mbps), full speed (12 Mbps) and low
speed (1.5 Mbps)
• Fully compatible with the USB 3.0 specification (backward compatible with USB
2.0)
• Fully compatible with the USB On-The-Go supplement to the USB 2.0
specification
• Hardware support for OTG signaling
• Host Negotiation Protocol (HNP) and Session Request Protocol (SRP)
implemented in hardware, which can also be controlled by software
USBOH The USBOH module has been specified which performs USB 2.0 On-The-Go
(OTG) and USB 2.0 Host functionality compatible with the USB 2.0 with OTG
supplement and HS IC-USB specification. This controller supports two
independent USB cores (1× USB2.0 OTG, 1× USB2.0 Host) and includes the PHY
and I/O interfaces to support this operation.
Key features:
• One USB2.0 OTG controller
• High Speed (480 Mbps), full speed (12 Mbps) and low speed (1.5 Mbps)
• Fully compatible with the USB 2.0 specification
• Fully compatible with the USB On-The-Go supplement to the USB 2.0
specification
• Hardware support for OTG signaling
• Host Negotiation Protocol (HNP) and Session Request Protocol (SRP)
implemented in hardware, which can also be controlled by software
• USB2.0 Host with HS IC-USB specification
• HS IC-USB transceiver-less downstream support (Host only).
Block
Block Name Brief Description
Mnemonic
VPU Video Processing Unit See the device reference manual for the complete list of the VPU’s
decoding/encoding capabilities.
WDOG Watchdog The Watchdog Timer supports two comparison points during each counting period.
Each of the comparison points is configurable to evoke an interrupt to the Arm core,
and a second point evokes an external event on the WDOG line.
XTAL OSC24M The 24 MHz clock source is an external crystal that acts as the main system clock.
The OSC24M is used as the source clock for subsystem PLLs. OSC24M can be
turned off by the System Control Unit (SCU) during sleep mode.
XTAL OSC32K The 32.768 kHz clock source is an external crystal. The OSC32K is intended to be
always on and is distributed by the SCU to modules in the chip.
4 Electrical characteristics
This section provides the device and module-level electrical characteristics for these processors.
VDD_A53
VDD_GPU0
VDD_GPU1
VDD_MAIN
VDD_MEMC
VDD_USB_OTG_1P0
VDD_PCIE_1P8 (PHY)
VDD_EMMC0_1P8_3P3
VDD_EMMC0_VSELECT_1P8_3P3
VDD_ENET_MDIO_1P8_3P3
VDD_MIPI_DSI_DIG_1P8_3P3
VDD_PCIE_DIG_1P8_3P3
VDD_QSPI0A_1P8_3P3
VDD_QSPI0B_1P8_3P3
VDD_SPI_MCLK_UART_1P8_3P3
VDD_SPI_SAI_1P8_3P3
VDD_TMPR_CSI_1P8_3P3
VDD_USDHC1_1P8_3P3
VDD_USDHC1_VSELECT_1P8_3P3
USB_OTG2_DP/USB_OTG2_DN
NOTE
HDMI CEC is 3.3V tolerant. HDMI DDC signals and HPD are 5V tolerant.
Refer to the Hardware Developer’s Guide for proper terminations.
29x29 mm
Rating Board Type1 Symbol Unit
package
VDD_A722 Power supply Overdrive 1.05 1.10 1.15 V Min frequency = 208.5 MHz
of Cortex-A72 Max frequency = 1.6 GHz
cluster
Nominal 0.95 1.00 1.10 V Max frequency = 1.06 GHz
2
VDD_A53 Power supply Overdrive 1.05 1.10 1.15 V Min frequency = 208.5 MHz
of Cortex-A53 Max frequency = 1.2 GHz
cluster
Nominal 0.95 1.00 1.10 V Max frequency = 900 MHz
VDD_DDR_CH0_VDDQ, Power LPDDR4 1.06 1.10 1.17 V Max frequency = 1.6 GHz
VDD_DDR_CH0_VDDQ_CKE, supplies of Supports LPDDR4-3200
VDD_DDR_CH1_VDDQ, memory I/Os
VDD_DDR_CH1_VDDQ_CKE,
VDD_DDR_CH0_VDDA_PLL_1P8, Power N/A 1.65 1.80 1.95 V PLL supply can be merged with
VDD_DDR_CH1_VDDA_PLL_1P8 supplies of other 1.8V supplies with proper
memory PLLs on board decoupling.
VDD_MIPI_CSI0_1P0, Power N/A 0.95 1.00 1.10 V These balls shall be connected to
VDD_MIPI_CSI1_1P0, supplies of the same power supply as
VDD_MIPI_DSI0_1P0, PHYs (1.0 V VDD_MAIN. It shall be a star
VDD_MIPI_DSI0_PLL_1P0, part) connection from the power
VDD_MIPI_DSI1_1P0, supply. Each VDD power supply
VDD_MIPI_DSI1_PLL_1P0, ball shall have its own dedicated
VDD_LVDS0_1P0, decoupling caps.
VDD_LVDS1_1P0
VDD_ANA1_1P8, VDD_ANA2_1P8, Power N/A 1.65 1.70 1.75 V These balls shall be powered by a
VDD_ANA3_1P8, VDD_CP_1P8, supplies of dedicated supply.
VDD_SCU_1P8, I/Os, analog Note: The disconnect between
VDD_SCU_ANA_1P8, and oscillator the ball naming, implying a 1.8 V
VDD_SCU_XTAL_1P8 of the SCU supply, and the actual required
operating voltage of 1.7 V is
known and correct as shown.
VDD_SNVS_4P2 Power supply N/A 2.80 3.30 4.20 V It can be supplied by a backup
of SNVS battery: a coin cell or a super cap.
Junction temperature
The typical values shown in Table 9 are required for use with NXP board support packages (BSPs) to
ensure precise time keeping and USB and HDMI operations.
VDD_DDR_CH0_VDDA_PLL_1P8 20 mA
VDD_DDR_CH1_VDDA_PLL_1P8 20 mA
VDD_SCU_ANA_1P8 5 mA
VDD_ANA0_1P8 175 mA
VDD_ANA1_1P8 45 mA
VDD_ANA2_1P8 140 mA
VDD_ANA3_1P8 110 mA
VDD_SIM0_1P8_3P3 15 mA
VDD_M4_GPT_UART_1P8_3P3 45 mA
VDD_ESAI1_SPDIF_SPI_1P8_3P3 40 mA
VDD_ESAI0_MCLK_1P8_3P3 25 mA
VDD_SPI_SAI_1P8_3P3 35 mA
VDD_FLEXCAN_1P8_3P3 15 mA
VDD_QSPI1A_1P8_3P3 20 mA
VDD_QSPI0_1P8_3P3 35 mA
VDD_EMMC0_1P8_3P3 55 mA
VDD_USDHC_VSELECT_1P8_3P3 5 mA
VDD_USDHC1_1P8_3P3 55 mA
VDD_USDHC2_1P8_3P3 35 mA
VDD_ENET_MDIO_1P8_3P3 15 mA
VDD_ENET0_1P8_3P3 25 mA
VDD_ENET1_1P8_2P5_3P3 25 mA
VDD_LVDS_DIG_1P8_3P3 25 mA
VDD_LVDSx_1P8 100 mA x is 0 or 1
VDD_LVDSx_1P0 5 mA x is 0 or 1
VDD_MIPI_DSI_DIG_1P8_3P3 20 mA
VDD_MIPI_DSIx_1P8 5 mA x is 0 or 1
VDD_MIPI_DSIx_1P0 35 mA x is 0 or 1
VDD_MIPI_DSIx_PLL_1P0 5 mA x is 0 or 1
VDD_MIPI_CSI_DIG_1P8 20 mA
VDD_MIPI_CSIx_1P8 5 mA x is 0 or 1
VDD_MIPI_CSIx_1P0 20 mA x is 0 or 1
VDD_HDMI_TX0_DIG_3P3 5 mA
VDD_HDMI_TX0_1P8 80 mA
VDD_ADC_1P8 5 mA
VDD_ADC_DIG_1P8 1 mA
VDD_MLB_DIG_1P8_3P31 10 mA
VDD_MLB_1P82 50 mA
VDD_USB_OTG1_3P3 30 mA
VDD_USB_OTG2_3P3 10 mA
VDD_USB_SS3_TC_3P3 10 mA
VDD_USB_HSIC0_1P2 10 mA
VDD_USB_HSIC0_1P8 5 mA
VDD_PCIE_DIG_1P8_3P3 5 mA
VDD_PCIE_IOB_1P8 45 mA
VDD_PCIE_LDO_1P8 190 mA
VDD_PCIE_SATA0_PLL_1P8 20 mA
VDD_PCIE0_PLL_1P8 20 mA
VDD_PCIE1_PLL_1P8 20 mA
VDD_SNVS_4P2 can draw up to 5 mA if the supply is capable of sourcing that current. If less than 5 mA is available, the
VDD_SNVS_LDO_1P8_CAP charge time will increase.
KS0 SNVS only, all other supplies OFF. RTC running, VDD_SNVS_4P2 (4.2 V) 50 μA
tamper not active, external 32K crystal.
VDD_GPU1 (OFF) — mA
VDD_MEMC (OFF) — mA
VDD_MAIN (0.8V) 12 mA
Total 21.94 mW
KS43 Leakage test, not intended as a customer use case. VDD_A53 (1.1V) 1066 mA
Overdrive conditions set, memories active, all
sub-systems powered ON. VDD_A72 (1.1V) 2000 mA
Active power minimized. VDD_GPU0 (1.0V) 2000 mA
Total 10852.6 mW
1
Maximum values are for 25 °C Tambient .
2
0.8 V nominal—voltage specification under this case is ± 3%.
3 Maximum values are for 125 °C T
junction . Stated supply voltages do not exceed +2% during test.
Table 13. USB 3.0 PHY typical current consumption in Power-Down Mode
Current — 10 μA 70 μA
The following table shows the current consumption for the USB 2.0 PHY embedded in the USB 3.0
PHY.
Table 14. Typical current consumption in Power-Down mode for USB 2.0 PHY embedded in USB 3.0 PHY
Electrical characteristics
Table 15. Power supplies usage
Supply Voltage
Groups
VDD_SNVS_4P2
i.MX 8QuadPlus Automotive and Infotainment Applications Processors, Rev. 3, 11/2021
VDD_MAIN VDD_ANA1_1P8
VDD_LVDSx_1P0 VDD_ANA2_1P8
VDD_MIPI_CSIx_1P0 VDD_ANA3_1P8
VDD_MIPI_DSIx_1P0 VDD_CP_1P8
VDD_MIPI_DSIx_PLL_1P0 VDD_SCU_1P8
VDD_SCU_x_1P8
VDD_HDMI_x_1P8 VDD_LVDS_DIG_1P8_3P3
VDD_LVDSx_1P8 VDD_M4_GPT_UART_1P8_3P3
VDD_MIPI_CSI_DIG_1P8 VDD_MIPI_DSI_DIG_1P8_3P3
VDD_MIPI_x_1P8 VDD_MLB_DIG_1P8_3P31
VDD_MLB_1P82 VDD_PCIE_DIG_1P8_3P3
VDD_PCIE_SATA0_PLL_1P8 VDD_QSPIx_1P8_3P3
VDD_PCIE_x_1P8 VDD_SPI_SAI_1P8_3P3
VDD_PCIEx_PLL_1P8 VDD_USDHC_VSELECT_1P8_3P3
VDD_USB_HSIC0_1P8
Group 3 1.1 - 1.1v 1.0v internal LDO's 1.2v 1.8v or 2.5v or 3.3v
VDD_ENET1_1P8_2P5_3P3
NXP Semiconductors
VDD_GPUx VDD_PCIEx_1P0
VDD_USB_OTGx_1P0
1
MLB is not supported on this product. This MLB power rail must be tied to the voltage specified in Table 8 if other I/O functions are used as determined by
IOMUX selection. Alternately, terminate the MLB supply, per the Hardware Developer’s Guide power supplies usage of unused features.
2
MLB is not supported on this product. The MLB power rail must be tied to the voltage specified in Table 8 or may be terminated, per the Hardware Developer’s
Guide power supplies of unused functions.
Electrical characteristics
Locking range1
Subsystem PLL usage Source clock Lock freq. Unit
Min freq. Max freq.
Locking range1
Subsystem PLL usage Source clock Lock freq. Unit
Min freq. Max freq.
is used to generate the 600 MHz slow operating point. See Table 8 to get associated voltages.
4 2500 MHz is used to generate 625 MHz for the max operating point, 1600 MHz is used to generate 400 MHz for the slow
The table below describes the PLL embedded in the USBOTG PHY.
The table below shows the characteristics for the reference clock PLL.
Clock output frequency 100 MHz Used to generate internal 100 MHz reference clock to PCIe lanes
The table below shows characteristics of the TX and RX PLLs used in each lane.
Reference clock 100 MHz From differential input clock pads or from internal PLL
Clock output range 6 ~ 10 GHz PCIe gen3: 8GHz to get 8GHz baud clock
PCIe gen2: 10GHz to get 5GHz baud clock
PCIe gen1: 10GHz to get 2.5GHz baud clock
1 PCIe 1.0 and 2.0 compliant. PCIe 3.0 capable, contact your NXP representative.
Clock output range 1.25 ~ 2.5 GHz Refer to HDMI / DP section of reference manual
The table below shows characteristics of the PLL embedded in HDMI/DP PHY.
Clock output range 0.75 ~ 1.5 GHz Dependent on targeted display configuration
Data rate range 175 ~ 1120 Mbps Dependent on targeted display configuration
4.4.1 OSC24M
This block integrates trimmable internal loading capacitors and driving circuitry. When combined with a
suitable 24 MHz external quartz element, it can generate a low-jitter clock. The oscillator is powered from
VDD_SCU_XTAL_1P8. The internal loading capacitors are trimmable to provide fine adjustment of the
24 MHz oscillation frequency. It is expected that customers burn appropriate trim values for the selected
crystal and board parasitics.
Frequency1 — 24 — MHz
Cload2 — 18 — pF
Maximum drive level 200 — — μW
ESR — — 60 Ω
1
The required frequency accuracy is set by the serial interfaces utilized for a specific application and is detailed in the
respective standard documents.
2
Cload is the specification of the quartz element, not for the capacitors coupled to the quartz element.
4.4.2 OSC32K
This block implements an internal amplifier, trimmable load capacitors and a bias network that when
combined with a suitable quartz crystal implements a low power oscillator.
Additionally, if the clock monitor determines that the 32KHz oscillation is not present, then the source of
the 32 KHz clock will automatically switch to the internal relaxation oscillator of lesser frequency
accuracy.
CAUTION
The internal ring oscillator is not meant to be used in customer applications,
due to gross frequency variation over wafer processing, temperature, and
supply voltage. These variations will cause timing issues to many different
circuits that use the internal ring oscillator for reference; and, if this timing
is critical, application issues will occur. To prevent application issues, it is
recommended to only use an external crystal or an accurate external clock.
If this recommendation is not followed, NXP cannot guarantee full
compliance of any circuit using this clock. The OSC32K runs from
VDD_SNVS_LDO_1P8_CAP, which is regulated from VDD_SNVS. The
target battery/voltage range is 2.8 to 4.2 V for VDD_SNVS, with a regulated
output of approximately 1.75 V.
1
The external clock is fed into the chip from the RTC_XTALI pin; the RTC_XTALO pin should be left floating.
2
The parameter specified here is a peak-to-peak value and VIH/VIL specifications do not apply.
3
The voltage applied on RTC_XTALI must be within the range of VSS to VDD_SNVS_LDO_1P8_CAP.
4
The rise/fall time of the applied clock are not strictly confined.
nmos (Rpd)
ovss
Figure 3. Circuit for Parameters Voh and Vol for I/O Cells
IOH= 2mA
PDRV=0
IOL= -2mA
PDRV=0
IOH= 2mA
PDRV=0
IOL= -2mA
PDRV=0
Ioh= 2mA
PDRV=0
Iol= -2mA
PDRV=0
Ioh= 2mA
PDRV=0
Iol= -2mA
PDRV=0
IOH= 2mA
DSE = 010 or 011
IOH= 4mA
DSE = 100 to 110
IOL= -2mA
DSE = 010 or 011
IOL= -4mA
DSE = 100 to 110
1
As programmed in the associated IOMUX (DSE field) register.
2
Refer to Section 4.6.1 for undershoot and overshoot specifications.
3
Refer to Section 4.6.2 for monotonic requirements.
IOH= 2mA
DSE = 10 or 11
IOL = -2mA
DSE = 10 or 11
High-level output voltage1 VOH Output Drive = All settings 0.9 × VDDQ — V
(40,48,60,80,120,240)
unterminated outputs
Low-level output voltage1 VOL Output Drive = All settings — 0.1 × VDDQ V
(40,48,60,80,120,240)
unterminated outputs
OVDD
80% 80%
20% 20%
Output (at pad) 0V
tr tf
NOTE
If a signal edge produces more than one overshoot/undershoot event, the
sum of all areas following the transition must be less than the area specified.
Overshoot/undershoot must be controlled through printed circuit board layout, transmission line
impedance matching, signal line termination, and other methods. Noncompliance to this specification may
affect device reliability or cause permanent damage to the device.
VPeak B
A
VIH_min and VIL_max are the guaranteed minimum logic-high and maximum logic-low voltage
specifications, respectively. NXP devices are typically better than guaranteed specifications; these values
are shown in the diagram as “typ”. Nominally, lower voltages than the guaranteed specification are
accepted by the device as logic high and higher voltages than the guaranteed specification are accepted as
logic low.
1.8 V application2
INPSL Slope of input signal at I/O Measured between 10% to 90% of the I/O swing — 3.5 ns
INPSL Slope of input signal at I/O Measured between 10% to 90% of the I/O swing — 1.5 ns
1
For all supply ranges of operation.
2 The dynamic input characteristic specifications are applicable for the digital bidirectional cells.
OVDD
PMOS (Rpu)
Ztl Ω, L = 20 inches
ipp_do pad
predriver
Cload = 1p
NMOS (Rpd)
U,(V) OVSS
Vin (do)
VDD
t,(ns)
0
U,(V)
Vout (pad)
OVDD
Vref1 Vref2
Vref
t,(ns)
0
Vovdd – Vref1
Rpu = × Ztl
Vref1
Vref2
Rpd = × Ztl
Vovdd – Vref2
1
As programmed in the associated IOMUX (PDRV field) register.
Typical
Parameter
ZQnPR0 ZQnPR0
Impedance Impedance
ZPROG_ASYM_PU_DRV ZPROG_ASYM_PD_DRV
9 48 Ω 7 60 Ω
11 40 Ω 9 48 Ω
Typical
Parameter ZQnPR0. ZPROG_HOST_ODT
Impedance
60.0 Ω 7
48.0 Ω 9
40.0 Ω 11
POR_B
(Input)
CC1
Figure 9. Reset timing diagram
NOTE
XTALOSC_RTC_XTALI is approximately 32 kHz.
XTALOSC_RTC_XTALI cycle is one period or approximately 30 μs.
Parameter LPDDR4
Number of Controllers 2
Table 54. Clock, data, and command address signals for LPDDR4 modes
DDR_CH[1:0].CK0_P CK_t_A
DDR_CH[1:0].CK0_N CK_c_A
DDR_CH[1:0].CK1_P CK_t_B
DDR_CH[1:0].CK1_N CK_c_B
DDR_CH[1:0].DQ_[15:0] DQ[15:0]_A
DDR_CH[1:0].DQ_[31:16] DQ[15:0]_B
DDR_CH[1:0].DQS_N_[3:0] DQS_N_[3:0]
DDR_CH[1:0].DQS_P_[3:0] DQS_P_[3:0]
DDR_CH[1:0].DM_[3:0] DM_[3:0]
DDR_CH[1:0].DCF00 CA2_A
DDR_CH[1:0].DCF01 CA4_A
DDR_CH[1:0].DCF02
DDR_CH[1:0].DCF03 CA5_A
DDR_CH[1:0].DCF04
DDR_CH[1:0].DCF05
DDR_CH[1:0].DCF06
DDR_CH[1:0].DCF07
DDR_CH[1:0].DCF08 CA3_A
DDR_CH[1:0].DCF09 ODT_CA_A
DDR_CH[1:0].DCF10 CS0_A
DDR_CH[1:0].DCF11 CA0_A
DDR_CH[1:0].DCF12 CS1_A
DDR_CH[1:0].DCF13
DDR_CH[1:0].DCF14 CKE0_A
DDR_CH[1:0].DCF15 CKE1_A
DDR_CH[1:0].DCF16 CA1_A
DDR_CH[1:0].DCF17 CA4_B
DDR_CH[1:0].DCF18 RESET_N
DDR_CH[1:0].DCF19 CA5_B
DDR_CH[1:0].DCF20
DDR_CH[1:0].DCF21
DDR_CH[1:0].DCF22
Table 54. Clock, data, and command address signals for LPDDR4 modes (continued)
DDR_CH[1:0].DCF23
DDR_CH[1:0].DCF24
DDR_CH[1:0].DCF25 ODT_CA_B
DDR_CH[1:0].DCF26 CA3_B
DDR_CH[1:0].DCF27 CA0_B
DDR_CH[1:0].DCF28 CS0_B
DDR_CH[1:0].DCF29 CS1_B
DDR_CH[1:0].DCF30 CKE0_B
DDR_CH[1:0].DCF31 CKE1_B
DDR_CH[1:0].DCF32 CA1_B
DDR_CH[1:0].DCF33 CA2_B
NF3 NF4
.!.$?#%?"
.!.$?7%?" NF5
NF8 NF9
.!.$?$!4!XX Command
NF1
.!.$?#,%
NF3
.!.$?#%?"
NF10
.!.$?7%?" NF5 NF11
NF8 NF9
NAND_DATAxx Address
.!.$?#,% NF1
.!.$?#%?" NF3
NF10
.!.$?7%?" NF5 NF11
NF8 NF9
.!.$?$!4!XX Data to NF
.!.$?#,%
.!.$?#%?"
NF14
.!.$?2%?" NF13 NF15
.!.$?2%!$9?" NF12
NF16 NF17
Figure 14. Read Data Latch Cycle Timing Diagram (Non-EDO Mode)
.!.$?#,%
.!.$?#%?"
NF14
NF16
NAND_DATAxx Data from NF
Figure 15. Read Data Latch Cycle Timing Diagram (EDO Mode)
Timing
T = GPMI Clock Cycle
ID Parameter Symbol Unit
Min Max
NF1 NAND_CLE setup time tCLS (AS + DS) × T - 0.12 [see 2,3] ns
NF2 NAND_CLE hold time tCLH DH × T - 0.72 [see 2] ns
NF3 NAND_CEx_B setup time tCS (AS + DS + 1) × T [see 3,2] ns
NF4 NAND_CEx_B hold time tCH (DH+1) × T - 1 [see 2] ns
NF5 NAND_WE_B pulse width tWP DS × T [see 2] ns
NF6 NAND_ALE setup time tALS (AS + DS) × T - 0.49 [see 3,2] ns
NF7 NAND_ALE hold time tALH (DH × T - 0.42 [see 2] ns
NF8 Data setup time tDS DS × T - 0.26 [see 2] ns
NF9 Data hold time tDH DH × T - 1.37 [see 2] ns
NF10 Write cycle time tWC (DS + DH) × T [see 2] ns
NF11 NAND_WE_B hold time tWH DH × T [see 2] ns
NF12 Ready to NAND_RE_B low tRR4 (AS + 2) × T [see 3,2] — ns
NF13 NAND_RE_B pulse width tRP DS × T [see 2] ns
NF14 READ cycle time tRC (DS + DH) × T [see 2] ns
NF15 NAND_RE_B high hold time tREH DH × T [see 2] ns
Timing
T = GPMI Clock Cycle
ID Parameter Symbol Unit
Min Max
In EDO mode (Figure 15), NF16/NF17 are different from the definition in non-EDO mode (Figure 14).
They are called tREA/tRHOH (NAND_RE_B access time/NAND_RE_B HIGH to output hold). The
typical value for them are 16 ns (max for tREA)/15 ns (min for tRHOH) at 50 MB/s EDO mode. In EDO
mode, GPMI will sample NAND_DATAxx at rising edge of delayed NAND_RE_B provided by an
internal DPLL. The delay value can be controlled by GPMI_CTRL1.RDN_DELAY (see the GPMI chapter
of the device reference manual. The typical value of this control register is 0x8 at 50 MT/s EDO mode.
However, if the board delay is large enough and cannot be ignored, the delay value should be made larger
to compensate the board delay.
NF23
NAND_CLE
NF25 NF26
NF24
NAND_ALE
NF25 NF26
NAND_WE/RE_B
NF22
NAND_CLK
NAND_DQS
NAND_DQS
Output enable
NF20 NF20
NF21 NF21
NAND_DATA[7:0]
Output enable
Figure 16. Source Synchronous Mode Command and Address Timing Diagram
NF19
NF18
.!.$?#%?"
NF23 NF24
.!.$?#,% NF25 NF26
NF23 NF24
.!.$?!,% NF25 NF26
NAND_WE/RE_B
NF22
.!.$?#,+
NF27
.!.$?$13 NF27
.!.$?$13
Output enable
NF29 NF29
.!.$?$1;=
NF28 NF28
.!.$?$1;=
Output enable
NF18
.!.$?#%?" NF19
NF23 NF24
.!.$?#,% NF25 NF26
NF23 NF24
NAND_ALE NF25 NF26
.!.$?7%2% NF25
NF25
NF22
NF26
.!.$?#,+
.!.$?$13
.!.$?$13
/UTPUT ENABLE
.!.$?$!4!;=
.!.$?$!4!;=
/UTPUT ENABLE
.!.$?$13
NF30
.!.$?$!4!;= D0 D1 D2 D3
Timing
T = GPMI Clock Cycle
ID Parameter Symbol Unit
Min Max
Figure 19 shows the timing diagram of NAND_DQS/NAND_DATAxx read valid window. For Source
Synchronous mode, the typical value of tDQSQ is 0.85 ns (max) and 1 ns (max) for tQHS at 200 MB/s.
GPMI will sample NAND_DATA[7:0] at both rising and falling edge of a delayed NAND_DQS signal,
which can be provided by an internal DPLL. The delay value can be controlled by GPMI register
GPMI_READ_DDR_DLL_CTRL.SLV_DLY_TARGET (see the GPMI chapter of the device reference
manual. Generally, the typical delay value of this register is equal to 0x7 which means 1/4 clock cycle
delay expected. However, if the board delay is large enough and cannot be ignored, the delay value should
be made larger to compensate the board delay.
DEV?CLK
.!.$?#%X?"
.&
.!.$?#,%
.!.$?!,%
T #+
.!.$?7%?" .& T #+
.!.$?2%?" .&
T #+
T #+
T #+
.!.$?$13
.!.$?$!4!;=
Timing
T = GPMI Clock Cycle
ID Parameter Symbol Unit
Min. Max.
2s,3]
NF1 NAND_CLE setup time tCLS (AS + DS) × T - 0.12 [see note
NF2 NAND_CLE hold time tCLH DH × T - 0.72 [see note2]
NF3 NAND_CE0_B setup time tCS (AS + DS) × T - 0.58 [see notes,2]
NF4 NAND_CE0_B hold time tCH DH × T - 1 [see note2]
NF5 NAND_WE_B pulse width tWP DS × T [see note2]
NF6 NAND_ALE setup time tALS (AS + DS) × T - 0.49 [see notes,2]
NF7 NAND_ALE hold time tALH DH × T - 0.42 [see note2]
NF8 Command/address NAND_DATAxx setup time tCAS DS × T - 0.26 [see note2]
NF9 Command/address NAND_DATAxx hold time tCAH DH × T - 1.37 [see note2]
NF18 NAND_CEx_B access time tCE CE_DELAY × T [see notes4,2] — ns
NF22 clock period tCK — — ns
NF23 preamble delay tPRE PRE_DELAY × T [see notes5,2] — ns
NF24 postamble delay tPOST POST_DELAY × T +0.43 [see — ns
note2]
Timing
T = GPMI Clock Cycle
ID Parameter Symbol Unit
Min. Max.
6
NF28 Data write setup tDS 0.25 × tCK - 0.32 — ns
NF29 Data write hold tDH6 0.25 × tCK - 0.79 — ns
NF30 NAND_DQS/NAND_DQ read setup skew tDQSQ7 — 3.18
NF31 NAND_DQS/NAND_DQ read hold skew tQHS7 — 3.27
1
The GPMI toggle mode output timing can be controlled by the module’s internal registers
HW_GPMI_TIMING0_ADDRESS_SETUP, HW_GPMI_TIMING0_DATA_SETUP, and HW_GPMI_TIMING0_DATA_HOLD.
This AC timing depends on these registers settings. In the table, AS/DS/DH represents each of these settings.
2
AS minimum value can be 0, while DS/DH minimum value is 1.
3
T = tCK (GPMI clock period) -0.075 ns (half of maximum p-p jitter).
4
CE_DELAY represents HW_GPMI_TIMING2[CE_DELAY]. NF18 is guaranteed by the design. Read/Write operation is started
with enough time of ALE/CLE assertion to low level.
5
PRE_DELAY+1) ≥ (AS+DS)
6 Shown in Figure 20.
7
Shown in Figure 21.
For DDR Toggle mode, Figure 21 shows the timing diagram of NAND_DQS/NAND_DATAxx read valid
window. The typical value of tDQSQ is 1.4 ns (max) and 1.4 ns (max) for tQHS at 133 MB/s. GPMI will
sample NAND_DATA[7:0] at both rising and falling edge of an delayed NAND_DQS signal, which is
provided by an internal DPLL. The delay value of this register can be controlled by GPMI register
GPMI_READ_DDR_DLL_CTRL.SLV_DLY_TARGET (see the GPMI chapter of the device reference
manual. Generally, the typical delay value is equal to 0x7 which means 1/4 clock cycle delay expected.
But if the board delay is big enough and cannot be ignored, the delay value should be made larger to
compensate the board delay.
Below are the LPSPI interfaces and their respective chip selects:
60 MHz in Master mode and 40 MHz in SPI0, SPI1, SPI2, SPI3 (primary mode) SPI1 is muxed behind ADC pins so it
Slave mode operates at 1.8 V only.
t1 SAI TXC pulse width low / high 45% 55% SAI_TXC period
t1 SAI TXC / RXC pulse width low / high 45% 55% TXC/RXC period
t11 SAI TXC/RXC pulse width low/high 45% 55% TXC/RXC period
SCKT
t1 t1
(Input / Output)
FST (bit) in
t5 t6
FST (word) in
t5 t6
Flags Out
t7
The following table shows the interface timing values. The ID field in the table refers to timing signals
found in Figure 27 and Figure 28.
t1 SCKT / SCKT pulse width high / low 45% 55% — SCKT / SCKR period
SD2
SD1
SD5
SDx_CLK
SD3
SD6
3
In normal (full) speed mode for MMC card, clock frequency can be any value between 0–20 MHz. In high-speed mode, clock
frequency can be any value between 0–52 MHz.
4
To satisfy hold timing, the delay difference between clock input and cmd/data input must not exceed 2 ns.
SD1
SDx_CLK
SD2 SD2
HS400 mode is the same as CMD input/output timing for SDR104 mode. Check SD5, SD6 and SD7
parameters in Table 71 SDR50/SDR104 Interface Timing Specification for CMD input/output timing for
HS400 mode.
SD1
SD2 SD3
SCK
SD4/SD5
SCK
SD5
SD4
SD6 SD7
SD8
1
x can be 0 or 1.
2
Except for RCLK50M and RMII_RXER, all other RMII functions are using the same pin muxing mode as RGMII.
4.10.5.1 RGMII
4.10.5.2 RMII
RMII interface is matching RMII v1.2 specification. In RMII mode, the reference clock can be generated
internally and provided to the PHY through RCLK50M_OUT. Or, it come from and external 50MHz clock
generator which is connected to the PHY and to i.MX8 through RCLK50M_IN pin.
Timings in table below are covering both cases: reference clock generated internally or externally.
4.10.5.3 MDIO
MDIO is the control link used to configure Ethernet PHY connected to i.MX8 device.
DVI mode and cannot detect the video timing. In DVI mode, without the AVI info frame, detection of the
video mode utilized is not possible. In addition, only HDCP 2.2 is supported.
For full HDMI-RX compliance, NXP recommends utilizing an external HDMI to MIPI CSI-2 bridge
device.
HDMI_TX0_DDC_SCL 1.5 — 2 kΩ
HDMI_TX0_DDC_SDA 1.5 — 2 kΩ
REXT 497.50 500 502.50 Ω REXT resistor is 500 Ω ± 0.5%. It shall be connected to ground.
IC9 Bus free time between a STOP and START condition 4.7 — 1.3 — µs
IC10/IC10b Rise time of both I2Cx_SDA and I2Cx_SCL signals — 1000 20 + 0.1Cb4 300 ns
IC11/IC11b Fall time of both I2Cx_SDA and I2Cx_SCL signals — 300 20 + 0.1Cb4 300 ns
IC12 Capacitive load for each bus line (Cb) — 400 — 400 pF
1 A device must internally provide a hold time of at least 300 ns for I2Cx_SDA signal in order to bridge the undefined region of
the falling edge of I2Cx_SCL.
2 The maximum hold time has only to be met if the device does not stretch the LOW period (ID no IC5) of the I2Cx_SCL signal.
3 A Fast-mode I2C-bus device can be used in a Standard-mode I2C-bus system, but the requirement of Set-up time (ID No IC7)
of 250 ns must be met. This automatically is the case if the device does not stretch the LOW period of the I2Cx_SCL signal.
If such a device does stretch the LOW period of the I2Cx_SCL signal, it must output the next data bit to the I2Cx_SDA line
max_rise_time (IC9) + data_setup_time (IC7) = 1000 + 250 = 1250 ns (according to the Standard-mode I2C-bus specification)
before the I2Cx_SCL line is released.
4 C = total capacitance of one bus line in pF.
b
IC9 Bus free time between a STOP and START 500 — 150 — ns
condition
IC12 Capacitive load for each bus line (Cb) — 550 — 100 pF
1 High-speed mode is only available for I2C modules in DMA, SCU and Cortex-M4 subsystems.
Single channel 4 pairs LVDS up to 1.12 Gbps per pair 4 pairs LVDS up to 1.12 Gbps per pair
Function1 Channel A
Differential Voltage Output Voltage VOD 100 Ω Differential load 0.25 0.4 V
Offset Static Voltage VOS Two 49.9 Ω resistors in series between 1.125 1.275 V
N-P terminal, with output in either Zero or
One state, the voltage measured between
the 2 resistors.
Output short-circuited to GND ISA ISB With the output common shorted to GND — 40 mA
VCMTX1 High Speed Transmit Static Common Mode Voltage 150 200 250 mV
tR and tF1 Rise Time and Fall Time (20% to 80%) 100 — 0.35 UI ps
1
UI is the long-term average unit interval.
TLP-PULSE-TX 4 Pulse width of the LP exclusive-OR clock: First LP exclusive-OR clock pulse after Stop 40 — — ns
state or last pulse before Stop state
ps UI ps mV
PCI Express Gen 1 Transition Bit 400 0.75 0 300 0 800 12001
PCI ExpressGen 1 De-emphasized Bit 400 0.75 0 300 0 505 757
PCI Express Gen 2 Transition Bit 200 0.75 0 150 0 800 12001
PCI Express Gen 2 De-emphasized Bit 200 0.75 0 150 0 379 850
1
VDIFFp-p eye opening is limited to VDDIO under matched termination conditions.
ps UI ps mV
PCI Express Gen 1 Transition Bit 400 0.4 0 160 0 175 1200
1
PCI Express Gen 2 Transition Bit 200 0.32 0 64 0 100 1200
1
For a lossy channel, the default DFE setting may not work for PCIe Gen2 -3.5dB TX de-emphasis. It is recommended to use
a higher DFE setting (reg241[7]=A1_force=1 and reg241[5:0]=A1_init) in this case.
2
PCIE 3.0 8 GT/s measured using PCIE reference equalizer + CDR per PCIE specification.PCIe 1.0 and 2.0 compliant. PCIe
3.0 capable, contact your NXP representative.
Table 94. PCIe differential output driver characteristics (including board and load)
Output skewTOSKEW — — 50 ps —
9
Reference Buffer Dynamic Power (Digital) — 0.015 0.66 μA
Reference Buffer Dynamic Power (Analog) — 2.8 3.14 mA 9
1
When the output is transitioning between logic 0 and logic 1, or logic 1 and logic 0, and driving a terminated
transmission line, the outputs monotonically transition between VOL and VOH, VOH, and VOL respectively. Target rise and
fall times observed at the receiver and are primarily set by board trace impedance and Load capacitance. Rise and fall
times are defined by 25% and 75% crossing points.
2 Calculated as: 2 × (TR–TF) / (TR+ TF)
3
IR is proportional to the reference current. Measured across RT. The primary contributor to output voltage spread is
VDD spread, and so a VDD tighter than ±10% may be required to achieve this spread.
4
Higher output voltages may occur depending on load, power supply, and selected output drive. Higher output voltages may
transiently occur during initialization period following TXENA assertion.
5
Peak change in output differential voltage when driving a logic 0 and when driving a logic 1 under DC conditions.
6
Peak change in output differential voltage when driving a logic 0 and when driving a logic 1 under AC conditions.
7
Measured under “clean power supply and ground” conditions, and after de-embedding the jitter of the input, measured over a
time span of 1000 cycles
8
Power supply induced jitter is included under this category, and the power supply variation is to be less than 8mVpp.
Note that customer has to be uncommonly careful with power supply fidelity due to the small jitter numbers.
9
Power consumption is simulated under the following conditions:
Typ: TT, VDD=1.0 V, VD18=1.8 V, 25 °C
Max: FF, VDD=1.1 V, VD18=1.98 V, 125 °C
Dynamic: TXENA=1, TXOE=1
Static: TXENA=0, TXOE=1
4.10.12.2 PCIE_REF_CLK
Contact an NXP representative to obtain the hardware development guide for this device, which contains
details on the PCIe reference clock requirements.
PWMn_OUT
The following read timing diagram is valid for FlexSPIn_MCR0[RXCLKSRC] = 0x0 or 0x1.
Figure 45. FlexSPI read with DQS timing diagram (SDR mode)
QSPIx[A/B]_DQS
QSPIx[A/B]_DATAy
t9 t10
Figure 48. FlexSPI read with DQS timing diagram (DDR mode)
Table 99. FlexSPI timings with FlexSPIn_MCR0[RXCLKSRC] = 0x0 (DDR mode) (continued)
Table 101. FlexSPI timings with FlexSPIn_MCR0[RXCLKSRC] = 0x3 (DDR mode) (continued)
JTAG_TMS PU 50 KΩ
JTAG_TCK PD
JTAG_TDI PU
JTAG_TRST_B PU
TEST_MODE_SELECT PD
1
PU = pull-up; PD = pull-down
SJ1
SJ2 SJ2
JTAG_TCK
(Input) VIH VM VM
VIL
SJ3 SJ3
JTAG_TCK
(Input) VIH
VIL
SJ4 SJ5
Data
Inputs Input Data Valid
SJ6
Data
Output Data Valid
Outputs
SJ7
Data
Outputs
SJ6
Data
Outputs Output Data Valid
JTAG_TCK
(Input) VIH
VIL
SJ8 SJ9
JTAG_TDI
JTAG_TMS Input Data Valid
(Input)
SJ10
JTAG_TDO
(Output) Output Data Valid
SJ11
JTAG_TDO
(Output)
SJ10
JTAG_TDO
(Output) Output Data Valid
JTAG_TCK
(Input)
SJ13
JTAG_TRST_B
(Input)
SJ12
All Frequencies
ID Parameter1,2 Unit
Min Max
srckp
stclkp
UA1 UA1
UA2 UA2
UARTx_TX_DATA
(output)
Start Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 POSSIBLE STOP
Bit PARITY BIT
BIT
UA3 Transmit Bit Time in IrDA mode tTIRbit 1/Fbaud_rate1 – Tref_clk2 1/Fbaud_rate + Tref_clk —
UARTx_RX_DATA
(input)
Start Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7 POSSIBLE STOP
Bit PARITY BIT
BIT
2
Fbaud_rate: Baud rate frequency. The maximum baud rate the UART can support is (LPUART_clk frequency)/(SBR[12:0] ×
(OSR+1)).
Tstrobe
USB_H_STROBE
Todelay
Todelay
USB_H_DATA
Todelay data output delay time 550 1350 ps Measured at 50% point
Tslew strobe/data rising/falling time 0.7 2 V/ns Averaged from 30% – 70% points
USB_H_STROBE
Thold
USB_H_DATA
Tsetup
Tslew strobe/data rising/falling time 0.7 2 V/ns Averaged from 30% – 70% points
1
The timings in the table are guaranteed when:
—AC I/O voltage is between 0.9× to 1× the I/O supply
—DDR_SEL configuration bits of the I/O are set to (10)b
TLDEOP Source Jitter in upstream direction (Differential to SE0 transition) - LS -40 — 100 ns
HS Eye Opening: Template 1 Differential eye opening at 37.5% US and 62.5% UI for a -300 — 300 mV
hub measured at TP2 and for a device without a captive
cable measured at TP3.
HS Eye Opening: Template 2 Differential eye opening at 37.5% US and 62.5% UI for a -175 — 175 mV
device with a captive cable measured at TP2.
HS Jitter: Template 1 Peak-Peak Jitter at Zero crossing for a hub measured at — — 15 %UI
TP2 and for a device without captive cable measured at
TP3. — — 312.5 ps
HS Jitter: Template 2 Peak-Peak Jitter at Zero crossing for a device with captive — — 25 %UI
cable measured at TP2.
— — 520.83 ps
HSRX Jitter: Template 3 HS RX Peak-Peak Jitter specification at differential zero crossing for a — — 20 %UI
device with captive cable when signal applied at TP2.
— — 416.66 ps
HSRX Jitter: Template 4 HS RX Peak-Peak Jitter specification at differential zero crossing for a — — 30 %UI
device without captive cable at TP3 and for a hub at TP2.
— — 625 ps
HSRX Input Eye Opening: HS RX differential sensitivity specification at 40% and 60% UI for a -275 — 275 mV
Template 3 device with captive cable when signal is applied at TP2.
HSRX Input Eye Opening: HS RX differential sensitivity specification at 35% and 65% UI for a -150 — 150 mV
Template 4 device without captive cable when signal is applied at TP3 and for a
hub when a signal is applied at TP2.
rext 497.5 500 502.5 Ω There needs to be an external resistor component connected at rext ball while the
internal resistor or current is getting calibrated. Package routing from rext ball to its
respective bump should not contribute more than 0.05 Ω.
Voltage/current parameters
RLTX-CM Transmitter common mode return — — 50Hz < -8dB < 15000Mhz dB
loss
Table 119. USB 3.0 PHY transmitter module electrical specifications (continued)
Voltage parameters
Tx signal characteristics
Voltage Parameters
Table 120. USB 3.0 PHY receiver module electrical specifications (continued)
Vcm, acRX RX AC Common Mode Voltage — — 100 mVp-p Simulated at 250 MHz
Jitter Parameters
Dividers
VCO
may be dominated by board parasitics. Care must be taken not to corrupt the desired channel being measured. This coupling
becomes worse at higher analog frequencies and with switching waveforms due to the harmonic content.
8 Error measured at fullscale at 1.8 V.
9 Error measured at zero scale at 0 V.
10 Power Configuration Select, PWRSEL, is set to 10 binary.
The following table shows the ADC electrical specifications for 1V≤VREFH<VDD_ADC_1P8.
possible. The results in this data sheet were derived from a system that had < 15 Ω analog source resistance. The RAS/CAS
(analog source capacitance) time constant should be kept to < 1 ns.
3 See Figure 61.
4 ADC conversion clock at max frequency and using linear histogram.
5 Input data used for test was 1 kHz sine wave.
6 Measured at VREFH = 1 V and pwrsel = 2.
7 ENOB can be lower than shown, if an ADC channel corrupts other ADC channels through capacitive coupling. This coupling
may be dominated by board parasitics. Care must be taken not to corrupt the desired channel being measured. This coupling
becomes worse at higher analog frequencies and with switching waveforms due to the harmonic content.
8 Error measured at fullscale at 1.0 V.
9 Error measured at zero scale at 0 V.
10 Power Configuration Select, PWRSEL, is set to 10 binary.
The following figure shows a plot of the ADC sample time versus RAS.
Table 124. Boot options and associated inputs used for Boot
The notes in the following figure pertain to the preceding figure., “29 x 29 mm Package Top, Bottom, and
Side Views.”
VSS_MAI FLEXCAN FLEXCAN USDHC2_ VSS_MAI VSS_MAI ENET1_MD VSS_MAI PCIE_SAT VSS_MAI VSS_MAI VSS_MAI PCIE1_TX0 PCIE0_TX0 VSS_MAI VSS_MAI VSS_MAI USB_SS3 USB_OTG USB_OTG VSS_MAI VSS_MAI ENET0_RG ENET1_RG VSS_MAI ENET1_RG VSS_MAI
C
N 2_RX 0_RX RESET_B N N IO N A0_TX0_N N N N _N _N N N N _RX_P 2_DN 1_DN N N MII_RXD2 MII_TXD1 N MII_RXD1 N
PCIE_CTR
VSS_MAI USDHC2_ ENET0_MD QSPI1A_D QSPI1A_D VSS_MAI VSS_MAI PCIE_REX VSS_MAI VSS_MAI VSS_MAI MLB_SIG_ MLB_CLK VSS_MAI VSS_MAI VSS_MAI VSS_MAI ENET0_RG ENET0_RG ENET1_RG ENET1_RG ENET1_RG
D MLB_CLK L0_PERST
N WP IO ATA0 ATA1 N N T N N N P _P N N N N MII_TXD3 MII_RXD1 MII_TXC MII_TXD3 MII_RXD2
_B
PCIE_SAT USB_HSIC
VSS_MAI VSS_MAI USB_SS3 QSPI1A_S VSS_MAI QSPI0A_D QSPI0A_S QSPI0B_S QSPI0B_D QSPI0B_S VSS_MAI USB_OTG VSS_MAI MLB_DAT VSS_MAI USDHC1_ USDHC1_ USDHC1_ VSS_MAI USDHC2_ VSS_MAI VSS_MAI
F A_REFCL 0_STROB
N N _TC2 CLK N ATA1 S1_B CLK ATA3 S0_B N 2_ID N A_P N DATA1 DATA3 DATA6 N CLK N N
K100M_P E
PCIE_CTR
DDR_CH1 DDR_CH1 VSS_MAI FLEXCAN VSS_MAI QSPI1A_S QSPI0A_D VSS_MAI QSPI0A_D QSPI0B_D VSS_MAI VSS_MAI VSS_MAI EMMC0_D EMMC0_D VSS_MAI EMMC0_D EMMC0_S VSS_MAI USDHC1_ USDHC1_ USDHC2_ ENET1_RG VSS_MAI DDR_CH0 DDR_CH0
G L1_PERST
_DQ05 _DQ06 N 1_TX N S1_B ATA0 N QS ATA2 N N N ATA0 ATA2 N ATA7 TROBE N CMD DATA5 DATA1 MII_TXD2 N _DQ06 _DQ05
_B
DDR_CH1 DDR_CH1 FLEXCAN USB_SS3 QSPI1A_D QSPI0A_D QSPI0A_D QSPI0B_D QSPI0B_D QSPI0B_D QSPI0B_S USB_HSIC EMMC0_C EMMC0_D EMMC0_D EMMC0_D EMMC0_D EMMC0_R USDHC1_ USDHC1_ USDHC2_ USDHC2_ DDR_CH0 DDR_CH0
H
_DM0 _DQ04 0_TX _TC3 QS ATA2 ATA3 ATA0 ATA1 QS S1_B 0_DATA LK ATA1 ATA3 ATA5 ATA6 ESET_B DATA4 DATA7 CMD DATA0 _DQ04 _DM0
VSS_MAI VSS_MAI VSS_MAI VSS_MAI USB_SS3 QSPI1A_S VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI EMMC0_C VSS_MAI VSS_MAI EMMC0_D VSS_MAI VSS_MAI USDHC1_ VSS_MAI USDHC1_ USDHC2_ VSS_MAI VSS_MAI VSS_MAI VSS_MAI
J
N N N N _TC0 S0_B N N N N N N N MD N N ATA4 N N CLK N STROBE DATA3 N N N N
DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0
K
_DQS0_P _DQ09 _DQ03 N N N N N N N N N N N N N N N N N N _DQ03 _DQ09 _DQS0_P
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 USB_SS3 VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI USDHC2_ DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
L
_DQS0_N _DQ11 _DQ08 _DQ02 _TC1 N N N N N N N N N N N N N N N N N DATA2 _DQ02 _DQ08 _DQ11 _DQS0_N
PCIE_SAT VDD_USB
VDD_MLB VDD_USB VDD_QSPI VDD_PCIE VDD_PCIE PCIE0_PH VDD_USB VDD_USB VDD_USD VDD_USD VDD_ENE
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI A0_PHY_ VDD_PCIE _SS3_LD VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI
M _DIG_1P8 _SS3_TC_ 1A_1P8_3 1_PLL_1P _SATA0_ Y_PLL_RE _OTG1_1P _OTG2_3P HC1_1P8_ HC2_1P8_ T0_1P8_3
N N N N N PLL_REF_ 0_1P0 O_1P0_C N N N N N
_3P3 3P3 P3 8 1P0 F_RETURN 0 3 3P3 3P3 P3
RETURN AP
VDD_ENE
VDD_FLE VDD_QSPI VDD_PCIE PCIE1_PH VDD_PCIE VDD_PCIE VDD_USB VDD_USB VDD_EMM VDD_USD VDD_ENE
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI T_MDIO_1 VDD_PCIE VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
N XCAN_1P 0_1P8_3P _SATA0_ Y_PLL_RE 0_PLL_1P _LDO_1P0 _OTG2_1P _OTG1_3P C0_1P8_3 HC1_1P8_ T0_1P8_3
_DQS1_P _DQ10 _DQ13 _DM1 _DQ01 _DQ07 N P8_2P5_3 1_1P0 N _DQ07 _DQ01 _DM1 _DQ13 _DQ10 _DQS1_P
8_3P3 3 PLL_1P8 F_RETURN 8 _CAP 0 3 P3 3P3 P3
P3
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
P
_DQS1_N _DQ14 _DQ15 _DQ12 _DQ00 N N _DQ00 _DQ12 _DQ15 _DQ14 _DQS1_N
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI
R
N N N N N N N N N N N N N N N N N N N N N N N N N
VDD_USD
VDD_ENE
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI HC_VSEL VSS_MAI VDD_PCIE VSS_MAI VDD_PCIE VSS_MAI VDD_MLB VSS_MAI VDD_MAI VSS_MAI VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
T T1_1P8_2
_DCF09 _DCF10 _DCF08 _DCF13 _DTO1 N N ECT_1P8_ N _DIG_1P8 N _IOB_1P8 N _1P8 N N N N _DTO1 _DCF13 _DCF08 _DCF10 _DCF09
P5_3P3
3P3
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VDD_MAI VSS_MAI VDD_MAI VDD_ANA VDD_PCIE VDD_ANA VDD_ANA VSS_MAI VDD_GPU VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
U _CH1_VD _CH0_VD
_DCF16 _DCF11 _DCF12 _DCF00 _DTO0 _VREF N N N N 1_1P8 _LDO_1P8 0_1P8 0_1P8 N 1 N _VREF _DTO0 _DCF00 _DCF12 _DCF11 _DCF16
DQ DQ
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VDD_MEM VSS_MAI VDD_GPU VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_GPU VSS_MAI VDD_MEM DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
W _CH1_VD _CH0_VD
_DCF14 _DCF07 _CK0_P _DCF01 _DCF06 _DCF04 C N 0 N N N N N 1 N C _DCF04 _DCF06 _DCF01 _CK0_P _DCF07 _DCF14
DQ DQ
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VDD_GPU VSS_MAI VDD_GPU VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_GPU VSS_MAI VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
Y _CH1_VD _CH0_VD
_DCF15 _CK0_N _DCF02 _DCF03 _DCF05 N 0 N 0 N N N N N 1 N N _DCF05 _DCF03 _DCF02 _CK0_N _DCF15
DQ DQ
VDD_DDR VDD_DDR
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_GPU VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_GPU VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI
AA _CH1_VD _CH0_VD
N N N N N N N N 0 N N N N N N N 1 N N N N N N N N
DQ DQ
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI VDD_GPU VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_GPU VSS_MAI VDD_GPU VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
AB _CH1_VD _CH0_VD
_DCF31 _CK1_N _DCF18 _DCF19 _DCF24 N N 0 N N N N N 1 N 1 N _DCF24 _DCF19 _DCF18 _CK1_N _DCF31
DQ_CKE DQ_CKE
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VDD_MEM VSS_MAI VDD_GPU VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_GPU VSS_MAI VDD_MEM VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
AC _CH1_VD _CH0_VD
_DCF30 _DCF22 _CK1_P _DCF17 _DCF23 _DCF20 N C N 0 N N N N N 1 N C N _DCF20 _DCF23 _DCF17 _CK1_P _DCF22 _DCF30
DQ_CKE DQ_CKE
VDD_DDR VDD_DDR
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_GPU VSS_MAI VDD_GPU VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_GPU VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI
AD _CH1_VD _CH0_VD
N N N N N N 0 N 0 N N N N N 1 N N N N N N N
DQ_CKE DQ_CKE
VDD_DDR VDD_DDR
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 _CH1_VD VSS_MAI VSS_MAI VDD_GPU VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_GPU VSS_MAI VSS_MAI _CH0_VD DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
AE _CH1_VD _CH0_VD
_DCF32 _DCF27 _DCF29 _DCF26 _DCF21 DA_PLL_1 N N 0 N N N N N N N 1 N N DA_PLL_1 _DCF21 _DCF26 _DCF29 _DCF27 _DCF32
DQ DQ
P8 P8
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
AF _CH1_VD _CH0_VD
_DCF25 _DCF28 _DCF33 _ATO _ZQ N N N N N N N N N N N N _ZQ _ATO _DCF33 _DCF28 _DCF25
DQ DQ
VDD_DDR VDD_DDR
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_MEM VSS_MAI VDD_MAI VSS_MAI VDD_MEM VSS_MAI VDD_MEM VSS_MAI VDD_MAI VSS_MAI VDD_MEM VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI
AG _CH1_VD _CH0_VD
N N N N N N N C N N N C N C N N N C N N N N N N N
DQ DQ
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VDD_MAI VSS_MAI VDD_MEM VSS_MAI VDD_MEM VSS_MAI VDD_MEM VSS_MAI VDD_MAI VSS_MAI VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
AH _CH1_VD _CH0_VD
_DQS2_N _DQ23 _DQ22 _DQ21 _DQ25 N N N C N C N C N N N N _DQ25 _DQ21 _DQ22 _DQ23 _DQS2_N
DQ DQ
VDD_DDR VDD_DDR
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MEM VSS_MAI VDD_MEM VSS_MAI VDD_MAI VSS_MAI VDD_ANA VSS_MAI VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
AJ _CH1_VD _CH0_VD
_DQS2_P _DQ19 _DQ20 _DM2 _DQ24 _DQ30 N N N N C N C N N N 2_1P8 N N _DQ30 _DQ24 _DM2 _DQ20 _DQ19 _DQS2_P
DQ DQ
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_ADC VSS_MAI VDD_ANA VSS_MAI VDD_MEM VSS_MAI VDD_MEM VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_SIM0 VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI
AK
N N N N N N _DIG_1P8 N 3_1P8 N C N C N N N N N _1P8_3P3 N N N N N
VDD_M4_
DDR_CH1 DDR_CH1 DDR_CH1 DDR_CH1 VREFH_A VSS_MAI VDD_ADC VDD_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VSS_MAI VSS_MAI VDD_MAI GPT_UAR VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0 DDR_CH0
AL ADC_IN6 VDD_A72 VDD_A72 SIM0_PD SIM0_CLK
_DQS3_N _DQ18 _DQ17 _DQ27 DC N _1P8 N N N N N N N N N T_1P8_3P N _DQ27 _DQ17 _DQ18 _DQS3_N
3
VDD_M4_
VDD_SPI_
DDR_CH1 DDR_CH1 DDR_CH1 VSS_MAI VREFL_A VSS_MAI VDD_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI GPT_UAR VSS_MAI M40_I2C0 VSS_MAI DDR_CH0 DDR_CH0 DDR_CH0
AM SAI_1P8_ VDD_A53 VDD_A53 VDD_A72 VDD_A72
_DQS3_P _DQ16 _DQ26 N DC N N N N N N N T_1P8_3P N _SCL N _DQ26 _DQ16 _DQS3_P
3P3
3
VDD_SPI_
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_CP_ VDD_SCU VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI
AN ADC_IN4 ADC_IN1 SAI_1P8_ VDD_A53 VDD_A72 VDD_A72 VDD_A72 SIM0_IO
N N N N N N N N N N N 1P8 _1P8 N N N N N N
3P3
VDD_ESAI
DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI VDD_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_MAI VDD_SCU VDD_M1P M41_GPIO SIM0_GPI DDR_CH0 DDR_CH0
AP ADC_IN7 ADC_IN2 ADC_IN0 0_MCLK_1 VDD_A53 VDD_A72 VDD_A72 SIM0_RST
_DM3 _DQ29 N N N N N N N N _1P8 8_CAP 0_00 O0_00 _DQ29 _DM3
P8_3P3
VDD_ESAI VDD_SCU
DDR_CH1 DDR_CH1 VSS_MAI VSS_MAI VDD_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VDD_MAI UART1_R M41_I2C0 M40_GPIO VSS_MAI DDR_CH0 DDR_CH0
AR ADC_IN5 ADC_IN3 0_MCLK_1 VDD_A53 VDD_A53 VDD_A72 VDD_A72 _ANA_1P
_DQ28 _DQ31 N N N N N N N N N TS_B _SCL 0_00 N _DQ31 _DQ28
P8_3P3 8
VSS_MAI VSS_MAI VSS_MAI VSS_MAI ESAI1_TX VSS_MAI VSS_MAI VDD_MAI VSS_MAI VSS_MAI VDD_MAI VSS_MAI VDD_MAI VSS_MAI VSS_MAI VDD_SNV VSS_MAI UART1_R VSS_MAI SIM0_PO VSS_MAI VSS_MAI
AT VDD_A53 VDD_A72
N N N N 5_RX0 N N N N N N N N N N S_4P2 N X N WER_EN N N
SCU_PMIC
ESAI0_TX ESAI0_TX ESAI1_TX VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI SCU_BOO VSS_MAI JTAG_TM GPT1_CO
BA SPI2_SDO SPI0_CS1 SPI0_SDI _STANDB GPT1_CLK
1 0 1 N N N N N N N N N N N N N N N T_MODE3 N S MPARE
Y
VSS_MAI VSS_MAI ESAI0_SC VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI SCU_BOO SCU_GPIO VSS_MAI SCU_WDO VSS_MAI
BB SPI0_SCK
N N KR N N N N N N N N N N N N N N N T_MODE0 0_03 N G_OUT N
TEST_MO SCU_PMIC
ESAI0_TX SPDIF0_R SPDIF0_T VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI SCU_BOO SCU_GPIO JTAG_TC
BC SPI0_CS0 MCLK_IN0 DE_SELEC _MEMC_O
3_RX2 X X N N N N N N N N N N N N N N N N N T_MODE1 0_04 K
T N
SNVS_TA SNVS_TA
ANA_TES MCLK_OU SPDIF0_E ESAI1_SC VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI MIPI_DSI0_ MIPI_DSI0_ LVDS1_I2 LVDS1_G LVDS0_I2 LVDS0_I2 LVDS0_G VSS_MAI VSS_MAI JTAG_TD
BD SPI3_CS1 MPER_OU MPER_OU
T_OUT1_N T0 XT_CLK KR N N N N N N N GPIO0_01 GPIO0_00 C1_SCL PIO00 C0_SDA C0_SCL PIO01 N N O
T1 T0
HDMI_RX0
ANA_TES VSS_MAI VSS_MAI VSS_MAI ESAI1_FS MIPI_CSI1_ MIPI_CSI0_ MIPI_CSI0_ MIPI_CSI0_ MIPI_CSI0_ MIPI_CSI0_ MIPI_DSI1_ MIPI_DSI0_ MIPI_DSI0_ LVDS1_I2 LVDS0_I2 LVDS0_I2 LVDS0_G SNVS_TA SNVS_TA VSS_MAI ON_OFF_ JTAG_TR
BE SPI3_SDI _DDC_SD POR_B JTAG_TDI
T_OUT1_P N N N R I2C0_SDA DATA3_N DATA1_N CLK_N DATA0_N DATA2_N I2C0_SCL I2C0_SCL I2C0_SDA C0_SDA C1_SDA C1_SCL PIO00 MPER_IN0 MPER_IN1 N BUTTON ST_B
A
PMIC_EAR
VSS_MAI ESAI1_TX ESAI1_FS HDMI_RX0 MIPI_CSI0_ MIPI_CSI0_ MIPI_CSI0_ MIPI_CSI0_ MIPI_CSI0_ VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI SCU_GPIO VSS_MAI
BF SPI3_SDO SPI3_SCK LY_WARN
N 0 T _HPD DATA3_P DATA1_P CLK_P DATA0_P DATA2_P N N N N N N N N N N 0_07 N
ING
HDMI_TX0
HDMI_TX0 VSS_MAI ESAI0_FS VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI MIPI_DSI1_ MIPI_DSI1_ MIPI_DSI1_ MIPI_DSI1_ MIPI_DSI1_ MIPI_DSI1_ LVDS0_C LVDS0_C LVDS0_C LVDS0_C LVDS0_C VSS_MAI SCU_GPIO PMIC_I2C_ ANA_TES
BG _DDC_SC SPI3_CS0
_AUX_N N T N N N N N N N I2C0_SDA DATA3_P DATA1_P CLK_P DATA0_P DATA2_P H1_TX3_N H1_TX2_N H1_TX1_N H1_TX0_N H1_CLK_N N 0_06 SDA T_OUT0_P
L
HDMI_RX0
HDMI_TX0 VSS_MAI HDMI_TX0 MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI1_ VSS_MAI MIPI_CSI0_ MIPI_DSI1_ MIPI_DSI1_ MIPI_DSI1_ MIPI_DSI1_ MIPI_DSI1_ LVDS1_G LVDS0_C LVDS0_C LVDS0_C LVDS0_C LVDS0_C PMIC_INT_ ANA_TES
BH _DDC_SC
_AUX_P N _HPD DATA3_N DATA1_N CLK_N DATA0_N DATA2_N N I2C0_SCL DATA3_N DATA1_N CLK_N DATA0_N DATA2_N PIO01 H1_TX3_P H1_TX2_P H1_TX1_P H1_TX0_P H1_CLK_P B T_OUT0_N
L
MIPI_CSI0_
HDMI_TX0 VSS_MAI VSS_MAI HDMI_TX0 HDMI_RX0 HDMI_RX0 MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI1_ VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI SCU_BOO
BJ MCLK_OU
_CEC N N _REXT _CEC _REXT DATA3_P DATA1_P CLK_P DATA0_P DATA2_P N N N N N N N N N N N N N N T_MODE2
T
HDMI_TX0
VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI VSS_MAI MIPI_DSI1_ MIPI_DSI0_ MIPI_DSI0_ LVDS1_C LVDS1_C LVDS1_C LVDS1_C LVDS1_C LVDS1_C LVDS0_C LVDS0_C VSS_MAI VSS_SCU SCU_BOO
BK _CLK_EDP
N N N N N N N N N GPIO0_01 DATA1_P DATA0_P H1_TX3_N H1_TX1_N H1_CLK_N H0_CLK_N H0_TX1_N H0_TX3_N H0_TX0_N H0_TX2_N N _XTAL T_MODE5
3_N
HDMI_TX0 MIPI_CSI1_
VSS_MAI HDMI_TX0 HDMI_TX0 HDMI_RX0 MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI1_ MIPI_CSI0_ VSS_MAI MIPI_DSI0_ MIPI_DSI0_ MIPI_DSI0_ LVDS1_C LVDS1_C LVDS1_I2 LVDS1_C LVDS1_C LVDS0_C LVDS0_C LVDS0_C RTC_XTA VSS_SCU
BN _DDC_SD MCLK_OU XTALI
N _TS_SDA _TS_SCL _MON_5V GPIO0_01 GPIO0_00 I2C0_SCL I2C0_SDA N DATA3_N CLK_N DATA2_N H1_TX2_P H1_TX0_P C1_SDA H0_TX0_P H0_TX2_P H0_CLK_P H0_TX1_P H0_TX3_P LI _XTAL
A T
VDD_A72 AL29, AL33, AM30, AM34, AN27, AN31, AN35, AP28, AP32, AR29, AR33, AT34
VDD_ADC_1P8 AL15
VDD_ADC_DIG_1P8 AK16
VDD_ANA1_1P8 U25
VDD_ANA2_1P8 AJ35
VDD_ANA3_1P8 AK20
VDD_CP_1P8 AN37
VDD_DDR_CH0_VDDA_PLL_1P8 AE43
VDD_DDR_CH0_VDDQ AA39, AE39, AF38, AG39, AH38, AJ39, U39, V38, W39, Y38
VDD_DDR_CH1_VDDA_PLL_1P8 AE11
VDD_DDR_CH1_VDDQ AA15, AE15, AF16, AG15, AH16, AJ15, U15, V16, W15, Y16
VDD_EMMC0_1P8_3P3 N35
VDD_ENET_MDIO_1P8_3P3 N17
VDD_ENET1_1P8_2P5_3P3 T38
VDD_ESAI1_SPDIF_SPI_1P8_3P3 AU15
VDD_FLEXCAN_1P8_3P3 N15
VDD_GPU0 AA19, AB20, AC21, AD18, AD22, AE19, V20, W21, Y18, Y22
VDD_GPU1 AA35, AB32, AB36, AC33, AD34, AE35, U35, V36, W33, Y34
VDD_HDMI_RX0_LDO0_1P0_CAP1 AU19
VDD_HDMI_RX0_LDO1_1P0_CAP1 AU21
VDD_HDMI_RX0_VH_RX_3P31 AV20
VDD_HDMI_TX0_1P0 AV16
VDD_HDMI_TX0_1P8 AW17
VDD_HDMI_TX0_DIG_3P3 AW21
VDD_HDMI_TX0_LDO_1P0_CAP AW15
VDD_LVDS_DIG_1P8_3P3 AV32
VDD_LVDS0_1P0 AV36
VDD_LVDS0_1P8 AV34
VDD_LVDS1_1P0 AW35
VDD_LVDS1_1P8 AW33
VDD_M1P8_CAP AP42
VDD_MAIN AA23, AA27, AA31, AB24, AB28, AC25, AC29, AD26, AD30, AE23, AE27, AE31, AF20,
AF24, AF28, AF32, AF36, AG21, AG33, AH18, AH34, AJ19, AJ31, AK32, AK36, AL17,
AL21, AL25, AL37, AM18, AN19, AP20, AP36, AR17, AR37, AT18, AT26, AT30, AU35,
T34, U19, U23, V24, V32, W25, W29, Y26, Y30
VDD_MEMC AC17, AC37, AG17, AG25, AG29, AG37, AH22, AH26, AH30, AJ23, AJ27, AK24, AK28,
W17, W37
VDD_MIPI_CSI_DIG_1P8 AV22
VDD_MIPI_CSI0_1P0 AV26
VDD_MIPI_CSI0_1P8 AV24
VDD_MIPI_CSI1_1P0 AW25
VDD_MIPI_CSI1_1P8 AU23
VDD_MIPI_DSI_DIG_1P8_3P3 AU27
VDD_MIPI_DSI0_1P0 AU29
VDD_MIPI_DSI0_1P8 AW31
VDD_MIPI_DSI0_PLL_1P0 AW29
VDD_MIPI_DSI1_1P0 AV28
VDD_MIPI_DSI1_1P8 AV30
VDD_MIPI_DSI1_PLL_1P0 AW27
VDD_MLB_1P82 T30
VDD_MLB_DIG_1P8_3P33 M14
VDD_PCIE_DIG_1P8_3P3 T22
VDD_PCIE_IOB_1P8 T26
VDD_PCIE_LDO_1P0_CAP N29
VDD_PCIE_LDO_1P8 U27
VDD_PCIE_SATA0_1P0 M24
VDD_PCIE_SATA0_PLL_1P8 N21
VDD_PCIE0_1P0 M26
VDD_PCIE0_PLL_1P8 N27
VDD_PCIE1_1P0 N25
VDD_PCIE1_PLL_1P8 M22
VDD_QSPI0_1P8_3P3 N19
VDD_QSPI1A_1P8_3P3 M18
VDD_SCU_ANA_1P8 AR39
VDD_SCU_XTAL_1P8 AU39
VDD_SIM0_1P8_3P3 AK42
VDD_SNVS_4P2 AT38
VDD_SNVS_LDO_1P8_CAP AW39
VDD_USB_HSIC0_1P2 V26
VDD_USB_HSIC0_1P8 V28
VDD_USB_OTG1_1P0 M32
VDD_USB_OTG1_3P3 N33
VDD_USB_OTG2_1P0 N31
VDD_USB_OTG2_3P3 M34
VDD_USB_SS3_LDO_1P0_CAP M30
VDD_USB_SS3_TC_3P3 M16
VDD_USDHC_VSELECT_1P8_3P3 T18
VDD_USDHC2_1P8_3P3 M38
VREFH_ADC AL11
VREFL_ADC AM10
VSS_MAIN A23, A3, A31, A51, AA1, AA11, AA13, AA17, AA21, AA25, AA29, AA3, AA33, AA37,
AA41, AA43, AA45, AA47, AA49, AA5, AA51, AA53, AA7, AA9, AB12, AB18, AB22,
AB26, AB30, AB34, AB42, AC13, AC19, AC23, AC27, AC31, AC35, AC41, AD10, AD12,
AD2, AD20, AD24, AD28, AD32, AD36, AD4, AD42, AD44, AD46, AD48, AD50, AD52,
AD6, AD8, AE13, AE17, AE21, AE25, AE29, AE33, AE37, AE41, AF12, AF18, AF22,
AF26, AF30, AF34, AF42, AG1, AG11, AG13, AG19, AG23, AG27, AG3, AG31, AG35,
AG41, AG43, AG45, AG47, AG49, AG5, AG51, AG53, AG7, AG9, AH12, AH20, AH24,
AH28, AH32, AH36, AH42, AJ13, AJ17, AJ21, AJ25, AJ29, AJ33, AJ37, AJ41, AK10,
AK12, AK18, AK2, AK22, AK26, AK30, AK34, AK38, AK4, AK44, AK46, AK48, AK50,
AK52, AK6, AK8, AL13, AL19, AL23, AL27, AL31, AL35, AL41, AM12, AM20, AM24,
AM28, AM32, AM36, AM42, AM46, AM8, AN1, AN13, AN17, AN21, AN25, AN29, AN3,
AN33, AN41, AN43, AN47, AN49, AN5, AN51, AN53, AN7, AP12, AP18, AP22, AP26,
AP30, AP34, AR11, AR19, AR23, AR27, AR31, AR35, AR49, AR5, AT12, AT16, AT2,
AT20, AT24, AT28, AT32, AT36, AT4, AT42, AT46, AT50, AT52, AT6, AT8, AU17, AU25,
AU31, AU33, AU37, AV12, AV38, AV42, AW11, AW19, AW23, AW3, AW37, AW43,
AW47, AW51, AW7, B12, B14, B18, B28, B36, B46, B6, BA13, BA15, BA17, BA19, BA21,
BA23, BA25, BA27, BA29, BA31, BA33, BA35, BA37, BA39, BA41, BA45, BB10, BB14,
BB16, BB18, BB2, BB20, BB22, BB24, BB26, BB28, BB30, BB32, BB34, BB36, BB38,
BB40, BB48, BB52, BB6, BC11, BC13, BC15, BC17, BC19, BC21, BC23, BC25, BC27,
BC29, BC31, BC33, BC35, BC37, BC39, BC41, BC43, BD14, BD16, BD18, BD20, BD22,
BD24, BD26, BD48, BD50, BE3, BE45, BE7, BE9, BF26, BF28, BF30, BF32, BF34,
BF36, BF38, BF4, BF40, BF42, BF44, BF52, BG11, BG13, BG15, BG17, BG19, BG21,
BG23, BG47, BG7, BH22, BH4, BJ25, BJ27, BJ29, BJ3, BJ31, BJ33, BJ35, BJ37, BJ39,
BJ41, BJ43, BJ45, BJ47, BJ49, BJ5, BJ51, BK10, BK12, BK14, BK16, BK18, BK20,
BK22, BK46, BK6, BK8, BL1, BL21, BL53, BM10, BM46, BN21, BN3, C1, C11, C15, C19,
C21, C23, C29, C31, C33, C41, C43, C49, C53, C9, D16, D18, D24, D26, D28, D34, D36,
D38, D40, D6, E19, E21, E47, E9, F12, F2, F24, F32, F36, F4, F44, F50, F52, G15, G21,
G23, G27, G33, G39, G49, G5, G9, J1, J13, J15, J17, J19, J21, J23, J25, J29, J3, J31,
J35, J37, J41, J47, J49, J5, J51, J53, J7, K12, K14, K16, K18, K20, K22, K24, K26, K28,
K30, K32, K34, K36, K38, K40, K42, K46, K8, L11, L13, L15, L17, L19, L21, L23, L25,
L27, L29, L31, L33, L35, L37, L39, L41, L43, M10, M2, M4, M44, M46, M48, M50, M52,
M6, M8, N13, N41, P12, P42, R1, R11, R15, R17, R19, R21, R23, R25, R27, R29, R3,
R31, R33, R35, R37, R39, R43, R45, R47, R49, R5, R51, R53, R7, R9, T12, T16, T20,
T24, T28, T32, T36, T42, U17, U21, U33, U37, V10, V12, V18, V2, V22, V30, V34, V4,
V42, V44, V46, V48, V50, V52, V6, V8, W19, W23, W27, W31, W35, Y12, Y20, Y24, Y28,
Y32, Y36, Y42
are used, as determined by IOMUX selection. Alternately, terminate the MLB supply, per the Hardware Developer’s Guide power
supplies of unused functions.
The following table shows functional contact assignments for the 29 × 29 mm package.
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BE1 ANA_TEST_OUT1_P
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BJ9 HDMI_RX0_CEC3
BL11 HDMI_RX0_CLK_N3
BM12 HDMI_RX0_CLK_P3
BL15 HDMI_RX0_DATA0_N3
BM16 HDMI_RX0_DATA0_P3
BL17 HDMI_RX0_DATA1_N3
BM18 HDMI_RX0_DATA1_P3
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BM20 HDMI_RX0_DATA2_P3
BH10 HDMI_RX0_DDC_SCL3
BE13 HDMI_RX0_DDC_SDA3
BF14 HDMI_RX0_HPD3
BN11 HDMI_RX0_MON_5V3
BJ11 HDMI_RX0_REXT3
BH2 HDMI_TX0_AUX_P
BJ1 HDMI_TX0_CEC
BK2 HDMI_TX0_CLK_EDP3_N
BL3 HDMI_TX0_CLK_EDP3_P
BM4 HDMI_TX0_DATA0_EDP2_N
BL5 HDMI_TX0_DATA0_EDP2_P
BM6 HDMI_TX0_DATA1_EDP1_N
BL7 HDMI_TX0_DATA1_EDP1_P
BM8 HDMI_TX0_DATA2_EDP0_N
BL9 HDMI_TX0_DATA2_EDP0_P
BG1 HDMI_TX0_DDC_SCL
BN5 HDMI_TX0_DDC_SDA
BH8 HDMI_TX0_HPD
BJ7 HDMI_TX0_REXT
BE51 JTAG_TDI PU
BA49 JTAG_TMS PU
BE53 JTAG_TRST_B
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BN41 LVDS0_CH0_CLK_P
BK42 LVDS0_CH0_TX0_N
BM42 LVDS0_CH0_TX0_P
BN43 LVDS0_CH0_TX1_P
BK44 LVDS0_CH0_TX2_N
BM44 LVDS0_CH0_TX2_P
BL45 LVDS0_CH0_TX3_N
BN45 LVDS0_CH0_TX3_P
BG45 LVDS0_CH1_CLK_N
BH46 LVDS0_CH1_CLK_P
BG43 LVDS0_CH1_TX0_N
BH44 LVDS0_CH1_TX0_P
BG41 LVDS0_CH1_TX1_N
BH42 LVDS0_CH1_TX1_P
BG39 LVDS0_CH1_TX2_N
BH40 LVDS0_CH1_TX2_P
BG37 LVDS0_CH1_TX3_N
BH38 LVDS0_CH1_TX3_P
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BM36 LVDS1_CH0_CLK_P
BL37 LVDS1_CH0_TX0_N
BN37 LVDS1_CH0_TX0_P
BK38 LVDS1_CH0_TX1_N
BM38 LVDS1_CH0_TX1_P
BL39 LVDS1_CH0_TX2_N
BN39 LVDS1_CH0_TX2_P
BK40 LVDS1_CH0_TX3_N
BM40 LVDS1_CH0_TX3_P
BK34 LVDS1_CH1_CLK_N
BL33 LVDS1_CH1_TX0_N
BN33 LVDS1_CH1_TX0_P
BK32 LVDS1_CH1_TX1_N
BM32 LVDS1_CH1_TX1_P
BL31 LVDS1_CH1_TX2_N
BN31 LVDS1_CH1_TX2_P
BK30 LVDS1_CH1_TX3_N
BM30 LVDS1_CH1_TX3_P
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BF20 MIPI_CSI0_CLK_P
BE23 MIPI_CSI0_DATA0_N
BF22 MIPI_CSI0_DATA0_P
BE19 MIPI_CSI0_DATA1_N
BF18 MIPI_CSI0_DATA1_P
BE25 MIPI_CSI0_DATA2_N
BF24 MIPI_CSI0_DATA2_P
BF16 MIPI_CSI0_DATA3_P
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BJ17 MIPI_CSI1_CLK_P
BH18 MIPI_CSI1_DATA0_N
BJ19 MIPI_CSI1_DATA0_P
BH14 MIPI_CSI1_DATA1_N
BJ15 MIPI_CSI1_DATA1_P
BH20 MIPI_CSI1_DATA2_N
BJ21 MIPI_CSI1_DATA2_P
BH12 MIPI_CSI1_DATA3_N
BJ13 MIPI_CSI1_DATA3_P
BL27 MIPI_DSI0_CLK_P
BM28 MIPI_DSI0_DATA0_N
BK28 MIPI_DSI0_DATA0_P
BM26 MIPI_DSI0_DATA1_N
BK26 MIPI_DSI0_DATA1_P
BN29 MIPI_DSI0_DATA2_N
BL29 MIPI_DSI0_DATA2_P
BN25 MIPI_DSI0_DATA3_N
BL25 MIPI_DSI0_DATA3_P
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BG31 MIPI_DSI1_CLK_P
BH32 MIPI_DSI1_DATA0_N
BG33 MIPI_DSI1_DATA0_P
BH28 MIPI_DSI1_DATA1_N
BG29 MIPI_DSI1_DATA1_P
BH34 MIPI_DSI1_DATA2_N
BG35 MIPI_DSI1_DATA2_P
BH26 MIPI_DSI1_DATA3_N
BG27 MIPI_DSI1_DATA3_P
E3 MLB_DATA4 MLB_DATA
4
E1 MLB_SIG MLB_SIG
D32 MLB_CLK_P5
E35 MLB_DATA_N5
F34 MLB_DATA_P5
E31 MLB_SIG_N5
D30 MLB_SIG_P5
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
D22 PCIE_REXT
M20 PCIE_SATA0_PHY_PLL_REF_RETURN
M28 PCIE0_PHY_PLL_REF_RETURN
N23 PCIE1_PHY_PLL_REF_RETURN
A19 PCIE_SATA0_RX0_P
C17 PCIE_SATA0_TX0_N
B16 PCIE_SATA0_TX0_P
B30 PCIE0_RX0_N
A29 PCIE0_RX0_P
C27 PCIE0_TX0_N
B26 PCIE0_TX0_P
B22 PCIE1_RX0_N
A21 PCIE1_RX0_P
C25 PCIE1_TX0_N
B24 PCIE1_TX0_P
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BL47 RTC_XTALO
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
BC45 SCU_BOOT_MODE1
BJ53 SCU_BOOT_MODE2
BA43 SCU_BOOT_MODE3
BE43 SNVS_TAMPER_IN1
BD46 SNVS_TAMPER_OUT0
BD42 SNVS_TAMPER_OUT1
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
B40 USB_OTG1_DP
A37 USB_OTG1_ID
A39 USB_OTG1_VBUS
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
B38 USB_OTG2_DP
F30 USB_OTG2_ID
E29 USB_OTG2_REXT
A35 USB_OTG2_VBUS
B34 USB_SS3_RX_N
C35 USB_SS3_RX_P
B32 USB_SS3_TX_N
A33 USB_SS3_TX_P
L9 USB_SS3_TC1 USB_SS3_TC1
F8 USB_SS3_TC2 USB_SS3_TC2
B4 USDHC1_VSELECT LSIO.GPIO4.IO07
Reset Condition
Ball
Ball Ball Name Power Domain
Type1 Default
Default function State2
mode
A7 USDHC2_VSELECT LSIO.GPIO4.IO10
BL49 XTALO
1 FASTD are GPIO balls configured for high speed operation using the FASTFRZ control.
2
Reset condition shown is before boot code execution. For pad changes after boot code execution, see the “System Boot” chapter of
the device reference manual,
3 HDMI-RX is not fully supported. See restrictions in Section 4.10.8.
4 MLB is not supported on this device. Users may choose alternate functions as determined by the IOMUX.
5 MLB is not supported on this device. Terminate these outputs per the Hardware Developer’s Guide for unused I/O signals.
The following table shows the DRAM pin function for the 29 x 29 mm package.
DDR_CHx_CK0_N Y50 Y4 CK_c_A The exact clock and control line connections will be
dependent on the memory configuration in use. Refer to
DDR_CHx_CK0_P W49 W5 CK_t_A the Hardware Developers Guide (HDG) for further details.
DDR_CHx_CK1_N AB50 AB4 CK_c_B
DDR_CHx_DCF02 Y48 Y6 —
DDR_CHx_DCF06 W45 W9 —
DDR_CHx_DCF07 W51 W3 —
DDR_CHx_DCF09 T52 T2 —
DDR_CHx_DCF13 T46 T8 —
DDR_CHx_DCF25 AF52 AF2 — The exact clock and control line connections will be
dependent on the memory configuration in use. Refer to
DDR_CHx_DCF26 AE47 AE7 CA3_B the Hardware Developers Guide (HDG) for further details.
DDR_CHx_DCF27 AE51 AE3 CA0_B
DDR_CHx_DM0 H52 H2 DMI[3..0] The exact mask, strobe and data connections to memory
are flexible as long as the correct byte mapping is used,
DDR_CHx_DM1 N47 N7 there is no restriction on the bit connections within each
DDR_CHx_DM2 AJ47 AJ7 byte.
DDR_CHx_DQ02 L47 L7
DDR_CHx_DQ03 K48 K6
DDR_CHx_DQ04 H50 H4
DDR_CHx_DQ05 G53 G1
DDR_CHx_DQ06 G51 G3
DDR_CHx_DQ08 L49 L5
DDR_CHx_DQ09 K50 K4
DDR_CHx_DQ10 N51 N3
DDR_CHx_DQ11 L51 L3
DDR_CHx_DQ12 P46 P8
DDR_CHx_DQ13 N49 N5
DDR_CHx_DQ14 P50 P4
DDR_CHx_DQ15 P48 P6
DDR_CHx_DQ20 AJ49 AJ5 DQ[31..0] The exact mask, strobe and data connections to memory
are flexible as long as the correct byte mapping is used,
DDR_CHx_DQ21 AH46 AH8 there is no restriction on the bit connections within each
DDR_CHx_DQ22 AH48 AH6 byte.
DDR_CHx_DQS1_N P52 P2
DDR_CHx_DQS1_P N53 N1
7 Release Notes
This table provides release notes for the data sheet.
Rev.
Date Substantive Change(s)
Number
3 11/2021 • Added HDMI Rx information to Table 1, "i.MX 8QuadPlus advanced features" and Table 4, "i.MX
8QuadPlus modules list".
• Updated the maximum value for the I/O Supply for GPIO Type 1.8 / 3.3V Dual Voltage Supply in Table 6,
"Absolute maximum ratings".
• Updated HDMI Rx footnote in Table 8, "Operating ranges".
• Added KS4 maximum values for VDD_GPU0 (1.0V) and VDD_GPU1 (1.0V), and updated total
maximum value in Table 11, "i.MX 8QuadPlus Key State (KSx) power consumption".
• Added footnote references to Low-Level input voltage in Table 30, Table 31, Table 32, Table 33, and
Table 34.
• Updated minimum and maximum values for Keeper Circuit Resistance in Table 35, "Single-voltage 1.8
V GPIO DC parameters" and Table 36, "Single-voltage 3.3 V GPIO DC parameters".
• Added reference to footnote on DC High-Level and DC Low-Level input voltages Table 38, "LPDDR4 DC
parameters".
• Corrected and rewrote Section 4.10.4.6, “Bus Operation Condition for 3.3 V and 1.8 V Signaling".
• Added Section 4.10.8, “HDMI Rx module".
• Corrected footnote 1 to PCIE Gen2 in Table 93, "PCIe receiver eye specifications for example
standards".
• Updated HDMI Rx footnote in Table 126, "29 x 29 mm power supplies contact assignments" and
Table 127, "29 × 29 mm functional contact assignments".
2 05/2021 • Clarified LVDS Tx port information in Table 1, "i.MX 8QuadPlus advanced features" under Display I/O.
• Updated Table 2, "i.MX 8QuadPlus Orderable part numbers" information.
• Updated the example in Section 1.2, “System Controller Firmware (SCFW) Requirements".
• Corrected document IDs in Table 3, "Related resources".
• Updated LVDS information and clarified KHz for XTAL OSC32K in Table 4, "i.MX 8QuadPlus modules
list".
• In Table 8, "Operating ranges", added min frequency for VDD_A72 and VDD_A53.
• Updated note in Section 4.1.5, “Maximum Supply Currents".
• Updated the value ranges in Table 26, "LVDS PHY PLL".
• Updated footnotes pointing to Section 4.6.2, “Input Signal Monotonic Requirements" in Table 30,
Table 31, Table 32, Table 33, Table 34, Table 35, and Table 36.
• Corrected test conditions in Table 38, "LPDDR4 DC parameters".
• Added Section 4.6.2, “Input Signal Monotonic Requirements".
• Corrected maximum frequency test conditions and footnotes 2 and 3 in Table 40, "General Purpose I/O
AC Parameters".
• In Table 81, "LVDS pins", updated single channel values.
• Updated PCI Express Gen 2 values for AOPENING and added footnote to Table 93, "PCIe receiver eye
specifications for example standards".
• Rewrote introductory paragraph for Section 5.1, “Boot mode configuration inputs".
• Clarified QSPI information in Table 125, "Interface allocation during boot".
• Corrected default function for Ball AP46 in Table 127, "29 × 29 mm functional contact assignments".
• Corrected x=0 column value for DDR_CHx_DTO1 in Table 128, "29 x 29 mm DRAM pin function".
Legal information
Objective [short] data sheet Development This document contains data from the objective specification for product
development.
Preliminary [short] data sheet Qualification This document contains data from the preliminary specification.
Product [short] data sheet Production This document contains the product specification.
[1] Please consult the most recently issued document before initiating or completing a design.
[2] The term 'short data sheet' is explained in section "Definitions".
[3] The product status of device(s) described in this document may have changed since this document was published and may differ in case of multiple devices.
The latest product status information is available on the Internet at URL http://www.nxp.com.
Definitions Disclaimers
Draft — A draft status on a document indicates that the content is still Limited warranty and liability — Information in this document is believed
under internal review and subject to formal approval, which may result to be accurate and reliable. However, NXP Semiconductors does not give
in modifications or additions. NXP Semiconductors does not give any any representations or warranties, expressed or implied, as to the accuracy
representations or warranties as to the accuracy or completeness of or completeness of such information and shall have no liability for the
information included in a draft version of a document and shall have no consequences of use of such information. NXP Semiconductors takes no
liability for the consequences of use of such information. responsibility for the content in this document if provided by an information
source outside of NXP Semiconductors.
Short data sheet — A short data sheet is an extract from a full data sheet with
In no event shall NXP Semiconductors be liable for any indirect, incidental,
the same product type number(s) and title. A short data sheet is intended for
punitive, special or consequential damages (including - without limitation -
quick reference only and should not be relied upon to contain detailed and full
lost profits, lost savings, business interruption, costs related to the removal or
information. For detailed and full information see the relevant full data sheet,
replacement of any products or rework charges) whether or not such damages
which is available on request via the local NXP Semiconductors sales office.
are based on tort (including negligence), warranty, breach of contract or any
In case of any inconsistency or conflict with the short data sheet, the full data
other legal theory.
sheet shall prevail.
Notwithstanding any damages that customer might incur for any reason
Product specification — The information and data provided in a Product data whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards
sheet shall define the specification of the product as agreed between NXP customer for the products described herein shall be limited in accordance with
Semiconductors and its customer, unless NXP Semiconductors and customer the Terms and conditions of commercial sale of NXP Semiconductors.
have explicitly agreed otherwise in writing. In no event however, shall an
agreement be valid in which the NXP Semiconductors product is deemed to Right to make changes — NXP Semiconductors reserves the right to make
offer functions and qualities beyond those described in the Product data sheet. changes to information published in this document, including without limitation
specifications and product descriptions, at any time and without notice. This
document supersedes and replaces all information supplied prior to the
publication hereof.
Applications — Applications that are described herein for any of these Suitability for use in automotive applications — This NXP product has been
products are for illustrative purposes only. NXP Semiconductors makes no qualified for use in automotive applications. If this product is used by customer
representation or warranty that such applications will be suitable for the in the development of, or for incorporation into, products or services (a)
specified use without further testing or modification. used in safety critical applications or (b) in which failure could lead to death,
personal injury, or severe physical or environmental damage (such products
Customers are responsible for the design and operation of their applications
and services hereinafter referred to as “Critical Applications”), then customer
and products using NXP Semiconductors products, and NXP Semiconductors
makes the ultimate design decisions regarding its products and is solely
accepts no liability for any assistance with applications or customer product
responsible for compliance with all legal, regulatory, safety, and security
design. It is customer’s sole responsibility to determine whether the NXP
related requirements concerning its products, regardless of any information
Semiconductors product is suitable and fit for the customer’s applications and
or support that may be provided by NXP. As such, customer assumes all risk
products planned, as well as for the planned application and use of customer’s
related to use of any products in Critical Applications and NXP and its suppliers
third party customer(s). Customers should provide appropriate design and
shall not be liable for any such use by customer. Accordingly, customer will
operating safeguards to minimize the risks associated with their applications
indemnify and hold NXP harmless from any claims, liabilities, damages and
and products.
associated costs and expenses (including attorneys’ fees) that NXP may incur
NXP Semiconductors does not accept any liability related to any default,
related to customer’s incorporation of any product in a Critical Application.
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 Quick reference data — The Quick reference data is an extract of the product
third party customer(s). Customer is responsible for doing all necessary testing data given in the Limiting values and Characteristics sections of this document,
for the customer’s applications and products using NXP Semiconductors and as such is not complete, exhaustive or legally binding.
products in order to avoid a default of the applications and the products or of the
application or use by customer’s third party customer(s). NXP does not accept Export control — This document as well as the item(s) described herein may be
any liability in this respect. subject to export control regulations. Export might require a prior authorization
from competent authorities.
Limiting values — Stress above one or more limiting values (as defined in
the Absolute Maximum Ratings System of IEC 60134) will cause permanent Evaluation products — This product is provided on an “as is” and “with
damage to the device. Limiting values are stress ratings only and (proper) all faults” basis for evaluation purposes only. NXP Semiconductors, its
operation of the device at these or any other conditions above those affiliates and their suppliers expressly disclaim all warranties, whether express,
given in the Recommended operating conditions section (if present) or the implied or statutory, including but not limited to the implied warranties of
Characteristics sections of this document is not warranted. Constant or non-infringement, merchantability and fitness for a particular purpose. The
repeated exposure to limiting values will permanently and irreversibly affect the entire risk as to the quality, or arising out of the use or performance, of this
Customer shall select products with security features that best meet rules,
regulations, and standards of the intended application and make the
ultimate design decisions regarding its products and is solely responsible
for compliance with all legal, regulatory, and security related requirements
concerning its products, regardless of any information or support that may be
provided by NXP.
Trademarks
Notice: All referenced brands, product names, service names, and
trademarks are the property of their respective owners.