Texas Instruments AM6442BSDGHAALV C20345221
Texas Instruments AM6442BSDGHAALV C20345221
An IMPORTANT NOTICE at the end of this data sheet addresses availability, warranty, changes, use in safety-critical applications,
intellectual property matters and other important disclaimers. PRODUCTION DATA.
AM6442, AM6441, AM6422, AM6421, AM6412, AM6411
SPRSP56F – JANUARY 2021 – REVISED OCTOBER 2023 www.ti.com
Functional Safety:
SoC architecture:
• Functional Safety-Compliant targeted
– Developed for functional safety applications • Supports primary boot from UART, I2C, OSPI/
– Documentation will be available to aid IEC QSPI Flash, SPI Flash, parallel NOR Flash,
61508 functional safety system design parallel NAND Flash, SD, eMMC, USB, PCIe, and
– Systematic capability up to SIL 3 targeted Ethernet interfaces
– Hardware integrity up to SIL 2 targeted • 16-nm FinFET technology
– Safety-related certification • 17.2 mm × 17.2 mm, 0.8-mm pitch, 441-pin BGA
• IEC 61508 certification planned package
• Functional Safety Features
– ECC or parity on calculation-critical memories
– ECC and parity on select internal bus
interconnect
– Built-In Self-Test (BIST) for CPU and on-chip
RAM
– Error Signaling Module (ESM) with error pin
– Runtime safety diagnostics, voltage,
temperature, and clock monitoring, windowed
watchdog timers, CRC engine for memory
integrity checks
– Dedicated MCU domain memory, interfaces,
and M4F core capable of being isolated from
the larger SoC with Freedom From Interference
(FFI) features
• Separate interconnect
• Firewalls and timeout gaskets
• Dedicated PLL
• Dedicated I/O supply
• Separate reset
2 Applications
• Programmable Logic Controller (PLC)
• Motor Drives
• Remote I/O
• Industrial Robots
• Condition-Monitoring Gateway
3 Description
AM64x is an extension of the Sitara™ Industrial-grade family of heterogeneous Arm® processors. AM64x is built
for industrial applications, such as motor drives and Programmable Logic Controllers (PLCs), which require a
unique combination of real-time processing and communications with applications processing. AM64x combines
two instances of the Sitara device's gigabit TSN-enabled PRU-ICSSG with up to two Arm® Cortex®-A53 cores,
up to four Cortex-R5F MCUs, and a Cortex-M4F MCU.
AM64x is architected to provide real-time performance through the high-performance R5Fs, Tightly-Coupled
Memory banks, configurable SRAM partitioning, and dedicated low-latency paths to and from peripherals for
rapid data movement in and out of the SoC. This deterministic architecture allows for AM64x to handle the tight
control loops found in servo drives while the peripherals like FSI, GPMC, PWMs, sigma delta decimation filters,
and absolute encoder interfaces help enable a number of different architectures found in these systems.
The Cortex-A53s provide the powerful computing elements necessary for Linux applications. Linux, and Real-
time (RT) Linux, is provided through TI’s Processor SDK Linux which stays updated to the latest Long Term
Support (LTS) Linux kernel, bootloader and Yocto file system on an annual basis. AM64x helps bridge the Linux
world with the real-time world by enabling isolation between Linux applications and real-time streams through
configurable memory partitioning. The Cortex-A53s can be assigned to work strictly out of DDR for Linux, and
the internal SRAM can be broken up into various sizes for the Cortex-R5Fs to use together or independently.
The AM64x provides flexible industrial communications capability including full protocol stacks for EtherCAT
SubDevice, PROFINET device, EtherNet/IP adapter, and IO-Link Master. The PRU-ICSSG further provides
capability for gigabit and TSN based protocols. In addition, the PRU-ICSSG also enables additional interfaces in
the SoC including sigma delta decimation filters and absolute encoder interfaces.
Functional safety features can be enabled through the integrated Cortex-M4F along with dedicated peripherals
which can all be isolated from the rest of the SoC. AM64x also supports secure boot.
Package Information
PART NUMBER PACKAGE(1) PACKAGE SIZE(2)
AM6442 ALV (FCBGA, 441) 17.2 mm × 17.2 mm
AM6441 ALV (FCBGA, 441) 17.2 mm × 17.2 mm
AM6422 ALV (FCBGA, 441) 17.2 mm × 17.2 mm
AM6421 ALV (FCBGA, 441) 17.2 mm × 17.2 mm
AM6412 ALV (FCBGA, 441) 17.2 mm × 17.2 mm
AM6411 ALV (FCBGA, 441) 17.2 mm × 17.2 mm
(1) For more information, see Mechanical, Packaging, and Orderable Information.
(2) The package size (length × width) is a nominal value and includes pins, where applicable.
Note
To understand what device features are currently supported by TI Software Development Kits
(SDKs), search for the AM64x Software Build Sheet located in the Downloads tab option provided
at Processor-SDK-AM64x.
AM64x
(A)
Application cores Real-time cores Isolated core
® ®
2x Arm
Arm Arm
®
Arm
®
Arm
®
Arm
®
Arm
®
Arm
®
®
Cortex -A53
Cortex
® -A53 ®
Cortex -A53
®
Cortex -R5F
®
Cortex -R5F
®
Cortex -R5F
®
Cortex -R5F
®
Cortex -M4F
System Memory
(A)
Industrial Connectivity General Connectivity Isolated Connectivity
(for use with Cortex-M4F)
intro_001
Table of Contents
1 Features............................................................................1 7.10 Timing and Switching Characteristics................... 112
2 Applications..................................................................... 4 8 Detailed Description....................................................232
3 Description.......................................................................4 8.1 Overview................................................................. 232
3.1 Functional Block Diagram........................................... 5 8.2 Processor Subsystems........................................... 233
4 Revision History.............................................................. 7 8.3 Accelerators and Coprocessors..............................235
5 Device Comparison....................................................... 10 8.4 Other Subsystems.................................................. 235
5.1 Related Products...................................................... 12 9 Applications, Implementation, and Layout............... 243
6 Terminal Configuration and Functions........................13 9.1 Device Connection and Layout Fundamentals....... 243
6.1 Pin Diagrams............................................................ 13 9.2 Peripheral- and Interface-Specific Design
6.2 Pin Attributes.............................................................14 Information................................................................ 244
6.3 Signal Descriptions................................................... 59 9.3 Clock Routing Guidelines........................................251
6.4 Pin Connectivity Requirements.................................94 10 Device and Documentation Support........................252
7 Specifications................................................................ 99 10.1 Device Nomenclature............................................252
7.1 Absolute Maximum Ratings...................................... 99 10.2 Tools and Software............................................... 255
7.2 ESD Ratings........................................................... 101 10.3 Documentation Support........................................ 255
7.3 Power-On Hours (POH).......................................... 101 10.4 Support Resources............................................... 255
7.4 Recommended Operating Conditions.....................102 10.5 Trademarks........................................................... 255
7.5 Operating Performance Points................................103 10.6 Electrostatic Discharge Caution............................256
7.6 Power Consumption Summary............................... 103 10.7 Glossary................................................................256
7.7 Electrical Characteristics.........................................104 11 Mechanical, Packaging, and Orderable
7.8 VPP Specifications for One-Time Programmable Information.................................................................. 257
(OTP) eFuses............................................................ 110 11.1 Packaging Information.......................................... 257
7.9 Thermal Resistance Characteristics........................111
4 Revision History
Changes from September 22, 2022 to October 31, 2023 (from Revision E (SEPTEMBER 2022)
to Revision F (OCTOBER 2023)) Page
• (Features): Updated the Security features to clarify what is supported..............................................................1
• (Package Information): Updated the table to match the new content standard..................................................4
• (Functional Block Diagram): Updated URL for Software Build Sheet.................................................................5
• (Device Comparison): Updated URL for Software Build Sheet........................................................................ 10
• (Device Comparison): Corrected the name of the JTAG User ID register........................................................ 10
• (Device Comparison): Defined the R5F cores enabled in each device and changed the R5F TCM memory
size from "256KB" to "4 x 64KB" in the 2 x Dual Core devices, and "2 x 128KB" in the 2 x Single Core
devices..............................................................................................................................................................10
• (Device Comparison): Added Functional Safety Optional for AM6422.............................................................10
• (Device Comparison): Changed General-Purpose Memory Controller (GPMC) address range from 1GB to
128MB.............................................................................................................................................................. 10
• (GPMC0 Signal Descriptions): Moved the GPMC0_FCLK_MUX signal from System Signal Descriptions to
GPMC0 Signal Descriptions............................................................................................................................. 59
• (System Signal Descriptions): Moved the GPMC0_FCLK_MUX signal from System Signal Descriptions to
GPMC0 Signal Descriptions............................................................................................................................. 59
• (Pin Connectivity Requirements): Updated the second paragraph of the note following the Connectivity
Requirements table. The update clarifies the operation of configurable device IOs and includes precautions
that must be taken to prevent floating signals from damaging device input buffers......................................... 94
• (Specifications): Remove note that says specifications are preliminary .......................................................... 99
• (Power-On Hours): Updated the table to match the new content standard....................................................101
• (Recommended Operating Conditions): Added the Automotive temperature range...................................... 102
• (I2C OD FS Electrical Characteristics): Changed the IOL minimum value from 20 to 10 for both 1.8 V and 3.3
V modes..........................................................................................................................................................104
• (DDR Electrical Characteristics): Added references to the respective JEDEC standards..............................109
• (System Timing): Removed the Timing Conditions table from this section and added separate Timing
Conditions tables to each of the Reset Timing, Safety Signal Timing, and Clock Timing sections................. 118
• (Reset Timing): Added Timing Conditions table to define conditions specific to reset inputs and outputs..... 118
• (MCU_RESETSTATz, and RESETSTATz Switching Characteristics): Changed the minimum value of
parameter RST8 from "4040*S" to "966*S" and the minimum value of parameter RST9 from "301200" to
"4040*S"..........................................................................................................................................................118
• (MCU_RESETSTATz, and RESETSTATz Switching Characteristics): Changed the minimum value of
parameter RST13 from "0" to "960"................................................................................................................ 118
• (RESETSTATz Switching Characteristics): Changed the minimum value of parameter RST16 from "T" to
"900*T", the minimum value of parameter RST17 from "W" to "4040*S", and replaced the contents of table
note 2.............................................................................................................................................................. 118
• (PORz_OUT Switching Characteristics): Changed the minimum value of parameter RST26 from "0" to
"1840"..............................................................................................................................................................118
• (Safety Signal Timing): Added Timing Conditions table to define conditions specific to
MCU_SAFETY_ERRORn output....................................................................................................................123
• (MCU_ERRORn Switching Characteristics): Changed "RST22" to "SFTY3" in table note 5......................... 123
• (Clock Timing): Added Timing Conditions table to define conditions specific to clock inputs and outputs..... 124
• (Clock Timing Requirements): Updated the Timing Requirements figure with a single generic waveform and
updated the parameter numbers in the Timing Requirements table to reference the generic clock waveform....
........................................................................................................................................................................124
• (Clock Switching Characteristics): Updated the Switching Characteristics figure with a single generic
waveform and updated the parameter numbers in the Switching Characteristics table to reference the generic
clock waveform............................................................................................................................................... 124
• (MCU_OSC0 Crystal Implementation): Changing the crystal oscillator circuit diagram back to the original
version used in previous revisions of this document...................................................................................... 127
• (CPSW3G MDIO Timing): Included PCB Connectivity Requirements in the Timing Conditions table, changed
the minimum setup time value (parameter MDIO1) from "90" to "45", and changed the minimum and
maximum output delay time values (parameter MDIO7) from "-150" and "150" to "-10" and "10"
respectively.....................................................................................................................................................133
• (GPMC0 IOSETs): Removed GPMC0_CLKLB since there is no pin with this name .....................................171
• (MCSPI Switching Characteristics - Controller Mode): Replaced previous table notes 2 and 3 with new table
notes 2, 3, 4, and 5.........................................................................................................................................176
• (MMC0 Timing Requirements – Legacy SDR Mode): Changed the minimum values for LSDR1 and LSDR3
from 9.69 to 1.56, and the minimum values for LSDR2 and LSDR4 from 27.97 to 5.44................................183
• (MMC0 Switching Characteristics – Legacy SDR Mode): Changed the minimum values for LSDR8 and
LSDR9 from -16.1 to -2.3, and the maximum values for HSSDR8 and HSSDR9 from 16.1 to 2.9................183
• (MMC0 Timing Requirements – High Speed SDR Mode): Changed the minimum values for HSSDR1 and
HSSDR3 from 2.99 to 2.55.............................................................................................................................184
• (MMC0 Switching Characteristics – High Speed SDR Mode): Changed the minimum values for HSSDR8 and
HSSDR9 from -6.35 to -2.3, and the maximum values for HSSDR8 and HSSDR9 from 6.35 to 2.9.............184
• (MMC0 Timing Requirements – High Speed DDR Mode): Changed the minimum values for HSDDR1 from
3.88 to 1.62, and the minimum values for HSDDR2 from 2.67 to 2.52.......................................................... 185
• (MMC0 Switching Characteristics – High Speed DDR Mode): Changed the maximum value for HSDDR8 from
16.19 to 7.65...................................................................................................................................................185
• (MMC1 DLL Delay Mapping for All Timing Modes): Changed the value of OTAPDLYENA from 0x0 to 0x1 for
Default Speed and High Speed modes. Also changed UHS-I DR50 to UHS-I DDR50 to correct a
typographical error in the mode name............................................................................................................187
• (Timing Requirements for MMC1 – Default Speed Mode): Changed the minimum values for DS1 and DS3
from 2.55 to 2.15, and the minimum values for DS2 and DS2 from 19.67 to 1.67.........................................189
• (Switching Characteristics for MMC1 – Default Speed Mode): Changed the minimum values for DS8 and DS9
from -14.1 to -1.8, and the maximum values for DS8 and DS9 from 14.1 to 1.8........................................... 189
• (Timing Requirements for MMC1 – High Speed Mode): Changed the minimum values for HS1 and HS3 from
2.55 to 2.15, and the minimum values for HS2 and HS2 from 2.67 to 1.67................................................... 190
• (Switching Characteristics for MMC1 – High Speed Mode): Changed the minimum values for HS8 and HS9
from -7.35 to -1.8, and the maximum values for HS8 and HS9 from 3.35 to 1.8........................................... 190
• (Timing Requirements for MMC1 – UHS-I SDR12 Mode): Changed the minimum values for SDR121 and
SDR123 from 21.65 to 2.35............................................................................................................................191
• (Switching Characteristics for MMC1 – UHS-I SDR12 Mode): Changed the minimum values for SDR128 and
SDR129 from -13.6 to 1.2, and the maximum values for SDR128 and SDR129 from 13.6 to 8....................191
• (Timing Requirements for MMC1 – UHS-I SDR25 Mode): Changed the minimum values for SDR251 and
SDR253 from 2.15 to 1.95..............................................................................................................................192
• (Switching Characteristics for MMC1 – UHS-I SDR25 Mode): Changed the minimum values for SDR258 and
SDR259 from -7.1 to 2.4, and the maximum values for SDR258 and SDR259 from 3.1 to 8........................192
• (Timing Requirements for MMC1 – UHS-I DDR50 Mode): Removed Timing Requirements since the UHS-I
DDR50 mode requires a tuning algorithm to be used for optimal input timing............................................... 194
• (Switching Characteristics for MMC1 – UHS-I DDR50 Mode): Changed the maximum value for DDR508 from
13.1 to 6.35.....................................................................................................................................................194
• (Switching Characteristics for MMC1 – UHS-I SDR104 Mode): Changed the minimum values for SDR1046
and SDR1047 from 2.08 to 2.12, the minimum values for SDR1048 and SDR1049 from 1.12 to 1.08, and
maximum values for SDR1048 and SDR1049 from 3.16 to 3.2..................................................................... 195
• (OSPI Switching Characteristics – PHY Data Training): Added maximum values to the OSPI0_CLK Cycle
Time parameter (O1) to define a minimum operating frequency of 133MHz. Also updated Note 1 and Note 4,
where "in ns" was added to the OSPI_CLK cycle time reference in Note 1 and "refclk" was changed to
"reference clock" in Note 4 so it matches the clock name used in the TRM.................................................. 199
• (OSPI0 Switching Characteristics – PHY SDR Mode): Updated Note 1 and Note 4, where "in ns" was added
to the OSPI_CLK cycle time reference in Note 1 and "refclk" was changed to "reference clock" in Note 4 so it
matches the clock name used in the TRM..................................................................................................... 201
• (OSPI0 Switching Characteristics – PHY DDR Mode): Updated Note 1 and Note 4, where "in ns" was added
to the OSPI_CLK cycle time reference in Note 1 and "refclk" was changed to "reference clock" in Note 4 so it
matches the clock name used in the TRM..................................................................................................... 203
• (OSPI0 Timing Requirements – Tap SDR Mode): Updated the constant values associated with the minimum
setup and minimum hold formulas in parameters O19 and O20. Note 2 was also updated to change "refclk" to
"reference clock" so it matches the clock name used in the TRM..................................................................205
• (OSPI0 Switching Characteristics – Tap SDR Mode): Updated Note 1 and Note 4, where "in ns" was added to
the OSPI_CLK cycle time reference in Note 1 and "refclk" was changed to "reference clock" in Note 4 so it
matches the clock name used in the TRM..................................................................................................... 205
• (OSPI0 Timing Requirements – Tap DDR Mode): Updated the constant values associated with the minimum
setup and minimum hold formulas in parameters O13 and O14. Note 2 was also updated to change "refclk" to
"reference clock" so it matches the clock name used in the TRM..................................................................207
• (OSPI0 Switching Characteristics – Tap DDR Mode): Changed the "OSPI_RD_DATA_CAPTURE_REG" bit
field from "DELAY_FLD" to "DDR_READ_DELAY_FLD" in the note associated with parameter O6.............207
• (OSPI0 Switching Characteristics – Tap DDR Mode): Updated the minimum data output delay and maximum
data output delay formulas in parameter O6. Also updated Note 1 and Note 5, where "in ns" was added to the
OSPI_CLK cycle time reference in Note 1 and "refclk" was changed to "reference clock" in Note 5 so it
matches the clock name used in the TRM..................................................................................................... 207
• (PCIe): Updated the "For more details about features and ..." paragraph......................................................208
• (PRUSS PRU Switching Characteristics – Direct Output Mode): Changed the maximum skew value for the
GPO to GPO parameter (PRDO1) from 3ns to 2ns........................................................................................209
• (PRU_ICSSG UART Switching Characteristics): Added the TRM UART baud rate settings reference to Note
1......................................................................................................................................................................218
• (USB): Updated the "For more details about features and ..." paragraph...................................................... 229
• (Power Supply Designs): Updated recommended PMIC from LP8733xx to TPS65220 or TPS65219.......... 243
• (USB VBUS Design Guidelines): Changed the 3.5 kΩ resistor value to 3.48kΩ since 3.5kΩ is not a standard
value for 1% resistors..................................................................................................................................... 248
• (Clock Routing Guidelines): Added new section............................................................................................ 251
• (Device Naming Convention): Added the Automotive temperature range......................................................254
5 Device Comparison
Table 5-1 shows a comparison between devices, highlighting the differences.
Note
Availability of features listed in this table are a function of shared IO pins, where IO signals associated
with many of the features are multiplexed to a limited number of pins. The SysConfig tool should
be used to assign signal functions to pins. This will provide a better understanding of limitations
associated with pin multiplexing.
Note
To understand what device features are currently supported by TI Software Development Kits
(SDKs), search for the AM64x Software Build Sheet located in the Downloads tab option provided
at Processor-SDK-AM64x.
CTRL_MMR_CFG0_JTAG_USER_ID[31:13](1)
Register bit values by device "Features" code (See Nomenclature Description table for more information on device features)
C: – – – – 0x19403 0x19203
D: 0x19464 0x19264 0x19424 0x19224 – –
E: 0x19465 0x19265 – 0x19225 – –
F: 0x19466 0x19266 – 0x19226 – –
PROCESSORS AND ACCELERATORS
Speed Grades (See Table 7-1) S S, K
Arm Cortex-A53 Microprocessor Subsystem Arm A53 Dual Core Single Core Dual Core Single Core Dual Core Single Core
2 × Dual Core
R5FSS0_CORE0 2 × Single Core
Single Core
Arm Cortex-R5F Arm R5F R5FSS0_CORE1 R5FSS0_CORE0
R5FSS0_CORE0
R5FSS1_CORE0 R5FSS1_CORE0
R5FSS1_CORE1
Single Core
Arm Cortex-M4F Arm M4F Single Core
Functional Safety Optional(4)
Device Management Security Controller DMSC-L Yes
Crypto Accelerators Security Yes
PROGRAM AND DATA STORAGE
On-Chip Shared Memory (RAM) in MAIN Domain OCSRAM 2MB
R5F Tightly Coupled Memory (TCM) TCM 4 x 64KB 2 x 128KB 1 x 128KB
On-Chip Shared Memory (RAM) in M4F Domain MCU_MSRAM 256KB
DDR4/LPDDR4 DDR Subsystem DDRSS Up to 2GB (16-bit data) with inline ECC
General-Purpose Memory Controller GPMC Up to 128MB with ECC
PERIPHERALS
Modular Controller Area Network Interface MCAN 2
Full CAN-FD Support(2) MCAN Optional Optional No Optional No No
General-Purpose I/O GPIO Up to 198
Inter-Integrated Circuit Interface I2C 6
Analog-to-Digital Converter ADC 1 No
Multichannel Serial Peripheral Interface MCSPI 7
MMCSD0 eMMC (8-bits)
Multi-Media Card/ Secure Digital Interface
MMCSD1 SD/SDIO (4-bits)
FSI_TX 2
Fast Serial Interface
FSI_RX 6
Flash Subsystem (FSS)(3) OSPI0/QSPI0 Yes
(1) For more details about the CTRL_MMR_CFG0_JTAG_USER_ID register and DEVICE_ID bit field, see the device TRM.
(2) Full CAN-FD Support is available when selecting an orderable part number that includes a feature code of E or F. Refer to
Nomenclature Description table for the definition of feature codes.
(3) One flash interface, configured as OSPI0 or QSPI0.
(4) Functional Safety is available when selecting an orderable part number that includes a feature code of F. Refer to Nomenclature
Description table for the definition of feature codes.
(5) Orderable part numbers with a feature code of C support using PRU_ICSSG for use cases other than industrial communication. Refer
to Nomenclature Description table for the definition of feature codes.
(6) PRU_ICSSG industrial communication includes Ethernet networking (MII/RGMII, MDIO), Sigma-Delta (SD) decimation, and three
channel peripheral interface (EnDat 2.2 and BiSS). PRU_ICSSG industrial communication support is available when selecting an
orderable part number that includes a feature code of D, E, or F. Refer to Nomenclature Description table for the definition of feature
codes.
(7) USB SuperSpeed and PCIe share a common SerDes PHY. Therefore, USB will be limited to non-SuperSpeed modes when using the
SerDes PHY for PCIe.
Figure 6-1 shows the ball locations for the 441-ball flip chip ball grid array (FCBGA) package to quickly locate
signal names and ball grid numbering. This figure is used in conjunction with Table 6-1 through Table 6-80 (Pin
Attributes table and all Signal Descriptions tables, including the Connectivity Requirements table).
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
PRG0_PRU0 PRG0_PRU0 PRG0_PRU1 PRG0_PRU0 PRG1 PRG1_PRU0 PRG1_PRU0 PRG1_PRU0 PRG1_PRU1 PRG1_PRU1 PRG1_PRU1 PRG1_PRU1 PRG1_PRU1 SERDES0 SERDES0
AA VSS _MDIO0 VSS VSS USB0_DP USB0_DM VSS
_GPO4 _GPO12 _GPO16 _GPO10 _MDIO _GPO6 _GPO11 _GPO14 _GPO11 _GPO14 _GPO2 _GPO5 _GPO17 _TX0_N _TX0_P
PRG0_PRU0 PRG0_PRU1 PRG0_PRU0 PRG0_PRU1 PRG0_PRU1 PRG1 PRG1_PRU0 PRG1_PRU0 PRG1_PRU0 PRG1_PRU1 PRG1_PRU1 PRG1_PRU1 PRG1_PRU1 SERDES0 SERDES0 GPMC0 GPMC0 GPMC0
Y _MDIO0 VSS VSS VSS
_GPO0 _GPO0 _GPO11 _GPO12 _GPO9 _MDC _GPO0 _GPO4 _GPO15 _GPO16 _GPO15 _GPO3 _GPO18 _RX0_N _RX0_P _WAIT1 _AD15 _AD14
PRG0_PRU0 PRG0_PRU1 PRG0_PRU1 PRG0_PRU1 PRG0_PRU1 PRG0_PRU0 PRG1_PRU0 PRG1_PRU0 PRG1_PRU0 PRG1_PRU1 PRG1_PRU1 PRG1_PRU0 PRG1_PRU1 SERDES0 SERDES0 GPMC0 GPMC0 GPMC0
W VSS RSVD4 VSS
_GPO19 _GPO1 _GPO4 _GPO11 _GPO7 _GPO9 _GPO19 _GPO2 _GPO13 _GPO0 _GPO4 _GPO8 _GPO10 _REFCLK0N _REFCLK0P _WAIT0 _AD11 _AD12
PRG0_PRU0 PRG0_PRU0 PRG0_PRU1 PRG0_PRU0 PRG0_PRU1 PRG0_PRU1 PRG1_PRU0 PRG1_PRU0 PRG1_PRU0 PRG1_PRU1 PRG1_PRU1 PRG1_PRU1 PRG1_PRU0 PRG1_PRU1 PRG1_PRU1 GPMC0
V RSVD5 VSS GPMC0_AD8 GPMC0_AD6 GPMC0_AD7
_GPO18 _GPO3 _GPO2 _GPO14 _GPO17 _GPO10 _GPO18 _GPO3 _GPO16 _GPO12 _GPO1 _GPO19 _GPO5 _GPO9 _GPO7 _AD13
PRG0_PRU0 PRG0_PRU0 PRG0_PRU0 PRG0_PRU1 PRG0_PRU1 PRG1_PRU0 PRG1_PRU0 PRG1_PRU0 PRG1_PRU1 PRG1_PRU1 PRG1_PRU1 PRG1_PRU0 PRG1_PRU0 PRG1_PRU0 USB0
U VSS USB0_ID GPMC0_AD4 GPMC0_AD5 GPMC0_AD3 GPMC0_AD1
_GPO17 _GPO2 _GPO16 _GPO15 _GPO14 _GPO17 _GPO1 _GPO12 _GPO13 _GPO6 _GPO8 _GPO7 _GPO10 _GPO9 _RCALIB
PRG0_PRU1 PRG0_PRU1 PRG0_PRU0 PRG0_PRU0 PRG0_PRU1 PRG0_PRU0 VDDA_3P3 VDDA_1P8 VDDA_1P8 GPMC0 GPMC0_OEn GPMC0 GPMC0 GPMC0
R VSS VDDSHV2 VSS VDDSHV2 CAP_VDDS2 VSS GPMC0_CLK
_GPO8 _GPO19 _GPO5 _GPO1 _GPO6 _GPO13 _USB0 _SERDES0 _USB0 _AD10 _REn _CSn0 _CSn1 _CSn3
PRG0 PRG0 PRG0_PRU1 PRG0_PRU1 VDDA_0P85 VDDA_0P85 VDDA_0P85 GPMC0 GPMC0 GPMC0
P VSS _MDIO0 _MDIO0 VSS VDDSHV1 VSS VDD_CORE VSS _SERDES0 VDDSHV3 VDDSHV3 VSS OSPI0_D5 OSPI0_D4
_MDIO _MDC _GPO5 _GPO18 _C _SERDES0 _SERDES0 _ADVn_ALE _BE0n_CLE _CSn2
OSPI0
N DDR0_DQS1 DDR0_DQ15 DDR0_DQ13 DDR0_DQ12 DDR0_DQ8 VDDSHV1 VSS VDD_CORE VSS VDD_CORE VSS VDDA_PLL0 VSS CAP_VDDS3 VSS GPMC0_WPn GPMC0_DIR OSPI0_D6 OSPI0_DQS OSPI0_CLK
_LBCLKO
DDR0_DQS1
M DDR0_DM1 DDR0_DQ11 DDR0_DQ14 DDR0_A12 VSS VDDSHV1 VSS VDD_CORE VSS VDD_CORE VSS VDDR_CORE VDDSHV4 VDDSHV4 CAP_VDDS4 OSPI0_D7 OSPI0_D1 OSPI0_D0 OSPI0_D2 OSPI0_D3
_n
DDR0_CAS VDDS_DDR
J DDR0_A11 DDR0_A6 DDR0_A8 DDR0_A9 VDDS_DDR VSS VSS VDD_CORE VDDA_PLL2 VDD_CORE VDDA_ADC VSS ADC0_REFP ADC0_REFN MMC0_DAT3 MMC0_DAT2 MMC1_CMD MMC0_DAT1 MMC0_CMD
_n _C
DDR0_CK0 DDR0_CS0 DDR0_CS1 MCU_SPI0 MCU_SPI0 MCU_UART0 MCU_I2C0 VMON_1P8 UART1 RESET USB0
E DDR0_A2 DDR0_ODT0 EMU1 VSS VSS UART1_TXD UART1_RXD PORz_OUT ADC0_AIN7 ADC0_AIN2
_n _n _n _CLK _D0 _RTSn _SCL _SOC _RTSn _REQz _DRVVBUS
DDR0_DQS0 MCU_SPI0 MCU_SPI1 MCU_UART1 MCU_UART1 MCU_I2C1 MCU MCU_RESETS UART0 MCU_OSC0
B DDR0_DM0 DDR0_DQ4 DDR0_DQ7 DDR0_DQ2 TCK SPI1_CS0 SPI1_D0 MCAN0_RX I2C0_SDA I2C1_SDA MCU_PORz
_n _D1 _CS1 _CTSn _RTSn _SDA _RESETz TATz _CTSn _XO
Not to scale
2. BALL NAME: Ball name assigned to each terminal of the Ball Grid Array package (this name is typically
taken from the primary MUXMODE 0 signal function).
3. SIGNAL NAME: Signal name(s) of all dedicated and pin multiplexed signal functions associated with a ball.
Note
Many device pins support multiple signal functions. Some signal functions are selected via a
single layer of multiplexers associated with pins. Other signal functions are selected via two or
more layers of multiplexers, where one layer is associated with the pins and other layers are
associated with peripheral logic functions.
Table 6-1, Pin Attributes only defines signal multiplexing at the pins. For more information,
related to signal multiplexing at the pins, see the Pad Configuration Registers section in the
Device Configuration chapter of the device TRM. For information associated with peripheral signal
multiplexing, see the respective peripheral chapter in the device TRM.
4. MUX MODE: The MUXMODE value associated with each pin multiplexed signal function:
a. MUXMODE 0 is the primary pin multiplexed signal function. However, the primary pin multiplexed signal
function is not necessarily the default pin multiplexed signal function.
Note
The value found in the MUX MODE AFTER RESET column defines the default pin
multiplexed signal function selected when MCU_PORz is deasserted.
b. MUXMODE values 1 through 15 are possible for pin multiplexed signal functions. However, not all
MUXMODE values have been implemented. The only valid MUXMODE values are those defined as pin
multiplexed signal functions within the Pin Attributes table. Only valid values of MUXMODE should be
used.
c. Bootstrap defines SOC configuration pins, where the logic state applied to each pin is latched on the
rising edge of PORz_OUT. These input signal functions are fixed to their respective pins and are not
programmable via MUXMODE.
d. An empty box means Not Applicable.
Note
The following configurations of MUXMODE must be avoided for proper device operation.
• Configuring multiple pins operating as inputs to the same pin multiplexed signal function is not
supported as it can yield unexpected results.
• Configuring a pin to an undefined pin multiplexing mode will cause the pin behavior to be
undefined.
10. I/O OPERATING VOLTAGE: This column describes I/O operating voltage options of the respective power
supply, when applicable.
An empty box means Not Applicable.
For more information, see valid operating voltage range(s) defined for each power supply in Section 7.4,
Recommended Operating Conditions.
11. POWER: The power supply of the associated I/O, when applicable.
An empty box means Not Applicable.
12. HYS: Indicates if the input buffer associated with this I/O has hysteresis:
• Yes: With hysteresis
• No: Without hysteresis
• An empty box means Not Applicable.
For more information, see the hysteresis values in Section 7.7, Electrical Characteristics.
13. BUFFER TYPE: This column defines the buffer type associated with a terminal. This information can be
used to determine which Electrical Characteristics table is applicable.
An empty box means Not Applicable.
For electrical characteristics, refer to the appropriate buffer type table in Section 7.7, Electrical
Characteristics.
14. PULL UP/DOWN TYPE: Indicates the presence of an internal pullup or pulldown resistor. Pullup and
pulldown resistors can be enabled or disabled via software.
• PU: Internal pull-up
• PD: Internal pull-down
• PU/PD: Internal pull-up and pull-down
• An empty box means No internal pull.
15. PADCONFIG Register:Name of the IO pad configuration register associated with Ball.
16. PADCONFIG Address:Physical address of the IO pad configuration register associated with Ball.
D10 PADCONFIG: EMU0 0 IO 1 On / Off / Up On / Off / Up 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG31
0x0408407C
EMU1 EMU1 0 IO 1
E10 PADCONFIG: On / Off / Up On / Off / Up 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG32 MCU_OBSCLK0 15 O
0x04084080
EXTINTn EXTINTn 0 I 1
C19 PADCONFIG: Off / Off / NA Off / Off / NA 7 1.8 V/3.3 V VDDSHV0 Yes I2C OD FS
PADCONFIG158 GPIO1_70 7 IOD pad
0x000F4278
EXT_REFCLK1 0 I 0
EXT_REFCLK1 SYNC1_OUT 1 O
A19 PADCONFIG: SPI2_CS3 2 IO 1 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG157
0x000F4274 CLKOUT0 5 O
GPIO1_69 7 IO pad
GPMC0_ADVn_ALE 0 O
FSI_RX5_CLK 1 I 0
GPMC0_ADVn_ALE UART5_RXD 2 I 1
P16 PADCONFIG: EHRPWM_TZn_IN3 3 I 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV3 Yes LVCMOS PU/PD
PADCONFIG33
0x000F4084 TRC_DATA15 6 O
GPIO0_32 7 IO pad
PRG0_PWM3_TZ_IN 9 I 0
GPMC0_CLK 0 O 0
FSI_RX4_CLK 1 I 0
UART4_RTSn 2 O
GPMC0_CLK
EHRPWM3_SYNCO 3 O
R17 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV3 Yes LVCMOS PU/PD
PADCONFIG31 GPMC0_FCLK_MUX 4 O
0x000F407C
TRC_DATA14 6 O
GPIO0_31 7 IO pad
PRG0_PWM3_TZ_OUT 9 O
A11 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG20 MCU_GPIO0_20 7 IO pad
0x04084050
MCU_I2C1_SDA MCU_I2C1_SDA 0 IOD 1
B10 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG21 MCU_GPIO0_21 7 IO pad
0x04084054
C21 MCU_OSC0_XI MCU_OSC0_XI I 1.8 V VDDS_OSC Yes HFOSC
B20 MCU_OSC0_XO MCU_OSC0_XO O 1.8 V VDDS_OSC Yes HFOSC
MCU_PORz
B13 PADCONFIG: Off / Low / Off Off / SS / Off 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG24 MCU_GPIO0_22 7 IO pad
0x04084060
MCU_RESETz
B12 PADCONFIG: MCU_RESETz 0 I On / Off / Up On / Off / Up 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG22
0x04084058
MCU_SAFETY_ERRORn
A20 PADCONFIG: MCU_SAFETY_ERRORn 0 IO Off / Off / Down On / SS / Down 0 1.8 V VDDS_OSC Yes LVCMOS PU/PD
MCU_PADCONFIG25
0x04084064
MCU_SPI0_CLK MCU_SPI0_CLK 0 IO 0
E6 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG2 MCU_GPIO0_11 7 IO pad
0x04084008
MCU_SPI1_CLK MCU_SPI1_CLK 0 IO 0
D7 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG7 MCU_GPIO0_7 7 IO pad
0x0408401C
MCU_SPI0_CS0 MCU_SPI0_CS0 0 IO 1
D6 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG0 MCU_GPIO0_13 7 IO pad
0x04084000
MCU_SPI0_CS1 0 IO 1
MCU_SPI0_CS1
MCU_OBSCLK0 1 O
C6 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG1 MCU_SYSCLKOUT0 2 O
0x04084004
MCU_GPIO0_12 7 IO pad
E7 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG3 MCU_GPIO0_10 7 IO pad
0x0408400C
MCU_SPI0_D1 MCU_SPI0_D1 0 IO 0
B6 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG4 MCU_GPIO0_4 7 IO pad
0x04084010
MCU_SPI1_CS0 MCU_SPI1_CS0 0 IO 1
A7 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG5 MCU_GPIO0_5 7 IO pad
0x04084014
MCU_SPI1_CS1 MCU_SPI1_CS1 0 IO 1
B7 PADCONFIG: MCU_EXT_REFCLK0 1 I 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG6
0x04084018 MCU_GPIO0_6 7 IO pad
MCU_SPI1_D0 MCU_SPI1_D0 0 IO 0
C7 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG8 MCU_GPIO0_8 7 IO pad
0x04084020
MCU_SPI1_D1 MCU_SPI1_D1 0 IO 0
C8 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG9 MCU_GPIO0_9 7 IO pad
0x04084024
MCU_UART0_CTSn 0 I 1
MCU_UART0_CTSn
MCU_TIMER_IO0 1 IO 0
D8 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG12 MCU_SPI0_CS2 2 IO 1
0x04084030
MCU_GPIO0_1 7 IO pad
MCU_UART0_RTSn 0 O
MCU_UART0_RTSn
MCU_TIMER_IO1 1 IO 0
E8 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG13 MCU_SPI1_CS2 2 IO 1
0x04084034
MCU_GPIO0_0 7 IO pad
MCU_UART0_RXD MCU_UART0_RXD 0 I 1
A9 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG10 MCU_GPIO0_3 7 IO pad
0x04084028
MCU_UART0_TXD MCU_UART0_TXD 0 O
A8 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG11 MCU_GPIO0_2 7 IO pad
0x0408402C
C9 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG14 MCU_GPIO0_14 7 IO pad
0x04084038
MCU_UART1_TXD MCU_UART1_TXD 0 O
D9 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG15 MCU_GPIO0_15 7 IO pad
0x0408403C
VDDS_MMC0,
F18 MMC0_CALPAD MMC0_CALPAD A 1.8 V VDD_MMC0, eMMCPHY
VDD_DLL_MMC0
VDDS_MMC0,
G18 MMC0_CLK MMC0_CLK IO On / Low / Off On / SS / Off 1.8 V VDD_MMC0, eMMCPHY PU/PD
VDD_DLL_MMC0
VDDS_MMC0,
J21 MMC0_CMD MMC0_CMD IO On / Off / Up On / SS / Up 1.8 V VDD_MMC0, eMMCPHY PU/PD
VDD_DLL_MMC0
VDDS_MMC0,
G19 MMC0_DS MMC0_DS IO On / Off / Down On / Off / Down 1.8 V VDD_MMC0, eMMCPHY PU/PD
VDD_DLL_MMC0
MMC1_CLK 0 IO
MMC1_CLK UART2_CTSn 1 I 1
L20 PADCONFIG: TIMER_IO4 2 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV5 Yes SDIO PU/PD
PADCONFIG163
0x000F428C UART4_RXD 3 I 1
GPIO1_75 7 IO pad
MMC1_CMD 0 IO 1
MMC1_CMD UART2_RTSn 1 O
J19 PADCONFIG: TIMER_IO5 2 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV5 Yes SDIO PU/PD
PADCONFIG165
0x000F4294 UART4_TXD 3 O
GPIO1_76 7 IO pad
N20 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG0 GPIO0_0 7 IO pad
0x000F4000
OSPI0_DQS OSPI0_DQS 0 I 0
N19 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG2 GPIO0_2 7 IO pad
0x000F4008
OSPI0_LBCLKO OSPI0_LBCLKO 0 IO 0
N21 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG1 GPIO0_1 7 IO pad
0x000F4004
OSPI0_CSn0 OSPI0_CSn0 0 O
L19 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG11 GPIO0_11 7 IO pad
0x000F402C
OSPI0_CSn1 OSPI0_CSn1 0 O
L18 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG12 GPIO0_12 7 IO pad
0x000F4030
OSPI0_CSn2 OSPI0_CSn2 0 O
K17 PADCONFIG: OSPI0_RESET_OUT1 2 O Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG13
0x000F4034 GPIO0_13 7 IO pad
M19 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG3 GPIO0_3 7 IO pad
0x000F400C
OSPI0_D1 OSPI0_D1 0 IO 0
M18 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG4 GPIO0_4 7 IO pad
0x000F4010
OSPI0_D2 OSPI0_D2 0 IO 0
M20 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG5 GPIO0_5 7 IO pad
0x000F4014
OSPI0_D3 OSPI0_D3 0 IO 0
M21 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG6 GPIO0_6 7 IO pad
0x000F4018
OSPI0_D4 OSPI0_D4 0 IO 0
P21 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG7 GPIO0_7 7 IO pad
0x000F401C
OSPI0_D5 OSPI0_D5 0 IO 0
P20 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG8 GPIO0_8 7 IO pad
0x000F4020
OSPI0_D6 OSPI0_D6 0 IO 0
N18 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG9 GPIO0_9 7 IO pad
0x000F4024
OSPI0_D7 OSPI0_D7 0 IO 0
M17 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV4 Yes LVCMOS PU/PD
PADCONFIG10 GPIO0_10 7 IO pad
0x000F4028
PORz_OUT
E17 PADCONFIG: PORz_OUT 0 O Off / Low / Off Off / SS / Off 0 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG171
0x000F42AC
PRG0_MDIO0_MDC PRG0_MDIO0_MDC 0 O
P3 PADCONFIG: GPIO1_41 7 IO pad Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV1 Yes LVCMOS PU/PD
PADCONFIG129
0x000F4204 GPMC0_A13 9 OZ
P2 PADCONFIG: GPIO1_40 7 IO pad Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV1 Yes LVCMOS PU/PD
PADCONFIG128
0x000F4200 GPMC0_A12 9 OZ
PRG0_PRU0_GPO0 0 IO 0
PRG0_PRU0_GPI0 1 I 0
PRG0_PRU0_GPO0
PRG0_RGMII1_RD0 2 I 0
Y1 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV1 Yes LVCMOS PU/PD
PADCONFIG88 PRG0_PWM3_A0 3 IO 0
0x000F4160
GPIO1_0 7 IO pad
UART2_CTSn 10 I 1
PRG0_PRU0_GPO1 0 IO 0
PRG0_PRU0_GPI1 1 I 0
PRG0_PRU0_GPO1
PRG0_RGMII1_RD1 2 I 0
R4 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV1 Yes LVCMOS PU/PD
PADCONFIG89 PRG0_PWM3_B0 3 IO 1
0x000F4164
GPIO1_1 7 IO pad
UART2_TXD 10 O
PRG0_PRU0_GPO2 0 IO 0
PRG0_PRU0_GPI2 1 I 0
PRG0_PRU0_GPO2 PRG0_RGMII1_RD2 2 I 0
U2 PADCONFIG: PRG0_PWM2_A0 3 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV1 Yes LVCMOS PU/PD
PADCONFIG90
0x000F4168 GPIO1_2 7 IO pad
GPMC0_A0 9 OZ
UART2_RTSn 10 O
PRG0_PRU0_GPO3 0 IO 0
PRG0_PRU0_GPI3 1 I 0
PRG0_PRU0_GPO3
PRG0_RGMII1_RD3 2 I 0
V2 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV1 Yes LVCMOS PU/PD
PADCONFIG91 PRG0_PWM3_A2 3 IO 0
0x000F416C
GPIO1_3 7 IO pad
UART3_CTSn 10 I 1
PRG0_PRU0_GPO4 0 IO 0
PRG0_PRU0_GPI4 1 I 0
PRG0_PRU0_GPO4 PRG0_RGMII1_RX_CTL 2 I 0
AA2 PADCONFIG: PRG0_PWM2_B0 3 IO 1 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV1 Yes LVCMOS PU/PD
PADCONFIG92
0x000F4170 GPIO1_4 7 IO pad
GPMC0_A1 9 OZ
UART3_TXD 10 O
Y6 PADCONFIG: MDIO0_MDC 4 O Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV2 Yes LVCMOS PU/PD
PADCONFIG87
0x000F415C GPIO0_86 7 IO pad
PRG1_MDIO0_MDIO PRG1_MDIO0_MDIO 0 IO 0
AA6 PADCONFIG: MDIO0_MDIO 4 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV2 Yes LVCMOS PU/PD
PADCONFIG86
0x000F4158 GPIO0_85 7 IO pad
F16 PADCONFIG: RESETSTATz 0 O Off / Low / Off Off / SS / Off 0 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG169
0x000F42A4
RESET_REQz
E18 PADCONFIG: RESET_REQz 0 I On / Off / Up On / Off / Up 0 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG168
0x000F42A0
H16 RSVD0 RSVD0 N/A
D21 RSVD1 RSVD1 N/A
G13 RSVD2 RSVD2 N/A
F17 RSVD3 RSVD3 N/A
W15 RSVD4 RSVD4 N/A
V16 RSVD5 RSVD5 N/A
K2 RSVD6 RSVD6 N/A
K1 RSVD7 RSVD7 N/A
F12 RSVD8 RSVD8 N/A
D13 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG132 GPIO1_44 7 IO pad
0x000F4210
SPI1_CLK SPI1_CLK 0 IO 0
C14 PADCONFIG: EHRPWM6_SYNCI 3 I 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG137
0x000F4224 GPIO1_49 7 IO pad
D12 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG130 GPIO1_42 7 IO pad
0x000F4208
SPI0_CS1 0 IO 1
CPTS0_TS_COMP 1 O
I2C2_SCL 2 IOD 1
SPI0_CS1
TIMER_IO10 3 IO 0
C13 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG131 PRG0_IEP0_EDIO_OUTVALID 4 O
0x000F420C
UART6_RXD 5 I 1
ADC_EXT_TRIGGER0 6 I 0
GPIO1_43 7 IO pad
SPI0_D0 SPI0_D0 0 IO 0
A13 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG133 GPIO1_45 7 IO pad
0x000F4214
SPI0_D1 SPI0_D1 0 IO 0
A14 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG134 GPIO1_46 7 IO pad
0x000F4218
SPI1_CS0 SPI1_CS0 0 IO 1
B14 PADCONFIG: EHRPWM6_A 3 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG135
0x000F421C GPIO1_47 7 IO pad
SPI1_CS1 0 IO 1
CPTS0_TS_SYNC 1 O
I2C2_SDA 2 IOD 1
SPI1_CS1
PRG1_IEP0_EDIO_OUTVALID 4 O
D14 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG136 UART6_TXD 5 O
0x000F4220
ADC_EXT_TRIGGER1 6 I 0
GPIO1_48 7 IO pad
TIMER_IO11 8 IO 0
SPI1_D0 SPI1_D0 0 IO 0
B15 PADCONFIG: EHRPWM6_SYNCO 3 O Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG138
0x000F4228 GPIO1_50 7 IO pad
SPI1_D1 SPI1_D1 0 IO 0
A15 PADCONFIG: EHRPWM6_B 3 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG139
0x000F422C GPIO1_51 7 IO pad
B11 PADCONFIG: TCK 0 I On / Off / Up On / Off / Up 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG26
0x04084068
TDI
C11 PADCONFIG: TDI 0 I On / Off / Up On / Off / Up 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG28
0x04084070
TDO
A12 PADCONFIG: TDO 0 OZ Off / Off / Up Off / SS / Up 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG29
0x04084074
TMS
C12 PADCONFIG: TMS 0 I On / Off / Up On / Off / Up 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG30
0x04084078
TRSTn
D11 PADCONFIG: TRSTn 0 I On / Off / Down On / Off / Down 0 1.8 V/3.3 V VDDSHV_MCU Yes LVCMOS PU/PD
MCU_PADCONFIG27
0x0408406C
UART0_CTSn 0 I 1
SPI0_CS2 1 IO 1
ADC_EXT_TRIGGER0 2 I 0
UART0_CTSn UART2_RXD 3 I 1
B16 PADCONFIG: TIMER_IO6 4 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG142
0x000F4238 SPI4_CLK 6 IO 0
GPIO1_54 7 IO pad
EQEP0_S 8 IO 0
CP_GEMAC_CPTS0_TS_SYNC 9 O
UART0_RTSn 0 O
SPI0_CS3 1 IO 1
UART0_RTSn UART2_TXD 3 O
A16 PADCONFIG: TIMER_IO7 4 IO 0 Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG143
0x000F423C SPI4_D0 6 IO 0
GPIO1_55 7 IO pad
EQEP0_I 8 IO 0
UART0_RXD 0 I 1
UART0_RXD
SPI2_D0 2 IO 0
D15 PADCONFIG: Off / Off / Off Off / Off / Off 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG140 GPIO1_52 7 IO pad
0x000F4230
EQEP0_A 8 I 0
E19 PADCONFIG: Off / Off / Down Off / Off / Down 7 1.8 V/3.3 V VDDSHV0 Yes LVCMOS PU/PD
PADCONFIG170 GPIO1_79 7 IO pad
0x000F42A8
VDDA_3P3_USB0,
U16 USB0_ID USB0_ID A 1.8 V/3.3 V VDDA_1P8_USB0, USB2PHY
VDDA_0P85_USB0
VDDA_3P3_USB0,
U17 USB0_RCALIB USB0_RCALIB A 1.8 V/3.3 V VDDA_1P8_USB0, USB2PHY
VDDA_0P85_USB0
VDDA_3P3_USB0,
T14 USB0_VBUS USB0_VBUS A 1.8 V/3.3 V VDDA_1P8_USB0, USB2PHY
VDDA_0P85_USB0
P12, P13 VDDA_0P85_SERDES0 VDDA_0P85_SERDES0 PWR
P11 VDDA_0P85_SERDES0_C VDDA_0P85_SERDES0_C PWR
T12 VDDA_0P85_USB0 VDDA_0P85_USB0 PWR
R14 VDDA_1P8_SERDES0 VDDA_1P8_SERDES0 PWR
R15 VDDA_1P8_USB0 VDDA_1P8_USB0 PWR
H15 VDDA_3P3_SDIO VDDA_3P3_SDIO PWR
R13 VDDA_3P3_USB0 VDDA_3P3_USB0 PWR
J13 VDDA_ADC VDDA_ADC PWR
K12 VDDA_MCU VDDA_MCU PWR
N12 VDDA_PLL0 VDDA_PLL0 PWR
H9 VDDA_PLL1 VDDA_PLL1 PWR
J11 VDDA_PLL2 VDDA_PLL2 PWR
G11 VDDA_TEMP0 VDDA_TEMP0 PWR
L11 VDDA_TEMP1 VDDA_TEMP1 PWR
L10, M13 VDDR_CORE VDDR_CORE PWR
F11, G12,
VDDSHV0 VDDSHV0 PWR
G14
M7, N6, P7 VDDSHV1 VDDSHV1 PWR
R10, R8, T9 VDDSHV2 VDDSHV2 PWR
P14, P15 VDDSHV3 VDDSHV3 PWR
M14, M15 VDDSHV4 VDDSHV4 PWR
L14, L15 VDDSHV5 VDDSHV5 PWR
F9, G10, G8 VDDSHV_MCU VDDSHV_MCU PWR
F7, G6, H7,
VDDS_DDR VDDS_DDR PWR
J6, K7, L6
J8 VDDS_DDR_C VDDS_DDR_C PWR
K14 VDDS_MMC0 VDDS_MMC0 PWR
H13 VDDS_OSC VDDS_OSC PWR
Note
Signal names and descriptions provided in each Signal Descriptions table, represent the pin
multiplexed signal function which is implemented at the pin and selected via PADCONFIG
registers. Device subsystems may provide secondary multiplexing of signal functions, which are
not described in these tables. For more information on secondary multiplexed signal functions,
see the respective peripheral chapter of the device TRM.
Note
The ADC can be configured to operate as eight general-purpose digital inputs. For more information,
see Analog-to-Digital Converter (ADC) section in Peripherals chapter in the device TRM.
(1) The General Purpose Input signal associated with this ADC0_AIN input has a debounce function when ADC0 is configured to operate
in GPI mode. For more information on configuring ADC0 to operate in GPI mode, see the TRM Analog-to-Digital Converter (ADC)
section in the Peripherals chapter. For more information on I/O Debounce configuration, see the TRM Device Configuration chapter.
(2) The ADC0_AIN[7:0] inputs only have hysterisis when ADC0 is configured to operate in GPI mode.
(3) Any unused ADC0_AIN inputs must be pulled to VSS through a resistor or connected directly to VSS when VDDA_ADC is connected
to a power source.
(4) The ADC0_REFP and ADC0_REFN reference inputs are analog inputs which must be treated like high transient power supply rails,
where ADC0_REFN is expected to be connected directly to the PCB ground plane along with all other VSS pins, and ADC0_REFP is
connected to a power source capable of providing at least 4mA of current. ADC0_REFP may be connected to the same power source
as VDDA_ADC0 if the voltage tolerance of the supply provides an acceptable accuracy for the ADC reference. A high frequency
decoupling capacitor must be connected directly between ADC0_REFP and ADC0_REFN. The high frequency decoupling capacitor
should be placed in the ball array on the back side of the PCB and connected directly to the ADC0_REFP and ADC0_REFN pins with
vias. ADC0_REFP may be connected to VSS if ADC0 is not used and VDDA_ADC0 has been connected to VSS. The high frequency
decoupling capacitor described above will not be required if ADC0 is not used and ADC0_REFP is connected to VSS. See the Pin
Connectivity Requirements section for more information on ADC0 connectivity.
6.3.2 CPSW3G
6.3.2.1 MAIN Domain
Table 6-3. CPSW3G0 RGMII1 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
RGMII1_RXC I RGMII Receive Clock AA5, W13
RGMII1_RX_CTL I RGMII Receive Control V13, W6
RGMII1_TXC IO RGMII Transmit Clock U14
RGMII1_TX_CTL O RGMII Transmit Control U15
RGMII1_RD0 I RGMII Receive Data 0 AA13, W5
RGMII1_RD1 I RGMII Receive Data 1 U12, Y5
RGMII1_RD2 I RGMII Receive Data 2 V6, Y13
RGMII1_RD3 I RGMII Receive Data 3 V12, V5
RGMII1_TD0 O RGMII Transmit Data 0 V15
RGMII1_TD1 O RGMII Transmit Data 1 V14
RGMII1_TD2 O RGMII Transmit Data 2 W14
RGMII1_TD3 O RGMII Transmit Data 3 AA14
6.3.3 CPTS
6.3.3.1 MAIN Domain
Table 6-6. CP GEMAC CPTS0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
CP_GEMAC_CPTS0_RFT_CLK I CPTS Reference Clock Input to CPSW3G0 CPTS D18
CPTS Time Stamp Counter Compare Output from
CP_GEMAC_CPTS0_TS_COMP
O CPSW3G0 CPTS E15, K18, W1
CPTS Time Stamp Counter Bit Output from CPSW3G0 B16, D16, K19,
CP_GEMAC_CPTS0_TS_SYNC
O CPTS U1
CPTS Hardware Time Stamp Push Input to CPSW3G0
CP_GEMAC_CPTS0_HW1TSPUSH
I CPTS E14, L21, V1
CPTS Hardware Time Stamp Push Input to CPSW3G0
CP_GEMAC_CPTS0_HW2TSPUSH
I CPTS E16, K21, T1
6.3.4 DDRSS
6.3.4.1 MAIN Domain
Table 6-8. DDRSS0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
DDR0_ACT_n O DDRSS Activation Command H2
DDR0_ALERT_n IO DDRSS Alert H1
DDR0_CAS_n O DDRSS Column Address Strobe J5
DDR0_PAR O DDRSS Command and Address Parity K5
DDR0_RAS_n O DDRSS Row Address Strobe F6
DDR0_WE_n O DDRSS Write Enable H4
DDR0_A0 O DDRSS Address Bus D2
DDR0_A1 O DDRSS Address Bus C5
DDR0_A2 O DDRSS Address Bus E2
DDR0_A3 O DDRSS Address Bus D4
DDR0_A4 O DDRSS Address Bus D3
DDR0_A5 O DDRSS Address Bus F2
DDR0_A6 O DDRSS Address Bus J2
DDR0_A7 O DDRSS Address Bus L5
DDR0_A8 O DDRSS Address Bus J3
DDR0_A9 O DDRSS Address Bus J4
DDR0_A10 O DDRSS Address Bus K3
DDR0_A11 O DDRSS Address Bus J1
DDR0_A12 O DDRSS Address Bus M5
DDR0_A13 O DDRSS Address Bus K4
DDR0_BA0 O DDRSS Bank Address G4
DDR0_BA1 O DDRSS Bank Address G5
DDR0_BG0 O DDRSS Bank Group G2
DDR0_BG1 O DDRSS Bank Group H3
DDR0_CAL0 (1) A IO Pad Calibration Resistor H5
DDR0_CK0 O DDRSS Clock F1
DDR0_CK0_n O DDRSS Negative Clock E1
DDR0_CKE0 O DDRSS Clock Enable F4
DDR0_CKE1 O DDRSS Clock Enable F3
DDR0_CS0_n O DDRSS Chip Select 0 E3
DDR0_CS1_n O DDRSS Chip Select 1 E4
DDR0_DM0 IO DDRSS Data Mask B2
DDR0_DM1 IO DDRSS Data Mask M2
DDR0_DQ0 IO DDRSS Data A3
DDR0_DQ1 IO DDRSS Data A2
DDR0_DQ2 IO DDRSS Data B5
DDR0_DQ3 IO DDRSS Data A4
(1) An external 240 Ω ±1% resistor must be connected between this pin and VSS. The maximum power dissipation for the resistor is
5.2mW. No external voltage should be applied to this pin.
6.3.5 ECAP
6.3.5.1 MAIN Domain
Table 6-9. ECAP0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
Enhanced Capture (ECAP) Input or Auxiliary PWM
ECAP0_IN_APWM_OUT
IO (APWM) Output D18
6.3.7 EPWM
6.3.7.1 MAIN Domain
Table 6-14. EPWM Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
EHRPWM_SOCA O EHRPWM Start of Conversion A C17
EHRPWM_SOCB O EHRPWM Start of Conversion B D17
EHRPWM_TZn_IN0 I EHRPWM Trip Zone Input 0 (active low) T18
EHRPWM_TZn_IN1 I EHRPWM Trip Zone Input 1 (active low) V21
EHRPWM_TZn_IN2 I EHRPWM Trip Zone Input 2 (active low) R16, R20
EHRPWM_TZn_IN3 I EHRPWM Trip Zone Input 3 (active low) P16
6.3.8 EQEP
6.3.8.1 MAIN Domain
Table 6-24. EQEP0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
EQEP0_A (1) I EQEP Quadrature Input A D15, N16, Y2
EQEP0_B (1) I EQEP Quadrature Input B C16, N17, W2
EQEP0_I (1) IO EQEP Index A16, R20, T6, Y5
EQEP0_S (1) IO EQEP Strobe B16, R19, V3
(1) This EQEP input signal has a debounce function. For more information on I/O Debounce configuration, see the TRM Device
Configuration chapter.
(1) This EQEP input signal has a debounce function. For more information on I/O Debounce configuration, see the TRM Device
Configuration chapter.
(1) This EQEP input signal has a debounce function. For more information on I/O Debounce configuration, see the TRM Device
Configuration chapter.
6.3.9 FSI
6.3.9.1 MAIN Domain
Table 6-27. FSI0 RX Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
FSI_RX0_CLK I FSI Clock V19
FSI_RX0_D0 I FSI Data T17
FSI_RX0_D1 I FSI Data R16
6.3.10 GPIO
6.3.10.1 MAIN Domain
Table 6-35. GPIO0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
GPIO0_0 IO General Purpose Input/Output N20
(1) This GPIO input signal has a debounce function. For more information on I/O Debounce configuration, see the TRM Device
Configuration chapter.
(1) This GPIO input signal has a debounce function. For more information on I/O Debounce configuration, see the TRM Device
Configuration chapter.
(1) This GPIO input signal has a debounce function. For more information on I/O Debounce configuration, see the TRM Device
Configuration chapter.
6.3.11 GPMC
6.3.11.1 MAIN Domain
Table 6-38. GPMC0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
GPMC Address Valid (active low) or Address Latch
GPMC0_ADVn_ALE
O Enable P16
GPMC0_CLK (1) O GPMC clock R17
GPMC0_DIR O GPMC Data Bus Signal Direction Control N17
GPMC functional clock output selected through a mux
GPMC0_FCLK_MUX
O logic R17
GPMC Output Enable (active low) or Read Enable
GPMC0_OEn_REn
O (active low) R18
GPMC0_WEn O GPMC Write Enable (active low) T21
GPMC0_WPn O GPMC Flash Write Protect (active low) N16
GPMC Address 0 Output. Only used to effectively
GPMC0_A0
OZ address 8-bit data non-multiplexed memories U2, U7
GPMC address 1 Output in A/D non-multiplexed mode
GPMC0_A1
OZ and Address 17 in A/D multiplexed mode AA2, V7
GPMC address 2 Output in A/D non-multiplexed mode
GPMC0_A2
OZ and Address 18 in A/D multiplexed mode T2, W7
GPMC address 3 Output in A/D non-multiplexed mode
GPMC0_A3
OZ and Address 19 in A/D multiplexed mode V4, W11
GPMC address 4 Output in A/D non-multiplexed mode
GPMC0_A4
OZ and Address 20 in A/D multiplexed mode U4, V11
GPMC address 5 Output in A/D non-multiplexed mode
GPMC0_A5
OZ and Address 21 in A/D multiplexed mode AA12, V1
GPMC address 6 Output in A/D non-multiplexed mode
GPMC0_A6
OZ and Address 22 in A/D multiplexed mode W1, Y12
(1) The RXACTIVE bit of the CTRLMMR_PADCONFIG32 register must be set to 0x1 and the TX_DIS bit of the
CTRLMMR_PADCONFIG32 register must be reset to 0x0 when GPMC0 is operating in synchronous mode.
6.3.12 I2C
6.3.12.1 MAIN Domain
Table 6-39. I2C0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
I2C0_SCL IOD I2C Clock A18
I2C0_SDA IOD I2C Data B18
6.3.13 MCAN
6.3.13.1 MAIN Domain
Table 6-45. MCAN0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
MCAN0_RX I MCAN Receive Data B17
MCAN0_TX O MCAN Transmit Data A17
6.3.14 MCSPI
6.3.14.1 MAIN Domain
Table 6-47. MCSPI0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
SPI0_CLK IO SPI Clock D13
SPI0_CS0 IO SPI Chip Select 0 D12
SPI0_CS1 IO SPI Chip Select 1 C13
SPI0_CS2 IO SPI Chip Select 2 B16
SPI0_CS3 IO SPI Chip Select 3 A16
SPI0_D0 IO SPI Data 0 A13
SPI0_D1 IO SPI Data 1 A14
6.3.15 MDIO
6.3.15.1 MAIN Domain
Table 6-54. MDIO0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
MDIO0_MDC O MDIO Clock R2, Y6
MDIO0_MDIO IO MDIO Data AA6, P5
6.3.16 MMC
6.3.16.1 MAIN Domain
Table 6-55. MMC0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
MMC0_CALPAD (1) A MMC/SD/SDIO Calibration Resistor F18
MMC0_CLK IO MMC/SD/SDIO Clock G18
MMC0_CMD IO MMC/SD/SDIO Command J21
MMC0_DS IO MMC Data Strobe G19
MMC0_DAT0 IO MMC/SD/SDIO Data K20
MMC0_DAT1 IO MMC/SD/SDIO Data J20
MMC0_DAT2 IO MMC/SD/SDIO Data J18
MMC0_DAT3 IO MMC/SD/SDIO Data J17
MMC0_DAT4 IO MMC/SD/SDIO Data H17
MMC0_DAT5 IO MMC/SD/SDIO Data H19
MMC0_DAT6 IO MMC/SD/SDIO Data H18
MMC0_DAT7 IO MMC/SD/SDIO Data G17
(1) An external 10 kΩ ±1% resistor must be connected between this pin and VSS. No external voltage should be applied to this pin.
(1) For MMC1_CLK signal to work properly, the RXACTIVE bit of the CTRLMMR_PADCONFIG164 register must remain in its default state
of 0x1 because of retiming purposes.
6.3.17 OSPI
6.3.17.1 MAIN Domain
Table 6-57. OSPI0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
OSPI0_CLK O OSPI Clock N20
OSPI0_DQS I OSPI Data Strobe (DQS) or Loopback Clock Input N19
OSPI0_ECC_FAIL I OSPI ECC Status L17
OSPI0_LBCLKO IO OSPI Loopback Clock Output N21
OSPI0_CSn0 O OSPI Chip Select 0 (active low) L19
OSPI0_CSn1 O OSPI Chip Select 1 (active low) L18
OSPI0_CSn2 O OSPI Chip Select 2 (active low) K17
OSPI0_CSn3 O OSPI Chip Select 3 (active low) L17
OSPI0_D0 IO OSPI Data 0 M19
OSPI0_D1 IO OSPI Data 1 M18
OSPI0_D2 IO OSPI Data 2 M20
OSPI0_D3 IO OSPI Data 3 M21
OSPI0_D4 IO OSPI Data 4 P21
OSPI0_D5 IO OSPI Data 5 P20
OSPI0_D6 IO OSPI Data 6 N18
OSPI0_D7 IO OSPI Data 7 M17
OSPI0_RESET_OUT0 O OSPI Reset L17
OSPI0_RESET_OUT1 O OSPI Reset K17
(1) This pin must always be connected via a 1-μF capacitor to VSS.
(2) This pin must always be connected via a 3.3-μF ±20% capacitor to VSS when the SDIO_LDO is being used to source VDDSHV5.
Otherwise, this pin may be connected directly to VSS when the VDDA_3P3_SDIO pin is also connected directly to VSS.
6.3.19 PRU_ICSSG
Note
The PRU_ICSSG contains a second layer of multiplexing to enable additional functionality on the PRU
GPO and GPI signals. This internal wrapper multiplexing is described in the PRU_ICSSG chapter in
the device TRM.
6.3.20 Reserved
Table 6-61. Reserved Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
RSVD0 N/A Reserved, must be left unconnected H16
RSVD1 N/A Reserved, must be left unconnected D21
RSVD2 N/A Reserved, must be left unconnected G13
RSVD3 N/A Reserved, must be left unconnected F17
RSVD4 N/A Reserved, must be left unconnected W15
RSVD5 N/A Reserved, must be left unconnected V16
RSVD6 N/A Reserved, must be left unconnected K2
RSVD7 N/A Reserved, must be left unconnected K1
RSVD8 N/A Reserved, must be left unconnected F12
6.3.21 SERDES
6.3.21.1 MAIN Domain
Table 6-62. SERDES0 Signal Descriptions
SIGNAL NAME [1] ((2)) PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
PCIE0_CLKREQn IO PCIE Clock Request Signal D16
SERDES0_REXT (1) A External SerDes PHY Calibration Resistor T13
SERDES0_REFCLK0N IO SerDes PHY Reference Clock Input/Output (negative) W16
(1) An external 3.01 kΩ ±1% resistor must be connected between this pin and VSS. No external voltage should be applied to this pin.
(2) The functionality of these pins is controlled by SERDES0_LN0_CTRL_LANE_FUNC_SEL.
6.3.22.2 Clock
6.3.22.2.1 MCU Domain
Table 6-64. MCU Clock Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
MCU_OSC0_XI I High frequency oscillator input C21
MCU_OSC0_XO O High frequency oscillator output B20
6.3.22.3 System
6.3.22.3.1 MAIN Domain
Table 6-65. System Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
RMII Clock Output (50 MHz). This pin is used for clock
CLKOUT0 source to the external PHY and must be routed back to
O the RMII_REF_CLK pin for proper device operation. A19, U13
EXTINTn I External Interrupt C19
6.3.22.4 VMON
Table 6-67. VMON Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
VMON_1P8_MCU A Voltage monitor input for 1.8 V MCU power supply K16
VMON_1P8_SOC A Voltage monitor input for 1.8 V SoC power supply E12
VMON_3P3_MCU A Voltage monitor input for 3.3 V MCU power supply F13
VMON_3P3_SOC A Voltage monitor input for 3.3 V SoC power supply F14
Voltage monitor input, fixed 0.45 V (+/-3%) threshold.
VMON_VSYS Use with external precision voltage divider to monitor a
A higher voltage rail such as the PMIC input supply. K10
6.3.23 TIMER
6.3.23.1 MAIN Domain
Table 6-68. TIMER Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
Timer Inputs and Outputs (not tied to single timer
TIMER_IO0
IO instance) C18, K18
Timer Inputs and Outputs (not tied to single timer
TIMER_IO1
IO instance) B19, K19
Timer Inputs and Outputs (not tied to single timer
TIMER_IO2
IO instance) A17, L21
Timer Inputs and Outputs (not tied to single timer
TIMER_IO3
IO instance) B17, K21
6.3.24 UART
6.3.24.1 MAIN Domain
Table 6-70. UART0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
UART0_CTSn I UART Clear to Send (active low) B16
UART0_DCDn I UART Data Carrier Detect (active low) C17
UART0_DSRn I UART Data Set Ready (active low) D17
UART0_DTRn O UART Data Terminal Ready (active low) A17
UART0_RIn I UART Ring Indicator B17
UART0_RTSn O UART Request to Send (active low) A16
UART0_RXD I UART Receive Data D15
UART0_TXD O UART Transmit Data C16
6.3.25 USB
6.3.25.1 MAIN Domain
Table 6-79. USB0 Signal Descriptions
SIGNAL NAME [1] PIN TYPE [2] DESCRIPTION [3] ALV PIN [4]
USB0_DM IO USB 2.0 Differential Data (negative) AA20
USB0_DP IO USB 2.0 Differential Data (positive) AA19
USB0_DRVVBUS O USB VBUS control output (active high) E19
USB0_ID A USB 2.0 Dual-Role Device Role Select U16
USB0_RCALIB (1) A Pin to connect to calibration resistor U17
USB0_VBUS (2) A USB Level-shifted VBUS Input T14
(1) An external 499 Ω ±1% resistor must be connected between this pin and VSS. The maximum power dissipation for the resistor is
7.2mW. No external voltage should be applied to this pin.
(2) An external resistor divider is required to limit the voltage applied to the device pin. For more information, see Section 9.2.3, USB
VBUS Design Guidelines.
Note
All power balls must be supplied with the voltages specified in the Recommended Operating
Conditions section, unless otherwise specified.
Note
For additional clarification, "leave unconnected" or "no connect" (NC) means no signal traces can be
connected to these device ball numbers.
(1) To determine which power supply is associated with any IO, see the POWER column of the Pin Attributes table.
Note
Internal pull resistors are weak and may not source enough current to maintain a valid logic level
for some operating conditions. This can be the case when connected to components with leakage
to the opposite logic level, or when external noise sources couple to signal traces attached to balls
which are only pulled to a valid logic level by the internal resistor. Therefore, external pull resistors are
recommended to hold a valid logic level on balls with external connections.
Many of the device IOs are turned off by default and external pull resistors may be required to hold
inputs of any attached device in a valid logic state until software initializes the respective IOs. The
state of configurable device IOs are defined in the BALL STATE DURING RESET RX/TX/PULL and
BALL STATE AFTER RESET RX/TX/PULL columns of the Pin Attributes table. Any IO with its input
buffer (RX) turned off is allowed to float without damaging the device. However, any IO with its input
buffer (RX) turned on shall never be allowed to float to any potential between VILSS and VIHSS. The
input buffer can enter a high-current state which could damage the IO cell if allowed to float between
these levels.
7 Specifications
7.1 Absolute Maximum Ratings
(1)(2)
over operating junction temperature range (unless otherwise noted)
PARAMETER MIN MAX UNIT
VDD_CORE Core supply -0.3 1.05 V
VDDR_CORE RAM supply -0.3 1.05 V
VDD_MMC0 MMC0 PHY core supply -0.3 1.05 V
VDD_DLL_MMC0 MMC0 PLL analog supply -0.3 1.05 V
VDDA_0P85_SERDES0 SERDES0 0.85-V analog supply -0.3 1.05 V
VDDA_0P85_SERDES0_C SERDES0 clock 0.85-V analog supply -0.3 1.05 V
VDDA_0P85_USB0 USB0 0.85-V analog supply -0.3 1.05 V
VDDS_DDR DDR PHY IO supply -0.3 1.57 V
VDDS_DDR_C DDR clock IO supply -0.3 1.57 V
VDDS_MMC0 MMC0 PHY IO supply -0.3 1.98 V
VDDS_OSC MCU_OSC0 supply -0.3 1.98 V
VDDA_MCU POR and MCU PLL analog supply -0.3 1.98 V
VDDA_ADC0 ADC0 analog supply -0.3 1.98 V
VDDA_PLL0 Main, PER1, and R5F PLL analog supply -0.3 1.98 V
VDDA_PLL1 ARM and DDR PLL analog supply -0.3 1.98 V
VDDA_PLL2 PER0 PLL analog supply -0.3 1.98 V
VDDA_1P8_SERDES0 SERDES0 1.8-V analog supply -0.3 1.98 V
VDDA_1P8_USB0 USB0 1.8-V analog supply -0.3 1.98 V
VDDA_TEMP0 TEMP0 analog supply -0.3 1.98 V
VDDA_TEMP1 TEMP1 analog supply -0.3 1.98 V
VPP eFuse ROM programming supply -0.3 1.98 V
VDDSHV_MCU IO supply for IO MCU -0.3 3.63 V
VDDSHV0 IO supply for IO group 0 -0.3 3.63 V
VDDSHV1 IO supply for IO group 1 -0.3 3.63 V
VDDSHV2 IO supply for IO group 2 -0.3 3.63 V
VDDSHV3 IO supply for IO group 3 -0.3 3.63 V
VDDSHV4 IO supply for IO group 4 -0.3 3.63 V
VDDSHV5 IO supply for IO group 5 -0.3 3.63 V
VDDA_3P3_USB0 USB0 3.3-V analog supply -0.3 3.63 V
VDDA_3P3_SDIO SDIO 3.3-V analog supply -0.3 3.63 V
MCU_PORz -0.3 3.63 V
MCU_I2C0_SCL, MCU_I2C0_SDA,
I2C0_SCL, I2C0_SDA, and EXTINTn -0.3 1.98(3) V
When operating at 1.8V
MCU_I2C0_SCL, MCU_I2C0_SDA,
I2C0_SCL, I2C0_SDA, and EXTINTn -0.3 3.63(3)
Steady-state max voltage at all fail-safe IO pins When operating at 3.3V
VMON_1P8_MCU, and
-0.3 1.98 V
VMON_1P8_SOC
VMON_3P3_MCU, and
-0.3 3.63 V
VMON_3P3_SOC
VMON_VSYS(4) -0.3 1.98 V
(1) Operation outside the Absolute Maximum Ratings may cause permanent device damage. Absolute Maximum Ratings do not imply
functional operation of the device at these or any other conditions beyond those listed under Recommended Operating Conditions. If
used outside the Section 7.4, Recommended Operating Conditions but within the Absolute Maximum Ratings, the device may not be
fully functional, and this may affect device reliability, functionality, performance, and shorten the device lifetime.
(2) All voltage values are with respect to VSS, unless otherwise noted.
(3) The absolute maximum ratings for these fail-safe pins depends on their IO supply operating voltage. Therefore, this value is also
defined by the maximum VIH value found in the I2C Open-Drain, and Fail-Safe (I2C OD FS) Electrical Characteristics section, where
the electrical characteristics table has separate parameter values for 1.8-V mode and 3.3-V mode.
(4) The VMON_VSYS pin provides a way to monitor the system power supply. For more information, see Section 9.2.4, System Power
Supply Monitor Design Guidelines.
(5) This parameter applies to all IO pins which are not fail-safe and the requirement applies to all values of IO supply voltage. For
example, if the voltage applied to a specific IO supply is 0 volts the valid input voltage range for any IO powered by that supply will be
–0.3 to +0.3 volts. Special attention should be applied anytime peripheral devices are not powered from the same power sources used
to power the respective IO supply. It is important the attached peripheral never sources a voltage outside the valid input voltage range,
including power supply ramp-up and ramp-down sequences.
(6) An external resistor divider is required to limit the voltage applied to this device pin. For more information, see Section 9.2.3, USB
Design Guidelines.
(7) The USB0_ID pin is connected to analog circuits in the USB0 PHY. The analog circuits source a known current while measuring
voltage, to determine the resistance value (RID), if connected to VSS through a resistor. This pin should be connected to VSS for USB
host operation, or left unconnected for USB device operation, and should never be connected to any external voltage source.
(8) VDD is the voltage on the corresponding power-supply pin(s) for the IO.
(9) For current pulse injection (I-Test):
• Pins stressed per JEDEC JESD78 (Class II) and passed with specified I/O pin injection current and clamp voltage of 1.5 times
maximum recommended I/O voltage and negative 0.5 times maximum recommended I/O voltage.
Fail-safe IO terminals are designed such they do not have dependencies on the respective IO power
supply voltage. This allows external voltage sources to be connected to these IO terminals when the
respective IO power supplies are turned off. The MCU_I2C0_SCL, MCU_I2C0_SDA, I2C0_SCL, I2C0_SDA,
EXTINTn, VMON_1P8_MCU, VMON_1P8_SOC, VMON_3P3_MCU, VMON_3P3_SOC, VMON_VSYS, and
MCU_PORz are the only fail-safe IO terminals. All other IO terminals are not fail-safe and the voltage applied to
them should be limited to the value defined by the Steady State Max. Voltage at all IO pins parameter in Section
7.1.
Tperiod
Tundershoot
(1) JEDEC document JEP155 states that 500-V HBM allows safe manufacturing with a standard ESD control process.
(2) JEDEC document JEP157 states that 250-V CDM allows safe manufacturing with a standard ESD control process.
(1) This information is provided solely for your convenience and does not extend or modify the warranty provided under TI's standard
terms and conditions for TI semiconductor products.
(2) Unless specified in the table above, all voltage domains and operating conditions are supported in the device at the noted
temperatures.
(3) POH is a function of voltage, temperature and time. Usage at higher voltages and temperatures will result in a reduction in POH.
(1) The voltage at the device ball must never drop below the MIN voltage or rise above the MAX voltage for any amount of time during
normal device operation.
(2) VDD_MMC0 and VDD_DLL_MMC0 must be connected to the same power source as VDD_CORE when MMC0 is not used. In this
case, VDD_MMC0 and VDD_DLL_MMC0 may be operated at a nominal voltage of 0.75 or 0.85.
(3) VDDS_DDR and VDDS_DDR_C shall be sourced from the same power source.
(4) The VMON_VSYS pin provides a way to monitor the system power supply. For more information, see Section 9.2.4, System Power
Supply Monitor Design Guidelines.
(5) An external resistor divider is required to limit the voltage applied to this device pin. For more information, see Section 9.2.3, USB
Design Guidelines.
(6) The USB0_ID pin is connected to analog circuits in the USB0 PHY. The analog circuits source a known current while measuring
voltage, to determine the resistance value (RID), if connected to VSS through a resistor. This pin should be connected to VSS for USB
host operation, or left unconnected for USB device operation, and should never be connected to any external voltage source.
(1) Maximum DDR Frequency will be limited based on the specific memory type (vendor) used in a system and by PCB implementation.
Refer to AM64x\AM243x DDR Board Design and Layout Guidelines for the proper PCB implementation to achieve maximum DDR
frequency.
(1) VDD stands for corresponding power supply. For more information on the power supply name and the corresponding ball(s), see
POWER column of the Pin Attributes table.
(2) This value also defines the Absolute Maximum Ratings value the IO.
(3) The IOL parameter defines the minimum Low Level Output Current for which the device is able to maintain the specified VOL value.
The value defined by this parameter should be considered the maximum current available to a system implementation which needs to
maintain the specified VOL value for attached components.
(4) f = toggle frequency of the input signal in Hz.
(5) This MIN parameter only applies to input signal functions which are not defined in their respective Timing and Switching
Characteristics sections. Select the MIN parameter which results in the largest value.
(6) I2C Hs-mode is not supported when operating the IO in 3.3 V mode.
(1) The IOL and IOH parameters define the minimum Low Level Output Current and High Level Output Current for which the device is
able to maintain the specified VOL and VOH values. Values defined by these parameters should be considered the maximum current
available to a system implementation which needs to maintain the specified VOL and VOH values for attached components.
(2) f = toggle frequency of the input signal in Hz.
(3) This MIN parameter only applies to input signal functions which are not defined in their respective Timing and Switching
Characteristics sections. Select the MIN parameter which results in the largest value.
(1) VDD stands for corresponding power supply. For more information on the power supply name and the corresponding ball(s), see
POWER column of the Pin Attributes table.
(2) The IOL and IOH parameters define the minimum Low Level Output Current and High Level Output Current for which the device is
able to maintain the specified VOL and VOH values. Values defined by these parameters should be considered the maximum current
available to a system implementation which needs to maintain the specified VOL and VOH values for attached components.
(3) f = toggle frequency of the input signal in Hz.
(4) This MIN parameter only applies to input signal functions which are not defined in their respective Timing and Switching
Characteristics sections. Select the MIN parameter which results in the largest value.
(1) The ADC0_REFP and ADC0_REFN reference inputs are analog inputs which must be treated like high transient power supply rails.
ADC0_REFN is expected to be connected directly to the PCB ground plane along with all other VSS pins, and ADC0_REFP is
connected to a power source capable of providing at least 4 mA of current. ADC0_REFP can be connected to the same power source
as VDDA_ADC0 if the voltage tolerance of the supply provides an acceptable accuracy for the ADC reference. A high frequency
decoupling capacitor must be connected directly to the ADC0_REFP and ADC0_REFN pins with vias and be placed in the ball array
on the back side of the PCB.
(2) The ADC0_AIN pins are connected to an internal sampling capacitor for a user configurable acquisition time and acquisition frequency.
The input impedance of the ADC0_AIN pins is a function of the sampling capacitance along with user configurable acquisition time and
acquisition frequency. The designer must understand the time required for the source impedance of each ADC0_AIN pin to charge the
internal sampling capacitor. The acquisition time must be set long enough for the internal sampling capacitor to settle to greater than
14 bits of accuracy.
(3) ADC0 can be configured to operate in General Purpose Input mode, where all ADC0_AIN[7:0] inputs are globally enabled to operate
as digital inputs via the ADC0_CTRL register (gpi_mode_en = 1).
Note
USB0 interface is compliant with Universal Serial Bus Revision 2.0 Specification dated April 27, 2000
including ECNs and Errata as applicable.
Note
The PCIe interface is compliant with the electrical parameters specified in PCI Express® Base
Specification Revision 4.0, February 19, 2014.
Note
USB0 instance is compliant with the USB3.1 SuperSpeed Transmitter and Receiver Normative
Electrical Parameters as defined in the Universal Serial Bus 3.1 Specification, Revision 1.0 , July
26, 2013.
Note
The DDR interface is compatible with DDR4 devices that are JESD79-4B standard-compliant, and
LPDDR4 devices that are JESD209-4B standard-compliant
(1) These values are based on a JEDEC defined 2S2P system (with the exception of the Theta JC [RΘJC] value, which is based on a
JEDEC defined 1S0P system) and is subject to change based on environment as well as application. For more information, see the
EIA/JEDEC standards.
• JESD51-2, Integrated Circuits Thermal Test Method Environment Conditions - Natural Convection (Still Air)
• JESD51-3, Low Effective Thermal Conductivity Test Board for Leaded Surface Mount Packages
• JESD51-6, Integrated Circuit Thermal Test Method Environmental Conditions - Forced Convection (Moving Air)
• JESD51-7, High Effective Thermal Conductivity Test Board for Leaded Surface Mount Packages
• JESD51-9, Test Boards for Area Array Surface Mount Packages
(2) °C/W = degrees Celsius per watt.
(3) m/s = meters per second.
Note
The default SLEWRATE settings in each pad configuration register must be used to ensure timings,
unless specific instructions are given otherwise.
Note
All power balls must be supplied with the voltages specified in the Recommended Operating
Conditions section, unless otherwise specified in Signal Descriptions and Pin Connectivity
Requirements.
Supply value
t
slew rate < 18 mV/μs
slew > (supply value) / (18 mV/μs)
or
supply value × 55.6 μs/V
SPRT740_ELCH_06
Figure 7-4 defines a transition region with one or more power rails which must be sourced from a single common
power supply. No transitions are shown within the region to represent a single ramp within the transition region.
Note 1 VSYS
VSYS, VMON_VSYS Note 2 VMON_VSYS
(12)
VDDSHV5
(7) (7)
VDDS_DDR , VDDS_DDR_C
(8)(10)
VDD_CORE
(9)(10) (10)
VDD_CORE , VDDR_CORE , VDDA_0P85_SERDES0_C,
VDDA_0P85_SERDES0, VDDA_0P85_USB0,
VDD_DLL_MMC0, VDD_MMC0
Hi-Z
(11)
VPP
MCU_PORz
MCU_OSC0_XI, MCU_OSC0_XO
AM64x_ELCH_01
1. VSYS represents the name of a supply which sources power to the entire system. This supply is expected to
be a pre-regulated supply that sources power management devices which source all other supplies.
2. VMON_VSYS input is used to monitor VSYS via an external resistor divider circuit. For more information,
see Section 9.2.4, System Power Supply Monitor Design Guidelines.
3. VDDSHV_MCU and VDDSHVx [x=0-5] are dual voltage IO supplies which can be operated at 1.8V or
3.3V depending on the application requirements. When any of the VDDSHV_MCU or VDDSHVx [x=0-5] IO
supplies are operating at 3.3V, they shall be ramped up with other 3.3V supplies during the 3.3V ramp period
defined by this waveform.
4. The VMON_3P3_MCU and VMON_3P3_SOC inputs are used to monitor supply voltage and shall be
connected to the respective 3.3V supply source.
5. VDDSHV_MCU and VDDSHVx [x=0-5] are dual voltage IO supplies which can be operated at 1.8V or
3.3V depending on the application requirements. When any of the VDDSHV_MCU or VDDSHVx [x=0-5] IO
supplies are operating at 1.8V, they shall be ramped up with other 1.8V supplies during the 1.8V ramp period
defined by this waveform.
6. The VMON_1P8_MCU and VMON_1P8_SOC inputs are used to monitor supply voltage and shall be
connected to the respective 1.8V supply source.
7. VDDS_DDR and VDDS_DDR_C are expected to be powered by the same source such that they ramp
together.
8. VDD_CORE can be operated at 0.75V or 0.85V. When VDD_CORE is operating at 0.75V, it shall be ramped
up prior to all 0.85V supplies as shown in this waveform.
9. VDD_CORE can be operated at 0.75V or 0.85V. When VDD_CORE is operating at 0.85V, it shall be ramped
up with other 0.85V supplies during the 0.85V ramp period defined by this waveform.
Copyright © 2023 Texas Instruments Incorporated Submit Document Feedback 115
Product Folder Links: AM6442 AM6441 AM6422 AM6421 AM6412 AM6411
AM6442, AM6441, AM6422, AM6421, AM6412, AM6411
SPRSP56F – JANUARY 2021 – REVISED OCTOBER 2023 www.ti.com
10. The potential applied to VDDR_CORE must never be greater than the potential applied to VDD_CORE +
0.18V during power-up or power-down. This requires VDD_CORE to ramp up before and ramp down after
VDDR_CORE when VDD_CORE is operating at 0.75V. VDD_CORE does not have any ramp requirements
beyond the one defined for VDDR_CORE. VDD_CORE and VDDR_CORE are expected to be powered by
the same source so they ramp together when VDD_CORE is operating at 0.85V.
11. VPP is the 1.8V eFuse programming supply, which shall be left floating (HiZ) or grounded during power-up/
down sequences and during normal device operation. This supply shall only be sourced while programming
eFuse.
12. VDDSHV5 was designed to support power-up, power-down, or dynamic voltage change without any
dependency on other power rails. This capability is required to support UHS-I SD Cards.
VSYS
VSYS, VMON_VSYS VMON_VSYS
(6)
VDDSHV5
VDDS_DDR, VDDS_DDR_C
(3)(5)
VDD_CORE
(4)(5) (5)
VDD_CORE , VDDR_CORE , VDDA_0P85_SERDES0_C,
VDDA_0P85_SERDES0, VDDA_0P85_USB0,
VDD_DLL_MMC0, VDD_MMC0
VPP Hi-Z
MCU_PORz
MCU_OSC0_XI, MCU_OSC0_XO
AM64x_ELCH_02
(1) VDD stands for corresponding power supply. For more information on the power supply name and the corresponding ball(s), see
POWER column of the Pin Attributes table.
(1) This timing parameter is valid only after all supplies are valid and MCU_PORz has been asserted for the specified time.
Figure 7-9. MCU_RESETz, MCU_RESETSTATz, and RESETSTATz Timing Requirements and Switching
Characteristics
(1) This timing parameter is valid only after all supplies are valid and MCU_PORz has been asserted for the specified time.
Figure 7-10. RESET_REQz and RESETSTATz Timing Requirements and Switching Characteristics
CLK1
CLK2 CLK3
Input Clock
CLK4
CLK5 CLK6
Output Clock
DEVICE
CLKOUT Reference Clock Output
MCU_OSC0_XI
External main crystal interface pins connected to internal oscillator
which provides reference clock to PLLs within MCU domain
MCU_OSC0_XO and MAIN domain.
MCU_OBSCLK0 / OBSCLK0 Observation Clock Outputs for MCU Domain Clock / MAIN Domain Clocks
MCU_EXT_REFCLK0 / EXT_REFCLK1 Optional External System Clock Inputs - (MCU Domain) / (MAIN Domain)
J7ES_CLOCK_01
For more information about Input clock interfaces, see Clocking section in Device Configuration chapter in the
device TRM.
Device
MCU_OSC0_XI MCU_OSC0_XO
Crystal
CL1 CL2
PCB Ground
AM65x_MCU_OSC_INT_01
The crystal must be in the fundamental mode of operation and parallel resonant. Table 7-19 summarizes the
required electrical constraints.
Table 7-19. MCU_OSC0 Crystal Circuit Requirements
PARAMETER MIN TYP MAX UNIT
Fxtal Crystal Parallel Resonance Frequency 25 MHz
Ethernet RGMII and RMII
±100
not used
Fxtal Crystal Frequency Stability and Tolerance ppm
Ethernet RGMII and RMII
±50
using derived clock
CL1+PCBXI Capacitance of CL1 + CPCBXI 12 24 pF
CL2+PCBXO Capacitance of CL2 + CPCBXO 12 24 pF
CL Crystal Load Capacitance 6 12 pF
ESRxtal = 30 Ω 25 MHz 7 pF
Cshunt Crystal Circuit Shunt Capacitance ESRxtal = 40 Ω 25 MHz 5 pF
ESRxtal = 50 Ω 25 MHz 5 pF
ESRxtal Crystal Effective Series Resistance (1) Ω
(1) The maximum ESR of the crystal is a function of the crystal frequency and shunt capacitance. See the Cshunt parameter.
When selecting a crystal, the system design must consider temperature and aging characteristics of the crystal
based on worst case environment and expected life expectancy of the system.
VDD_CORE (min.)
VDD_CORE
VSS
Voltage
VSS MCU_OSC0_XO
tsX
Time
AM65x_MCU_OSC_STARTUP_02
Device
Crystal Circuit PCB
Components Signal Traces
MCU_OSC0_XI
MCU_OSC0_XO
AM65x_MCU_OSC_CC_05
Load capacitors, CL1 and CL2 in Figure 7-17, should be chosen such that the below equation is satisfied. CL in
the equation is the load specified by the crystal manufacturer.
CL = [(CL1 + CPCBXI + CXI) × (CL2 + CPCBXO + CXO)] / [(CL1 + CPCBXI + CXI) + (CL2 + CPCBXO + CXO)]
To determine the value of CL1 and CL2, multiply the capacitive load value CL by 2. Using this result, subtract the
combined values of CPCBXI + CXI to determine the value of CL1 and the combined values of CPCBXO + CXO to
determine the value of CL2. For example, if CL = 10 pF, CPCBXI = 2.9 pF, CXI = 0.5 pF, CPCBXO = 3.7 pF, CXO =
0.5 pF, the value of CL1 = [(2CL) - (CPCBXI + CXI)] = [(2 × 10 pF) - 2.9 pF - 0.5 pF)] = 16.6 pF and CL2 = [(2CL) -
(CPCBXO + CXO)] = [(2 × 10 pF) - 3.7 pF - 0.5 pF)] = 15.8 pF
7.10.4.1.1.2 Shunt Capacitance
The crystal circuit must also be designed such that it does not exceed the maximum shunt capacitance for
MCU_OSC0 operating conditions defined in Table 7-19. Shunt capacitance, Cshunt, of the crystal circuit is a
combination of crystal shunt capacitance and parasitic contributions. PCB signal traces which connect crystal
circuit components to MCU_OSC0 have mutual parasitic capacitance to each other, CPCBXIXO, where the PCB
designer should be able to extract mutual parasitic capacitance between these signal traces. The device
package also has mutual parasitic capacitance, CXIXO, where this mutual parasitic capacitance value is defined
in Table 7-20.
PCB routing should be designed to minimize mutual capacitance between XI and XO signal traces. This is
typically done by keeping signal traces short and not routing them in close proximity. Mutual capacitance can
also be minimized by placing a ground trace between these signals when the layout requires them to be routed
in close proximity. It is important to minimize the mutual capacitance on the PCB to provide as much margin as
possible when selecting a crystal.
Device
Crystal Circuit PCB
Components Signal Traces
MCU_OSC0_XI
CPCBXIXO CXIXO
CO
MCU_OSC0_XO
AM65x_MCU_OSC_SC_06
A crystal should be chosen such that the below equation is satisfied. CO in the equation is the maximum shunt
capacitance specified by the crystal manufacturer.
Cshunt ≥ CO + CPCBXIXO + CXIXO
For example, the equation would be satisfied when the crystal being used is 25 MHz with an ESR = 30 Ω,
CPCBXIXO = 0.04 pF, CXIXO = 0.01 pF, and shunt capacitance of the crystal is less than or equal to 6.95 pF.
Note
A DC steady-state condition is not allowed on MCU_OSC0_XI when the oscillator is powered up. This
is not allowed because MCU_OSC0_XI is internally AC coupled to a comparator that can enter an
unknown state when DC is applied to the input. Therefore, application software must power down
MCU_OSC0 any time MCU_OSC0_XI is not toggling between logic states.
Device
MCU_OSC0_XI MCU_OSC0_XO
PCB Ground
AM65x_MCU_OSC_EXT_CLK_03
Note
For more information, see:
• Device Configuration / Clocking / PLLs section in the device TRM.
• Programmable Real-Time Unit Subsystem and Industrial Communication Subsystem - Gigabit
(PRU_ICSSG) section in the device TRM.
Note
The input reference clock (MCU_OSC0_XI / MCU_OSC0_XO) is specified and the lock time is
ensured by the PLL controller, as documented in the Device Configuration chapter in the device TRM.
7.10.4.4 Recommended System Precautions for Clock and Control Signal Transitions
All clock and strobe signals must transition between VIH and VIL (or between VIL and VIH) in a monotonic
manner.
Monotonic transitions are more likely to occur with fast signal transitions. It is easy for noise to create non-
monotonic events on a signal with slow transitions. Therefore, avoid slow signal transitions on all clock and
control signals since they are more likely to generate glitches inside the device.
7.10.5 Peripherals
7.10.5.1 CPSW3G
For more details about features and additional description information on the device Gigabit Ethernet MAC, see
the corresponding subsections within Signal Descriptions and Detailed Description sections.
Note
CPSW3G MDIO0, CPSW3G RMII1, CPSW3G RMII2, and CPSW3G RGMII1 have one or more
signals which can be multiplexed to more than one pin. Timing requirements and switching
characteristics defined in this section are only valid for specific pin combinations known as IOSETs.
Valid pin combinations or IOSETs for these interfaces can be found in the tables of the CPSW3G
IOSETs section.
MDIO3
MDIO4
MDIO5
MDIO[x]_MDC
MDIO1
MDIO2
MDIO[x]_MDIO
(input)
MDIO7
MDIO[x]_MDIO
(output)
CPSW2G_MDIO_TIMING_01
(1) VDD stands for corresponding power supply. For more information on the power supply name and the corresponding ball(s), see
POWER column of the Pin Attributes table.
RMII1
RMII2
RMII[x]_REF_CLK
RMII3
Table 7-26. RMII[x]_RXD[1:0], RMII[x]_CRS_DV, and RMII[x]_RX_ER Timing Requirements – RMII Mode
see Figure 7-24
NO. PARAMETER DESCRIPTION MIN MAX UNIT
RMII4 tsu(RXD-REF_CLK) Setup time, RMII[x]_RXD[1:0] valid before RMII[x]_REF_CLK 4 ns
tsu(CRS_DV-REF_CLK) Setup time, RMII[x]_CRS_DV valid before RMII[x]_REF_CLK 4 ns
tsu(RX_ER-REF_CLK) Setup time, RMII[x]_RX_ER valid before RMII[x]_REF_CLK 4 ns
RMII5 th(REF_CLK-RXD) Hold time RMII[x]_RXD[1:0] valid after RMII[x]_REF_CLK 2 ns
th(REF_CLK-CRS_DV) Hold time, RMII[x]_CRS_DV valid after RMII[x]_REF_CLK 2 ns
th(REF_CLK-RX_ER) Hold time, RMII[x]_RX_ER valid after RMII[x]_REF_CLK 2 ns
RMII4
RMII5
RMII[x]_REF_CLK
RMII[x]_RXD[1:0], RMII[x]_CRS_DV,
RMII[x]_RX_ER
RMII6
RMII[x]_REF_CLK
RMII[x]_TXD[1:0], RMII[x]_TX_EN
RGMII1
RGMII2
RGMII3
(A)
RGMII[x]_RXC
RGMII4
RGMII5
(B)
RGMII[x]_RD[3:0] 1st Half-byte 2nd Half-byte
(B)
RGMII[x]_RX_CTL RXDV RXERR
A. RGMII[x]_RXC must be externally delayed relative to the data and control pins.
B. Data and control information is received using both edges of the clocks. RGMII[x]_RD[3:0] carries data bits 3-0 on the rising edge of
RGMII[x]_RXC and data bits 7-4 on the falling edge of RGMII[x]_RXC. Similarly, RGMII[x]_RX_CTL carries RXDV on rising edge of
RGMII[x]_RXC and RXERR on falling edge of RGMII[x]_RXC.
RGMII6
RGMII7
RGMII8
(A)
RGMII[x]_TXC
RGMII9
(B)
RGMII[x]_TD[3:0] 1st Half-byte 2nd Half-byte
RGMII10
(B)
RGMII[x]_TX_CTL TXEN TXERR
A. TXC is delayed internally before being driven to the RGMII[x]_TXC pin. This internal delay is always enabled.
B. Data and control information is received using both edges of the clocks. RGMII[x]_TD[3:0] carries data bits 3-0 on the rising edge of
RGMII[x]_TXC and data bits 7-4 on the falling edge of RGMII[x]_TXC. Similarly, RGMII[x]_TX_CTL carries TXEN on rising edge of
RGMII[x]_TXC and TXERR on falling edge of RGMII[x]_TXC.
Table 7-34 defines valid pin combinations of each CPSW3G RMII1 and RMII2 IOSET.
Table 7-34. CPSW3G RMII1 and RMII2 IOSETs
SIGNALS IOSET1 IOSET2
BALL NAME MUXMODE BALL NAME MUXMODE
RMII_REF_CLK(1) PRG1_PRU0_GPO10 5 PRG0_PRU0_GPO10 5
RMII1_CRS_DV PRG1_PRU1_GPO19 5 PRG0_PRU1_GPO19 5
RMII1_RX_ER PRG1_PRU0_GPO9 5 PRG0_PRU0_GPO9 5
RMII1_RXD0 PRG1_PRU1_GPO7 5 PRG0_PRU1_GPO7 5
RMII1_RXD1 PRG1_PRU1_GPO9 5 PRG0_PRU1_GPO9 5
RMII1_TXD0 PRG1_PRU1_GPO10 5 PRG0_PRU1_GPO10 5
RMII1_TXD1 PRG1_PRU1_GPO17 5 PRG0_PRU1_GPO17 5
RMII1_TX_EN PRG1_PRU1_GPO18 5 PRG0_PRU1_GPO18 5
RMII2_CRS_DV PRG1_PRU1_GPO13 5 PRG1_PRU1_GPO13 5
RMII2_RX_ER PRG1_PRU1_GPO4 5 PRG1_PRU1_GPO4 5
RMII2_RXD0 PRG1_PRU1_GPO0 5 PRG1_PRU1_GPO0 5
RMII2_RXD1 PRG1_PRU1_GPO1 5 PRG1_PRU1_GPO1 5
RMII2_TXD0 PRG1_PRU1_GPO11 5 PRG1_PRU1_GPO11 5
RMII2_TXD1 PRG1_PRU1_GPO12 5 PRG1_PRU1_GPO12 5
RMII2_TX_EN PRG1_PRU1_GPO15 5 PRG1_PRU1_GPO15 5
(1) RMII_REF_CLK is common to both RMII1 and RMII2. For proper operation, all pin multiplexed
signal assignments must use the same IOSET.
Table 7-35 defines valid pin combinations of each CPSW3G RGMII1 IOSET.
Table 7-35. CPSW3G RGMII1 IOSETs
SIGNALS IOSET1 IOSET2
BALL NAME MUXMODE BALL NAME MUXMODE
RGMII1_TX_CTL PRG1_PRU0_GPO9 4 PRG1_PRU0_GPO9 4
RGMII1_TXC PRG1_PRU0_GPO10 4 PRG1_PRU0_GPO10 4
RGMII1_TD0 PRG1_PRU1_GPO7 4 PRG1_PRU1_GPO7 4
RGMII1_TD1 PRG1_PRU1_GPO9 4 PRG1_PRU1_GPO9 4
RGMII1_TD2 PRG1_PRU1_GPO10 4 PRG1_PRU1_GPO10 4
RGMII1_TD3 PRG1_PRU1_GPO17 4 PRG1_PRU1_GPO17 4
RGMII1_RX_CTL PRG0_PRU0_GPO9 4 PRG1_PRU0_GPO5 4
RGMII1_RXC PRG0_PRU0_GPO10 4 PRG1_PRU0_GPO8 4
RGMII1_RD0 PRG0_PRU1_GPO7 4 PRG1_PRU1_GPO5 4
RGMII1_RD1 PRG0_PRU1_GPO9 4 PRG1_PRU1_GPO8 4
RGMII1_RD2 PRG0_PRU1_GPO10 4 PRG1_PRU1_GPO18 4
RGMII1_RD3 PRG0_PRU1_GPO17 4 PRG1_PRU1_GPO19 4
7.10.5.2 DDRSS
For more details about features and additional description information on the device (LP)DDR4 Memory
Interface, see the corresponding subsections within Signal Descriptions and Detailed Description sections.
Table 7-36 and Figure 7-28 present switching characteristics for DDRSS.
Table 7-36. DDRSS Switching Characteristics
see Figure 7-28
NO. PARAMETER DDR TYPE MIN MAX UNIT
(1) Minimum DDR clock Cycle time will be limited based on the specific memory type (vendor) used in a system and by PCB
implementation. Refer to AM64x\AM243x DDR Board Design and Layout Guidelines for the proper PCB implementation to achieve
maximum DDR frequency.
DDR0_CKP
DDR0_CKN
For more information, see DDR Subsystem (DDRSS) section in Memory Controllers chapter in the device TRM.
7.10.5.3 ECAP
Table 7-37, Table 7-38, Figure 7-29, Table 7-39, and Figure 7-30 present timing conditions, requirements, and
switching characteristics for ECAP.
Table 7-37. ECAP Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 1 4 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 2 7 pF
CAP1
CAP
EPERIPHERALS_TIMNG_01
CAP2
APWM
EPERIPHERALS_TIMNG_02
For more information, see Enhanced Capture (ECAP) Module section in Peripherals chapter in the device TRM.
7.10.5.4 EPWM
Table 7-40, Table 7-41, Figure 7-31, Table 7-42, Figure 7-32, Figure 7-33, and Figure 7-34 present timing
conditions, requirements, and switching characteristics for EPWM.
Table 7-40. EPWM Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 1 4 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 2 7 pF
PWM6
EHRPWM_SYNCI
PWM7
EHRPWM_TZn_IN
EPERIPHERALS_TIMNG_07
PWM1
EHRPWM_A/B
PWM1
PWM2
EHRPWM_SYNCO
PWM5
EHRPWM_SOCA/B
EPERIPHERALS_TIMNG_04
PWM3
EHRPWM_A/B
EHRPWM_TZn_IN
EPERIPHERALS_TIMING_05
PWM4
EHRPWM_A/B
EHRPWM_TZn_IN
For more information, see Enhanced Pulse Width Modulation (EPWM) Module section in Peripherals chapter in
the device TRM.
7.10.5.5 EQEP
Table 7-43, Table 7-44, Figure 7-35, and Table 7-45 present timing conditions, requirements, and switching
characteristics for EQEP.
Table 7-43. EQEP Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 1 4 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 2 7 pF
QEP1
QEP_A/B
QEP2
QEP_I
QEP3
QEP4
QEP_S
QEP5 EPERIPHERALS_TIMNG_03
For more information, see Enhanced Quadrature Encoder Pulse (EQEP) Module section in Peripherals chapter
in the device TRM.
7.10.5.6 FSI
Table 7-46, Table 7-47, Figure 7-36, Table 7-48, Figure 7-37, Table 7-49, and Figure 7-38 present timing
conditions, requirements, and switching characteristics for FSI.
Table 7-46. FSI Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 0.8 4 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 1 7 pF
FSIR1
FSIR2 FSIR2
FSI_RXn_CLK
FSI_RXn_D0
FSI_RXn_D1
FSIR3 FSIR4
FSIT1
FSIT2 FSIT2
FSI_TXn_CLK
FSI_TXn_D0
FSI_TXn_D1
FSIT3
FSIT4
FSIT5 FSIT5
FSI_TXn_CLK
FSIT6
FSI_TXn_D0
FSIT8
FSIT7
FSI_TXn_D1
For more information, see Fast Serial Interface section in Peripherals chapter in the device TRM.
7.10.5.7 GPIO
Table 7-50, Table 7-51, and Table 7-52 present timing conditions, requirements, and switching characteristics for
GPIO.
The device has three instances of the GPIO module.
• MCU_GPIO0
• GPIO0
• GPIO1
Note
GPIOn_x is generic name used to describe a GPIO signal, where n represents the specific GPIO
module and x represents one of the input/output signals associated with the module.
For additional description information on the device GPIO, see the corresponding subsections within
Signal Descriptions and Detailed Description sections.
For more information, see General-Purpose Interface (GPIO) section in Peripherals chapter in the device TRM.
7.10.5.8 GPMC
For more details about features and additional description information on the device General-Purpose Memory
Controller, see the corresponding subsections within Signal Descriptions and Detailed Description sections.
Note
GPMC has one or more signals which can be multiplexed to more than one pin. Timing requirements
and switching characteristics defined in this section are only valid for specific pin combinations known
as IOSETs. Valid pin combinations or IOSETs for this interface is shown in Section 7.10.5.8.4.
For more information, see General-Purpose Memory Controller (GPMC) section in Peripherals chapter in the
device TRM.
7.10.5.8.1 GPMC and NOR Flash — Synchronous Mode
Hold time, input wait GPMC_WAIT[j] valid after output clock GPMC_CLK high (th(clkH-waitV))
Table 7-54 and Table 7-55 present timing requirements and switching characteristics for GPMC and NOR Flash -
Synchronous Mode.
Table 7-54. GPMC and NOR Flash Timing Requirements — Synchronous Mode
see Figure 7-39, Figure 7-40, and Figure 7-43
MIN MAX MIN MAX
NO. PARAMETER DESCRIPTION MODE(5) GPMC_FCLK = GPMC_FCLK = UNIT
100 MHz(2) 133 MHz(2)
F12 tsu(dV-clkH) Setup time, input data div_by_1_mode; 1.81 1.12 ns
GPMC_AD[n:0](1) valid before GPMC_FCLK_MUX;
output clock GPMC_CLK high TIMEPARAGRANULARITY_X1
not_div_by_1_mode; 1.06 3.5 ns
GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
F13 th(clkH-dV) Hold time, input data div_by_1_mode; 2.29 2.29 ns
GPMC_AD[n:0](1) valid after output GPMC_FCLK_MUX;
clock GPMC_CLK high TIMEPARAGRANULARITY_X1
not_div_by_1_mode; 2.29 2.29 ns
GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
F21 tsu(waitV-clkH) Setup time, input wait div_by_1_mode; 1.81 1.12 ns
GPMC_WAIT[j](3) (4) valid before GPMC_FCLK_MUX;
output clock GPMC_CLK high TIMEPARAGRANULARITY_X1
not_div_by_1_mode; 1.06 3.5 ns
GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
Table 7-54. GPMC and NOR Flash Timing Requirements — Synchronous Mode (continued)
see Figure 7-39, Figure 7-40, and Figure 7-43
MIN MAX MIN MAX
NO. PARAMETER DESCRIPTION MODE(5) GPMC_FCLK = GPMC_FCLK = UNIT
100 MHz(2) 133 MHz(2)
F22 th(clkH-waitV) Hold time, input wait div_by_1_mode; 2.29 2.29 ns
GPMC_WAIT[j](3) (4) valid after GPMC_FCLK_MUX;
output clock GPMC_CLK high TIMEPARAGRANULARITY_X1
not_div_by_1_mode; 2.29 2.29 ns
GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
(1) Synchronous Mode supports 16-bit data bus up to 133 MHz and 32-bit data bus up to 100 MHz
(2) GPMC_FCLK select
• gpmc_fclk_sel[1:0] = 2b01 to select the 100MHz GPMC_FCLK
• gpmc_fclk_sel[1:0] = 2b00 to select the 133MHz GPMC_FCLK
(3) In GPMC_WAIT[j], j is equal to 0 or 1.
(4) Wait monitoring support is limited to a WaitMonitoringTime value > 0. For a full description of wait monitoring feature, see General-
Purpose Memory Controller (GPMC) section in the device TRM.
(5) For div_by_1_mode:
• GPMC_CONFIG1_i Register: GPMCFCLKDIVIDER = 0h:
– GPMC_CLK frequency = GPMC_FCLK frequency
For not_div_by_1_mode:
• GPMC_CONFIG1_i Register: GPMCFCLKDIVIDER = 1h to 3h:
– GPMC_CLK frequency = GPMC_FCLK frequency / (2 to 4)
For GPMC_FCLK_MUX:
• CTRLMMR_GPMC_CLKSEL[1-0] CLK_SEL = 01 = PER1_PLL_CLKOUT / 3 = 300 / 3 = 100MHz
For TIMEPARAGRANULARITY_X1:
• GPMC_CONFIG1_i Register: TIMEPARAGRANULARITY = 0h = x1 latencies (affecting RD/WRCYCLETIME, RD/
WRACCESSTIME, PAGEBURSTACCESSTIME, CSONTIME, CSRD/WROFFTIME, ADVONTIME, ADVRD/WROFFTIME,
OEONTIME, OEOFFTIME, WEONTIME, WEOFFTIME, CYCLE2CYCLEDELAY, BUSTURNAROUND, TIMEOUTSTARTVALUE,
WRDATAONADMUXBUS)
Table 7-55. GPMC and NOR Flash Switching Characteristics – Synchronous Mode
see Figure 7-39, Figure 7-40, Figure 7-41, Figure 7-42, and Figure 7-43
NO. (17)
MIN MAX MIN MAX
(3) PARAMETER DESCRIPTION MODE UNIT
100 MHz 133 MHz
(16)
F0 1 / tc(clk) Period, output clock GPMC_CLK div_by_1_mode; 10.00 7.52 ns
GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
F1 tw(clkH) Typical pulse duration, output clock div_by_1_mode; 0.475P 0.475P ns
GPMC_CLK high GPMC_FCLK_MUX; - 0.3(15) - 0.3(15)
TIMEPARAGRANULARITY_X1
F1 tw(clkL) Typical pulse duration, output clock div_by_1_mode; 0.475P 0.475P ns
GPMC_CLK low GPMC_FCLK_MUX; - 0.3(15) - 0.3(15)
TIMEPARAGRANULARITY_X1
F2 td(clkH-csnV) Delay time, output clock GPMC_CLK div_by_1_mode; F - 2.2 F+ F - 2.2 F+ ns
rising edge to output chip select GPMC_FCLK_MUX; (6) 3.75 (6) 3.75
(14)
GPMC_CSn[i] transition TIMEPARAGRANULARITY_X1;
no extra_delay
F3 td(clkH-CSn[i]V) Delay time, output clock GPMC_CLK div_by_1_mode; E - 2.2 E+ E - 2.2 E + 4.5 ns
rising edge to output chip select GPMC_FCLK_MUX; (5) 3.18 (5)
(14)
GPMC_CSn[i] invalid TIMEPARAGRANULARITY_X1;
no extra_delay
Table 7-55. GPMC and NOR Flash Switching Characteristics – Synchronous Mode (continued)
see Figure 7-39, Figure 7-40, Figure 7-41, Figure 7-42, and Figure 7-43
NO. (17)
MIN MAX MIN MAX
(3) PARAMETER DESCRIPTION MODE UNIT
100 MHz 133 MHz
F4 td(aV-clk) Delay time, output address div_by_1_mode; B - 2.3 B + 4.5 B - 2.3 B + 4.5 ns
GPMC_A[27:1] valid to output clock GPMC_FCLK_MUX; (3) (3)
Table 7-55. GPMC and NOR Flash Switching Characteristics – Synchronous Mode (continued)
see Figure 7-39, Figure 7-40, Figure 7-41, Figure 7-42, and Figure 7-43
NO. (17)
MIN MAX MIN MAX
(3) PARAMETER DESCRIPTION MODE UNIT
100 MHz 133 MHz
F17 td(clkL-be[x]n) Delay time, GPMC_CLK falling edge div_by_1_mode; J - 2.3 J + 1.9 J - 2.3 J + 1.9 ns
to GPMC_BE0n_CLE, GPMC_BE1n GPMC_FCLK_MUX; (10) (10)
(12)
transition TIMEPARAGRANULARITY_X1
F17 td(clkL-be[x]n). Delay time, GPMC_CLK falling edge div_by_1_mode; J - 2.3 J + 1.9 J - 2.3 J + 1.9 ns
to GPMC_BE0n_CLE, GPMC_BE1n GPMC_FCLK_MUX; (10) (10)
(13)
transition TIMEPARAGRANULARITY_X1
F18 tw(csnV) Pulse duration, output chip select Read A A ns
(14)
GPMC_CSn[i] low
Write A A ns
F19 tw(be[x]nV) Pulse duration, output lower byte Read C C ns
enable and command latch enable
Write C C ns
GPMC_BE0n_CLE, output upper byte
enable GPMC_BE1n low
F20 tw(advnV) Pulse duration, output address Read K K ns
valid and address latch enable
Write K K ns
GPMC_ADVn_ALE low
(1) Synchronous Mode supports 16-bit data bus up to 133 MHz and 32-bit data bus up to 100 MHz
(2) For single read: A = (CSRdOffTime - CSOnTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
For burst read: A = (CSRdOffTime - CSOnTime + (n - 1) × PageBurstAccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
For burst write: A = (CSWrOffTime - CSOnTime + (n - 1) × PageBurstAccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
With n being the page burst access number.
(3) B = ClkActivationTime × GPMC_FCLK(15)
(4) For single read: D = (RdCycleTime - AccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
For burst read: D = (RdCycleTime - AccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
For burst write: D = (WrCycleTime - AccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
(5) For single read: E = (CSRdOffTime - AccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
For burst read: E = (CSRdOffTime - AccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
For burst write: E = (CSWrOffTime - AccessTime) × (TimeParaGranularity + 1) × GPMC_FCLK(15)
(6) For csn falling edge (CS activated):
• Case GPMCFCLKDIVIDER = 0:
– F = 0.5 × CSExtraDelay × GPMC_FCLK(15)
• Case GPMCFCLKDIVIDER = 1:
– F = 0.5 × CSExtraDelay × GPMC_FCLK(15) if (ClkActivationTime and CSOnTime are odd) or (ClkActivationTime and
CSOnTime are even)
– F = (1 + 0.5 × CSExtraDelay) × GPMC_FCLK(15) otherwise
• Case GPMCFCLKDIVIDER = 2:
– F = 0.5 × CSExtraDelay × GPMC_FCLK(15) if ((CSOnTime - ClkActivationTime) is a multiple of 3)
– F = (1 + 0.5 × CSExtraDelay) × GPMC_FCLK(15) if ((CSOnTime - ClkActivationTime - 1) is a multiple of 3)
– F = (2 + 0.5 × CSExtraDelay) × GPMC_FCLK(15) if ((CSOnTime - ClkActivationTime - 2) is a multiple of 3)
(7) For ADV falling edge (ADV activated):
• Case GPMCFCLKDIVIDER = 0:
– G = 0.5 × ADVExtraDelay × GPMC_FCLK(15)
• Case GPMCFCLKDIVIDER = 1:
– G = 0.5 × ADVExtraDelay × GPMC_FCLK(15) if (ClkActivationTime and ADVOnTime are odd) or (ClkActivationTime and
ADVOnTime are even)
– G = (1 + 0.5 × ADVExtraDelay) × GPMC_FCLK(15) otherwise
• Case GPMCFCLKDIVIDER = 2:
– G = 0.5 × ADVExtraDelay × GPMC_FCLK(15) if ((ADVOnTime - ClkActivationTime) is a multiple of 3)
– G = (1 + 0.5 × ADVExtraDelay) × GPMC_FCLK(15) if ((ADVOnTime - ClkActivationTime - 1) is a multiple of 3)
– G = (2 + 0.5 × ADVExtraDelay) × GPMC_FCLK(15) if ((ADVOnTime - ClkActivationTime - 2) is a multiple of 3)
• Case GPMCFCLKDIVIDER = 1:
– G = 0.5 × ADVExtraDelay × GPMC_FCLK(15) if (ClkActivationTime and ADVRdOffTime are odd) or (ClkActivationTime and
ADVRdOffTime are even)
– G = (1 + 0.5 × ADVExtraDelay) × GPMC_FCLK(15) otherwise
• Case GPMCFCLKDIVIDER = 2:
– G = 0.5 × ADVExtraDelay × GPMC_FCLK(15) if ((ADVRdOffTime - ClkActivationTime) is a multiple of 3)
– G = (1 + 0.5 × ADVExtraDelay) × GPMC_FCLK(15) if ((ADVRdOffTime - ClkActivationTime - 1) is a multiple of 3)
– G = (2 + 0.5 × ADVExtraDelay) × GPMC_FCLK(15) if ((ADVRdOffTime - ClkActivationTime - 2) is a multiple of 3)
For GPMC_FCLK_MUX:
• CTRLMMR_GPMC_CLKSEL[1-0] CLK_SEL = 01 = PER1_PLL_CLKOUT / 3 = 300 / 3 = 100MHz
For TIMEPARAGRANULARITY_X1:
• GPMC_CONFIG1_i Register: TIMEPARAGRANULARITY = 0h = x1 latencies (affecting RD/WRCYCLETIME, RD/
WRACCESSTIME, PAGEBURSTACCESSTIME, CSONTIME, CSRD/WROFFTIME, ADVONTIME, ADVRD/WROFFTIME,
OEONTIME, OEOFFTIME, WEONTIME, WEOFFTIME, CYCLE2CYCLEDELAY, BUSTURNAROUND, TIMEOUTSTARTVALUE,
WRDATAONADMUXBUS)
For no extra_delay:
• GPMC_CONFIG2_i Register: CSEXTRADELAY = 0h = CSn Timing control signal is not delayed
• GPMC_CONFIG4_i Register: WEEXTRADELAY = 0h = nWE timing control signal is not delayed
• GPMC_CONFIG4_i Register: OEEXTRADELAY = 0h = nOE timing control signal is not delayed
• GPMC_CONFIG3_i Register: ADVEXTRADELAY = 0h = nADV timing control signal is not delayed
F1
F0 F1
GPMC_CLK
F2 F3
F18
GPMC_CSn[i]
F4
GPMC_A[MSB:1] Valid Address
F6 F7
F19
GPMC_BE0n_CLE
F19
GPMC_BE1n
F6 F8 F8
F20 F9
GPMC_ADVn_ALE
F10 F11
GPMC_OEn_REn
F13
F12
GPMC_AD[15:0] D0
GPMC_WAIT[j]
GPMC_01
A. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3.
B. In GPMC_WAIT[j], j is equal to 0 or 1.
Figure 7-39. GPMC and NOR Flash — Synchronous Single Read (GPMCFCLKDIVIDER = 0)
F1
F0 F1
GPMC_CLK
F2 F3
GPMC_CSn[i]
F4
GPMCA[MSB:1] Valid Address
F6 F7
GPMC_BE0n_CLE
F7
GPMC_BE1n
F6 F8 F8 F9
GPMC_ADVn_ALE
F10 F11
GPMC_OEn_REn
F13 F13
F12 F12
GPMC_AD[15:0] D0 D1 D2 D3
F21 F22
GPMC_WAIT[j]
GPMC_02
A. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3.
B. In GPMC_WAIT[j], j is equal to 0 or 1.
Figure 7-40. GPMC and NOR Flash — Synchronous Burst Read — 4x16–bit (GPMCFCLKDIVIDER = 0)
F1
F1 F0
GPMC_CLK
F2 F3
GPMC_CSn[i]
F4
GPMC_A[MSB:1] Valid Address
F17
F6 F17 F17
GPMC_BE0n_CLE
F17
F17 F17
GPMC_BE1n
F6 F8 F8 F9
GPMC_ADVn_ALE
F14 F14
GPMC_WEn
F15 F15 F15
GPMC_AD[15:0] D0 D1 D2 D3
GPMC_WAIT[j]
GPMC_03
A. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3.
B. In GPMC_WAIT[j], j is equal to 0 or 1.
F1
F0 F1
GPMC_CLK
F2 F3
GPMC_CSn[i]
F6 F7
GMPC_BE0n_CLE Valid
F6 F7
GPMC_BE1n Valid
F4
GPMC_A[27:17] Address (MSB)
F12
F4 F5 F13 F12
GPMC_AD[15:0] Address (LSB) D0 D1 D2 D3
F8 F8 F9
GPMC_ADVn_ALE
F10 F11
GPMC_OEn_REn
GPMC_WAIT[j]
GPMC_04
A. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3.
B. In GPMC_WAIT[j], j is equal to 0 or 1.
Figure 7-42. GPMC and Multiplexed NOR Flash — Synchronous Burst Read
F1
F1 F0
GPMC_CLK
F2 F3
F18
GPMC_CSn[i]
F4
GPMC_A[27:17] Address (MSB)
F17
F6 F17 F17
GPMC_BE1n
F17
F6 F17 F17
BPMC_BE0n_CLE
F8 F8
F20 F9
GPMC_ADVn_ALE
F14 F14
GPMC_WEn
F15 F15 F15
GPMC_AD[15:0] Address (LSB) D0 D1 D2 D3
F22 F21
GPMC_WAIT[j]
GPMC_05
A. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3.
B. In GPMC_WAIT[j], j is equal to 0 or 1.
Figure 7-43. GPMC and Multiplexed NOR Flash — Synchronous Burst Write
(1) The FA5 parameter illustrates the amount of time required to internally sample input data. It is expressed in number of GPMC
functional clock cycles. From start of read cycle and after FA5 functional clock cycles, input data is internally sampled by active
functional clock edge. FA5 value must be stored inside the AccessTime register bit field.
(2) The FA20 parameter illustrates amount of time required to internally sample successive input page data. It is expressed in number of
GPMC functional clock cycles. After each access to input page data, next input page data is internally sampled by active functional
clock edge after FA20 functional clock cycles. The FA20 value must be stored in the PageBurstAccessTime register bit field.
(3) P = PageBurstAccessTime × (TimeParaGranularity + 1) × GPMC_FCLK(5)
(4) H = AccessTime × (TimeParaGranularity + 1) × GPMC_FCLK(5)
(5) GPMC_FCLK is general-purpose memory controller internal functional clock period in ns.
Table 7-57. GPMC and NOR Flash Switching Characteristics – Asynchronous Mode
see Figure 7-44, Figure 7-45, Figure 7-46, Figure 7-47, Figure 7-48, and Figure 7-49
(15)
MIN MAX
NO. PARAMETER DESCRIPTION MODE UNIT
133 MHz
FA0 tw(be[x]nV) Pulse duration, output lower-byte enable and Read N (12) ns
command latch enable GPMC_BE0n_CLE, output (12)
Write N
upper-byte enable GPMC_BE1n valid time
FA1 tw(csnV) Pulse duration, output chip select GPMC_CSn[i](13) Read A (1) ns
low
Write A (1)
FA3 td(csnV-advnIV) Delay time, output chip select GPMC_CSn[i](13) Read B - 2.1 B + 2.1 ns
valid to output address valid and address latch (2) (2)
FA4 td(csnV-oenIV) Delay time, output chip select GPMC_CSn[i](13) div_by_1_mode; C - 2.1 C + 2.1 ns
valid to output enable GPMC_OEn_REn invalid GPMC_FCLK_MUX; (3) (3)
TIMEPARAGRANULARITY_X1
FA10 td(be[x]nV-csnV) Delay time, output lower-byte enable and div_by_1_mode; J - 2.1 (9) J + 2.1 ns
command latch enable GPMC_BE0n_CLE, output GPMC_FCLK_MUX; (9)
TIMEPARAGRANULARITY_X1
FA16 tw(aIV) Pulse duration output address GPMC_A[26:1] div_by_1_mode; G (7) ns
invalid between 2 successive read and write GPMC_FCLK_MUX;
accesses TIMEPARAGRANULARITY_X1
Table 7-57. GPMC and NOR Flash Switching Characteristics – Asynchronous Mode (continued)
see Figure 7-44, Figure 7-45, Figure 7-46, Figure 7-47, Figure 7-48, and Figure 7-49
(15)
MIN MAX
NO. PARAMETER DESCRIPTION MODE UNIT
133 MHz
FA18 td(csnV-oenIV) Delay time, output chip select GPMC_CSn[i](13) div_by_1_mode; I - 2.1 (8) I + 2.1 (8) ns
valid to output enable GPMC_OEn_REn invalid GPMC_FCLK_MUX;
(Burst read) TIMEPARAGRANULARITY_X1
FA20 tw(aV) Pulse duration, output address GPMC_A[27:1] div_by_1_mode; D (4) ns
valid - 2nd, 3rd, and 4th accesses GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
FA25 td(csnV-wenV) Delay time, output chip select GPMC_CSn[i](13) div_by_1_mode; E - 2.1 E + 2.1 ns
valid to output write enable GPMC_WEn valid GPMC_FCLK_MUX; (5) (5)
TIMEPARAGRANULARITY_X1
FA27 td(csnV-wenIV) Delay time, output chip select GPMC_CSn[i](13) div_by_1_mode; F - 2.1 (6) F + 2.1 ns
valid to output write enable GPMC_WEn invalid GPMC_FCLK_MUX; (6)
TIMEPARAGRANULARITY_X1
FA28 td(wenV-dV) Delay time, output write enable GPMC_WEn valid div_by_1_mode; 2.1 ns
to output data GPMC_AD[15:0] valid GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
FA29 td(dV-csnV) Delay time, output data GPMC_AD[15:0] valid to div_by_1_mode; J - 2.1 (9) J + 2.1 ns
output chip select GPMC_CSn[i](13) valid GPMC_FCLK_MUX; (9)
TIMEPARAGRANULARITY_X1
FA37 td(oenV-aIV) Delay time, output enable GPMC_OEn_REn valid div_by_1_mode; 2.1 ns
to output address GPMC_AD[15:0] phase end GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
For GPMC_FCLK_MUX:
• CTRLMMR_GPMC_CLKSEL[1-0] CLK_SEL = 00 = CPSWHSDIV_CLKOUT3 = 2000/15 = 133.33 MHz
For TIMEPARAGRANULARITY_X1:
• GPMC_CONFIG1_i Register: TIMEPARAGRANULARITY = 0h = x1 latencies (affecting RD/WRCYCLETIME, RD/
WRACCESSTIME, PAGEBURSTACCESSTIME, CSONTIME, CSRD/WROFFTIME, ADVONTIME, ADVRD/WROFFTIME,
GPMC_FCLK
GPMC_CLK
FA5
FA1
GPMC_CSn[i]
FA9
GPMC_A[MSB:1] Valid Address
FA0
FA10
GPMC_BE0n_CLE Valid
FA0
GPMC_BE1n Valid
FA10
FA3
FA12
GPMC_ADVn_ALE
FA4
FA13
GPMC_OEn_REn
GPMC_AD[15:0] Data IN 0 Data IN 0
GPMC_WAIT[j]
GPMC_06
Figure 7-44. GPMC and NOR Flash — Asynchronous Read — Single Word
GPMC_FCLK
GPMC_CLK
FA5 FA5
FA1 FA1
GPMC_CSn[i]
FA16
FA9 FA9
FA3 FA3
FA12 FA12
GPMC_ADCn_ALE
FA4 FA4
FA13 FA13
GPMC_OEn_REn
GPMC_AD[15:0] Data Upper
GPMC_WAIT[j]
GPMC_07
GPMC_FCLK
GPMC_CLK
FA21 FA20 FA20 FA20
FA1
GPMC_CSn[i]
FA9
GPMC_A[MSB:1] Add0 Add1 Add2 Add3 Add4
FA0
FA10
GPMC_BE0n_CLE
FA0
FA10
GPMC_BE1n
FA12
GPMC_ADVn_ALE
FA18
FA13
GPMC_OEn_REn
GPMC_AD[15:0] D0 D1 D2 D3 D3
GPMC_WAIT[j]
GPMC_08
Figure 7-46. GPMC and NOR Flash — Asynchronous Read — Page Mode 4x16–Bit
GPMC_FCLK
GPMC_CLK
FA1
GPMC_CSn[i]
FA9
GPMC_A[MSB:1] Valid Address
FA0
FA10
GPMC_BE0n_CLE
FA0
FA10
GPMC_BE1n
FA3
FA12
GPMC_ADVn_ALE
FA27
FA25
GPMC_WEn
FA29
GPMC_AD[15:0] Data OUT
GPMC_WAIT[j]
GPMC_09
Figure 7-47. GPMC and NOR Flash — Asynchronous Write — Single Word
GPMC_FCLK
GPMC_CLK
FA1
FA5
GPMC_CSn[i]
FA9
GPMC_A[27:17] Address (MSB)
FA0
FA10
GPMC_BE0n_CLE Valid
FA0
FA10
GPMC_BE1n Valid
FA3
FA12
GPMC_ADVn_ALE
FA4
FA13
GPMC_OEn_REn
FA29 FA37
GPMC_AD[15:0] Address (LSB) Data IN Data IN
GPMC_WAIT[j]
GPMC_10
Figure 7-48. GPMC and Multiplexed NOR Flash — Asynchronous Read — Single Word
GPMC_FCLK
GPMC_CLK
FA1
GPMC_CSn[i]
FA9
GPMC_A[27:17] Address (MSB)
FA0
FA10
GPMC_BE0n_CLE
FA0
FA10
GPMC_BE1n
FA3
FA12
GPMC_ADVn_ALE
FA27
FA25
GPMC_WEn
FA29 FA28
GPMC_AD[15:0] Valid Address (LSB) Data OUT
GPMC_WAIT[j]
GPMC_11
Figure 7-49. GPMC and Multiplexed NOR Flash — Asynchronous Write — Single Word
(1) The GNF12 parameter illustrates the amount of time required to internally sample input data. It is expressed in number of GPMC
functional clock cycles. From start of the read cycle and after GNF12 functional clock cycles, input data is internally sampled by the
active functional clock edge. The GNF12 value must be stored inside AccessTime register bit field.
(2) J = AccessTime × (TimeParaGranularity + 1) × GPMC_FCLK(3)
(3) GPMC_FCLK is general-purpose memory controller internal functional clock period in ns.
(4) For div_by_1_mode:
• GPMC_CONFIG1_i Register: GPMCFCLKDIVIDER = 0h:
– GPMC_CLK frequency = GPMC_FCLK frequency
For GPMC_FCLK_MUX:
• CTRLMMR_GPMC_CLKSEL[1-0] CLK_SEL = 00 = CPSWHSDIV_CLKOUT3 = 2000/15 = 133.33 MHz
For TIMEPARAGRANULARITY_X1:
• GPMC_CONFIG1_i Register: TIMEPARAGRANULARITY = 0h = x1 latencies (affecting RD/WRCYCLETIME, RD/
WRACCESSTIME, PAGEBURSTACCESSTIME, CSONTIME, CSRD/WROFFTIME, ADVONTIME, ADVRD/WROFFTIME,
OEONTIME, OEOFFTIME, WEONTIME, WEOFFTIME, CYCLE2CYCLEDELAY, BUSTURNAROUND, TIMEOUTSTARTVALUE,
WRDATAONADMUXBUS)
Table 7-59. GPMC and NAND Flash Switching Characteristics – Asynchronous Mode
see Figure 7-50, Figure 7-51, Figure 7-52 and Figure 7-53
(4)
NO. PARAMETER MODE MIN MAX UNIT
GNF0 tw(wenV) Pulse duration, output write enable GPMC_WEn div_by_1_mode; A ns
valid GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF1 td(csnV-wenV) Delay time, output chip select GPMC_CSn[i](2) div_by_1_mode; B-2 B+2 ns
valid to output write enable GPMC_WEn valid GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF2 tw(cleH-wenV) Delay time, output lower-byte enable and div_by_1_mode; C-2 C+2 ns
command latch enable GPMC_BE0n_CLE high to GPMC_FCLK_MUX;
output write enable GPMC_WEn valid TIMEPARAGRANULARITY_X1
GNF3 tw(wenV-dV) Delay time, output data GPMC_AD[15:0] valid to div_by_1_mode; D-2 D+2 ns
output write enable GPMC_WEn valid GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF4 tw(wenIV-dIV) Delay time, output write enable GPMC_WEn div_by_1_mode; E-2 E+2 ns
invalid to output data GPMC_AD[15:0] invalid GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF5 tw(wenIV-cleIV) Delay time, output write enable GPMC_WEn div_by_1_mode; F-2 F+2 ns
invalid to output lower-byte enable and command GPMC_FCLK_MUX;
latch enable GPMC_BE0n_CLE invalid TIMEPARAGRANULARITY_X1
GNF6 tw(wenIV-CSn[i]V) Delay time, output write enable GPMC_WEn div_by_1_mode; G-2 G+2 ns
invalid to output chip select GPMC_CSn[i](2) GPMC_FCLK_MUX;
invalid TIMEPARAGRANULARITY_X1
GNF7 tw(aleH-wenV) Delay time, output address valid and address latch div_by_1_mode; C-2 C+2 ns
enable GPMC_ADVn_ALE high to output write GPMC_FCLK_MUX;
enable GPMC_WEn valid TIMEPARAGRANULARITY_X1
Table 7-59. GPMC and NAND Flash Switching Characteristics – Asynchronous Mode (continued)
see Figure 7-50, Figure 7-51, Figure 7-52 and Figure 7-53
(4)
NO. PARAMETER MODE MIN MAX UNIT
GNF8 tw(wenIV-aleIV) Delay time, output write enable GPMC_WEn div_by_1_mode; F-2 F+2 ns
invalid to output address valid and address latch GPMC_FCLK_MUX;
enable GPMC_ADVn_ALE invalid TIMEPARAGRANULARITY_X1
GNF9 tc(wen) Cycle time, write div_by_1_mode; H ns
GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF10 td(csnV-oenV) Delay time, output chip select GPMC_CSn[i](2) div_by_1_mode; I-2 I+2 ns
valid to output enable GPMC_OEn_REn valid GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF13 tw(oenV) Pulse duration, output enable GPMC_OEn_REn div_by_1_mode; K ns
valid GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF14 tc(oen) Cycle time, read div_by_1_mode; L ns
GPMC_FCLK_MUX;
TIMEPARAGRANULARITY_X1
GNF15 tw(oenIV-CSn[i]V) Delay time, output enable GPMC_OEn_REn div_by_1_mode; M-2 M+2 ns
invalid to output chip select GPMC_CSn[i](2) GPMC_FCLK_MUX;
invalid TIMEPARAGRANULARITY_X1
For GPMC_FCLK_MUX:
• CTRLMMR_GPMC_CLKSEL[1-0] CLK_SEL = 00 = CPSWHSDIV_CLKOUT3 = 2000/15 = 133.33 MHz
For TIMEPARAGRANULARITY_X1:
• GPMC_CONFIG1_i Register: TIMEPARAGRANULARITY = 0h = x1 latencies (affecting RD/WRCYCLETIME, RD/
WRACCESSTIME, PAGEBURSTACCESSTIME, CSONTIME, CSRD/WROFFTIME, ADVONTIME, ADVRD/WROFFTIME,
OEONTIME, OEOFFTIME, WEONTIME, WEOFFTIME, CYCLE2CYCLEDELAY, BUSTURNAROUND, TIMEOUTSTARTVALUE,
WRDATAONADMUXBUS)
GPMC_FCLK
GNF1 GNF6
GPMC_CSn[i]
GNF2 GNF5
GPMC_BE0n_CLE
GPMC_ADCn_ALE
GPMC_OEn_REn
GNF0
GPMC_WEn
GNF3 GNF4
GPMC_AD[15:0] Command
GPMC_12
A. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3.
GPMC_FCLK
GNF1 GNF6
GPMC_CSn[i]
GPMC_BE0n_CLE
GNF7 GNF8
GPMC_ADVn_ALE
GPMC_OEn_REn
GNF9
GNF0
GPMC_WEn
GNF3 GNF4
GPMC_AD[15:0] Address
GPMC_13
A. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3.
GPMC_FCLK
GNF12
GNF10 GNF15
GPMC_CSn[i]
GPMC_BE0n_CLE
GPMC_ADVn_ALE
GNF14
GNF13
GPMC_OEn_REn
GPMC_AD[15:0] DATA
GPMC_WAIT[j]
GPMC_14
A. GNF12 parameter illustrates amount of time required to internally sample input data. It is expressed in number of GPMC functional
clock cycles. From start of read cycle and after GNF12 functional clock cycles, input data will be internally sampled by active functional
clock edge. GNF12 value must be stored inside AccessTime register bits field.
B. GPMC_FCLK is an internal clock (GPMC functional clock) not provided externally.
C. In GPMC_CSn[i], i is equal to 0, 1, 2 or 3. In GPMC_WAIT[j], j is equal to 0 or 1.
GPMC_FCLK
GNF1 GNF6
GPMC_CSn[i]
GPMC_BE0n_CLE
GPMC_ADVn_ALE
GPMC_OEn_REn
GNF9
GNF0
GPMC_WEn
GNF3 GNF4
GPMC_AD[15:0] DATA
GPMC_15
7.10.5.9 I2C
The device contains six multicontroller Inter-Integrated Circuit (I2C) controllers. Each I2C controller was
designed to be compliant to the Philips I2C-bus™ specification version 2.1. However, the device IOs are not
fully compliant to the I2C electrical specification. The speeds supported and exceptions are described per port
below:
• MCU_I2C1, I2C1, I2C2, and I2C3
– Speeds:
• Standard-mode (up to 100 Kbits/s)
– 1.8 V
– 3.3 V
• Fast-mode (up to 400 Kbits/s)
– 1.8 V
– 3.3 V
– Exceptions:
• The IOs associated with these ports are not compliant to the fall time requirements defined in the I2C
specification because they are implemented with higher performance LVCMOS push-pull IOs that were
designed to support other signal functions that could not be implemented with I2C compatible IOs. The
LVCMOS IOs being used on these ports are connected such they emulate open-drain outputs. This
emulation is achieved by forcing a constant low output and disabling the output buffer to enter the Hi-Z
state.
• The I2C specification defines a maximum input voltage VIH of (VDDmax + 0.5 V), which exceeds the
absolute maximum ratings for the device IOs. The system must be designed to ensure the I2C signals
never exceed the limits defined in the Absolute Maximum Ratings section of this datasheet.
• MCU_I2C0 and I2C0
– Speeds:
• Standard-mode (up to 100 Kbits/s)
– 1.8 V
– 3.3 V
• Fast-mode (up to 400 Kbits/s)
– 1.8 V
– 3.3 V
• Hs-mode (up to 3.4 Mbit/s)
– 1.8 V
– Exceptions:
• The IOs associated with these ports were not design to support Hs-mode while operating at 3.3 V. So
Hs-mode is limited to 1.8-V operation.
• The rise and fall times of the I2C signals connected to these ports must not exceed a slew rate of 0.8
V/ns (or 8E+7 V/s). This limit is more restrictive than the minimum fall time limits defined in the I2C
specification. Therefore, it may be necessary to add additional capacitance to the I2C signals to slow
the rise and fall times such that they do not exceed a slew rate of 0.8 V/ns.
• The I2C specification defines a maximum input voltage VIH of (VDDmax + 0.5 V), which exceeds the
absolute maximum ratings for the device IOs. The system must be designed to ensure the I2C signals
never exceed the limits defined in the Absolute Maximum Ratings section of this datasheet.
Refer to the Philips I2C-bus specification version 2.1 for timing details.
For more details about features and additional description information on the device Inter-Integrated Circuit, see
the corresponding subsections within Signal Descriptions and Detailed Description sections.
7.10.5.10 MCAN
Table 7-61 and Table 7-62 presents timing conditions and switching characteristics for MCAN.
For more details about features and additional description information on the device Controller Area Network
Interface, see the corresponding subsections within Signal Descriptions and Detailed Description sections.
Note
The device has multiple MCAN modules. MCANn is a generic prefix applied to MCAN signal names,
where n represents the specific MCAN module.
For more information, see Controller Area Network (MCAN) section in Peripherals chapter in the device TRM.
7.10.5.11 MCSPI
For more details about features and additional description information on the device Serial Port Interface, see
the corresponding subsections within Signal Descriptions and Detailed Description sections.
Table 7-63 presents timing conditions for MCSPI.
Table 7-63. MCSPI Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 2 8.5 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 6 12 pF
For more information, see Multichannel Serial Peripheral Interface (MCSPI) section in Peripherals chapter in the
device TRM.
PHA=0
EPOL=1
SPI_CS[i] (OUT)
SM1
SM3
SM8 SM2 SM9
SPI_SCLK (OUT) POL=0
SM1
SM3
SM2
POL=1
SPI_SCLK (OUT)
SM5
SM5
SM4 SM4
SPI_D[x] (IN) Bit n-1 Bit n-2 Bit n-3 Bit n-4 Bit 0
PHA=1
EPOL=1
SPI_CS[i] (OUT)
SM2
SM1
SM8 SM3 SM9
SPI_SCLK (OUT) POL=0
SM1
SM2
SM3
POL=1
SPI_SCLK (OUT)
SM5
SM4
SM4 SM5
SPI_D[x] (IN) Bit n-1 Bit n-2 Bit n-3 Bit 1 Bit 0
SPRSP08_TIMING_McSPI_02
PHA=0
EPOL=1
SPI_CS[i] (OUT)
SM1
SM3
SM8 SM2 SM9
SPI_SCLK (OUT) POL=0
SM1
SM3
POL=1 SM2
SPI_SCLK (OUT)
SPI_D[x] (OUT) Bit n-1 Bit n-2 Bit n-3 Bit n-4 Bit 0
PHA=1
EPOL=1
SPI_CS[i] (OUT)
SM1
SM2
SM8 SM3 SM9
SPI_SCLK (OUT) POL=0
SM1
SM2
POL=1 SM3
SPI_SCLK (OUT)
SPI_D[x] (OUT) Bit n-1 Bit n-2 Bit n-3 Bit 1 Bit0
SPRSP08_TIMING_McSPI_01
PHA=0
EPOL=1
SPI_CS[i] (IN)
SS1
SS2
SS8 SS3 SS9
SPI_SCLK (IN) POL=0
SS1
SS2
POL=1 SS3
SPI_SCLK (IN)
SS5 SS4
SS4 SS5
SPI_D[x] (IN) Bit n-1 Bit n-2 Bit n-3 Bit n-4 Bit 0
PHA=1
EPOL=1
SPI_CS[i] (IN)
SS1
SS2
SS8 SS3 SS9
POL=0
SPI_SCLK (IN)
SS1
SS3
POL=1 SS2
SPI_SCLK (IN)
SS4
SS5
SS4 SS5
SPI_D[x] (IN) Bit n-1 Bit n-2 Bit n-3 Bit 1 Bit 0
SPRSP08_TIMING_McSPI_04
PHA=0
EPOL=1
SPI_CS[i] (IN)
SS1
SS2
SS8 SS3 SS9
SPI_SCLK (IN) POL=0
SS1
SS2
POL=1 SS3
SPI_SCLK (IN)
SPI_D[x] (OUT) Bit n-1 Bit n-2 Bit n-3 Bit n-4 Bit 0
PHA=1
EPOL=1
SPI_CS[i] (IN)
SS1
SS2
SS8 SS3 SS9
POL=0
SPI_SCLK (IN)
SS1
SS3
POL=1 SS2
SPI_SCLK (IN)
SPI_D[x] (OUT)
Bit n-1 Bit n-2 Bit n-3 Bit 1 Bit 0
SPRSP08_TIMING_McSPI_03
7.10.5.12 MMCSD
The MMCSD Host Controller provides an interface to embedded Multi-Media Card (MMC), Secure Digital (SD),
and Secure Digital IO (SDIO) devices. The MMCSD Host Controller deals with MMC/SD/SDIO protocol at
transmission level, data packing, adding cyclic redundancy checks (CRCs), start/end bit insertion, and checking
for syntactical correctness.
For more details about MMCSD interfaces, see the corresponding MMC0 and MMC1 subsections within Signal
Descriptions and Detailed Description sections.
Note
Some operating modes require software configuration of the MMC DLL delay settings, as shown in
Table 7-68 and Table 7-77.
The modes which show a value of "Tuning" in the ITAPDLYSEL column of Table 7-68 and Table 7-77
require a tuning algorithm to be used for optimizing input timing. Refer to the MMCSD Programming
Guide in the device TRM for more information on the tuning algorithm and configuration of input
delays required to optimize input timing.
For more information, see Multi-Media Card/Secure Digital (MMCSD) Interface section in Peripherals chapter in
the device TRM.
7.10.5.12.1 MMC0 - eMMC Interface
MMC0 interface is compliant with the JEDEC eMMC electrical standard v5.1 (JESD84-B51) and supports the
following eMMC applications:
• Legacy speed
• High speed SDR
• High speed DDR
• HS200
Table 7-68 presents the required DLL software configuration settings for MMC0 timing modes.
Table 7-68. MMC0 DLL Delay Mapping for all Timing Modes
REGISTER NAME MMCSD0_SS_PHY_CTRL_4_REG MMCSD0_SS_PHY_CTRL_5_REG
BIT FIELD [31:24] [20] [15:12] [8] [4:0] [17:16] [10:8] [2:0]
SELDLYTXCLK
BIT FIELD NAME STRBSEL OTAPDLYENA OTAPDLYSEL ITAPDLYENA ITAPDLYSEL FRQSEL CLKBUFSEL
SELDLYRXCLK
OUTPUT OUTPUT INPUT INPUT DLL DELAY
STROBE DLL REF
MODE DESCRIPTION DELAY DELAY DELAY DELAY DELAY CHAIN BUFFER
DELAY FREQUENCY
ENABLE VALUE ENABLE VALUE SELECT DURATION
8-bit PHY
Legacy
operating 1.8 V, 0x0 0x0 NA(1) 0x1 0x10 0x1 0x0 0x7
SDR
25 MHz
High 8-bit PHY
Speed operating 1.8 V, 0x0 0x0 NA(1) 0x1 0xA 0x1 0x0 0x7
SDR 50 MHz
High 8-bit PHY
Speed operating 1.8 V, 0x0 0x1 0x6 0x1 0x3 0x0 0x4 0x7
DDR 50 MHz
8-bit PHY
HS200 operating 1.8 V, 0x0 0x1 0x7 0x1 Tuning(2) 0x0 0x0 0x7
200 MHz
td(Trace Mismatch Propagation delay mismatch across all Legacy SDR, High Speed SDR 100 ps
Delay) traces High Speed DDR, HS200 8 ps
(1) Tuning means this mode requires a tuning algorithm to be used for optimal input timing
td(Trace Mismatch Propagation delay mismatch across all UHS–I DDR50, UHS–I SDR104 20 ps
Delay) traces All other modes 100 ps
MMC[x]_CLK
DS1 DS2
MMC[x]_CMD
DS3 DS4
MMC[x]_DAT[3:0]
DS5
DS6 DS7
MMC[x]_CLK
D S8
MMC[x]_CMD
D S9
MMC[x]_DAT[3:0]
MMC[x]_CLK
HS1 H S2
MMC[x]_CMD
HS3 H S4
MMC[x]_DAT[3:0]
HS5
HS6 HS7
MMC[x]_CLK
H S8
MMC[x]_CMD
H S9
MMC[x]_DAT[3:0]
MMC[x]_CLK
SDR121 SDR122
MMC[x]_CMD
SDR123 SDR124
MMC[x]_DAT[3:0]
SDR125
SDR126 SDR127
MMC[x]_CLK
SDR128 SDR128
MMC[x]_CMD
SDR129 SDR129
MMC[x]_DAT[3:0]
MMC[x]_CLK
SDR251 SDR252
MMC[x]_CMD
SDR253 SDR254
MMC[x]_DAT[3:0]
SDR255
SDR256 SDR257
MMC[x]_CLK
SDR258 SDR258
MMC[x]_CMD
SDR259 SDR259
MMC[x]_DAT[3:0]
SDR505
SDR506 SDR507
MMC[x]_CLK
SDR508 SDR508
MMC[x]_CMD
SDR509 SDR509
MMC[x]_DAT[3:0]
DDR505
DDR506 DDR507
MMC[x]_CLK
DDR508
MMC[x]_CMD
DDR509 DDR509
MMC[x]_DAT[3:0]
SDR1045
SDR1046 SDR1047
MMC[x]_CLK
SDR1048 SDR1048
MMC[x]_CMD
SDR1049 SDR1049
MMC[x]_DAT[3:0]
7.10.5.13 CPTS
Table 7-90, Table 7-91, Figure 7-76, Table 7-92, and Figure 7-77 present timing conditions, requirements, and
switching characteristics for CPTS.
Table 7-90. CPTS Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 0.5 5 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 2 10 pF
T1 T2
HWn_TSPUSH
T3 T4 T5
RFT_CLK
T6 T7
TS_COMP
T8 T9
TS_SYNC
T10 T11
SYNCn_OUT
For more information, see Data Movement Architecture (DMA) chapter in the device TRM.
7.10.5.14 OSPI
OSPI0 offers two data capture modes, PHY mode and Tap mode.
PHY mode uses an internal reference clock to transmit and receive data via a DLL based PHY, where each
reference clock cycle produces a single cycle of OSPI0_CLK for Single Data Rate (SDR) transfers or a half
cycle of OSPI0_CLK for Double Data Rate (DDR) transfers. PHY mode supports four clocking topologies
for the receive data capture clock. Internal PHY Loopback - uses the internal reference clock as the PHY
receive data capture clock. Internal Pad Loopback - uses OSPI0_LBCLKO looped back into the PHY from the
OSPI0_LBCLKO pin as the PHY receive data capture clock. External Board Loopback - uses OSPI0_LBCLKO
looped back into the PHY from the OSPI0_DQS pin as the PHY receive data capture clock. DQS - uses the DQS
output from the attached device as the PHY receive data capture clock. SDR transfers are not supported when
using the Internal Pad Loopback and DQS clocking topologies. DDR transfers are not supported when using the
Internal PHY Loopback or Internal Pad Loopback clocking topologies.
Tap mode uses an internal reference clock with selectable taps to adjusted data transmit and receive capture
delays relative to OSPI0_CLK, which is a divide by 4 of the internal reference clock for SDR transfers or a divide
by 8 of the internal reference clock for DDR transfers. Tap mode only supports one clocking topology for the
receive data capture clock. No Loopback - uses the internal reference clock as the Tap receive data capture
clock. This clocking topology supports a maximum internal reference clock rate of 200 MHz, which produces an
OSPI0_CLK rate up to 50 MHz for SDR mode or 25 MHz for DDR mode.
For more details about features and additional description information on the device Octal Serial Peripheral
Interface, see the corresponding subsections within Signal Descriptions and Detailed Description sections.
Section 7.10.5.14.1 defines timing requirements and switching characteristics associated with PHY mode and
Section 7.10.5.14.2 defines timing requirements and switching characteristics associated with Tap mode.
Table 7-93 presents timing conditions for OSPI0.
Table 7-93. OSPI0 Timing Conditions
PARAMETER MODE MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 1 6 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 3 10 pF
PCB CONNECTIVITY REQUIREMENTS
No Loopback
Propagation delay of OSPI0_CLK trace Internal PHY Loopback 450 ps
Internal Pad Loopback
td(Trace Delay)
Propagation delay of OSPI0_LBCLKO
External Board Loopback 2L(1) - 30 2L(1) + 30 ps
trace
Propagation delay of OSPI0_DQS trace DQS L(1) - 30 L(1) + 30 ps
Propagation delay mismatch of
td(Trace Mismatch
OSPI0_D[7:0] and OSPI0_CSn[3:0] All modes 60 ps
Delay)
relative to OSPI0_CLK
For more information, see Octal Serial Peripheral Interface (OSPI) section in Peripherals chapter in the device
TRM.
Receive
All modes PHY_CONFIG_RX_DLL_DELAY_FLD (2)
(1) Minimum setup and hold time requirements for OSPI0_D[7:0] inputs are not defined when Data Training is used to find the optimum
data valid window.
OSPI_DQS
OSPI_D[i:0]
OSPI_TIMING_04
Figure 7-78. OSPI0 Timing Requirements – PHY Data Training, DDR with DQS
OSPI_CSn
O4 O3 O5
OSPI_CLK
O2
O6 O6
O1
OSPI_D[i:0]
OSPI_TIMING_01
Note
Timing parameters defined in this section are only applicable when data training is not implemented
and DLL delays are configured as described in Table 7-97 and Table 7-100.
Setup time, OSPI0_D[7:0] valid before 1.8V, SDR with Internal PHY Loopback 4.8 ns
O19 tsu(D-CLK)
active OSPI0_CLK edge 3.3V, SDR with Internal PHY Loopback 5.19 ns
Hold time, OSPI0_D[7:0] valid after active 1.8V, SDR with Internal PHY Loopback -0.5 ns
O20 th(CLK-D)
OSPI0_CLK edge 3.3V, SDR with Internal PHY Loopback -0.5 ns
Setup time, OSPI0_D[7:0] valid before 1.8V, SDR with External Board Loopback 0.6 ns
O21 tsu(D-LBCLK)
active OSPI0_DQS edge 3.3V, SDR with External Board Loopback 0.9 ns
Hold time, OSPI0_D[7:0] valid after active 1.8V, SDR with External Board Loopback 1.7 ns
O22 th(LBCLK-D)
OSPI0_DQS edge 3.3V, SDR with External Board Loopback 2.0 ns
OSPI_CLK
O19 O20
OSPI_D[i:0]
OSPI_TIMING_05
Figure 7-80. OSPI0 Timing Requirements – PHY SDR with Internal PHY Loopback
OSPI_DQS
O21 O22
OSPI_D[i:0]
OSPI_TIMING_06
Figure 7-81. OSPI0 Timing Requirements – PHY SDR with External Board Loopback
OSPI_CSn
O10 O7 O11
OSPI_CLK O9 O8
O12
OSPI_D[i:0]
OSPI_TIMING_02
Setup time, OSPI0_D[7:0] valid before 1.8V, DDR with DQS -0.46 ns
O15 tsu(D-LBCLK)
active OSPI0_DQS edge 3.3V, DDR with External Board Loopback 1.23 ns
3.3V, DDR with DQS -0.66 ns
1.8V, DDR with External Board Loopback 1.24(1) ns
Hold time, OSPI0_D[7:0] valid after active 1.8V, DDR with DQS 3.59 ns
O16 th(LBCLK-D)
OSPI0_DQS edge 3.3V, DDR with External Board Loopback 1.44(1) ns
3.3V, DDR with DQS 7.92 ns
(1) This Hold time requirement is larger than the Hold time provided by a typical OSPI/QSPI/SPI device. Therefore, the trace length
between the SoC and attached OSPI/QSPI/SPI device must be sufficiently long enough to ensure that the Hold time is met at the SoC.
The length of the SoC's external loopback clock (OSPI0_LBCLKO to OSPI0_DQS) may need to be shortened to compensate.
OSPI_DQS
OSPI_D[i:0]
OSPI_TIMING_04
Figure 7-83. OSPI0 Timing Requirements – PHY DDR with External Board Loopback or DQS
OSPI_CSn
O4 O3 O5
OSPI_CLK
O2
O6 O6
O1
OSPI_D[i:0]
OSPI_TIMING_01
(1) T = OSPI_RD_DATA_CAPTURE_REG[DELAY_FLD]
(2) R = reference clock cycle time in ns
OSPI_CLK
O19 O20
OSPI_D[i:0]
OSPI_TIMING_05
OSPI_CSn
O10 O7 O11
OSPI_CLK O9 O8
O12
OSPI_D[i:0]
OSPI_TIMING_02
(1) T = OSPI_RD_DATA_CAPTURE_REG[DELAY_FLD]
(2) R = reference clock cycle time in ns
OSPI_CLK
OSPI_D[i:0]
OSPI_TIMING_03
OSPI_CSn
O4 O3 O5
OSPI_CLK
O2
O6 O6
O1
OSPI_D[i:0]
OSPI_TIMING_01
7.10.5.15 PCIe
The PCI-Express Subsystem is compliant with the PCIe® Base Specification, Revision 4.0. Refer to the
specification for timing details.
For more details about features and additional description information on the device Peripheral Component
Interconnect Express (PCIe), see the SERDES0 Signal Descriptions and the corresponding subsection within
Detailed Description.
For more information, see Peripheral Component Interconnect Express (PCIe) Subsystem section in Peripherals
chapter of the device TRM.
7.10.5.16 PRU_ICSSG
The device has integrated two identical Programmable Real-Time Unit Subsystem and Industrial Communication
Subsystems - Gigabit (PRU_ICSSG), PRU_ICSSG0 and PRU_ICSSG1. The programmable nature of the PRU
cores, along with their access to pins, events and all device resources, provides flexibility in implementing fast
real-time responses, specialized data handling operations, custom peripheral interfaces, and in offloading tasks
from the other processor cores in the device.
For more details about features and additional description information on the device PRU_ICSSG, see the
corresponding subsections within Signal Descriptions and Detailed Description sections.
Note
The PRU_ICSSG contains a second layer of multiplexing to enable additional functionality on the PRU
GPO and GPI signals. This internal wrapper multiplexing is described in the PRU_ICSSG chapter in
the device TRM.
Note
The PRU_ICSSG PRU signals have different functionality depending on the mode of operation. The
signal naming in this section matches the naming used in the PRU Module Interface section in the
device TRM.
GPO[n:0]
PRDO1 PRU_TIMING_02
A. n in GPO[n:0] = 19.
PRPC1
PRPC3
PRPC2
CLOCKIN
DATAIN
PRPC5
PRPC4 PRU_TIMING_03
Figure 7-90. PRU_ICSSG PRU Parallel Capture Timing Requirements – Rising Edge Mode
PRPC1
PRPC3
PRPC2
CLOCKIN
DATAIN
PRPC5
PRPC4 PRU_TIMING_04
Figure 7-91. PRU_ICSSG PRU Parallel Capture Timing Requirements – Falling Edge Mode
(1) P = Internal shift in clock period, defined by PRUn_GPI_DIV0 and PRUn_GPI_DIV1 bit fields in the ICSSG_GPCFGn_REG register.
PRUn represents the respective PRU0 or PRU1 instance.
PRSI1
PRSI2
DATAIN
PRU_TIMING_05
(1) P = Software programmable shift out clock period, defined by PRUn_GPO_DIV0 and PRUn_GPO_DIV1 bit fields in the
ICSSG_GPCFGn_REG register, where PRUn represents the respective PRU0 or PRU1 instance.
(2) The Z parameter is defined as follows, where PRUn represents the respective PRU0 or PRU1 instance.
a. If PRUn_GPI_DIV0 and PRUn_GPI_DIV1 are INTEGERS -or- if PRUn_GPI_DIV0 is a NON-INTEGER and PRUn_GPI_DIV1 is
an EVEN INTEGER then, Z equals (PRUn_GPI_DIV0 * PRUn_GPI_DIV1).
b. If PRUn_GPI_DIV0 is a NON-INTEGER and PRUn_GPI_DIV1 is an ODD INTEGER then, Z equals (PRUn_GPI_DIV0 *
PRUn_GPI_DIV1 + 0.5).
c. If PRUn_GPI_DIV0 is an INTEGER and PRUn_GPI_DIV1 is a NON-INTEGER then, Z equals (PRUn_GPI_DIV0 *
PRUn_GPI_DIV1 + 0.5 * PRUn_GPI_DIV0).
d. If PRUn_GPI_DIV0 and PRUn_GPI_DIV1 are NON-INTEGERS then, Z equals (PRUn_GPI_DIV0 * PRUn_GPI_DIV1 + 0.25 *
PRUn_GPI_DIV0).
(3) The Y parameter is defined as follows, where PRUn represents the respective PRU0 or PRU1 instance.
a. If PRUn_GPI_DIV0 and PRUn_GPI_DIV1 are INTEGERS -or- if PRUn_GPI_DIV0 is a NON-INTEGER and PRUn_GPI_DIV1 is
an EVEN INTEGER then, Y equals (PRUn_GPI_DIV0 * PRUn_GPI_DIV1).
b. If PRUn_GPI_DIV0 is a NON-INTEGER and PRUn_GPI_DIV1 is an ODD INTEGER then, Y equals (PRUn_GPI_DIV0 *
PRUn_GPI_DIV1 - 0.5).
c. If PRUn_GPI_DIV0 is an INTEGER and PRUn_GPI_DIV1 is a NON-INTEGER then, Y equals (PRUn_GPI_DIV0 *
PRUn_GPI_DIV1 - 0.5 * PRUn_GPI_DIV0).
d. If PRUn_GPI_DIV0 and PRUn_GPI_DIV1 are NON-INTEGERS then, Y1 equals (PRUn_GPI_DIV0 * PRUn_GPI_DIV1 - 0.25 *
PRUn_GPI_DIV0) and Y2 equals (PRUn_GPI_DIV0 * PRUn_GPI_DIV1 + 0.25 * PRUn_GPI_DIV0), where Y1 is the first high
pulse and Y2 is the second high pulse.
PRSO1
PRSO2H PRSO2L
CLOCKOUT
DATAOUT
PRSO3
PRU_TIMING_06
PRSD1
PRSD2H
SDx_CLK
PRSD2L
SDx_D
PRSD4
PRSD3 PRU_TIMING_07
PRSD2L
SDx_CLK
SDx_D
PRSD4
PRSD3 PRU_TIMING_08
(1) P = 1x (or TX) clock period in ns, defined by PRUn_ED_TX_DIV_FACTOR and PRUn_ED_TX_DIV_FACTOR_FRAC in the
ICSSG_PRUn_ED_TX_CFG_REG register. PRUn represents the respective PRU0 or PRU1 instance.
PRPIF1 PRPIF2
PIF_DATA_IN
PRUPIF_TIMING_01
(1) P = 1x (or TX) clock period in ns, defined by PRUn_ED_TX_DIV_FACTOR and PRUn_ED_TX_DIV_FACTOR_FRAC in the
ICSSG_PRUn_ED_TX_CFG_REG register. PRUn represents the respective PRU0 or PRU1 instance.
PRPIF3
PRPIF4 PRPIF5
PIF_CLK
PRPIF6
PIF_DATA_OUT
PRPIF7
PIF_DATA_EN
PWM_A/B
PRPWM1
PRU_PWM_TIMING_01
EDC_SYNC_OUTx
PRIEP2 PRIEP1
PRIEP3
PRIEP4
EDIO_DATA_IN[7:0]
PRU_IEP_TIMING_01
EDIO_DATA_OUT
IEPIO4 PRU_EDIO_DATA_OUT_TIMING_00
PRLA1
EDC_LATCH_INx
PRLA2
PRU_IEP_TIMING_02
(1) This value represents an absolute maximum load capacitance. As the UART baud rate increases, it may be necessary to reduce the
load capacitance to a value less than this maximum limit to provide enough timing margin for the attached device. The output rise/fall
times increase as capacitive load increases, which decreases the time data is valid for the receiver of the attached devices. Therefore,
it is important to understand the minimum data valid time required by the attached device at the operating baud rate. Then use the
device IBIS models to verify the actual load capacitance on the UART signals does not increase the rise/fall times beyond the point
where the minimum data valid time of the attached device is violated.
0.95U(1)
2 tw(RXDS) Pulse width, receive start bit low (2) ns
(1) U = UART baud time in ns = 1/actual baud rate, where the actual baud rate is defined in the UART Baud Rate Settings table of the
device TRM.
2
1
Start
Bit VIH
PRGi_UART0_RXD
VIL
Data Bits
4
3
Start
Bit
PRGi_UART0_TXD
Data Bits
PRU_UART_TIMING_01_RCVRVIHVIL
PREP1
CAP
PREP2
SYNCI
PREP3
APWM
PREP4
SYNCO
MDIO3
MDIO4
MDIO5
MDIO[x]_MDC
MDIO1
MDIO2
MDIO[x]_MDIO
(input)
MDIO7
MDIO[x]_MDIO
(output)
CPSW2G_MDIO_TIMING_01
Note
In order to ensure the MII_G_RT I/O timing values published in the device data sheet, the
PRU_ICSSG ICSSGn_CORE_CLK (where n = 0 to 1) core clock must be configured for 200 MHz,
225 MHz, or 250 MHz and the TX_CLK_DELAYn (where n = 0 or 1) bit field in the ICSSG_TXCFG0/1
register must be set to 0h (default value).
Table 7-131, Table 7-132, Figure 7-106, Table 7-133, Figure 7-107, Table 7-134, Figure 7-108, Table 7-135, and
Figure 7-109 present timing conditions, requirements, and switching characteristics for PRU_ICSSG MII.
Table 7-131. PRU_ICSSG MII Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 0.9 3.6 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 2 20 pF
PMIR1
PMIR2 PMIR3
MII_RX_CLK
PRU_MII_RT_TIMING_04
Table 7-133. PRU_ICSSG MII Timing Requirements – MII[x]_RXD[3:0], MII[x]_RX_DV, and MII[x]_RX_ER
see Figure 7-107
NO. PARAMETER DESCRIPTION MODE MIN MAX UNIT
tsu(RXD-RX_CLK) Setup time, MII[x]_RXD[3:0] valid before MII[x]_RX_CLK 8 ns
tsu(RX_DV-RX_CLK) Setup time, MII[x]_RX_DV valid before MII[x]_RX_CLK 10 Mbps 8 ns
tsu(RX_ER-RX_CLK) Setup time, MII[x]_RX_ER valid before MII[x]_RX_CLK 8 ns
PMIR4
tsu(RXD-RX_CLK) Setup time, MII[x]_RXD[3:0] valid before MII[x]_RX_CLK 8 ns
100
tsu(RX_DV-RX_CLK) Setup time, MII[x]_RX_DV valid before MII[x]_RX_CLK 8 ns
Mbps
tsu(RX_ER-RX_CLK) Setup time, MII[x]_RX_ER valid before MII[x]_RX_CLK 8 ns
th(RX_CLK-RXD) Hold time, MII[x]_RXD[3:0] valid after MII[x]_ RX_CLK 8 ns
th(RX_CLK-RX_DV) Hold time, MII[x]_RX_DV valid after MII[x]_RX_CLK 10 Mbps 8 ns
th(RX_CLK-RX_ER) Hold time, MII[x]_RX_ER valid after MII[x]_RX_CLK 8 ns
PMIR5
th(RX_CLK-RXD) Hold time, MII[x]_RXD[3:0] valid after MII[x]_ RX_CLK 8 ns
100
th(RX_CLK-RX_DV) Hold time, MII[x]_RX_DV valid after MII[x]_RX_CLK 8 ns
Mbps
th(RX_CLK-RX_ER) Hold time, MII[x]_RX_ER valid after MII[x]_RX_CLK 8 ns
PMIR4
PMIR5
MII_RX_CLK
MII_RXD[3:0],
MII_RX_DV, MII_RX_ER
PMIT1
PMIT2 PMIT3
MII_TX_CLK
PMIT4
MII_TX_CLK
MII_TXD[3:0], MII_TX_EN
RGMII1
RGMII2
RGMII3
(A)
RGMII[x]_RXC
RGMII4
RGMII5
(B)
RGMII[x]_RD[3:0] 1st Half-byte 2nd Half-byte
(B)
RGMII[x]_RX_CTL RXDV RXERR
A. RGMII[x]_RXC must be externally delayed relative to the data and control pins.
B. Data and control information is received using both edges of the clocks. RGMII[x]_RD[3:0] carries data bits 3-0 on the rising edge of
RGMII[x]_RXC and data bits 7-4 on the falling edge of RGMII[x]_RXC. Similarly, RGMII[x]_RX_CTL carries RXDV on rising edge of
RGMII[x]_RXC and RXERR on falling edge of RGMII[x]_RXC.
RGMII6
RGMII7
RGMII8
(A)
RGMII[x]_TXC
RGMII9
(B)
RGMII[x]_TD[3:0] 1st Half-byte 2nd Half-byte
RGMII10
(B)
RGMII[x]_TX_CTL TXEN TXERR
A. TXC is delayed internally before being driven to the RGMII[x]_TXC pin. This internal delay is always enabled.
B. Data and control information is received using both edges of the clocks. RGMII[x]_TD[3:0] carries data bits 3-0 on the rising edge of
RGMII[x]_TXC and data bits 7-4 on the falling edge of RGMII[x]_TXC. Similarly, RGMII[x]_TX_CTL carries TXEN on rising edge of
RGMII[x]_TXC and TXERR on falling edge of RGMII[x]_TXC.
7.10.5.17 Timers
For more details about features and additional description information on the device Timers, see the
corresponding subsections within Signal Descriptions and Detailed Description sections.
Table 7-141. Timer Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 0.5 5 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 2 10 pF
T1 T2
TIMER_IOx (inputs)
T3 T4
TIMER_IOx (outputs)
TIMER_01
For more information, see Timers section in Peripherals chapter in the device TRM.
7.10.5.18 UART
For more details about features and additional description information on the device Universal Asynchronous
Receiver Transmitter, see the corresponding subsections within Signal Descriptions and Detailed Description
sections.
Table 7-144. UART Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 0.5 5 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 1 30(1) pF
(1) This value represents an absolute maximum load capacitance. As the UART baud rate increases, it may be necessary to reduce the
load capacitance to a value less than this maximum limit to provide enough timing margin for the attached device. The output rise/fall
times increase as capacitive load increases, which decreases the time data is valid for the receiver of the attached devices. Therefore,
it is important to understand the minimum data valid time required by the attached device at the operating baud rate. Then use the
device IBIS models to verify the actual load capacitance on the UART signals does not increase the rise/fall times beyond the point
where the minimum data valid time of the attached device is violated.
0.95U(1)
2 tw(RXDS) Pulse width, receive start bit low (2) ns
2
1
Start
VIH
UARTi_RXD Bit
VIL
Data Bits
4
3
Start
UARTi_TXD Bit
Data Bits
UART_TIMING_01_RCVRVIHVIL
For more information, see Universal Asynchronous Receiver/Transmitter (UART) section in Peripherals chapter
in the device TRM.
7.10.5.19 USB
The USB 2.0 subsystem is compliant with the Universal Serial Bus (USB) Specification, revision 2.0. Refer to the
specification for timing details.
The USB 3.1 GEN1 subsystem is compliant with the Universal Serial Bus (USB) 3.1 Specification, revision 1.0.
Refer to the specification for timing details.
For more details about features and additional description information on the device Universal Serial Bus
Subsystem (USB), see the SERDES0 Signal Descriptions and the corresponding subsection within Detailed
Description.
DBTR5 toh(TRC_CLK-TRC_DATAI) Output hold time, TRC_CLK edge to TRC_DATA invalid 0.81 ns
DBTR6 tosu(TRC_CTLV-TRC_CLK) Output setup time, TRC_CTL valid to TRC_CLK edge 0.81 ns
DBTR7 toh(TRC_CLK-TRC_CTLI) Output hold time, TRC_CLK edge to TRC_CTL invalid 0.81 ns
3.3V Mode
DBTR1 tc(TRC_CLK) Cycle time, TRC_CLK 8.67 ns
DBTR2 tw(TRC_CLKH) Pulse width, TRC_CLK high 3.58 ns
DBTR3 tw(TRC_CLKL) Pulse width, TRC_CLK low 3.58 ns
tosu(TRC_DATAV-
DBTR4 Output setup time, TRC_DATA valid to TRC_CLK edge 1.08 ns
TRC_CLK)
DBTR5 toh(TRC_CLK-TRC_DATAI) Output hold time, TRC_CLK edge to TRC_DATA invalid 1.08 ns
DBTR6 tosu(TRC_CTLV-TRC_CLK) Output setup time, TRC_CTL valid to TRC_CLK edge 1.08 ns
DBTR7 toh(TRC_CLK-TRC_CTLI) Output hold time, TRC_CLK edge to TRC_CTL invalid 1.08 ns
DBTR1
DBTR2 DBTR3
TRC_CLK
(Worst Case 1)
(Ideal)
(Worst Case 2)
DBTR4 DBTR5 DBTR4 DBTR5
DBTR6 DBTR7 DBTR6 DBTR7
TRC_DATA
TRC_CTL
SPRSP08_Debug_01
7.10.6.2 JTAG
Table 7-149. JTAG Timing Conditions
PARAMETER MIN MAX UNIT
INPUT CONDITIONS
SRI Input slew rate 0.5 2.0 V/ns
OUTPUT CONDITIONS
CL Output load capacitance 5 15 pF
PCB CONNECTIVITY REQUIREMENTS
td(Trace Delay) Propagation delay of each trace 83.5 1000(1) ps
td(Trace Mismatch Delay) Propagation delay mismatch across all traces 100 ps
(1) Maximum propagation delay associated with the JTAG signal traces has a significant impact on maximum TCK operating frequency. It
may be possible to increase the trace delay beyond this value, but the operating frequency of TCK must be reduced to account for the
additional trace delay.
(1) The maximum TCK operating frequency assumes the following timing requirements and switching characteristics for the attached
debugger. The operating frequency of TCK must be reduced to provide appropriate timing margin if the debugger exceeds any of these
assumptions.
• Minimum TDO setup time of 2.2 ns relative to the rising edge of TCK
• TDI and TMS output delay in the range of -16.1 ns to 14.1 ns relative to the falling edge of TCK
(2) P = TCK cycle time in ns
J1
J2 J3
TCK
J4 J5 J4 J5
TDI / TMS
J7
J6
TDO
8 Detailed Description
8.1 Overview
AM64x is an extension of the Sitara™ industrial-grade family of heterogeneous Arm processors. AM64x is built
for industrial applications, such as motor drives and programmable logic controllers (PLCs), which require a
unique combination of real-time processing and communications with applications processing. AM64x combines
two instances of Sitara’s gigabit TSN-enabled PRU-ICSSG, up to two Arm Cortex-A53 cores, up to four Cortex-
R5F MCUs, and a Cortex-M4F MCU domain.
AM64x is architected to provide real-time performance through the high-performance R5Fs, Tightly-Coupled
Memory banks, configurable SRAM partitioning, and low-latency paths to and from peripherals for rapid data
movement in and out of the SoC. This deterministic architecture allows for AM64x to handle the tight control
loops found in servo drives, while the peripherals like FSI, GPMC, PWMs, sigma delta decimation filters, and
absolute encoder interfaces help enable a number of different architectures found in these systems.
The Cortex-A53s provide the powerful computing elements necessary for Linux applications. Linux, and Real-
time (RT) Linux, is provided through TI’s Processor SDK Linux which stays updated to the latest Long Term
Support (LTS) Linux kernel, bootloader and Yocto file system on an annual basis. AM64x helps bridge the Linux
world with the real-time world by enabling isolation between Linux applications and real-time streams through
configurable memory partitioning. The Cortex-A53s can be assigned to work strictly out of DDR for Linux, and
the internal SRAM can be broken up into various sizes for the Cortex-R5Fs to use together or independently.
The PRU_ICSSG in AM64x provides the flexible industrial communications capability necessary to run gigabit
TSN, EtherCAT, PROFINET, EtherNet/IP, and various other protocols. In addition, the PRU_ICSSG also enables
additional interfaces in the SoC including sigma delta decimation filter modules and absolute encoder interfaces.
Functional safety features can be enabled through the MCU domain with an integrated Cortex-M4F and
dedicated peripheral set which can all be shared or isolated from the rest of the SoC. AM64x also supports
secure boot.
Note
For more information on features, subsystems, and architecture of superset device System on Chip
(SoC), see the device TRM.
Note
The Cortex®-R5F processor is a Cortex-R5 processor that includes the optional Floating Point Unit
(FPU) extension.
For more information, see Dual-R5F Subsystem (R5FSS) section in Processors and Accelerators chapter in the
device TRM.
8.2.3 Arm Cortex-M4F (M4FSS)
The M4FSS module on the AM64x device provides a safety channel (secondary channel - working in conjunction
with an external microcontroller)- or- a general purpose MCU.
The M4FSS module supports the following features:
• Cortex M4F With MPU
• ARMv7-M architecture
• Support for Nested Vectored Interrupt Controller (NVIC) with 64 inputs
For more information, see PDMA Controller section in DMA Controllers chapter in the device TRM.
8.4.2 Peripherals
8.4.2.1 ADC
The analog-to-digital converter (ADC) module is a single-channel general purpose analog-to-digital converter
with an 8-input analog multiplexer, which supports 12-bit conversion samples from an analog front end (AFE).
Additionally, the EPWM integration allows this synchronization scheme to be extended to the capture peripheral
modules (ECAP). The number of modules is device-dependent and based on target application needs. Modules
can also operate stand-alone.
The device has six instances of EPWM modules.
For more information, see Enhanced Pulse Width Modulation (EPWM) Module section in Peripherals chapter in
the device TRM.
8.4.2.6 ELM
The Error Location Module (ELM) is used with the GPMC. Syndrome polynomials generated on-the-fly when
reading a NAND flash page and stored in GPMC registers are passed to the ELM. A host processor can then
correct the data block by flipping the bits to which the ELM error-location outputs point.
When reading from NAND flash memories, some level of error-correction is required. In the case of NAND
modules with no internal correction capability, sometimes referred to as bare NANDs, the correction process is
delegated to the memory controller. ELM can be also used to support parallel NOR flash or NAND flash.
The General-Purpose Memory Controller (GPMC) probes data read from an external NAND flash and uses
this to compute checksum-like information, called syndrome polynomials, on a per-block basis. Each syndrome
polynomial gives a status of the read operations for a full block, including 512 bytes of data, parity bits,
and an optional spare-area data field, with a maximum block size of 1023 bytes. Computation is based on
a Bose-Chaudhuri-Hocquenghem (BCH) algorithm. The ELM extracts error addresses from these syndrome
polynomials.
For more information, see Error Location Module (ELM) section in Peripherals chapter in the device TRM.
8.4.2.7 ESM
The Error Signaling Module (ESM) aggregates safety-related events and/or errors from throughout the device
into one location. The module can signal both low and high priority interrupts to a processor to deal with a safety
event and/or manipulate an I/O error pin to signal external hardware that an error has occurred. This allows an
external controller to reset the device or keep the system in safe, known state.
For more information, see Error Signaling Module (ESM) section in Peripherals chapter in the device TRM.
8.4.2.8 GPIO
The general-purpose input/output (GPIO) peripheral provides dedicated general-purpose pins that can be
configured as either inputs or outputs. When configured as an output, user can write to an internal register
to control the state driven on the output pin. When configured as an input, user can obtain the state of the input
by reading the state of an internal register.
In addition, the GPIO peripheral can produce host CPU interrupts and DMA synchronization events in different
interrupt/event generation modes.
For more information, see General-Purpose Interface (GPIO) section in Peripherals chapter in the device TRM.
8.4.2.9 EQEP
The Enhanced Quadrature Encoder Pulse (EQEP) peripheral is used for direct interface with a linear or rotary
incremental encoder to get position, direction and speed information from a rotating machine for use in high
performance motion and position control system. The disk of an incremental encoder is patterned with a single
track of slots patterns. These slots create an alternating pattern of dark and light lines. The disk count is
defined as the number of dark/light line pairs that occur per revolution (lines per revolution). As a rule, a second
track is added to generate a signal that occurs once per revolution (index signal: QEPI), which can be used
to indicate an absolute position. Encoder manufacturers identify the index pulse using different terms such as
index, marker, home position and zero reference.
To derive direction information, the lines on the disk are read out by two different photo-elements that "look"
at the disk pattern with a mechanical shift of 1/4 the pitch of a line pair between them. This shift is realized
with a reticle or mask that restricts the view of the photo-element to the desired part of the disk lines. As the
disk rotates, the two photo-elements generate signals that are shifted 90 degrees out of phase from each other.
These are commonly called the quadrature QEPA and QEPB signals. The clockwise direction for most encoders
is defined as the QEPA channel going positive before the QEPB channel and vice versa.
The encoder wheel typically makes one revolution for every revolution of the motor or the wheel can be at a
geared rotation ratio with respect to the motor. Therefore, the frequency of the digital signal coming from the
QEPA and QEPB outputs varies proportionally with the velocity of the motor. For example, a 2000-line encoder
directly coupled to a motor running at 5000 revolutions per minute (rpm) results in a frequency of 166.6 KHz, so
by measuring the frequency of either the QEPA or QEPB output, the processor can determine the velocity of the
motor.
For more information, see Enhanced Quadrature Encoder Pulse (EQEP) Module section in Peripherals chapter
in the device TRM.
8.4.2.10 General-Purpose Memory Controller (GPMC)
The General-Purpose Memory Controller is a unified memory controller dedicated for interfacing with external
memory devices like:
• Asynchronous SRAM-like memories and application-specific integrated circuit (ASIC) devices
• Asynchronous, synchronous, and page mode (available only in non-multiplexed mode) burst NOR flash
devices
• NAND flash
• Pseudo-SRAM devices
For more information, see General-Purpose Memory Controller section in Peripherals chapter in the device
TRM.
8.4.2.11 I2C
The Inter-IC Bus (I2C) interface is implemented using the mshsi2c module. This peripheral implements the
multi-controller I2C bus, which allows serial transfer of 8-bit data to and from other I2C controller and target
devices, through a two-wire interface.
The I2C module supports the following main features:
• Compliant with Philips I2C specification version 2.1
• Supported Speeds:
– Standard mode (up to 100 K bits/s)
– Fast mode (up to 400 K bits/s)
– High-speed mode (up to 3.4 M bits/s), I2C0 and MCU_I2C0 only
• Multi-controller transmitter and target receiver mode
• Multi-controller receiver and target transmitter mode
• Combined controller transmit/receive and receive/transmit modes
• 7-bit and 10-bit device addressing modes
• Built-in 32-byte FIFO for buffered read or write
• Programmable multi-target channel (responds to 4 separates addresses)
• Programmable clock generation
• Support for asynchronous wake-up
• One interrupt line
For more information, see Inter-Integrated Circuit (I2C) Interface section in Peripherals chapter in the device
TRM.
8.4.2.12 MCAN
The Controller Area Network (CAN) is a serial communications protocol which efficiently supports distributed
real-time control with a high level of security. CAN has high immunity to electrical interference and the ability
to self-diagnose and repair data errors. In a CAN network, many short messages are broadcast to the entire
network, which provides for data consistency in every node of the system.
The MCAN module supports both classic CAN and CAN FD (CAN with Flexible Data-Rate) specifications. CAN
FD feature allows high throughput and increased payload per data frame. The classic CAN and CAN FD devices
can coexist on the same network without any conflict.
The device supports 2 MCAN modules
For more information, see Modular Controller Area Network (MCAN) section in Peripherals chapter in the device
TRM.
8.4.2.13 MCRC Controller
VBUSM CRC controller is a module which is used to perform CRC (Cyclic Redundancy Check) to verify the
integrity of a memory system. A signature representing the contents of the memory is obtained when the
contents of the memory are read into MCRC Controller. The responsibility of MCRC controller is to calculate
the signature for a set of data and then compare the calculated signature value against a pre-determined good
signature value. MCRC controller provides four channels to perform CRC calculation on multiple memories in
parallel and can be used on any memory system. Channel 1 can also be put into data trace mode, where MCRC
controller compresses each data being read through CPU read data bus.
For more information, see MCRC Controller section in Interprocessor Communication chapter in the device
TRM.
8.4.2.14 MCSPI
The MCSPI module is a multichannel transmit/receive, controller/peripheral synchronous serial bus.
There are total of seven MCSPI modules in the device.
For more information, see Multichannel Serial Peripheral Interface (MCSPI) section in Peripherals chapter in the
device TRM.
8.4.2.15 MMCSD
There are two Multi-Media Card/Secure Digital (MMCSD) modules inside the device - MMCSD0 and MMCSD1.
Each MMCSD module includes one MMCSD Host Controller, where MMCSD0 is associated with MMC0 and
MMCSD1 is associated with MMC1.
The MMCSD Host Controller supports:
• One controller with 8-bit wide data bus
• One controller with 4-bit wide data bus
• Support of eMMC5.1 Host Specification (JESD84-B51)
• Support of SD Host Controller Standard Specification - SDIO 3.00
• Integrated DMA controller supporting SD Advanced DMA - ADMA2 and ADMA3
• eMMC Electrical Standard 5.1 (JESD84-B51)
• Multi-Media card features:
– Backward compatible with earlier eMMC standards
– Legacy MMC SDR: 1.8 V, 8/4/1-bit bus width, 0-25 MHz, 25/12.5/3.125 MB/s
– High Speed SDR: 1.8 V, 8/4/1-bit bus width, 0-50 MHz, 50/25/6.25 MB/s
– High Speed DDR: 1.8 V, 8/4-bit bus width, 0-50 MHz, 100/50 MB/s
– HS200 SDR: 1.8 V, 0-200 MHz, 8/4-bit bus width, 200/100 MB/s
• SD card support: SDIO, SDR12, SDR25, SDR50, DDR50
• System bus interface: CBA 4.0 VBUSM initiator port with 64-bit data width and 64-bit address, little Endian
only
• Configuration bus interface: CBA 4.0 VBUSM with 32-bit data width, 32-bit aligned accesses only, linear
incrementing addressing mode, little Endian only
For more information, see Multi-Media Card/Secure Digital (MMCSD) Interface section in Peripherals chapter in
the device TRM.
8.4.2.16 OSPI
The Octal Serial Peripheral Interface (OSPI) module is a kind of Serial Peripheral Interface (SPI) module which
allows single, dual, quad or octal read and write access to external flash devices. This module has a memory
mapped register interface, which provides a direct memory interface for accessing data from external flash
devices, simplifying software requirements.
The OSPI module is used to transfer data, either in a memory mapped direct mode (for example a processor
wishing to execute code directly from external flash memory), or in an indirect mode where the module is
set-up to silently perform some requested operation, signaling its completion via interrupts or status registers.
For indirect operations, data is transferred between system memory and external flash memory via an internal
SRAM which is loaded for writes and unloaded for reads by a device controller at low latency system speeds.
Interrupts or status registers are used to identify the specific times at which this SRAM should be accessed using
user programmable configuration registers.
For more information, see Octal Serial Peripheral Interface (OSPI) section in Peripherals chapter in the device
TRM.
8.4.2.17 Peripheral Component Interconnect Express (PCIe)
The PCIe subsystem supports the following main features:
• Dual mode – root port (RP) or end point (EP) modes.
• 1-lane configuration with up to 5.0GT/lane.
• 62.5/125 MHz operation on PIPE interface for Gen1/Gen2 respectively
• Constant 32-bit PIPE width for Gen1/Gen2 modes
• Maximum outbound payload size of 128 bytes
• Maximum inbound payload size of 128 bytes
• Maximum remote read request size of 4K bytes
• Maximum number of nonposted outstanding transactions: 8 on each VBUSM interface.
• Four virtual channels (4VC)
• Resizable BAR capability
• SRIS support
• Power Management
– L1 Power Management Substate support
– D1 support
– L1 Power Shutoff support
• Legacy, MSI, and MSI-X interrupt support
• 32 outbound address translation regions
• Precision time measurement (PTM)
For more information, see Peripheral Component Interconnect Express (PCIe) Subsystem section in Peripherals
chapter in the device TRM.
8.4.2.18 Serializer/Deserializer (SerDes) PHY
Integrated in the MAIN domain is one instance of high-speed differential interface implemented with Serializer/
Deserializer (SerDes) Multi-protocol Multi-link PHY with the following main blocks:
• Single-lane SerDes PHY with common module for peripheral and Tx clocking handling
• Physical coding sub-block for data translation from/to the parallel interface, as well as data encoding/
decoding and symbol alignment
• MUX module for device interface multiplexing into a single SerDes lane (Tx and Rx)
• A wrapper for sending control and reporting status signals from the SerDes and muxes
For more information, see Serializer/Deserializer (SerDes) section in Peripherals chapter in the device TRM.
8.4.2.19 Real Time Interrupt (RTI/WWDT)
This section describes the Real Time Interrupt (RTI) modules with Windowed Watchdog Timer (WWDT)
functionality for the device.
For more information, see Real Time Interrupt (RTI/WWDT) Module section in Peripherals chapter of the device
TRM.
8.4.2.20 Dual Mode Timer (DMTIMER)
The Dual Mode Timer (DMTIMER) module supports the following main features:
• Interrupts generated on overflow, compare, and capture events
• Free running 32-bit upward counter
• Supported operating modes:
– Compare and capture modes
– Auto-reload mode
– Start-stop mode
• Programmable divider clock source (2n with n=[0:8])
• Dedicated input trigger for capture mode, and dedicated output trigger/PWM (pulse width modulation) signal
• On the fly read/write register (while counting)
• Generate 1-ms tick with 32768-Hz functional clock
For more information, see Timers section in Peripherals chapter in the device TRM.
8.4.2.21 UART
The UART module supports the following main features:
• 16C750 compatibility
• Baud rate from 300 bps up to 12 Mbps (MCU_UART0 and MCU_UART1 limited to 3.7 Mbps)
• Auto-baud between 1200 bps and 115.2 Kbps
• Software/hardware flow control
– Programmable Xon/Xoff characters
– Programmable Auto-RTS and Auto CTS
• Programmable serial interface characteristics
– 5-, 6-, 7-, 8-bit characters
– Even, odd, mark (always 1), space (always 0), or no parity (non-parity bit frame) bit generation and
detection
– 1-, 1.5-, or 2-stop bit generation
• Optional multi-drop transmission
• Configurable time-guard feature
• False start bit detection
• Line break generation and detection
• Modem control functions on UART0 (CTS, RTS, DSR, DTR, RI, and DCD)
• Fully prioritized interrupt system controls
• Internal test and loopback capabilities
• RS-485 External transceiver auto flow control support
For more information, see Universal Synchronous/Asynchronous Receiver/Transmitter (UART) section in
Peripherals chapter in the device TRM.
8.4.2.22 Universal Serial Bus Subsystem (USBSS)
The Universal Serial Bus Subsystem (USBSS) module supports the following main features:
General USB interface:
• Compliant with USB 3.1 specification
• Compliant with xHCI 1.1 specification
• Port configurable as:
– USB host:
• SuperSpeed Gen 1 (5 Gbps)
• High-speed (480 Mbps)
Note
AM64x also supports discrete power supply topologies and customized power designs to meet various
system requirements.
A B
R1
0 Ω*
OSPI/QSPI/SPI
OSPI[x]_CLK
Device Clock Input
OSPI[x]_LBCLKO
E F
OSPI[x]_D[y], OSPI/QSPI/SPI
OSPI[x]_CSn[z] Device IO[y], CS#
OSPI_Board_01
* 0 Ω resistor (R1), located as close as possible to the OSPI[x]_CLK pin, is placeholder for fine tuning, if needed.
Figure 9-1. OSPI Connectivity Schematic for No Loopback, Internal PHY Loopback, and Internal Pad
Loopback
Note
The External Board Loopback hold time requirement (defined by parameter number O16 in Table
7-101, OSPI0 Timing Requirements - PHY DDR Mode) may be larger than the hold time provided by
a typical OSPI/QSPI/SPI device. In this case, the propagation delay of OPSI[x]_LBCLKO pin to the
OSPI[x]_DQS pin (C to D) can be reduced to provide additional hold time.
A B
R1
0 Ω*
OSPI/QSPI/SPI
OSPI[x]_CLK
Device Clock Input
C
R1
0 Ω*
OSPI[x]_LBCLKO
E F
OSPI[x]_D[y], OSPI/QSPI/SPI
OSPI[x]_CSn[z] Device IO[y], CS#
OSPI_Board_02
* 0 Ω resistor (R1), located as close as possible to the OSPI[x]_CLK and OSPI[x]_LBCLKO pins, is a placeholder for fine tuning, if
needed.
A B
R1
0 Ω*
OSPI/QSPI/SPI
OSPI[x]_CLK
Device Clock Input
OSPI[x]_LBCLKO
C D
E F
OSPI[x]_D[y], OSPI/QSPI/SPI
OSPI[x]_CSn[z] Device IO[y], CS#
OSPI_Board_03
* 0 Ω resistor (R1), located as close as possible to the OSPI[x]_CLK pin, is a placeholder for fine tuning, if needed.
Device
USBn_VBUS
16.5 kΩ 3.48 kΩ
±1% ±1%
VBUS signal
10 kΩ
±1% 6.8V
(BZX84C6V8 or equivalent)
VSS VSS
J7ES_USB_VBUS_01
The USB0_VBUS pin can be considered to be fail-safe because the external circuit in Figure 9-4 limits the input
current to the actual device pin in a case where VBUS is applied while the device is powered off.
9.2.4 System Power Supply Monitor Design Guidelines
The VMON_VSYS pin provides a way to monitor a system power supply. This system power supply is typically
a single pre-regulated power source for the entire system and can be connected to the VMON_VSYS pin via
and external resistor divider circuit. This system supply is monitored by comparing the external voltage divider
output voltage to an internal voltage reference, where a power fail event is triggered when the voltage applied
to VMON_VSYS drops below the internal reference voltage. The actual system power supply voltage trip point
is determined by the system designer when selecting component values used to implement the external resistor
voltage divider circuit.
When building the resistor divider circuit the designer must understand various factors which contribute to
variability in the system power supply monitor trip point. The first thing to consider is the initial accuracy of
the VMON_VSYS input threshold which has a nominal value of 0.45 V, with a variation of ±3%. Precision
1% resistors with similar thermal coefficient are recommended for implementing the resistor voltage divider.
This minimizes variability contributed by resistor value tolerances. Input leakage current associated with
VMON_VSYS must also be considered since any current flowing into the pin creates a loading error on the
voltage divider output. The VMON_VSYS input leakage current can be in the range of 10 nA to 2.5 µA when
applying 0.45 V.
Note
The resistor voltage divider shall be designed such that the output voltage never exceeds the
maximum value defined in the Recommended Operating Conditions section, during normal operating
conditions.
Figure 9-5 presents an example, where the system power supply is nominally 5 V and the maximum trigger
threshold is 5 V - 10%, or 4.5 V.
For this example, the designer must understand which variables effect the maximum trigger threshold when
selecting resistor values. A device which has a VMON_VSYS input threshold of 0.45 V + 3% needs to be
considered when trying to design a voltage divider that doesn’t trip until the system supply drops 10%. The effect
of resistor tolerance and input leakage also needs to be considered, but the contribution to the maximum trigger
point is not obvious. When selecting component values which produce a maximum trigger voltage, the system
designer must consider a condition where the value of R1 is 1% low and the value of R2 is 1% high combined
with a condition where input leakage current for the VMON_VSYS pin is 2.5 µA. When implementing a resistor
divider where R1 = 4.81 KΩ and R2 = 40.2 KΩ, the result is a maximum trigger threshold of 4.517 V.
Once component values have been selected to satisfy the maximum trigger voltage as described above, the
system designer can determine the minimum trigger voltage by calculating the applied voltage that produces an
output voltage of 0.45 V - 3% when the value of R1 is 1% high and the value of R2 is 1% low, and the input
leakage current is 10 nA, or zero. Using an input leakage of zero with the resistor values given above, the result
is a minimum trigger threshold of 4.013 V.
This example demonstrates a system power supply voltage trip point that ranges from 4.013 V to 4.517
V. Approximately 250 mV of this range is introduced by VMON_VSYS input threshold accuracy of ±3%,
approximately 150 mV of this range is introduced by resistor tolerance of ±1%, and approximately 100 mV
of this range is introduced by loading error when VMON_VSYS input leakage current is 2.5 µA.
The resistor values selected in this example produces approximately 100 µA of bias current through the resistor
divider when the system supply is 4.5 V. The 100 mV of loading error mentioned above can be reduced to about
10 mV by increasing the bias current through the resistor divider to approximately 1 mA. So resistor divider bias
current vs loading error is something the system designer needs to consider when selecting component values.
The system designer must also consider implementing a noise filter on the voltage divider output since
VMON_VSYS has minimum hysteresis and a high-bandwidth response to transients. This can be done by
installing a capacitor across R1 as shown in Figure 9-5. However, the system designer must determine the
response time of this filter based on system supply noise and expected response to transient events.
Device
VMON_VSYS
R2
VSYS
40.2 kΩ ±1% (System Power Supply)
R1 4.81 kΩ
C1
±1%
Value = Determined by system designer
VSS
SPRSP56_VMON_ER_MON_01
VMON_1P8_MCU and VMON_1P8_SOC pins provide a way to monitor external 1.8 V power supplies. These
pins must be connected directly to their respective power source. An internal resistor divider with software
control is implemented inside the SoC for each of these pins. Software can program each internal resistor divider
to create appropriate under voltage and over voltage interrupts.
VMON_3P3_MCU and VMON_3P3_SOC pins provide a way to monitor external 3.3 V power supplies. These
pins must be connected directly to their respective power source. An internal resistor divider with software
control is implemented inside the SoC for each of these pins. Software can program each internal resistor divider
to create appropriate under voltage and over voltage interrupts.
Note
Implementing a ground guard between the MCU_OSC0_XI and MCU_OSC0_XO signals is critical
to minimize shunt capacitance between the two signals. Routing these two signals adjacent to each
other without a ground guard between them will effectively reduce the gain of the oscillator amplifier,
which reduces its ability to start oscillation.
GND vias
Device
Cap
GND guard
MCU_OSC0_XO
GND vias
Figure 9-6. MCU_OSC0 PCB requirements
TMDX Development-support product that has not yet completed Texas Instruments internal qualification testing.
TMDS Fully-qualified development-support product.
X and P devices and TMDX development-support tools are shipped against the following disclaimer:
"Developmental product is intended for internal evaluation purposes."
Production devices and TMDS development-support tools have been characterized fully, and the quality and
reliability of the device have been demonstrated fully. TI's standard warranty applies.
Predictions show that prototype devices (X or P) have a greater failure rate than the standard production
devices. Texas Instruments recommends that these devices not be used in any production system because their
expected end-use failure rate still is undefined. Only qualified production devices are to be used.
For orderable part numbers of AM64x devices in the ALV package type, see the Package Option Addendum at
the end of this document, the TI website (ti.com), or contact your TI sales representative.
Note
Some devices may have a cosmetic circular marking visible on the top of the device package which
results from the production test process. In addition, some devices may also show a color variation in
the package substrate which results from the substrate manufacturer. These differences are cosmetic
only with no reliability impact.
SITARA
aBBBBBBr
ZfYytPPPQ1
XXXXXXX
A1 (PIN ONE INDICATOR) YYY G1
Note
BLANK in the symbol or part number is collapsed so there are no gaps between characters.
10.7 Glossary
TI Glossary This glossary lists and explains terms, acronyms, and definitions.
www.ti.com 8-Nov-2023
PACKAGING INFORMATION
Orderable Device Status Package Type Package Pins Package Eco Plan Lead finish/ MSL Peak Temp Op Temp (°C) Device Marking Samples
(1) Drawing Qty (2) Ball material (3) (4/5)
(6)
AM6411BKCGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6411B Samples
KCGHAALV
709
AM6411BSCGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6411B Samples
SCGHAALV
709
AM6412BKCGHAALVR ACTIVE FCBGA ALV 441 500 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6412B Samples
KCGHAALV
709
AM6412BSCGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6412B Samples
SCGHAALV
709
AM6421BSDGHAALVR ACTIVE FCBGA ALV 441 500 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6421B Samples
SDGHAALV
709
AM6421BSEFHAALVR ACTIVE FCBGA ALV 441 500 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6421B Samples
SEFHAALV
709
AM6421BSFFHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6421B Samples
SFFHAALV
709
AM6421BSFGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6421B Samples
SFGHAALV
709
AM6422BSDFHAALVR ACTIVE FCBGA ALV 441 500 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6422B Samples
SDFHAALV
709
AM6422BSDGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6422B Samples
SDGHAALV
709
AM6441BSEFHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6441B Samples
SEFHAALV
709
AM6441BSEGHAALVR ACTIVE FCBGA ALV 441 500 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6441B Samples
SEGHAALV
Addendum-Page 1
PACKAGE OPTION ADDENDUM
www.ti.com 8-Nov-2023
Orderable Device Status Package Type Package Pins Package Eco Plan Lead finish/ MSL Peak Temp Op Temp (°C) Device Marking Samples
(1) Drawing Qty (2) Ball material (3) (4/5)
(6)
709
AM6441BSFFHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6441B Samples
SFFHAALV
709
AM6442BSDGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6442B Samples
SDGHAALV
709
AM6442BSEFHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6442B Samples
SEFHAALV
709
AM6442BSEGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6442B Samples
SEGHAALV
709
AM6442BSFFHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6442B Samples
SFFHAALV
709
AM6442BSFGHAALV ACTIVE FCBGA ALV 441 84 RoHS & Green Call TI Level-3-250C-168 HR -40 to 105 AM6442B Samples
SFGHAALV
709
(1)
The marketing status values are defined as follows:
ACTIVE: Product device recommended for new designs.
LIFEBUY: TI has announced that the device will be discontinued, and a lifetime-buy period is in effect.
NRND: Not recommended for new designs. Device is in production to support existing customers, but TI does not recommend using this part in a new design.
PREVIEW: Device has been announced but is not in production. Samples may or may not be available.
OBSOLETE: TI has discontinued the production of the device.
(2)
RoHS: TI defines "RoHS" to mean semiconductor products that are compliant with the current EU RoHS requirements for all 10 RoHS substances, including the requirement that RoHS substance
do not exceed 0.1% by weight in homogeneous materials. Where designed to be soldered at high temperatures, "RoHS" products are suitable for use in specified lead-free processes. TI may
reference these types of products as "Pb-Free".
RoHS Exempt: TI defines "RoHS Exempt" to mean products that contain lead but are compliant with EU RoHS pursuant to a specific EU RoHS exemption.
Green: TI defines "Green" to mean the content of Chlorine (Cl) and Bromine (Br) based flame retardants meet JS709B low halogen requirements of <=1000ppm threshold. Antimony trioxide based
flame retardants must also meet the <=1000ppm threshold requirement.
(3)
MSL, Peak Temp. - The Moisture Sensitivity Level rating according to the JEDEC industry standard classifications, and peak solder temperature.
(4)
There may be additional marking, which relates to the logo, the lot trace code information, or the environmental category on the device.
Addendum-Page 2
PACKAGE OPTION ADDENDUM
www.ti.com 8-Nov-2023
(5)
Multiple Device Markings will be inside parentheses. Only one Device Marking contained in parentheses and separated by a "~" will appear on a device. If a line is indented then it is a continuation
of the previous line and the two combined represent the entire Device Marking for that device.
(6)
Lead finish/Ball material - Orderable Devices may have multiple material finish options. Finish options are separated by a vertical ruled line. Lead finish/Ball material values may wrap to two
lines if the finish value exceeds the maximum column width.
Important Information and Disclaimer:The information provided on this page represents TI's knowledge and belief as of the date that it is provided. TI bases its knowledge and belief on information
provided by third parties, and makes no representation or warranty as to the accuracy of such information. Efforts are underway to better integrate information from third parties. TI has taken and
continues to take reasonable steps to provide representative and accurate information but may not have conducted destructive testing or chemical analysis on incoming materials and chemicals.
TI and TI suppliers consider certain information to be proprietary, and thus CAS numbers and other limited information may not be available for release.
In no event shall TI's liability arising out of such information exceed the total purchase price of the TI part(s) at issue in this document sold by TI to Customer on an annual basis.
Addendum-Page 3
PACKAGE MATERIALS INFORMATION
www.ti.com 19-Aug-2023
B0 W
Reel
Diameter
Cavity A0
A0 Dimension designed to accommodate the component width
B0 Dimension designed to accommodate the component length
K0 Dimension designed to accommodate the component thickness
W Overall width of the carrier tape
P1 Pitch between successive cavity centers
Sprocket Holes
Q1 Q2 Q1 Q2
Pocket Quadrants
Pack Materials-Page 1
PACKAGE MATERIALS INFORMATION
www.ti.com 19-Aug-2023
Width (mm)
H
W
Pack Materials-Page 2
PACKAGE MATERIALS INFORMATION
www.ti.com 19-Aug-2023
TRAY
W-
Outer
tray
width
Text
Pack Materials-Page 3
PACKAGE OUTLINE
ALV0441A SCALE 0.900
FCBGA - 2.657 mm max height
BALL GRID ARRAY
17.3 A
B
17.1
BALL A1 CORNER
PIN 1 ID
(OPTIONAL) 17.3
17.1
( 12.8)
0.1 C
( 10.8)
( 16.8)
SEATING PLANE
(0.662)
0.15 C
0.5
TYP
0.3
16 TYP
AA
Y
W
V
U
T
R
P
N
SYMM M
L 16
K
J TYP
H
G
F
E
D
0.55 C
441X
0.45 B
0.25 C A B A
1 2 3 4 5 6 7 8 9 10 12 14 16 18 20
0.1 C 11 13 15 17 19 21
0.8 TYP
4225999/A 06/2020
NOTES:
1. All linear dimensions are in millimeters. Any dimensions in parenthesis are for reference only. Dimensioning and tolerancing
per ASME Y14.5M.
2. This drawing is subject to change without notice.
www.ti.com
EXAMPLE BOARD LAYOUT
ALV0441A FCBGA - 2.657 mm max height
BALL GRID ARRAY
441X ( 0.4)
(0.8) TYP
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
(0.8) TYP A
B
C
D
E
F
G
H
J
K
SYMM
L
M
N
P
R
T
U
V
W
Y
AA
SYMM
0.07 MAX
( 0.4) 0.07 MIN METAL UNDER
METAL SOLDER MASK
EXPOSED METAL
NOTES: (continued)
3. Final dimensions may vary due to manufacturing tolerance considerations and also routing constraints.
For more information, see Texas Instruments literature number SPRU811 (www.ti.com/lit/spru811).
www.ti.com
EXAMPLE STENCIL DESIGN
ALV0441A FCBGA - 2.657 mm max height
BALL GRID ARRAY
(0.8) TYP A
B
C
D
E
F
G
H
J
K
SYMM
L
M
N
P
R
T
U
V
W
Y
AA
SYMM
4225999/A 06/2020
NOTES: (continued)
4. Laser cutting apertures with trapezoidal walls and rounded corners may offer better paste release.
www.ti.com
IMPORTANT NOTICE AND DISCLAIMER
TI PROVIDES TECHNICAL AND RELIABILITY DATA (INCLUDING DATA SHEETS), DESIGN RESOURCES (INCLUDING REFERENCE
DESIGNS), APPLICATION OR OTHER DESIGN ADVICE, WEB TOOLS, SAFETY INFORMATION, AND OTHER RESOURCES “AS IS”
AND WITH ALL FAULTS, AND DISCLAIMS ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION ANY
IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT OF THIRD
PARTY INTELLECTUAL PROPERTY RIGHTS.
These resources are intended for skilled developers designing with TI products. You are solely responsible for (1) selecting the appropriate
TI products for your application, (2) designing, validating and testing your application, and (3) ensuring your application meets applicable
standards, and any other safety, security, regulatory or other requirements.
These resources are subject to change without notice. TI grants you permission to use these resources only for development of an
application that uses the TI products described in the resource. Other reproduction and display of these resources is prohibited. No license
is granted to any other TI intellectual property right or to any third party intellectual property right. TI disclaims responsibility for, and you
will fully indemnify TI and its representatives against, any claims, damages, costs, losses, and liabilities arising out of your use of these
resources.
TI’s products are provided subject to TI’s Terms of Sale or other applicable terms available either on ti.com or provided in conjunction with
such TI products. TI’s provision of these resources does not expand or otherwise alter TI’s applicable warranties or warranty disclaimers for
TI products.
TI objects to and rejects any additional or different terms you may have proposed. IMPORTANT NOTICE
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2023, Texas Instruments Incorporated