• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 64 subscribers
  • Views 532 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux/UCD90120A: Developing Linux Utility to Read UCD90120a Configuration

David Finkel
Prodigy 230 points
Part Number: UCD90120A

Tool/software: Linux

I'm trying to figure out how to write a Linux (C-language) utility that will read the configuration of a UCD90120a on a running system.

My initial inclination is to try to use the TI Fusion's "PMBus Logging" feature.

The hope is that the log file will capture the PMBus command sequence Fusion uses initialize itself by reading the UCD configs.

Does this make sense? Is there a better way to do what I'm trying to do?

So far I've got a PMBus log file, but I'm a bit confused about what I'm looking at.

1. I would expect the PMBus log file to capture all the config information, e.g. all the data fields in the "Click to configure device" pop-up box tabs.

But, I don't think I see it all.

Why, for example don't I see the "Rail Name" data in the PMBus log file?

TI Fusion is clearly retrieving it, but I don't see it.

2. What does "SAA" mean?

It looks like the log file lines in which the "Adapter" field = "SAA" are the actual PMBus commands, and those in which the "Adapter" field = "PMBus" are just comments. 

Can you comment on this please?

Any suggestions you can offer would be greatly appreciated.

  • 0
    TI__Mastermind 24075 points
    Hi David,

    We will have someone to take a look.

    Thanks
    Qian
  • 0 in reply to Qian Chen
    Prodigy 230 points

    Hi Qian,

    Thank you for the timely reply. Let me try to clarify more precisely what I'm trying to do.

    The ultimate objective is to be able to compare an unknown UCD configuration with existing UCD XML configuration files.

    To this end I want to write a Linux/C program that executes on a running system, and with PMBus commands:

    1. Read the UCD configuration

    2. Generate a file in a format that can be imported into TI Fusion.

    3. Import that file into TI Fusion.

    4. Then export the configuration to an XML file.

  • 0 in reply to David Finkel
    TI__Guru 66310 points

    Hello David

    PMBus Log is used to stored all the pmubs communicaiton between PC(Fusion GUI) and Device. It only captures the command after the logging is enabled.

    Rail name is not part of the configuraiton, instead it is just a mega data stored in the PC, it will not included in the log file.

    SAA is the USB-TO_GPIO adapter, it is just a indicatio in the case there are multiple USB-To-GPIO adater in the system.

    Regards

    Yihe

  • 0 in reply to David Finkel
    TI__Guru 66310 points

    Hi David

    You can use PARM_INFO(0xE2) and PARM_VALUE(0xE3) command to retrieve the configuraiton from the live device. The details of the command is listed at section 10.19 and 10.20 of http://www.ti.com/lit/ug/slvu352f/slvu352f.pdf. 

    The configuraiton data is stored at  data flash starting with 0x18800 with 2KB space.

    The most favorable file format is the intel hex format. you have to manually generate such file with the data retrieved by 0xE2 and 0xE3.

    Once you have the data flash hex file, you can import the file and compare with the XML file.

    By the way, if you can connect the USB-To-GPIO dongle directly to your system, Fusion GUI can help to compare the existiing configuraitno with xml file online without any conversion.

    Regards

    Yihe

  • 0 in reply to yihe
    Prodigy 230 points
    Hi Yihe,

    Great information!
    I think I've got it working, but I'm not positive.
    Does the address range 0x18DA0 to 0x18FF9F contain the UCD log?
    If not, what's in there?
    The reason I ask:
    If I compare the Intel hex file TI Fusion generates with the one my tool generates, the data is different starting at 0x18DA0 and ending 0x18F9F.
    From 0x18FA0 to 0x18FFF the two files matches again.

    Thanks,
    David
  • 0 in reply to David Finkel
    TI__Guru 66310 points

    Hello David

    The valid configuration is from 0x18000 to 0x18DA0. the remainig are log data which varies upon devices.

    Please refer section 3.3 of

    http://www.ti.com/lit/an/slua815a/slua815a.pdf

    Bascially, you can ignore the data after 0x18DA0.

    Regards

    Yihe