SPRAD85D December 2024 – October 2025 AM62A1-Q1 , AM62A3 , AM62A3-Q1 , AM62A7 , AM62A7-Q1 , AM62D-Q1
The processor families support multiple, general connectivity peripherals and instances. The processor families support the following peripherals:
The following peripherals (UART, MCAN, MCSPI, MCASP, I2C) implements IOSET. Make sure the usage of the correct IOSET in the custom board design. Timing closure is based on the IOSETs.
Multichannel Serial Peripheral Interface (MCSPI):
The processor families support x5 (five) (x3 MAIN domain, x2 MCU domain) instances of MCSPI. The MCSPI module is a multichannel transmit/receive, synchronous serial bus and can operate in controller mode or peripheral mode. In controller mode, the processor SPI interface sources the clock to the attached device. In peripheral mode, the attached device is required to source the SPI clock to processor.
A series resistor (22Ω) is recommended (as a starting point) for the MCSPI clock output signals. The resistor is recommended to be placed near to the processor clock output pin (used for retiming). A pulldown (10kΩ) is recommended close to the attached device clock input pin.
A pullup (10kΩ) is recommended for the chip select (CS) pin close to the attached device.
The MCSPI peripherals do not support boot. The OSPI0 interface supports SPI boot.
For the MCSPI interface SPIx_D0 and SPIx_D1 are the data lines. The data lines support programming the signals either to transmit data (transmission, output) or receive data (reception, input).
Processor IO buffers are off during reset and after reset. Parallel pulls are recommended for any of the processor IOs (MCSPI interface signals) that can float (to prevent the attached device inputs from floating until driven by the host).
The recommendation is to connect the SPI interface to x1 (single) memory device. When connecting to multiple memory devices, the recommendation is to follow high-speed design practices and perform simulations to make sure the layout is not going to generate non-monotonic clock transitions when the single clock source is connected to multiple SPI attached devices.
See the following FAQs:
[FAQ] SK-AM64B: MCSPI Integration Guide
[FAQ] AM6412: AM64x SPI D0 and D1 - MISO/MOSI
The FAQ is generic and can also be used for AM62A7, AM62A7-Q1, AM62A3, AM62A3-Q1, AM62A1-Q1 and AM62D-Q1 processor families.
Inter-Integrated Circuit (I2C):
Refer below Section 7.8.1.
Universal Asynchronous Receiver/Transmitter (UART):
The processor families support x9 (nine) (x7 MAIN domain, x1 MCU domain, x1 WKUP domain) instances of UART interface. Supported UART functions include data transfer (TXD, RXD), Modem control functions (CTS, RTS) and extended modem control signals (DCD, RI, DTR, DSR - supported by MAIN domain UART1).
Refer to the Signal Descriptions section of the device-specific data sheet for the supported functionalities for each of the UART instances.
Refer to the Timing and Switching Characteristics section of the device-specific data sheet for supported data rate (programmable baud rate).
When external UART interface signals are directly connected to the processor UART interface signals, verify IO level compatibility and fail-safe operation. The recommendation is to provide provision for external ESD protection.
The recommendation is to provision for UART boot (UART0) for early board builds for board bring-up and debug.
Processor IO buffers are off during reset and after reset. Parallel pulls are recommended for any of the processor IOs (UART interface signals) that can float (to prevent the attached device inputs from floating until driven by the host).
General Purpose Input/Output (GPIO):
The processor families support GPIO0, GPIO1 and MCU_GPIO1 instances of GPIO modules. Processor GPIOs include LVCMOS and SDIO buffer types and are push-pull type outputs. Some specific IOs support open-drain output type IO buffer interface. LVCMOS IOs when configured as I (input) have input slew requirements and O (output) has capacitor loading recommendations. The recommendation is to perform simulation with the connected load capacitor to make sure the output is within the ROC as per device-specific data sheet electrical characteristics.
Processor IO buffers are off during reset and after reset. Parallel pulls are recommended for any of the processor IOs that has a trace connected to the processor pads and can float (to prevent the attached device inputs from floating until driven by the host).
For more information, see the following FAQs:
PADCONFIG register bit configuration - ST_EN: The recommendation is to keep the ST_EN bit enabled in case the PADCONFIG register is modified by the software. The minimum Input Slew Rate parameter defined in each Electrical Characteristics table of device-specific data sheet is associated with long-term reliability. The parameters are not a function of the ST_EN bit. The schmitt trigger function implemented in the input buffer only changes the output results of the input buffer, by filtering noise pulses that do not exceed the hysteresis. The schmitt trigger function does not change how the input buffer operates when a system applies a slew rate to its input that is slower than defined in the device-specific data sheet.
Audio Peripheral - Multichannel Audio Serial Port (MCASP):
The processor families support x3 (three) (x3 MAIN domain) instances of Audio peripheral - Multichannel Audio Serial Port (MCASP). MCASP supports up to 4/6/16 Serial Data Pins (serializer) across x3 MCASP with Independent TX and RX Clocks. MCASP supports Time Division Multiplexing (TDM), Inter-IC Sound (I2S), and similar formats. A series resistor 22Ω is recommended (as a starting point) for the MCASP clock output. The resistor is recommended to be placed near to the processor clock output pin (used for retiming). A pulldown is recommended close to the attached device clock input pin.
Processor IO buffers are off during reset and after reset. Parallel pulls are recommended for any of the processor IOs (MCASP interface signals) that can float (to prevent the attached device inputs from floating until driven by the host).
For more information, see the following FAQ:
Industrial and Control Interfaces:
The processor families support multiple instances (refer Device Comparison table of the device-specific data sheet) of Industrial and Control Interfaces.
Modular Controller Area Network (MCAN) with Full CAN-FD support:
The processor families support x3 (three) (x1 MAIN domain, x2 MCU domain) instances of Modular Controller Area Network (MCAN) with Full CAN-FD support.
The MCAN module supports both classic CAN and CAN-FD (CAN with Flexible Data-Rate) specifications.
Processor IO buffers are off during reset and after reset. Parallel pulls are recommended for any of the processor IOs (MCAN interface signals) that can float (to prevent the attached device inputs from floating until driven by the host).
The required interfaces can be configured using the SysConfig-PinMux tool.
For more information on the supported peripherals, see the Peripherals chapter of the device-specific TRM.