Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

UCD90320U: Fusion TIFSP: Multiple instances of the same pin ID

Part Number: UCD90320U

Tool/software:

We are trying to write our own parser to report on relevant information from a TIFSP, such as rails and GPIOs, with accompanying human-readable metadata, i.e., our application-specific names.

Upon running it, we noticed that the same pin ID appears multiple times throughout the same file under different TraceDefinitions, with variances in the <Name> field and <Order_Index> fields.

My question is, what do the <TraceDefinition> and <Order_Index> fields refer to, and is the difference between these 3 instances of the same pin? And for our parsing specifically, which pin instance do you advise we keep?

Appreciate the help,

Adrianna

  • Hi, Adrianna,

    The <TraceDefinition> is to keep track of the rails and pins names which are not stored on the device. GUI displays the rails and pins names based on device ID (such as UCD90320U), device address (in this case 49d), pin ID (in this case 42), pin type (in this case Static-GPO), and pin index (different index of 27, 33, and 31). If match, the name will be displayed. So if your current configuration has pin 42 assigned as Static-GPO index 2, then the name shown in the most left <TraceDefinition> will be displayed on the GUI.

    Regards

    Anne Ngo

  • Thanks for your response. What we are confused about is we have three TraceDefinitions that correspond to the same pin. However, when we open the .tifsp file in the GUI, only one of these actually shows up in the list. How does the tool determine which one to pick as the correct one? For example, in the picture we sent above, the three TraceDefinitions have different names, but only one of the names actually shows up in the GUI GPIO list. In other cases, they may have different Extra1 fields as well (i.e. some may be a GPO, some maybe be GPI). We are trying to parse the file to create our own software interface to the sequencer, but we have no way of algorithmically determining which TraceDefinition is the correct one to use for that pin.

    Your post implies that the <Trace_Definition> with the lowest <Order_Index> value is the one that shows up in the GUI. Is this assumption correct?

    And will this indeed correspond to the configuration for the pin, if it were to be exported as a CSV (seeing as the Extra1 fields can differ)?

  • Hi, Andriana,

    <Trace_Definition> saved when you use Fusion GUI connected to device. There might be the same device (UCD90320U at address 49) but with configuration changed over time => That is why there are multiple <Trace_Definition> with the same ID, but with different <Order_Index>.

    How to choose the name to display on GUI: if device ID, address, pin ID, pin assignment (Extra1) and Order_Index matches, then that name is selected, not the lowest one.

    Pin names are not stored on device configuration => It will not be in the .csv file. 

    Regards

    Anne Ngo

  • How to choose the name to display on GUI: if device ID, address, pin ID, pin assignment (Extra1) and Order_Index matches, then that name is selected, not the lowest one.

    What did you mean by this? What is being matched here?

  • Adrianna,

    Device ID + Address + Pin ID + Pin Assignment + Order, must match.

    Example of "Order Index" is shown below: LGPO #1 is Order_Index 0. LGPO #4 is Order_Index 3

    Anne

  • Thanks Anne. But is there a way to determine which pin configuration will be displayed on the GUI (which I assume corresponds to the config that will eventually be flashed onto the device, without opening the GUI? 

  • Hi, Adrianna,

    Not sure I understand your question. GUI displays what configured on device. If GUI find a name stored on the PC that match the naming convention, then GUI displays that name; otherwise, will display as default name such as "LGPO #1, GPI #2, etc. NOTE that names are not stored on device.

    Anne Ngo

  • Hi Anne,

    When you say

    If GUI find a name stored on the PC that match the naming convention, then GUI displays that name

    Is the matching happening between the GUI and the TIFSP? You said

    Device ID + Address + Pin ID + Pin Assignment + Order, must match

    So one of these exists in the TIFSP, and we're matching that to the GUI?

  • Hi, 

    If you open project file in offline mode (disconnected device), names will be populated into field names.

    If you have live device connected to PC and launch Fusion GUI, since the names are not stored on device, GUI will look for the information on the current PC if GUI can find any references to the GPIO names. If none found, GUI displays names as default names. You will need to import the naming information from the file to device:

    On Device window, click on File menu -> Import to device, then select Project File.

    Make sure to uncheck "Import Write Device Configuration" checkbox (if you don't need to import configuration data) and check on "Import Rail names ..." checkbox.

    Regards

    Anne Ngo