UCD90120A : Monitoring

Thank you. I think I found the answer by myself.

Monitor pins (MON1 - MON13) can be configured to monitor voltage supply rail margining or just monitoring signal voltage. Using Digital Power Designer any of monitor pins (MON1 - MON13) can be configured to monitor one specific voltage supply rail. Similarly, any of montor pins (MON1 - MON13) can be configured just to monitor signal voltages.

Hi Masaya Emi /all,

     We are using the same chip on board for monitoring purpose.

Is it possible to monitor the rails, by using fusion digital power designer which is running on the same board with out any i2c adapter?

My Board details are given bellow?

CPU : Intel sandybridge

Chipset: Patsburg

OS: windows server 2008 R2

Interface: SMBUS

--

  Sebastian

It would be possible but Fusion Digital Power Designer currently only supports the Texas Instruments USB-TO-GPIO I2C/SMBus adapter

Hi Eric,

       Thanks for your clarification

       Do you have any Linux application for reading the voltage information from the chip?

Windows server 2008 is using for only testing. Our product will be releasing with Redhat Linux Enterprise 6

Is there any driver is required for this?

In our board this IC is connected to Intel patsburg chipset via SMBUS.

-- 

 Thanks

       Sebastian V P

Hi Eric,

    We are using UCD90120A is only for the monitoring purpose and this data has to pass to Intel patsburg via SMBUS.

I have gone through the USB adapter datasheet (http://www.ti.com/lit/ml/sllu093/sllu093.pdf).  Our plan is  to program the onboard chip using this device, 

Datasheet says the target board is connected using a 10pin ribbon cable and 100 mil connector (Table2-1). 

1.  From this table what are all the signals required to provide on the on board programming header for this chip (UCD90120A) programming.

2. PMBUS_CNTRL: Is it required to connect the external header? Is ther any PU/PD is require

USB adapter pin out from the datasheet (http://www.ti.com/lit/ml/sllu093/sllu093.pdf)

--

  Sebastian V P

The "bare minimum" signals are: GROUND (6), SCL (9), SDA (10).

PMBCTRL1 (7) provides additional ON/OFF functionality to the UCD chip but is not required. I would suggest hooking it up just in case.

PMBALERT (8) provides global chip status to the PMBus master and is also useful for providing an "interrupt".

Hi  Eric,

    Thanks for your valuable information.

We have two   UCD90120 on our board in same bus . Is it possibele to program using a common header. My understanding is we can generate 2 seperate PMBUS script with 2 diiferent I2C address using fusion gui and configure (program) it using the same header.

--

  Sebastian V P

You are correct. Just set up each UCD90xxx with a different address using the ADDR resistors and then use a single PMBus header to communicate with multiple bus's. Fusion will find and show each device in the GUI so you can use a single session of Fusion to configure multiple devices.

Hi Eric

     We are using UCD90120A device on SMLINK1 of Intel patsburg chipset and it is operating with a frequency of 100KHz. Is UCD90120A compatible for this BUS?

--

   Sebastian V P

UCD90120A can operate from 100kHz SMBus or I2C.

Hi Eric,

        I got the evaluation module. Now my chip is already mounted on board. Isolated this device using header assembly and connected to evaluation module. Configured the device. And is reading the reading also.

        UCD90120A has 13 inputs. But in fusion GUI I am able to add only 12 rails. How can I add the 13 th input (Pin 56 : Mon13)

--

   Sebastian V P

The 13th MON can be added as a current or temperature MON to an existing voltage rail.

Hi Eric,

         We are using UCD90120 with Intel Patsburg chipset. It has total 3 SMBUS controllers (SMBUS, SMLINK0 and SMLINK1)

Our requirement is to work this device on SMLINK1 ( Which is basically an SMBUS). When we run the commands for reding the register value, it is giving an error code and the scope shots shows clock line is stretched more than 35 ms ie the time out condition.

         Then we wired the chip to the SMBUS. In this bus it is working fine and we are able to read the voltage monitor register values.

Both SMBUS and SMLINK 1 is configured in the same frequency (100KHz)

Temperature sensors on the SMLINK1 is working fine.

Can you please give your suggestion on this issue?

--

   Sebastian V P

Obtain a bus monitor/sniffer such as Total Phase Beagle or Aardvark to help diagnose bus issues.