TMS320F280025C: Chaining CLB tiles

Henry Jacobs

Part Number: TMS320F280025C

I would like information on chaining the output of Tile1 to the input of Tile2. The CLB tool shows connections between the two tiles but is there additional work to be done by the user?

It appears that OUT5 and OUT6 can be directly connected, but what about the other outputs? Do I have to find unused GPIOs to route the signal between GPIO XBARS to connect the

other CLB I/Os ?

over 4 years ago

0 Nima Eskandari over 4 years ago

TI__Guru 52040 points

No need for GPIO with the F280025C device, you can connect one CLB to other CLBs through the CLB Global/Local Mux. The outputs should be available to be used as inputs in the other CLBs.

0 Henry Jacobs over 4 years ago in reply to Nima Eskandari

Prodigy 70 points

My reading of the TRM (p1264) shows this is true only for OUT4 and OUT5 of the CLB.

0 Nima Eskandari over 4 years ago in reply to Henry Jacobs

TI__Guru 52040 points

OUT4 and OUT5 for all devices including the previous family of devices (F28004x and F2837xD).

For your device, you have all OUTPUTs available in the GLOBAL MUX:

Remember for example, CLB1_OUT16 is CLB1 OUT0 (copied to OUT8, OUT16)

0 Henry Jacobs over 4 years ago in reply to Nima Eskandari

Prodigy 70 points

I did not find values for CLB1_OUT16, etc. in the header file xbar.h.

Please explain where to find the #defines or how to generate them myself.

Thanks.

+1 Nima Eskandari over 4 years ago in reply to Henry Jacobs

TI__Guru 52040 points

No, NOT THE xbar.h. This is in the CLB Global MUX! Not the XBAR. In the CLB.h file.

0 Henry Jacobs over 4 years ago in reply to Nima Eskandari

Prodigy 70 points

I just revisited this issue. Tried this but it didn't seem to work?

CLB_configGlobalInputMux(CLB2_BASE, CLB_IN0, CLB_GLOBAL_IN_MUX_CLB1_OUT16); // B2.ETO from CLB1 to CLB2 direct (OUT16 is copy of OUT0)

XBAR_setOutputMuxConfig (CLBOUTPUTXBAR_BASE, XBAR_OUTPUT8, XBAR_OUT_MUX08_CLB2_OUT0); // B2.ETO GPIO00
XBAR_enableOutputMux (CLBOUTPUTXBAR_BASE, XBAR_OUTPUT8, XBAR_MUX08); // B2.ETO GPIO00

GPIO_setPadConfig (0, GPIO_PIN_TYPE_STD); // B2.ETO GPIO00
GPIO_setDirectionMode(0, GPIO_DIR_MODE_OUT); // B2.ETO GPIO00
GPIO_setPinConfig (GPIO_0_CLB_OUTPUTXBAR8); // B2.ETO GPIO00

The .syscfg file does a copy from BOUNDARY.in0 to OUTLUT_0 and AOC_0 does a Bypass.

Get output from GPIO00 using CLB1:

XBAR_setOutputMuxConfig (CLBOUTPUTXBAR_BASE, XBAR_OUTPUT8, XBAR_OUT_MUX00_CLB1_OUT0); // B2.ETO GPIO00
XBAR_enableOutputMux (CLBOUTPUTXBAR_BASE, XBAR_OUTPUT8, XBAR_MUX00); // B2.ETO GPIO00

+1 Nima Eskandari over 4 years ago in reply to Henry Jacobs

TI__Guru 52040 points

What is your boundary input setting for the CLB2? Are you USING the global mux? Is the local mux using the global mux signal and the GPREG is not used?

+1 Henry Jacobs over 4 years ago in reply to Nima Eskandari

Prodigy 70 points

Using Global Mux: CLB_configLocalInputMux(CLB2_BASE, CLB_IN0, CLB_LOCAL_IN_MUX_GLOBAL_IN);

TILE2 BOUNDARY in0 = TILE1_BOUNDARY.out0

GPREG not used, unless it is used by default?

0 Henry Jacobs over 4 years ago in reply to Henry Jacobs

Prodigy 70 points

I feel rather foolish. Need to enable second CLB!

CLB_enableCLB (CLB2_BASE);
initTILE1 (CLB2_BASE);

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F280025C: Chaining CLB tiles