• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 83 subscribers
  • Views 227 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.

TMS320F28386D: sysCfg tool does not allocate CLB INPUTXBAR

ken hutchinson
Prodigy 195 points
Part Number: TMS320F28386D
Other Parts Discussed in Thread: SYSCONFIG

Hello, I'm using the sysConfig tool to allocate the resources for a new F28386D project. I have 2GPIO  inputs to each of 5 CLB tiles, plus some extra GPIO. I set these up in the CLB INPUTXBAR section, but the pin selections don't show up in the pinmux.csv file in column C under 'Selected Mode'. I get all the PWM's and SCI and EQE, but none of the XBAR configurations. 

Also, the generic GPIO show up in the csv, but only labelled as GPIO108 etc. They don't show the name I've given them in the tool. Makes it difficult to figure out the schematic

How do I get those to show up in the output?

thanks

  • 0
    TI__Guru 52020 points

    Ken,

    1. The PinMux CSV does not use the customer names. We can add this feature for the next revision. We use the actual resource name in the device's hardware.

    2. The Input XBARs (GPIO input xbar or CLB input xbar) are not pinmux resources. that means that if a peripheral is using the GPIO, Input Xbar can also use it in parallel. But again I can add this feature into the next revision of the tool as well.

    If you would like an early look at these features, I can send them to you once completed.

    Nima

  • 0 in reply to Nima Eskandari
    Prodigy 195 points

    Thanks for your reply.

    What I was hoping to do, was use the sysConfig tool to assign all the peripheral pins and provide a form to the hardware designer so he can ensure those peripherals are connected to the correct pins. I thought that would be the goal of this tool. Am I missing a way to do that?

  • 0 in reply to ken hutchinson
    TI__Guru 52020 points

    No thats a great idea. Unfortunately we just dont have the INPUT and CLB Input xbar included in the pinmux since they are not mutually exclusive pinmux peripherals.

  • 0 in reply to Nima Eskandari
    Prodigy 195 points

    Hi Nima, I'm not clear what you mean by not having the GPIO associated with the CLB Input XBAR. In SysCfg, I created 10 instances of CLB INPUT XBAR (I need 5 CLB tiles with 2 inputs per tile) and can set the GPIO number for each. But I don't see that selection linking anywhere. It doesn't appear in the output CSV and doesn't prevent overlap with the generic GPIO

  • 0 in reply to ken hutchinson
    TI__Guru 52020 points

    Thats because IT ALLOWS overlap... That is what I meant by it's not really a mutually exclusive PinMux option.

    The INPUT XBAR module operates in parallel and just taps the GPIO signal.

    Nima