The i.MX RT500 is a family of dual-core microcontrollers for
embedded applications featuring an Arm Cortex-M33 CPU
combined with a Cadence® Xtensa® Fusion F1 Audio Digital
Signal Processor CPU. The Cortex-M33 includes two hardware
coprocessors providing enhanced performance for an array of
complex algorithms along with a 2D Vector GPU with LCD
Interface and MIPI DSI PHY. The family offers a rich set of
peripherals and very low power consumption. The device has up
to 5 MB SRAM, two FlexSPIs (Octal/Quad SPI Interfaces) each
with 32 KB cache, one with dynamic decryption, high-speed USB
device/host + PHY, 12-bit 1 MS/s ADC, Analog Comparator,
Audio subsystems supporting up to 8 DMIC channels, 2D GPU
and LCD Controller with MIPI DSI PHY, SDIO/eMMC; FlexIO;
AES/SHA/Crypto M33 coprocessor and PUF key generation
Control processor core
• Arm Cortex-M33 processor, running at frequencies of
up to 200 MHz
• Arm TrustZone
• Arm Cortex-M33 built-in Memory Protection Unit (MPU)
supporting eight regions
• Single-precision Hardware Floating Point Unit (FPU).
• Arm Cortex-M33 built-in Nested Vectored Interrupt
Controller (NVIC).
• Non-maskable Interrupt (NMI) input.
• Two coprocessors for the Cortex-M33: a hardware
accelerator for fixed and floating point DSP functions
(PowerQuad) and a Crypto/FFT engine (Casper). The
DSP coprocessor uses a bank of four dedicated 2 KB
SRAMs. The Crypto/FFT engine uses a bank of two 2
KB SRAMs that are also AHB accessible by the CPU
and the DMA engine.
• Serial Wire Debug with eight break points, four watch
points, and a debug timestamp counter. It includes
Serial Wire Output (SWO) trace and ETM trace.
• Cortex-M33 System tick timer
DSP processor core
• Cadence Tensilica Fusion F1 DSP processor, running
at frequencies of up to 200 MHz.
• Hardware Floating Point Unit.
• Serial Wire Debug (shared with Cortex-M33 Control
Domain CPU).
Communication interface
• 9 configurable universal serial interface modules
(Flexcomm Interfaces). Each module contains an
integrated FIFO and DMA support. Each of the nine
modules can be configured as:
• Two additional high-speed SPI interfaces supporting
50 MHz operation
• One additional I2C interface with open-drain pads
• Two I3C bus interfaces
• A digital microphone interface supporting up to 8
channels with associated decimators and Voice
MIMXRT5XXSFFOC
MIMXRT5XXSFFOCR
MIMXRT5XXSFAWCR
249 FOWLP 7.0mm x
7.0mm x 0.725mm,
0.4mm pitch
• A USART with dedicated fractional baud rate
generation and flow-control handshaking
signals. The USART can optionally be clocked
at 32 kHz and operated when the chip is in
reduced power mode, using either the 32 kHz
clock or an externally supplied clock. The
USART also provides partial support for
LIN2.2.
• An I2C-bus interface with multiple address
recognition, and a monitor mode. It supports
400 Kb/sec Fast-mode and 1 Mb/sec Fastmode Plus. It also supports 3.4 Mb/sec highspeed when operating in slave mode.
• An SPI interface.
• An I2S (Inter-IC Sound) interface for digital
audio input or output. Each I2S supports up to
four channel-pairs.
141 WLCSP 4.525mm
x 4.525mm x 0.49mm,
0.35mm pitch
NXP reserves the right to change the production detail specifications as may be
required to permit improvements in the design of its products.
Five I/O Power Rails
• Five independent supplies powering different clusters
of pins to permit interfacing directly to off-chip
peripherals operating at different supply levels.
On-chip memory
• Up to 5 MB of system SRAM accessible by both CPUs,
both DMA engines, the Graphics Subsystem and all
other AHB masters.
• Additional SRAMs for USB traffic (16 KB), Cortex-M33
co-processors (4 x 2 KB), SDIO FIFOs (2 x 512 B dualport), PUF secure key generation (2 KB), FlexSPI
caches (32 KB each), SmartDMA commands (32 KB),
and a variety of dual and single port RAMs for
graphics.
• 16 kbits OTP fuses
• Up to 192 KB ROM memory for factory-programmed
drivers and APIs
• System boot from High-speed SPI, FlexSPI Flash, HS
USB, I2C, UART or eMMC via on-chip bootloader
software included in ROM. FlexSPI boot mode will
include an option for Execute-in-place start-up for nonsecure boot.
Digital peripherals
• Two general purpose DMA engines, each with 37
channels and up to 27 programmable request/trigger
sources.
• Can be configured such that one DMA is secure
and the other non-secure and/or one can be
designated for use by the M33 CPU and the
other by the DSP
• Smart DMA Controller with dedicated 32KB code RAM
• USB high-speed host/device controller with on-chip
PHY and dedicated DMA controller.
• Two FlexSPI (Octal/Quad) Interfaces up to 200 MHz
DDR/SDR (target). 32 KB caches with selectable
cache policies based on programmable address
regions. One of the FlexSPI interface will include onthe-fly decryption for execute-in-place and addressremapping to support dual-image boot. DMA supported
(both modules).
• Two SD/eMMC memory card interfaces with dedicated
DMA controllers. One supports eMMC 5.0 with
HS400/DDR operation.
Analog peripherals
• One 12-bit ADC with sampling rates of 1 Msamples/sec
and an enhanced ADC controller. It supports up to 10
single-ended channels or 5 differential channels. The
ADC supports DMA.
• Temperature sensor.
• Analog comparator
Activation Detect. One pair of channels can be
streamed directly to I2S. The DMIC supports DMA.
Timers
• One 32-bit SCTimer/PWM module (SCT). Multipurpose timer with extensive event-generation,
match/compare, and complex PWM and output
control features.
• It supports DMA and can trigger external DMA
events
• It supports fractional match values for high
resolution
• Five general purpose, 32-bit timer/counter modules
with PWM capability
• 24-bit multi-rate timer module with 4 channels each
capable of generating repetitive interrupts at
different, programmable frequencies.
• Two Windowed Watchdog Timers (WDT) with
dedicated watchdog oscillator (1 MHz LPOSC)
• Frequency measurement module to determine the
frequency of a selection of on-chip or off-chip clock
sources.
• Real-Time Clock (RTC) with independent power
supply and dedicated oscillator. Integrated wake-up
timer can be used to wake the device up from lowpower modes. The RTC resides in the “always-on”
voltage domain. RTC includes eight 32-bit generalpurpose registers which can retain contents when
power is removed from the rest of the chip.
• Ultra-low power micro-tick Timer running from the
Watchdog oscillator with capture capability for
timestamping. Can be used to wake up the device
from low-power modes.
• 64-bit OS/Event Timer common to both processors
with individual match/capture and interrupt
generation logic. Enabled on POR
Clocks
• Crystal oscillator with an operating range of 4 MHz
to 26 MHz.
• Dual trim option: Internal 192/96 MHz FRO
oscillator. Trimmed to 1% accuracy.
• FRO capable of being tuned using an accurate
reference clock (eg. XTAL Osc) to 0.1% accuracy
with 46% duty cycle to support MIPI PHY and
FlexSPI.
• Internal 1 MHz low-power oscillator with 5%
accuracy. Serves as the watchdog oscillator and
clock for the OS/Event Timer and the Systick among
others. Also available as the system clock to both
domains.
• 32 kHz real-time clock (RTC) oscillator that can
optionally be used as a system clock.
• Main System PLL:
• allows CPU operation up to the maximum rate
without the need for a high-frequency crystal.
• 2D Vector Graphics Processing Unit, running at
frequencies of up to 200 MHz.
• LCD Display Interface supporting smart LCD displays
and video mode.
• MIPI DSI Interface with on-chip PHY supporting
transfer rates up to 895.1 Mbps.
• FlexIO can be configured to provide a parallel interface
to an LCD
I/O Peripherals
• Up to 136 general purpose I/O (GPIO) pins with
configurable pull-up/pull-down resistors. Ports can be
written as words, half-words, bytes, or bits.
• Mirrored, secure GPIO0.
• Individual GPIO pins can be used as edge and level
sensitive interrupt sources, each with its own interrupt
vector.
• All GPIO pins can contribute to one of two ganged
(OR’d) interrupts from the GPIO_HS module.
• A group of up to 7 GPIO pins (from Port0/1) can be
selected for Boolean pattern matching which can
generate interrupts and/or drive a “pattern-match”
output.
• Adjustable output driver slew rates.
• JTAG boundary scan
Security
• Secure Isolation: Protection from software and remote
attacks using Trustzone for armV8M. Hardware
isolation of AES keys
• Secure Boot: firmware in ROM providing immutable
root of trust
• Secure Storage: Physically Unclonable Function
(PUF) based key store, On-the-fly-AES decryption
(OTFAD) of off-chip flash for code storage
• Secure Debug: Certificate based debug authentication
mechanism
• Secure Loader: Supports firmware update mechanism
with authenticity (RSA signed) and confidentiality
(AES-CTR encrypted) protection
• Symmetric cryptography (AES) with
128/192/256-bit key strength and protection
against Side-channel analysis (Differential Power
Analysis and Template attacks)
• Asymmetric cryptography acceleration using
CASPER co-processor
• NIST SP 800-90b compliant TRNG design with
512-bit output per call
• Hash engine with SHA-256 and SHA1
May be run from the FRO, the crystal
oscillator or the CLKIN pin.
• a second, independent PLL output provides
alternate high-frequency clock source for the
DSP CPU if the required frequency is different
from the main system clock. (Note: 2nd PFD
output from Main System PLL)
• two additional PLL outputs provide potential
clock sources to various peripherals.
• Audio PLL for the audio subsystem.
Power Control
• Main external power supply: 1.8V ± 5%
• Vddcore supply (from PMIC or internal PMU):
adjustable from 0.6 V to 1.1 V (including retention
mode)
• Analog supply: 1.71-3.6 V
• Five VDDIO supplies (can be shared or
independent): 1.71 - 3.6 V
• USB Supply: 3.0-3.6 V
• Reduced power modes:
• Sleep mode: CPU clock shut down (each CPU
independently)
• Deep_sleep mode: User-selectable
configuration via PDSLEEPCFG
• Deep_powerdown mode: Internal power
removed from entire chip except “always-on”
domain
• Each individual SRAM partition can be
independently powered-off or put into a lowpower retain mode
• DSP Domain can be powered-off
independently from the rest of the system.
• Ability to operate the synchronous serial
interfaces in sleep or deep-sleep as a slave or
USART clocked by the 32 kHz RTC oscillator
• Wake-up from low-power modes via interrupts
from various peripherals including the RTC
and the OS/Event timer
• RBB/FBB to provide additional control over power/
performance trade-offs
description of the structure and function (operation) of a device.
Data SheetRefers to this document which includes electrical characteristics and signal connections.
Chip ErrataThe chip mask set Errata provides additional or corrective information for a particular device mask
This section provides the device-level electrical characteristics for the IC. See the
following table for a quick reference to the individual tables and sections.
Table 1. i.MX RT500 chip-level conditions
For these charateristicsTopic appears
Absolute maximum voltage and current ratingsAbsolute maximum voltage and current ratings
Thermal handling ratingsThermal handling ratings
Moisture handling ratingsMoisture handling ratings
ESD handling ratingsESD handling ratings
Thermal characteristicsThermal characteristics
General operating conditionsGeneral operating conditions
I/O parametersI/O parameters
Power consumption operating behaviorPower consumption operating behavior
1.1.1Thermal handling ratings
SymbolDescriptionMin.Max.UnitNotes
T
STG
T
SDR
1. Determined according to JEDEC Standard JESD22-A103, High Temperature Storage Life.
2. Determined according to IPC/JEDEC Standard J-STD-020, Moisture/Reflow Sensitivity Classification for NonhermeticSolid State Surface Mount Devices.
1. Determined according to JEDEC Standard JESD22-A114, Electrostatic Discharge (ESD) Sensitivity Testing HumanBody Model (HBM).
2. Determined according to JEDEC Standard JESD22-C101, Field-Induced Charged-Device Model Test Method forElectrostatic-Discharge-Withstand Thresholds of Microelectronic Components.
3. Determined according to JEDEC Standard JESD78, IC Latch-Up Test.
Electrostatic discharge voltage, human body model-20002000V1
Electrostatic discharge voltage, charged-device
model
Latch-up current at ambient temperature of 70 °C-100100mA3
-500500V2
1.1.4Absolute maximum voltage and current ratings
Stress beyond those listed under the following table may
cause permanent damage to the device. These are stress
ratings only. Functional operation of the device at these or
any other conditions beyond those indicated under
“recommended operating conditions” is not implied.
Exposure to absolute-maximum-rated conditions for
extended periods may affect device reliability.
Table 2. Absolute maximum ratings1
SymbolParameterConditionsNotesMin.Max.Unit
VDD_AO1V8Supply 1.8 V
supply for
“always on”
features
VDD1V81.8 V supply
voltage for onchip analog
functions
other than the
ADC and
comparator.
based on
package heat
transfer, not
device power
consumption
WLCSP141-1.42W
Thermal specifications
3-100mA
3-100mA
-100mA
4-1.86W
1. In accordance with the Absolute Maximum Rating System (IEC 60134). The following applies to the limiting values:
• This product includes circuitry specifically designed for the protection of its internal devices from the damaging
effects of excessive static charge. Nonetheless, it is suggested that conventional precautions be taken to avoid
applying greater than the rated maximum.
• Parameters are valid over operating temperature range unless otherwise specified. All voltages are with respect
to VSS unless otherwise noted.
• The limiting values are stress ratings only and operating the part at these values is not recommended and
proper operation is not guaranteed. The conditions for functional operation are specified in Table 1.
2. Maximum/minimum voltage above the maximum operating voltage (see Table 1) and below ground that can be
applied for a short time (< 10 ms) to a device without leading to irrecoverable failure. Failure includes the loss of
reliability and shorter lifetime of the device.
3. The peak current should not exceed the total supply current.
4. Determined in accordance to JEDEC JESD51-2A natural convection environment (still air).
1.1.5
1.1.5.1
Thermal specifications
Thermal operating requirements
Table 3. Thermal operating requirements
SymbolDescriptionMin.Max.UnitNotes
T
j
T
A
Die junction
temperature
Ambient
temperature
-20105°C1
-2070°C1
1. Maximum TA can be exceeded only if the user ensures that TJ does not exceed maximum TJ. The simplest method to
determine TJ is: TJ = TA + R
The average chip junction temperature, Tj (°C), can be calculated using the following
equation:
(1)
• T
• R
= ambient temperature (°C),
amb
= the package junction-to-ambient thermal resistance (°C/W)
th(j-a)
• PD = sum of internal and I/O power dissipation
The internal power dissipation is the product of IDD and VDD. The I/O power dissipation
of the I/O pins is often small and many times can be negligible. However it can be
significant in some applications.
Table 4. Thermal resistance1
SymbolParameterConditionsMax/MinUnit
249 FOWLP Package
R
R
R
R
th(j-a)
Ψ(JT)
th(j-a)
Ψ(JT)
thermal resistance from
junction to ambient
thermal resistance from
junction to package top
thermal resistance from
junction to ambient
thermal resistance from
junction to package top
JESD51-9, 2s2p, still
air
JESD51-9, 2s2p, still
air
141 WCLSP Package
JESD51-9, 2s2p, still
air
JESD51-9, 2s2p, still
air
29.6°C/W
0.2°C/W
35.3°C/W
0.1°C/W
1. Determined in accordance to JEDEC JESD51-2A natural convection environment (still air). Thermal resistance data in
this report is solely for a thermal performance comparison of one package to another in a standardized specified
environment. It is not meant to predict the performance of a package in an application-specific environment
1. Typical ratings are not guaranteed. The values listed are for room temperature (25 °C), nominal supply voltages.
2. 1.8 V supply voltage for on-chip digital logic during active mode. In deep-sleep mode, this pin can be powered off to
conserve additional current (~20 uA).
3. The maximum frequency for the specified VDDCORE voltage is the frequency of the main clock. This is before the CPU
CLOCK Divider. The VDDCORE voltage has to be set according to the chosen main clock frequency.
4. When LDO_ENABLE is externally tied low, the user must boot at VDDCORE = 1.0 V or higher (Low power/Normal clock
mode - OTP setting - BOOT_CLK_SPEED) or VDDCORE = 1.13 V (High Speed clock - OTP setting BOOT_CLK_SPEED). Thereafter, the VDDCORE can be adjusted to the desired level.
5. When LDO_ENABLE is externally tied high, the on-chip regulator to the VDDCORE Core voltage in PMC is set to the
default value 1.05 V (Low power/Normal clock mode - OTP setting - BOOT_CLK_SPEED) or 1.13 V (High Speed clock OTP setting - BOOT_CLK_SPEED). Thereafter, the POWER_SetLdoVoltageForFreq API function can be used to
internally configure the on-chip regulator voltage to the VDDCORE.
6. When performing any OTP read/write function, the VDDCORE voltage must be set to 1.0 V or higher when
LDO_ENABLE is externally tied high or low.
7. GPU, SPI, and CTIMER are disabled.
8. Although i.MX RT500 is targeted to operate up to 200 MHz for low power operation, it can operate up to 275 MHz;
however, there will be an increase in current consumption.
9. VDD_BIAS must be equal to maximum ADC input voltage or maximum comparator input voltage.
10. The USB PHY provides two options for reporting VBUS valid back to the USB controller:
• A programmable internal VBUS_VALID comparator (the default option), or
• An alternate VBUS_VALID_3V detector that will report VBUS valid for voltages above 3 V
USBPHY_USB1_VBUS_DETECTn[VBUSVALID_SEL] selects which option is used. If the VBUS_VALID comparator is
used, USBPHY_USB1_VBUS_DETECTn[VBUSVALID_THRESH] determines the threshold voltage for a valid VBUS.
The programmable range is 4.0V to 4.4V (default).
11. The USB PHY provides two options for reporting VBUS valid back to the USB controller:
• A programmable internal VBUS_VALID comparator (the default option), or
• An alternate VBUS_VALID_3V detector that will report VBUS valid for voltages above 3 V
USBPHY_USB1_VBUS_DETECTn[VBUSVALID_SEL] selects which option is used. If the VBUS_VALID_3V detector
is used, the detector voltage is not programmable.
1.1.7I/O parameters
1.1.7.1I/O DC parameters
T
= -20 °C to +70 °C, unless otherwise specified. Values tested in production unless otherwise specified.
3. All GPIO pins are fail safe up to 3.6 V when VDDIO supply = 0 V except following pins: PIO1_18 to PIO1_29, PIO1_30
to PIO1_31, PIO2_0 to PIO2_8, PIO2_24 to PIO2_31, PIO3_8 to PIO3_18, PIO4_11 to PIO4_17, and PIO5_15 to
PIO5_18.
4. Based on characterization. Not tested in production.
1.1.8Power consumption operating behavior
NOTE
For the lowest power consumption, use the lowest SRAM
partition number.
T
= -20 °C to +70 °C, unless otherwise specified.
amb
Table 7. Power consumption in active mode
SymbolParameterConditionsNotesMin.Typ.1,
Cortex M33 in Active mode, DSP no clock
enhanced while (1) code executed from SRAM partition 305; Internal LDO disabled
I
DDVDDCORE
VDDCORE supply
current
HCLK = 12 MHz
VDDCORE = 0.7 V
HCLK = 24 MHz
VDDCORE = 0.7 V
HCLK = 48 MHz
VDDCORE = 0.7 V
HCLK = 96 MHz
VDDCORE = 0.8 V
HCLK = 192 MHz
VDDCORE = 0.9 V
HCLK = 192 MHz
VDDCORE = 1.0 V
HCLK = 192 MHz
VDDCORE = 1.1 V
4
6-1.62-mA
6-2.50-mA
6-4.33-mA
6-9.35-mA
6-20.73-mA
6-23.97-mA
6-28.01-mA
2, 3
Max.Unit
1. Typical ratings are not guaranteed. Typical values listed are at room temperature (25 °C). VDD_AO1V8 = VDD1V8 =
VDDIO_0/1/2/3/4 = VDDA_ADC1V8 = 1.8 V. VDDA_BIAS = VREFP = 1.8 V. USB1_VDD3V3 = 3.3
2. Characterized through bench measurements using typical samples.
3. Compiler settings: IAR C/C++ Compiler for Arm ver 8.40.1. High, Speed, No Size Constraints. The optimization level is
Low, Balanced.
4. Based on the power API library from the SDK software package available on nxp.com
5. SRAM partition 30 represents the worst case partition.
Cortex M33 in Active mode, DSP no clock
CoreMark code executed from SRAM partition 30
I
DDVDDCORE
VDDCORE supply
current
HCLK = 12 MHz
VDDCORE = 0.7 V
HCLK = 24 MHz
4
5
-1.61-mA
-2.51-mA
VDDCORE = 0.7 V
HCLK = 48 MHz
-4.26-mA
VDDCORE = 0.7 V
HCLK = 96 MHz
-9.28-mA
VDDCORE = 0.8 V
HCLK = 192 MHz
-20.44-mA
VDDCORE = 0.9 V
HCLK = 192 MHz
-23.73-mA
VDDCORE = 1.0 V
HCLK = 192 MHz
-27.87-mA
VDDCORE = 1.1 V
1. Typical ratings are not guaranteed. Typical values listed are at room temperature (25 °C). VDD_AO1V8 = VDD1V8 =
VDDIO_0/1/2/3/4 = VDDA_ADC1V8 = 1.8 V. VDDA_BIAS = VREFP = 1.8 V. USB1_VDD3V3 = 3.3 V
2. Characterized through bench measurements using typical samples.
3. Compiler settings: IAR C/C++ Compiler for Arm ver 8.40. High Speed, No Size constraints. The optimization level is
Low, Balanced.
4. Based on the power API library from the SDK software package available on nxp.com
5. SRAM partition 30 represents the worst case partition.
T
= -20 °C to +70 °C, unless otherwise specified.
amb
Table 9. Power consumption in active mode
SymbolParameterConditionsNotesMinTyp1, 2,
FFT code executed from SRAM partition 30 and 314; Internal LDO disabled
DSP in Active mode, M33 in WFI
Table 9. Power consumption in active mode (continued)
SymbolParameterConditionsNotesMinTyp1, 2,
VDDCORE = 0.8 V
HCLK = 100 MHz
6-10.74-mA
VDDCORE = 0.8 V
HCLK = 150 MHz
6-17.81-mA
VDDCORE = 0.9 V
HCLK = 200 MHz
6-22.94-mA
VDDCORE = 0.9 V
1. Typical ratings are not guaranteed. Typical values listed are at room temperature (25 °C). VDD_AO1V8 = VDD1V8 =
VDDIO_0/1/2/3/4 = VDDA_ADC1V8 = 1.8 V. VDDA_BIAS = VREFP = 1.8 V. USB1_VDD3V3 = 3.3 V
2. Characterized through bench measurements using typical samples.
3. Compiler settings: IAR C/C++ Compiler for Arm ver 8.40. High Speed, No Size constraints. The optimization level is
Low, Balanced.
4. SRAM partitions 30 and 31 represent the worst case partitions. The Fusion F1 DSP requires DRAM and IRAM in
different partitions. DSP_DRAM is in partition 30, DSP_IRAM is in partition 31.
5. Based on the power API library from the SDK software package available on nxp.com
6. PLL clock source, FBB enabled
3
MaxUnit
Table 10. Power consumption in sleep mode
SymbolParameterConditionsNotesMin.Typ.Max.Unit
Cortex-M33 in Sleep mode, DSP no clock
I
DDVDDCORE
supply
current
HCLK=12 MHz
VDDCORE=0.7 V
HCLK=12 MHz
VDDCORE=1.0 V
HCLK=24 MHz
VDDCORE=1.0 V
HCLK=48 MHz
VDDCORE=1.0 V
HCLK=96 MHz
VDDCORE=1.0 V
HCLK=192 MHz
VDDCORE=0.9 V
HCLK=192 MHz
VDDCORE=1.0 V
Following power-on sequence should be followed when using the internal LDO in i.MX
RT500:
1. VDD_AO1V8, VDD1V8, and VDD1V8_1 pins should be powered first. There is
no power sequence requirement between powering the VDD_AO1V8 and
VDD1V8 pins.
2. VDDA_ADC1V8 and VREFP can be powered concurrently with VDD_AO1V8
and VDD1V8 or later
3. VDDIO_x and VDDA_BIAS pins can be powered concurrently with
VDD_AO1V8 and VDD1V8 if these pins are 1.8 V range or later if these pins are
3.3 V range. If the VDDIO_x is not powered concurrently with the VDD1V8, the
delta voltage between VDDIO_x and VDD1V8 must be 1.89 V or less.
The VDDCORE pin will be supplied from the internal LDO and the LDO is powered
from the VDD1V8. An external capacitor (4.7 uF) must be connected on the
VDDCORE pin. USB1_VDD3V3 can be powered at any time, independent of the other
supplies.
Following power-on sequence should be followed when using an external PMIC or
external IC to drive the VDDCORE pin (internal LDO is disabled, see timing diagram
below):
1. VDD_AO1V8, VDD1V8, and VDD1V8_1 pins should be powered first. There is
no power sequence requirement between powering the VDD_AO1V8 and
VDD1V8 pins.
2. VDDA_ADC1V8 and VREFP can be powered concurrently with VDD_AO1V8
and VDD1V8 or later.
3. VDDIO_x and VDDA_BIAS pins can be powered concurrently with VDD1V8 if
these pins are 1.8 V range or later if these pins are 3.3 V range. If the VDDIO_x
is not powered concurrently with the VDD1V8, the delta voltage between
VDDIO_x and VDD1V8 must be 1.89 V or less.
4. Power up the VDDCORE. The external RESETN should be held low until
VDDCORE is valid in the timing diagram.VDDCORE should not be ramped up
until after all the other supplies have completed ramp up.
USB1_VDD3V3 can be powered at any time, independent of the other supplies.
Sequence of operations is handled internally so there is no specific timing requirement
between the supplies. The time delays caused by any of the bypass capacitors will
have no effect on the operation of the part. The internal POR detectors on
VDD_AO1V8, VDD1V8 pins, and the Low Voltage Detector on VDDCORE pin,
require a fall time of at least 10us (preliminary) to trigger. There is no restriction on
the rise time, except for the sequencing defined above.
Table 15. Power-on characteristics
SymbolTiming
Parameter
AVDDIO_x valid to
VDDCORE valid
BVDDCORE valid to
De-assertion of
RESETN
AAMode pin validWhen the mode
DescriptionMin.Max.Unit
The delay from
when the IO pad
voltages become
valid to core
voltage valid
The delay from
when the VDD
core is valid to
when the RESETN
can be released
pins becomes
valid. On power-
on, the mode pins
are reset to 00 and
are controlled via a
• JTAG20—20—ns
J4TCLK rise and fall times—3—3ns
J5Boundary scan input data setup time to TCLK
rise
J6Boundary scan input data hold time after TCLK
rise
J7TCLK low to boundary scan output data valid—28—28ns
J8TCLK low to boundary scan output high-Z—25—25ns
J9TMS, TDI input data setup time to TCLK rise10.5—19—ns
J10TMS, TDI input data hold time after TCLK rise2.5—2—ns
J11TCLK low to TDO data valid—19—19ns
J12TCLK low to TDO high-Z2—2—ns
J13TRST assert time100—100—ns
J14TRST setup time (negation) to TCLK high8—8—ns
Table 25. Typical wake-up times from low power modes
SymbolParameterConditionsNotesMin.Typ.
t
wake
t
wake
t
wake
wake-up time from sleep
mode, 200
MHz
wake-up time from deep-
sleep mode,
using
RESETN.
from deepsleep mode,
using
PMIC_IRQ_N
.
wake-up time from full deep
power-down
mode, using
RESETN
from full deep
power-down
mode, using
PMIC_IRQ_N
2, 3-150-μs
4-120-μs
4-120-μs
4-8.64-ms
4-8.64-ms
1
Max.Unit
1. Typical ratings are not guaranteed. The values listed are at room temperature (25 C), nominal supply voltages.
2. The wake-up time measured is the time between when a GPIO input pin is triggered to wake the device up from the low
power modes and from when a GPIO output pin is set in the interrupt service routine (ISR) wake-up handler.
3. FRO disbled, all peripherals off. PLL disabled.
4. Wake up from deep power-down causes the part to go through entire reset process. The wake-up time measured is the
time between when the Wake-Up pin is triggered to wake the device up and when a GPIO output pin is set in the reset
handler.
Tamb = -20 °C to +70 °C, VDDIO_x = 1.71 V to 1.89 V; VDDCORE = 1.13 V; CL =
5 pF balanced loading on all pins; Full Drive Mode on all pins, Input slew = 1 ns,
SLEW setting = standard mode for all pins; Parameters sampled at the 50 % level of
the rising or falling edge.
= -20 °C to 70 °C; VDD = 2.7 V to 3.6 V; CL = 30 pF. Simulated values.
amb
Table 27. LCDIF characteristics
SymbolParameterConditionsMin.Typ.Max.Unit
f
t
v(Q)
clk
clock frequencyon pin LCD_DCLK--60MHz
data output valid timeon all LCD output pins0.3-4.5ns
1.5.2MIPI DSI timing
The i.MX RT500 conforms to the MIPI D-PHY electrical specifications MIPI DSI
Version 1.01 and D-PHY specification Rev. 1.0 (and also DPI version 2.0, DBI version
2.0, DSC version 1.0a at protocol layer) for MIPI display port x2 lanes.
1. Typical ratings are not guaranteed. The values listed are at room temperature (25 °C), nominal supply voltages.
2. CADIN represents the external capacitance on the analog input channel for sampling speeds of 1.0 Msamples/s. No
parasitic capacitances included.
3. This resistance is external to the MCU. To achieve the best results, the analog source resistance must be kept as low
possible. The results in this data sheet were derived from a system that had less than 15 Ω analog source resistance.
See Figure 1
4. Based on characterization; not tested in production.
5. The differential linearity error (ED) is the difference between the actual step width and the ideal step width. See Figure 1.
6. The integral non-linearity (EL
) is the peak difference between the center of the steps of the actual and the ideal
(adj)
transfer curve after appropriate adjustment of gain and offset errors. See Figure 1.
7. The offset error (EO) is the absolute difference between the straight line which fits the actual curve and the straight line
which fits the ideal curve. See Figure 1.
8. The full-scale error voltage or gain error (EG) is the difference between the straight-line fitting the actual transfer curve
after removing offset error, and the straight line which fits the ideal transfer curve. See Figure 1.
Table 30. Temperature sensor static and dynamic characteristics
(VDDA_BIAS = 3.3 V, All other supplies = 1.8 V)
SymbolParameterConditionsNotesMinTypMaxUnit
DT
sen
E
L
1. Absolute temperature accuracy. Based on characterization. Not tested in production
Table 31. Temperature sensor Linear-Least-Square (LLS) fit parameters
Fit parameterConditionsNotesMinTypMaxUnit
LLS slopeT
LLS intercept at
0° C
LLS intercept at
25 °C
sensor
temperature
accuracy
linearity error Tamb = -20
T
= -20 °C
amb
to 70 °C
°C to 70 °C
1--2.77°C
--2.79°C
(VDDA_BIAS = 3.3 V, All other supplies = 1.8 V)
= -20 °C to
amb
70 °C
Tamb = -20 °C
to 70 °C
Tamb = -20 °C
to 70 °C
1, 2--1.5738-mV/°C
1, 2-809.55-mV
1, 2-770.4-mV
1. Based on characterization, Not tested in production.
2. Equation: Temp = 25 - ((Vtemp -Vtemp25)/m) Where: VTEMP is the voltage of the temperature sensor channel at the
ambient temperature VTEMP is the voltage of the temperature sensor channel at 25°C and VDD = 1.8 V m is the voltage
versus temperature slope in V/°C.
1. Characterized on typical samples, not tested in production
2. 100 mV overdrive corresponds to a square wave from 50 mV below the reference (VIC) to 50 mV above the reference.
3. Input hysteresis is relative to the reference input channel and is software programmable.
hysteresis
3
voltage
HYSTCRT[1:0] =
01
HYSTCRT[1:0] =
10
HYSTCRT[1:0] =
11
——13mV
—120—ns
—27—mV
—35—mV
1
Max.Unit
1.7Communication interfaces
1.7.1USART interface
Excluding delays introduced by external device and PCB, the maximum supported bit
rate for USART master synchronous mode is 20 Mbit/s, and the maximum supported
bit rate for USART slave synchronous mode is 20.0 Mbit/s.
The actual USART bit rate depends on the delays introduced by the external trace, the
external device, system clock (HCLK), and capacitive loading.
T
= -20 °C to 70 °C; VDD = 1.71 V to 1.89 V; CL = 20 pF balanced loading on all pins; Input slew = 1 ns, SLEW setting
amb
= standard mode for all pins; Parameters sampled at the 50 % level of the rising or falling edge.
1. Guaranteed by design. Not tested in production.
2. A device must internally provide a hold time of at least 300 ns for the SDA signal (with respect to the VIH(min) of the
SCL signal) to bridge the undefined region of the falling edge of SCL.
3. Cb = total capacitance of one bus line in pF. If mixed with Hs-mode devices, faster fall times are allowed.
4. The maximum tf for the SDA and SCL bus lines is specified at 300 ns. The maximum fall time for the SDA output
stage tf is specified at 250 ns. This allows series protection resistors to be connected in between the SDA and the
SCL pins and the SDA/SCL bus lines without exceeding the maximum specified tf.
5. In Fast-mode Plus, fall time is specified the same for both output stage and bus timing. If series resistors are used,
designers should allow for this when considering bus timing.
6. The MSTTIME register allows programming of certain times for the clock (SCL) high and low times. Please see i.MX
RT500 Low-Power Crossover MCU Reference Manual for further details.
7. t
is the data hold time that is measured from the falling edge of SCL; applies to data in transmission and the
HD;DAT
acknowledge.
8. The maximum t
maximum of t
LOW period (t
releases the clock.
9. t
is the data set-up time that is measured with respect to the rising edge of SCL; applies to data in transmission
SU;DAT
and the acknowledge.
10. A Fast-mode I2C-bus device can be used in a Standard-mode I2C-bus system but the requirement t
must then be met. This will automatically be the case if the device does not stretch the LOW period of the SCL signal.
If such a device does stretch the LOW period of the SCL signal, it must output the next data bit to the SDA line
tr(max) + t
is released. Also the acknowledge timing must meet this set-up time.
data hold time7, 2, 8Standard-mode0-μs
Fast-mode0-μs
Fast-mode Plus0-μs
data set-up time9, 10Standard-mode4.7-ns
Fast-mode0.6-ns
Fast-mode Plus0.26-ns
could be 3.45 s and 0.9 s for Standard-mode and Fast-mode but must be less than the
HD;DAT
or t
VD;DAT
) of the SCL signal. If the clock stretches the SCL, the data must be valid by the set-up time before it
LOW
= 1000 + 250 = 1250 ns (according to the Standard-mode I2C-bus specification) before the SCL line
SU;DAT
by a transition time. This maximum must only be met if the device does not stretch the
= -20 °C to 70 °C; VDD = 1.71 V to 1.89 V; CL = 30 pF balanced loading on all pins; Input slew = 1.0 ns, SLEW setting =
amb
standard mode for all pins; Parameters sampled at the 50 % level of the rising or falling edge.
Table 35. I2S-bus interface pins1, 2
SymbolParameterConditionsNotesMin.Typ.
Common to master and slave
t
WH
t
WL
t
v(Q)
t
su(D)
t
h(D)
t
v(Q)
t
su(D)
t
h(D)
pulse width
HIGH
pulse width
LOW
data output
valid time
data input setup time
data input
hold time
data output
valid time
data input setup time
data input
hold time
on pins I2Sx_TX_SCK and I2Sx_RX_SCK
(T
cyc
on pins I2Sx_TX_SCK and I2Sx_RX_SCK
(T
cyc
Master
on pin
5
I2Sx_TX_SD
A
on pin I2Sx_WS
on pin
51.3--ns
I2Sx_RX_SD
A
on pin
52.9--ns
I2Sx_RX_SD
A
Slave
on pin
513.823.6ns
I2Sx_TX_SD
A
on pin
54.7--ns
I2Sx_RX_SD
A
on pin
I2Sx_WS
on pin
50--ns
I2Sx_RX_SD
A
on pin
I2Sx_WS
4
/2) -1-(T
4
/2) -1-(T
6.798-17.505ns
5-16.055ns
0.9--ns
0--ns
3
Max.Unit
/2) +1ns
cyc
/2) +1ns
cyc
1. Based on simulation; not tested in production.
2. The Flexcomm Interface function clock frequency should not be above 48 MHz. See the data rates section in the I2S
chapter in the i.MX RT500 Low-Power Crossover MCU Reference Manual (IMXRT500RM) to calculate clock and sample
rates.
Excluding delays introduced by external device and PCB, the maximum supported bit
rate for SPI master mode (transmit/receive) is 25 Mbit/s and the maximum supported
bit rate for SPI slave mode (transmit/receive) is 25 Mbit/s.
T
= -20 °C to 70 °C; 1.71 V ≤ VDD≤ 1.89 V; CL = 10 pF balanced loading on all pins; Input slew = 1 ns, SLEW setting =
amb
standard mode for all pins;. Parameters sampled at the 50 % level of the rising or falling edge.
The actual SPI bit rate depends on the delays introduced by the external trace, the
external device, system clock (HCLK), and capacitive loading.
Excluding delays introduced by external device and PCB, the maximum supported bit
rate for SPI master mode (transmit/receive) is 50 Mbit/s.
Excluding delays introduced by external device and PCB, the maximum supported bit
rate for SPI slave mode (receive) is 50 Mbit/s and for SPI slave mode (transmit) is 35
Mbit/s.
T
= -20 °C to 70 °C; 1.71 V ≤ VDD≤ 1.89 V; CL = 10 pF balanced loading on all pins; Input slew = 1 ns, SLEW setting =
amb
standard mode for all pins;. Parameters sampled at the 50 % level of the rising or falling edge.
= -20 °C to +70 °C, VDD = 1.71 V to 1.89 V; VDDCORE = 1.13 V; CL = 10 pF. DLL_CTRL = 0x200, Full Drive Mode
on all pins, Input slew = 1 ns, SLEW setting = standard mode for all pins;. Parameters sampled at the 50 % level of the
rising or falling edge. Based on simulation, not tested in production.
Table 38. SD/MMC and SDIO characteristics (Default Speed (DS), High Speed (HS) SDR-12
Table 38. SD/MMC and SDIO characteristics (Default Speed (DS), High Speed (HS) SDR-12
and SDR-25) (continued)
SymbolParameterConditionsMin.Typ.Max.Unit
t
su(D)
t
h(D)
t
v(Q)
data input setup time
data input hold
time
data output
valid time
on pins
SD_DATn as
inputs
on pins
SD_CMD as
inputs
on pins
SD_DATn as
inputs
on pins
SD_CMD as
inputs
on pins
SD_DATn as
outputs
on pins
SD_CMD as
outputs
7.5--ns
7.5--ns
1.0--ns
1.0--ns
--7.5ns
--7.5ns
T
= -20 °C to +70 °C, VDD = 1.71 V to 1.89 V; VDDCORE = 1.13 V; CL = 10 pF. DLL_CTRL = 0x200, Full Drive Mode on
amb
all pins, Input slew = 1 ns, SLEW setting = standard mode for all pins;. Parameters sampled at the 50 % level of the rising or
falling edge. Based on simulation, not tested in production.
Table 39. SD/MMC and SDIO characteristics ((SDR-50, SDR-104, HS-200 (MMC))
= -20 °C to +70 °C, VDD = 1.71 V to 1.89 V; VDDCORE = 1.13 V; CL = 10 pF. DLL_CTRL = 0x200, Full Drive Mode
amb
on all pins, Input slew = 1 ns, SLEW setting = standard mode for all pins;. Parameters sampled at the 50 % level of the
rising or falling edge. Based on simulation, not tested in production. HS-400 supported on SD port 0 only.
Table 40. SD/MMC and SDIO characteristics ((DDR-50, HS DDR (MMC))
= -20 °C to +70 °C, VDD = 1.71 V to 1.89 V; VDDCORE = 1.13 V; CL = 10 pF. DLL_CTRL = 0x200, Full Drive Mode on
amb
all pins, Input slew = 1 ns, SLEW setting = standard mode for all pins;. Parameters sampled at the 50 % level of the rising or
falling edge. Based on simulation, not tested in production. HS-400 supported on SD port 0 only.
Table 41. SD/MMC and SDIO characteristics (HS-400(MMC))
= -20 °C to 70 °C; VDD = 2.7 V to 3.6 V; CL = 20 pF balanced loading on all pins; Input slew = 1 ns, SLEW set to
amb
standard mode for all pins; Bypass bit = 0; Parameters sampled at the 50% level of the rising or falling edge.
Table 42. Dynamic characteristics1
SymbolParameterConditionsMin.Typ.Max.Unit
t
DS
t
DH
1. Based on simulated values.
data set-up time-13--ns
data hold time-0--ns
Figure 32. DMIC timing diagram
1.7.8
USB interface characteristics
This section describes the USB1 port High Speed/Full Speed (HS/FS) transceiver. The
USB HS/FS meets the electrical compliance requirements defined in the Universal
Serial Bus Revision 2.0 Specification.
1.7.9
SymbolDescriptionMin.Typ.Max.Unit
V
DP_SRC
V
DM_SRC
V
I
DP_SRC
I
DM_SINK
I
DP_SINK
R
DM_DWN
V
DAT_REF
USB DCD electrical specifications
Table 43. USB DCD electrical specifications
,
USB_DP and USB_DM source voltages (up to 250
μA)
LGC
Threshold voltage for logic high0.8—2.0V
USB_DP source current71013μA
,
USB_DM and USB_DP sink currents50100150μA
D- pulldown resistance for data pin contact detect14.25—24.8kΩ
Data detect voltage0.250.330.4V
1.7.10USB High Speed Transceiver and PHY specifications
This section describes the High Speed USB PHY parameters. The high speed PHY is
capable of full speed signaling as well.
The USB PHY meets the electrical compliance requirements defined in the Universal
Serial Bus Revision 2.0 Specification with the amendments below.
• USB ENGINEERING CHANGE NOTICE
• Title: 5V Short Circuit Withstand Requirement Change
• Applies to: Universal Serial Bus Specification, Revision 2.0
• Errata for USB Revision 2.0 April 27, 2000 as of 12/7/2000
• USB ENGINEERING CHANGE NOTICE
• Title: Pull-up/Pull-down resistors
• Applies to: Universal Serial Bus Specification, Revision 2.0
• USB ENGINEERING CHANGE NOTICE
• Title: Suspend Current Limit Changes
• Applies to: Universal Serial Bus Specification, Revision 2.0
• On-The-Go and Embedded Host Supplement to the USB Revision 2.0 Specification
• Revision 2.0 plus errata and ecn June 4, 2010
• Battery Charging Specification (available from USB-IF)
• Revision 1.2, December 7, 2010
USB0_VBUS pin is a detector function which is 5v tolerant and complies with the
above specifications without needing any external voltage division components.
The Arm Cortex-M33 includes two AHB-Lite buses: the code bus and the system bus.
The i.MX RT500 uses a multi-layer AHB matrix to connect the Arm Cortex-M33
buses and other bus masters to peripherals in a flexible manner that optimizes
performance by allowing peripherals that are on different slave ports of the matrix to
be accessed simultaneously by different bus masters.
2.1
Detailed block diagram
The following figure shows the detailed block diagram for i. MX RT500
- Orange shaded blocks support General Purpose DMA.
- Yellow shaded blocks include dedicated DMA Ctrl.
ISP & Debug
Access Ports
General
Purpose
)
x
2
kB
Tensilica
Fusion
DSP
Pwr
M2
M3
(intended for M33 - only)
FBB
2KB
General
Smart
Purpose
DMA
DMA
1
DMA
0
Inst
M4
M5
APB slave group0
RSTCTLa, CLKCTLa, SYSCTLa
PVT
I/O Configuration
PUF
Windowed WDT0
MicroTick Timer
DSI
LCDIF
GPU
/
SDIO
SDIO
eMMC
eMMC
Data
M9
M8
M6
M7
P18
P13
registers
AHB to
APB bridge
0,1, 2
3
4
Periph Input Mux Selects
6
14
15
AXI Switch
-
HASH
/
P14
P15
P16
CRYPT
DMA
registers
CRC
Engine
M10
0
AIPS
bridge
S0
:
AHB
AXI
bridge
DMA
registers
Audio Subsys
-
(8
ch D
Decimator
Lite
1
M11
+
P17
SCTimer
PWM
AXI Switch
LCDIF
registers
RSTCTLb, CLKCTLb, SYSCTLb
GPIO interrupt Control
Smart DMA Controller
5x32-bit Timers (T0 - 4)
-Rate Timer
Multi
FlexIO Regs
S1-9
0
1
GPIO
,
-Mic
, etc)
FlexSPI
OTFAD
registers
Random
Number Gen
/
Secure
GPIO 0
Cache Ctrl0 Regs
Cache Ctrl1 Regs
I-ram
-
D
I-ram
D
P0
P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
HS
-7
0
0
Secure
Control
registers
APB bridge
0,1,2
ram
-
ram
-
AHB to
8-12
bridges
-
- SPIs 0-3 - I2Cs 0-3
UARTs 4-7
SPIs 4-7 - I2Cs 4-7
FlexSPI1
registers
5
13
18
19
20
Host
Interface
: AHB
AXI
TCM Bus
0
0
1
1
Boot Rom
192
Flexcoms 0-3
UARTs 0-3 - I2Cs 0-3
Flexcoms 4
-
USB PHY
registers
HS USB
host
registers
PwrQuad
registers
14
15
22-23
6
7
16
17
MIPI
PHY
HS USB
PHY
1-9
To Shared SRAM partitions 0 - 31
MIPI DSI Interface
HS USB Bus
To Shared SRAM partitions 0 - 27
To Shared SRAM partitions 28 - 31
32
KB
cache ram
KB
Cache
Controller
OTFAD
FlexSPI0
Flash Interface
To Shared SRAM partitions 0,1 (32 KB each)
To Shared SRAM partitions 2,3 (32 KB each)
To Shared SRAM partitions 4-7 (32 KB each)
To Shared SRAM partitions 8-11 (64 KB each)
To Shared SRAM partitions 12-15 (128 KB each)
To Shared SRAM partitions 16-19 (256 KB each)
To Shared SRAM partitions 20-23 (256 KB each)
To Shared SRAM partitions 24-27 (256 KB each)
To Shared SRAM partitions 28-31 (256 KB each)
Smart DMA
RAM 32KB
AIPS-Lite
bridge
0
-
7
Flexcom
SPI 14
SDIO0
registers
ACMP
registers
USB Ram
HS USB
device
Interface
registers
Flexcoms8-13
- UARTs8-13
- SPIs8-13
I2Cs8-13 - I2Ss8-13
-
MU0
14
registers
registers
-
I2Cs 4-7
cache ram
Controller
SDIO
PMC
32
KB
Cache
Flexcom15
I2C14
1
controller
16Kb OTP
Array
SRAM
16
-
HASH
slave interface
GPU
registers
SEMA
OTP
KB
CRYPT
FlexSPI
Flash I’face
OS
Timer
Flexcom16
- SPI 15
ADC
-
12
Temp
Sensor
CASPER
registers
CASPER
rams
APB slave group1
Windowed WDT1
WDT Osc
FreqMeasure
I3C0,1
Always-on Power Domain
RTC Alarm Match
RTC Wake Counter
RTC Alarm Counter
32 kHz Osc
& Dividers
RTC Count
RTC Subsec Counter
DSI Phy/Host Controller
1
ch
x
2
2KB
Figure 34. i.MX RT500 detailed block diagram
2.2
Shared system SRAM
The entire system TCM SRAM space (accessed in single cycle) of up to 5 MB is
divided into up to 32 separate partitions, which are accessible to both CPUs, both DMA
engines, and all other AHB bus masters. The Fusion CPU TCMI (Instruction) & TCMD
(Data) interfaces and the Graphics (GPU/LCD) subsystem each access the RAM via
separate, dedicated 64-bit interfaces. All other masters, including the Cortex-M33
processor and the DMA engines, access RAM via the main 32-bit AHB bus. All of
these accesses are single-cycle with the exception of the GPU/LCD. Hardware
interface modules arbitrate access to each RAM partition between the main AHB bus,
the graphics AHB bus and the Fusion Tightly-Coupled-Memory buses.
Under software control, each of the 32 individual SRAM partitions can be used
exclusively as code or as data, dedicated either CPU, or shared among the various
masters. Each partition can be independently placed in a low-power retention mode or
powered off entirely.
2.3
RT500 modules list
The i.MX RT500 contains a variety of digital and analog modules. The following
table describes briefly about these modules.
Table 48. i.MX RT500 modules list
Block NameBlock
Mnemonic
ARM Cortex M33 processor MCUCore moduleThe Arm Cortex-M33 is a general
Table continues on the next page...
SubsystemBrief description
Arm core modules
purpose, 32-bit microprocessor, which
offers high performance and very low
power consumption. The Arm CortexM33 offers many new features, including
a Thumb-2 instruction set, low interrupt
latency, hardware multiply and divide,
interruptable/continuable multiple load
and store instructions, automatic state
save and restore for interrupts, tightly
integrated interrupt controller with wakeup interrupt controller, and multiple core
buses capable of simultaneous
accesses. M33 includes ARM’s
TrustZone M for enhanced security as
well as a co-processor interface. This
interface is used on this device to provide
hardware acceleration for DSP functions
(Powerquad co-processor) and Security/
cryptography operations (CASPER coprocessor). A 3-stage pipeline is
employed so that all parts of the
processing and memory systems can
operate continuously. Typically, while
one instruction is being executed, its
NVICCore modulesThe NVIC is an integral part of the
Table continues on the next page...
SubsystemBrief description
successor is being decoded, and a third
instruction is being fetched from memory.
add, subtract, multiply, divide, multiply
and accumulate, and square root
operations. It also provides conversions
between fixed-point and floating-point
data formats, and floating-point constant
instructions. The FPU provides floatingpoint computation functionality that is
compliant with the ANSI/IEEE Std
754-2008, IEEE Standard for Binary
Floating-Point Arithmetic, referred to as
the IEEE 754 standard.
Protection Unit (MPU) which can be used
to improve the reliability of an embedded
system by protecting critical data within
the user application. The MPU allows
separating processing tasks by
disallowing access to each other's data,
disabling access to memory regions,
allowing memory regions to be defined
as read-only and detecting unexpected
memory accesses that could potentially
break the system. The MPU separates
the memory into distinct regions and
implements protection by preventing
disallowed accesses. The MPU supports
up to eight regions each of which can be
divided into eight subregions. Accesses
to memory locations that are not defined
in the MPU regions, or not permitted by
the region setting, will cause the Memory
Management Fault exception to take
place.
Cortex-M33. The tight coupling to the
CPU allows for low interrupt latency and
efficient processing of late arriving
interrupts.
tick timer (SysTick) that is intended to
generate a dedicated SYSTICK
exception. The clock source for the
SysTick can be the FRO or the CortexM33 core clock.
On-chip ROMROMMemoriesThe 192 KB on-chip ROM contains the
One-Time Programmable
memory
192 MHz Free Running
Oscillator (FRO)
1 MHz Low Power Oscillator LPOSystem ControlThe 1 MHz oscillator provides an ultra
Crystal Oscillator-System ControlThe main crystal oscillator on the i.MX
OTPMemoriesThe i.MX RT500 contains up to 16 kbits
FROSystem controlThe 192 MHz FRO oscillator provides a
Table continues on the next page...
SubsystemBrief description
for higher throughput and individual
power control for low-power operation.
boot loader and the following Application
Programming Interfaces (API):
• In-Application Programming (IAP)
and In-System Programming (ISP).
• ROM-based USB drivers (HID,
CDC, MSC). Supports flash
updates via USB.
• Supports booting from valid Octal/
Quad SPI, eMMC, USB, USART,
SPI, and I2C. • Legacy, Single, and
Dual image boot.
• OTP API for programming OTP
memory.
• Random Number Generator (RNG)
API.
one-time-programmable memory used
for part configuration, key storage (as an
alternative to PUF) and other uses.
Clock sources
high-frequency clock source that can be
used without the need for a high-power
PLL for many applications. This oscillator
is factory trimmed to ±1% accuracy but
can optionally be tuned to ±0.1%
accuracy using an accurate, known
reference clock such as the crystal
oscillator. The 192 MHz FRO, or a
divided version of it, may be used as the
main system clock and for many other
purposes.
low-power, low-frequency clock source
that can be used to clock a variety of
functions including the Watchdog Timer
(WWDT) and the OS/EVENT Timer. It
can also be used as the main system
clock for low-power operation. On Reset,
the device boots using this 1 MHz
oscillator.
The 1 MHz Low Power oscillator is
accurate to ±5% over temperature.
RT500 can be used with crystal
frequencies from 4 MHz to 26 MHz. The
32 KHz Crystal Oscillator-System ControlThe 32KHz oscillator resides in the
System Control (PLLs)
System PLL (PLL0)PLL0System ControlThe system PLL accepts an input clock
Audio PLL (PLL1)PLL1System ControlThe audio PLL accepts an input clock
General Purpose I/O (GPIO) GPIOPin MuxingThe i.MX RT500 provides up to six GPIO
Pin Interrupt and Pattern
Match (PINT)
-I/O MuxThe pin interrupt block configures up to
Table continues on the next page...
SubsystemBrief description
crystal oscillator may be used to drive a
PLL to achieve higher clock rates.
"always-on" domain and is used to drive
the Real Time Clock. It is also available
for use for a variety of other purposes
including low-power UART operation or
as the main system clock for very low
frequency operation
frequency in the range of 32.768 kHz to
25 MHz. The input frequency is multiplied
up to a high frequency with a Current
Controlled Oscillator (CCO). Generates
four independent outputs (PFD0-3).
frequency in the range of 1 MHz to 25
MHz. The input frequency is multiplied up
to a high frequency with a Current
Controlled Oscillator (CCO). The PLL can
be enabled or disabled by software.
I/O Muxing
ports with a total of up to 136 GPIO pins.
Device pins that are not connected to a
specific peripheral function are controlled
by the GPIO registers. Pins may be
dynamically configured as inputs or
outputs. Separate registers allow setting
or clearing any number of outputs
simultaneously. The current level of a
port pin can be read back no matter what
peripheral is selected for that pin. It can
optionally contribute to one of two GPIO
group interrupts, with selection of
polarity, level or edge detection.
eight pins from all digital pins for
providing eight external interrupts
connected to the NVIC. The pattern
match engine can optionally be used in
conjunction with software to create
complex state machines based on pin
inputs. Any digital pin, independent of the
function selected through the switch
matrix can be configured through the
SYSCON block as an input to the pin
interrupt or pattern match engine. The
registers that control the pin interrupt or
pattern match engine are located on the
I/O+ bus for fast single-cycle access.
Communication peripherals
USB1Communication interfacesThe Universal Serial Bus (USB) is a 4-
wire bus that supports communication
between a host and one or more (up to
127) peripherals. The host controller
allocates the USB bandwidth to attached
devices through a token-based protocol.
The device controller enables 480 Mbit/s
data exchange with a USB host
controller. It consists of a register
interface, serial interface engine,
endpoint buffer memory. The bus
supports hot plugging and dynamic
configuration of the devices. All
transactions are initiated by the host
controller.
supporting Octal and Quad SPI memory
devices are provided. The first FlexSPI
instance is primarily intended for code
execution from off-chip SPI flash
memory. The second instance is
primarily intended to access data from
RAMs like HyperRAM or pSRAM
(particularly for graphics). The second
instance is accessible by the DSP
processor as well as the M33. Target will
be for both interfaces to support up to
200 MHz DDR/SDR The FlexSPI
interfaces support HyperFlash,
HyperRAM and Xccela memory types,
among others. The first FlexSPI interface
(FlexSPI0) supports execute-in-place and
on-the-fly decryption using the latest
OTFAD module. It also provides a
mechanism to shift a designated range of
addresses to a different region of off-chip
memory to support dual-image boot. Both
FlexSPI Interfaces include a 32 KB cache
with an CACHE64 AHB-cache controller.
Additional logic is provided at the
CACHE64 interface to enable different
caching policies for different address
regions. These policies include:
I3CCommunication interfaceTwo I3C master/slave interfaces are
Counter/Timer modules
-Counter/TimersThe i.MX RT500 includes five general-
SCT/PWMCounters/TimersThe SCTimer/PWM allows a wide variety
Table continues on the next page...
SubsystemBrief description
are provided. One instance of this
interface (SDIO0) supports the eMMC
5.0 standard including HS400 DDR
mode. The other instance supports 100
MHz SDR, 50 MHz DDR.
• USART with asynchronous
operation or synchronous master
or slave operation.
• SPI master or slave, with up to 4
slave selects.
• I2C, including separate master,
slave, and monitor functions.
• Two I2S functions using Flexcomm
Interface 6 and Flexcomm Interface
7.
• Data for USART, SPI, and I2S
traffic uses the Flexcomm Interface
FIFO. The I2C function does not
use the FIFO.
provided, both of which support DDR.
purpose 32-bit timer/counters. The timer/
counter is designed to count cycles of the
system derived clock or an externallysupplied clock. It can optionally generate
interrupts, generate timed DMA requests,
or perform other actions at specified
timer values, based on four match
registers. Each timer/counter also
includes two capture inputs to trap the
timer value when an input signal
transitions, optionally generating an
interrupt.
of timing, counting, output modulation,
and input capture operations. The inputs
and outputs of the SCTimer/PWM are
shared with the capture and match
inputs/outputs of the 32-bit generalpurpose counter/timers. The
SCTimer/PWM can be configured as two
16-bit counters or a unified 32-bit
counter. In the two-counter case, in
addition to the counter value the following
operational elements are independent for
each half:
Real Time Clock TimerRTC TimerTimersThe RTC timer is a 32-bit timer which
Multi-Rate TimerMRTTimersThe Multi-Rate Timer (MRT) provides a
OS/Event Timer-TimersAn OS/EVENT Timer module provides a
WWDTTimersThe purpose of the watchdog is to reset
SubsystemBrief description
• State variable
• Limit, halt, stop, and start
conditions.
• Values of Match/Capture registers,
plus reload or capture control
values.
In the two-counter case, the following
operational elements are global to the
SCTimer/PWM, but the last three can
use match conditions from either counter:
• Clock selection
• Inputs
• Events
• Outputs
• Interrupts
the controller if software fails to
periodically service it within a
programmable time window. A separate
Watchdog Timer is provided for each of
the two CPUs.
counts down from a preset value to zero.
At zero, the preset value is reloaded and
the counter continues. The RTC timer
uses the 32.768 kHz clock input to create
a 1 Hz or 1 kHz clock.
repetitive interrupt timer with four
channels. Each channel can be
programmed with an independent time
interval, and each channel operates
independently from the other channels.
common timebase between the two
CPUs for event synchronization and
timestamping. The OS/EVENT Timer is
comprised of a shared, free-running
counter readable by each CPU and
individual match and capture registers for
each CPU. The shared and local
counters in this module are implemented
using Gray code. This will enable them to
be read asynchronously by the
processing domains. The main counter in
the OS/EVENT Timer module begins
counting immediately following power-up
and continues counting through any
subsequent system resets (except those
caused by a new POR).
GPU2DGraphicsA 2D graphics engine is provided. The
MIPI-DSIGraphicsLCD Display Controller, with on-chip MIPI
Other Digital Peripherals
Table continues on the next page...
SubsystemBrief description
the 1 MHz low-power oscillator. This
timer can wake up the device from
reduced power modes up to deep-sleep,
with extremely low power consumption.
The MicroTick timer has an added
timestamp feature in the form of 4
capture registers.
GPU is used to generate graphics data
for display by the LCD Display Controller.
The GPU supports displays up to
640x480.
DSI Phy provides transfer rates up to
895.1 Mbps to support 1024x480
displays with 24-bit color at 60 frames
per second. A parallel DBI interface is
also provided (alternative to the serial
PHY).
category can be used to interface to an
LCD with a parallel interface.
memory, memory-to-peripheral, and
memory-to-memory transactions. Each
DMA stream provides unidirectional DMA
transfers for a single source and
destination. Two identical DMA
controllers are provided on i.MX RT500.
The user may elect to dedicate one of
these to the Cortex M-33 CPU and the
other for use by the DSP CPU and/or one
may be used as a secure DMA the other
non-secure.
• Pulse-Density Modulation (PDM)
data input for left and/or right
channels on 1 or 2 buses.
• Flexible decimation.
• 16 entry FIFO for each channel.
• DC blocking or unaltered DC bias
can be selected.
• Data can be transferred using DMA
from deep-sleep mode without
waking up the CPU, then
Temperature Sensor-AnalogThe temperature sensor transducer uses
CRCOtherThe Cyclic Redundancy Check (CRC)
ADCAnalogThe ADC supports a resolution of 12-bit
OtherSmart DMA Controller with dedicated 32
SubsystemBrief description
automatically returning to deepsleep mode.
• Data can be streamed directly to
I2S on Flexcomm Interface 7.
KB code RAM
module is capable of supporting a wide
range of protocols including, but not
limited to: UART, I2C, SPI, I2S, camera
interface, display interface, PWM
waveform generation, and so on
generator with programmable polynomial
settings supports several CRC standards
commonly used. To save system power
and bus bandwidth, the CRC engine
supports DMA transfers.
Analog Peripherals
and fast conversion rates of up to 1
Msamples/s. Sequences of analog-todigital conversions can be triggered by
multiple sources. Possible trigger
sources are the SCTimer/PWM, external
pins, and the Arm TXEV interrupt.
an intrinsic pn-junction diode reference
and outputs a CTAT voltage
(Complement To Absolute Temperature).
The output voltage varies inversely with
device temperature with an absolute
accuracy of better than ±5 °C over the
full temperature range (-20 °C to +70 °C).
The temperature sensor is only
approximately linear with a slight
curvature. The output voltage is
measured over different ranges of
temperatures and fit with linear-leastsquare lines. After power-up, the
temperature sensor output must be
allowed to settle to its stable value before
it can be used as an accurate ADC input.
For an accurate measurement of the
temperature sensor by the ADC, the ADC
must be configured in single-channel
burst mode. The last value of a nineconversion (or more) burst provides an
accurate result.
Analog ComparatorCMPAnalogThe Comparator (CMP) module provides
Security Subsystem-SecurityComprises of:
On-The-Fly AES Decryption
True Random Number
Generator
OTFADSecurityThe On-The-Fly AES Decryption
TRNGSecurityThe True Random Number Generator
SubsystemBrief description
a circuit for comparing two analog input
voltages. The comparator circuit is
designed to operate across the full range
of the supply voltage (rail to rail
operation).
Security
• Trust Zone M
• AES256 Decryption Engine.
• SHA-1, SHA-2 HASH Engine.
• Physical Unclonable Function
(PUF) Key Generation
• CASPAR security Cortex-M33 coprocessor
• OTP memory
• Random number generator (RNG)
• On-the-Fly Decryption on FlexSPI
interface
.
(OTFAD) module provides an advanced
hardware implementation that minimizes
any incremental cycles of latency
introduced by the decryption in the
overall external memory access time.
The OTFAD engine also includes
complete hardware support for a
standard AES key unwrap mechanism to
decrypt a key BLOB data instruction
containing the parameters needed for up
to 4 unique AES contexts.
(TRNG) module is used to generate high
quality, cryptographically secure, random
data. The TRNG module is capable of
generating its own entropy using an
integrated ring oscillator.
3Application information
3.1Current consumption vs. memory partitions
The following figure shows the current consumption vs memory partitions:
M33 active, running enhanced-while(1) code in different partitions.
Typical silicon, VDDCore=1.1V, Temperature=25℃, FBB, HCLK=192MHz (FRO).
All memories array/periphery ON (PDRUNCFG2/3) and only one partition clocked
(AHB_SRAM_ACCESS_DISABLE register).
Figure 35. Current consumption vs. memory partitions
3.2
Standard I/O pin configuration
The following figure shows the possible pin modes for standard I/O pins:
The default configuration for standard I/O pins is Z mode. The weak MOS devices
provide a drive capability equivalent to pull-up and pull-down resistors.
I/O pins are contributing to the overall dynamic and static power consumption of the
part. If pins are configured as digital inputs, a static current can flow depending on the
voltage level at the pin and the setting of the internal pull-up and pull-down resistors.
This current can be calculated using the parameters Rpu and Rpd given in Table 6 for a
given input voltage VI. For pins set to output, the current drive strength is given by
parameters IOH and IOL in Table 6, but for calculating the total static current, you also
need to consider any external loads connected to the pin.
I/O pins also contribute to the dynamic power consumption when the pins are switching
because the VDD supply provides the current to charge and discharge all internal and
external capacitive loads connected to the pin in addition to powering the I/O circuitry.
The contribution from the I/O switching current Isw can be calculated as follows for any
given switching frequency fsw if the external capacitive load (C
In the RTC oscillator circuit, only the crystal (XTAL) and the capacitances CX1 and
CX2 need to be connected externally on RTCXIN and RTCXOUT. See the following
figure.
Figure 37. RTC oscillator components
For best results, it is very critical to select a matching crystal for the on-chip oscillator.
Load capacitance (CL), series resistance (RS), and drive level (DL) are important
parameters to consider while choosing the crystal. After selecting the proper crystal,
the external load capacitor CX1 and CX2 values can also be generally determined by
the following expression:
CX1 = C
= 2CL - C
X2
Pad
- 2C
STRAY
Where:
CL - Crystal load capacitance
C
- Pad capacitance of the RTCXIN and RTCXOUT pins (~3 pF, for each pad).
Pad
C
STRAY
– stray capacitance between RTCXIN and RTCXOUT pins.
For example:
CL = 9 pF
CX1 = C
CX1 = C
= 2CL - C
X2
= 2*9 - 3 - 0 = 15 pF
X2
Pad
- 2C
STRAY
Although C
external components influences the optimal values of external load capacitors.
Therefore, it is recommended to fine tune the values of external load capacitors on
can be ignored in general, the actual board layout and placement of
NXP Semiconductors
75
Application information
actual hardware board to get the accurate clock frequency. For fine tuning, output the
RTC Clock to the CLOCKOUT pin and optimize the values of external load capacitors
for minimum frequency deviation.
To use bypass mode on RTC, remove the crystal, drive an external clock to RTCIN pin,
and float the RTCOUT pin.
• Connect the crystal and external load capacitors on the PCB as close as possible to
the oscillator input and output pins of the chip.
• The length of traces in the oscillation circuit should be as short as possible and must
not cross other signal lines.
• Ensure that the load capacitors CX1, CX2, and CX3, in case of third overtone
crystal usage, have a common ground plane.
• Loops must be made as small as possible to minimize the noise coupled in through
the PCB and to keep the parasitics as small as possible.
• Lay out the ground (GND) pattern under crystal unit.
• Do not lay out other signal lines under crystal unit for multi-layered PCB.
3.5
XTAL oscillator
In the XTAL oscillator circuit, only the crystal (XTAL) and the capacitances CX and C
need to be connected externally on XTALIN and XTALOUT. See the figure below.
Figure 39. XTAL oscillator connection - High Gain Mode
For best results, it is very critical to select a matching crystal for the on-chip oscillator.
Load capacitance (CL), series resistance (RS), and drive level (DL) are important
parameters to consider while choosing the crystal. After selecting the proper crystal,
the external load capacitor CX1 and CX2 values can also be generally determined by
the following expression:
Cx = Cy = 2CL - C
Pad
- 2C
STRAY
Where:
CL - Crystal load capacitance
C
- Pad capacitance of the XTALIN and XTALOUT pins (~3 pF, for each pad).
– stray capacitance between XTALIN and XTALOUT pins.
NXP Semiconductors
77
Application information
CL = 9 pF
Cx = Cy = 2CL - C
Pad
- 2C
STRAY
Cx = Cy = 2*9 - 3 - 0 = 15 pF
Although C
STRAY
can be ignored in general, the actual board layout and placement of
external components influences the optimal values of external load capacitors.
Therefore, it is recommended to fine tune the values of external load capacitors on
actual hardware board to get the accurate clock frequency. For fine tuning, measure the
clock on the XTALOUT pin and optimize the values of external load capacitors for
minimum frequency deviation.
To use bypass mode on system oscillator, set bit 1 to "1" in the system oscillator control
0 (CLKCTL0_SYSOSCCTL0), float the XTALIN pin, and drive XTALOUT with < 0.7
V to 1.8 V.
For oscillator high gain mode, a larger voltage swing is used at the crystal pin. This
gives a higher noise immunity within the oscillator and less edge to edge jitter of the
internal clock. When high gain mode is not required, power used by the crystal
oscillator can be reduced by using low power mode.
NOTE
High gain mode requires a 1 megaohm resistor (RF) to be
inserted.
In the TXCO circuit, only the oscillator should be connected to the XTALIN pin while
the XTALOUT pin remains floating when driving the device with a TXCO. See the
following figure.
Figure 41. USB interface on a self-powered device where USB_VBUS = 5 V
The internal pull-up (1.5 kΩ) can be enabled by setting the DCON bit in the
DEVCMDSTAT register to prevent the USB from timing out when there is a
significant delay between power-up and handling USB traffic. External circuitry is not
required.
Figure 42. USB interface on a bus-powered device
In the figure above, two options exist for connecting VBUS to the USB_VBUS pin:
1. Connect the regulator output to USB_VBUS. In this case, the USB_VBUS signal is
HIGH whenever the part is powered.
2. Connect the VBUS signal directly from the connector to the USB_VBUS pin. In
this case, 5 V are applied to the USB_VBUS pin while the regulator is ramping up
to to supply USB1_VDD3V3
AHBAdvanced High-performance Bus
APBAdvanced Peripheral Bus
APIApplication Programming Interface
DMADirect Memory Access
FRO oscillatorInternal Free-Running Oscillator, tuned to the factory
specified frequency
GPIOGeneral Purpose Input/Output
FROFree Running Oscillator
LSBLeast Significant Bit
MCUMicroController Unit
PDMPulse Density Modulation
PLLPhase-Locked Loop
SPISerial Peripheral Interface
TCP/IPTransmission Control Protocol/Internet Protocol
TTLTransistor-Transistor Logic
USARTUniversal Asynchronous Receiver/Transmitter
5Pinouts
5.1Signal multiplexing and pinouts
The table below shows the pin functions available on each pin, and for each package.
These functions are selectable using IOCON control registers.
Some functions, such as ADC or comparator inputs, are available only on specific
pins when digital functions are disabled on those pins. By default, the GPIO function
is selected except on pins PIO2_25 and PIO2_26, which are the serial wire debug
pins. This allows debug to operate through reset.
Most pins have all pull-ups, pull-downs, and inputs turned off at reset. This prevents
power loss through pins prior to software configuration. Due to special pin functions,
some pins have a different reset configuration: If the Boot ROM OTP is configured to
use the ISP Select pins at boot, then these pins PIO1_15, PIO3_28, and PIO3_29 have
pull-ups enabled by ROM; otherwise these pull-ups are not enabled at boot. The SWD
pins PIO2_25 and PIO2_26 have the input buffers enabled at reset.
The state of pins PIO1_15, PIO3_28, and PIO3_29 at Reset determine the boot source
for the part (if configured in the Boot ROM OTP) or if the ISP handler is invoked.
The JTAG functions TRST, TCK, TMS, TDI, and TDO, are selected on pins PIO0_7 to
PIO0_11 by hardware when the part is in boundary scan mode.