This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F280039C: CLB Input Pipelining vs. AOC Block when Global input = CLBx_OUTy

Part Number: TMS320F280039C
Other Parts Discussed in Thread: TMS320F280049C

Hello,

 

I am developing an application using 2 CLB blocks which interact and exchange signals. 

Using the CLBx_OUTy signals as input on the global mux of the other CLB works fine, but how to make sure there is no input instability and -if possible- only 1 cycle delay?

a) BYPASS (CLB_OUT_COND_CTL_x.ASYNC_COND_EN = 1) on the AOC and CLB_INPUT_FILTER.PIPE(x) = 1?

Means direct output of the OUTLUT without synchronization and sync by the PIPE latch within the input.

b) No Bypass from OUTLUT (ASYNC_COND_EN = 0) on the AOC and CLB_INPUT_FILTER.PIPE(x) = 0?

Means OUTLUT Latch on the output conditioning block synchronizing signal and the delay thru the Global mux is neglectable, so the signal can directly be used by the other CLB Tile without the PIPE latch.

c) both needed? Will it give 2 cycles delay?

 

Additional questions:

That about GPREG inputs. Do they need the PIPE latch active? I did not find anything about it.

What about the TMS320F280049C? It does not implement the PIPE input latch. Will it work just with the AOC block? Is it because it will only clock up to 100 MHz instead of 120 MHz?

 

And btw: The CCS syscfg Tool allows to activate input filter on GPREG inputs, which actually makes no sense to me. 

grafik.png

grafik.png

 

 

  • Hi Carl,
    CLB_OUT does not need Synchronization for it to be input for another CLB tile. But Pipeline need to enabled as mentioned in TRM. This will introduce 1 cycle delay deterministically. AOC will be used only when you want to condition the output of CLB tile. If AOC is being used, then an additional delay of atleast 1cylce delay will be introduced.
    For GPREG, as it is written in software which is synchronous to SYSCLK, synchronization is not needed, and pipeline can be enabled to add deterministic 1 cycle delay.
    For 49C, pipeline is not available, so only synchronization option is there, This could be due to the frequency you have mentioned,
    The Syscfg is a bug, we will fix it in the next version of syscfg, thanks for letting us know.
    Thanks
    Praneeth