SPRAD62 February 2023 F29H850TU , F29H859TU-Q1 , TMS320F280023C , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038C-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1
In most cases, input signals need to be passed to the CLB tile. Generally, there are three categories of signals to consider:
These input signals can be connected to the eight CLB tile inputs using the CLB global and local muxes in combination with the different XBARs on the device. For more information, see the device-specific TRM.
There are often multiple paths which can be used to connect a CLB tile to an input signal. Table 2-1 lists the recommended path to bring in these signals to the CLB tile boundary.
Input Signal Type | Recommended Input Path |
---|---|
External serial bus signals (for example, serial bus clock, frame, and data signals) | GPIO pin ⇨ CLB input XBAR 1 ⇨ CLB local mux ⇨ CLB input |
Internal on-chip peripheral signals (for example, clock signal generated using a PWMnA) | Peripheral signal ⇨ CLB global mux or CLB local mux ⇨ CLB input |
Custom signal directly controlled by CPU | Memory-mapped GPREG bit ⇨ CLB input |