Public Version
www.ti.com
Control Module Pad Multiplexing Register Fields
B.5
Control Module Pad Multiplexing Register Fields
and
provide for each pad configuration register field the address offset, reset values,
and associated signal name for each multiplexing mode (as set by the MUXMODE bit field). Mode 0 is
always defined. Modes without a signal name are undefined for the given pad.
NOTE:
The pad names are the signal names that are available in mode 0 of the pad; that is, the
pad names are listed in the Mode 0 column.
CAUTION
D2D and CHASSIS pads are present on the die; however, they can be used
only in stacked mode.
Do not modify the D2D/CHASSIS PADCONF registers, because the devices in
the CUS package are offered only as stand-alone. Modifying these registers is
dangerous for the device pads. For a list of these registers, see
System Control Module.
NOTE:
•
Pad configuration registers are split into two types, which correspond to the following
two tables:
–
lists the pad configuration registers instantiated in the CORE power
domain that drive the pads in the CORE power domain.
–
lists the pad configuration registers instantiated in the WKUP power
domain that drive the pads in the WKUP power domain.
•
The rows highlighted in orange in
and
represent pads that are not
connected to a package ball. The corresponding PADCONF bit fields must be left at
their default state (usually Mode 7, safe_mode), and must not be altered.
•
Even though some signals are available, the corresponding module or function may not
be available. For example, some hsusb3_tll signals are present, but the HSUSB function
on port 3 is not supported.
•
In these tables, a blank cell indicates that the mode or pull is not available for the
corresponding pad.
3711
SWPU177N – December 2009 – Revised November 2010
OMAP36xx Multimedia Device in CUS Package
Copyright © 2009–2010, Texas Instruments Incorporated
