• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 621 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28388D: CLB Input X-BAR and CLB Output X-BAR

Irene Boben
Expert 1030 points
Part Number: TMS320F28388D

In the TRM for F2838x and F28002x, it is mentioned that the structure of CLB Input X-bar and CLB Output X-bar is that of Input X-Bar and Output X-bar respectively. Does this mean that the register names are also exactly same?

We can refer to registers like ClbOutputXbarRegs.OUTPUT1MUX0TO15CFG or ClbInputXbarRegs.INPUT1SELECT and so on?

Also for CLB Output X-BAR MUX16-31 are reserved, do we still have OUTPUT#MUX16TO31CFG register for CLB Outputs?

  • 0
    TI__Guru 52010 points

    Yes the registers are there. But if they are reserved you shouldn't write to them. The name of the registers are available in the TRM.

    On another note, use driverlib... It is much easier to use and more portable between devices.

  • 0 in reply to Nima Eskandari
    TI__Guru 52010 points

    But yes, the register structure is the same.

  • 0 in reply to Nima Eskandari
    Expert 1030 points

    Hi Nima,

    In TRM I could only find that the structure of ClbOutputXbarRegs and ClbInputXbarRegs is similar to Input X-Bar and Output X-bar respectively. However, I could not find the names of the registers for CLB Input X-bar and CLB Output X-bar. Could you share the TRM where the register names for these are present?

    Thanks,

    Irene

  • +1 in reply to Irene Boben
    TI__Guru 52010 points

    The structure type is EXACTLY: INPUT_XBAR_REGS and OUTPUT_XBAR_REGS.

    We dont provide duplicates. The register base is duplicated and named ClbOutputXbarRegs and ClbInputXbarRegs.

     

    Example:

    We provide the definiton for EPWM_REGS, not repeating it for EPWM1, EPWM2, etc. It is the same structure.