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.

UCD90320EVM-783: UCD90320 connection to PC using USB2ANY + general doubts

Part Number: UCD90320EVM-783

Hi,

I want to control AMON (r1) pins using DMON (d1) states.

On power up r1 should turn on only of d1 is power good.

and if d1 is NOT POWER GOOD r1 should shutdown.

 

I have attached the config file I have done. First time it worked i.e fault in DMON caused r1 to shutdown.

But I when I tried the same after clearing the faults, d1 as IDLE even if I connected it to PULL UP(3.3V).

0066.test1.xml

Thanks and regards,

Ashwath.test1.xml

  • When D1 has a UV fault, based on your settings, both D1 and R1 will be shutdown. that's exactly what you observed. Since resequncing feature is not enabled on the UV fault response of D1, both D1 and R1 rail will stay at IDLE. manually pulling the D1 up to 3.3V does change the state of the rail. those rails are off.
    you can change the on_off_configure of both D1 and R1 to CONTROL_PIN only. so that you can toggle control pin on the GUI to bring those bring out of IDLE.

    Regards
    Yihe
  • Hi,

    I dont want to use control pin since its not software controllable..Is there any PMBus command to toggle control pins??

    Or can you just explain me how to implement my following requirements-

    1) r1 depends on d1 power good to turn ON.
    Fault on d1 should cause r1 to shutdown (I 'm able to do that for the first time after power up.But after the UVF of d1 ,its been in IDLE state even if I supply 3.3V) and d1 should not go into IDLE state. I saw that restart continously option not available for UVF in fault respnoses.

    2)If control pin is command controllable then it will be fine. Only other option I saw was to reset the device and bring the rail states up.

    3)Also restart upto option is not changing the value also. Its been a constant value at 1.

    4) I even observed that, after the first fault in d1:

    d1-IDLE

    r1-IDLE

    I pulled up d1 to 3.3V (still its in IDLE state only). I gave the OPERATION turn on command for r1 to power up. Surprisingly r1 came up. Now I pulled down d1 which

    is in IDLE. But this didnt shut down r1. This is very serious issue I'm concerned about.

    I think its a bug. r1 should not only depend on POWER GOOD of d1 but also it should depend on d1's rail status. Even if the rail status of d1 is IDLE, some external device

    which drives voltage on d1 will  turn on r1 (ofcourse on turn on operation command). Its not a desired result



    Thanks and regards,
    Ashwath.

  • www.ti.com/.../slua815.pdf please read section 4.9 to understand the restart and re-sequencer. most of your questions are answered there.
    if pmbus_control is not applicable, you can configure rails' ON_OFF_CONFIG to OPERATION only, so that you can issue pmbus OPERATION command to turn on and off both D1 and R1 rail manually. this shall help you case.

    as said before, manually pulling the d1 up to 3.3V does not change the state of the D1, D1 is still under IDLE. under IDLE case, there is no UV fault even you manually drop the pull-up to the 3.3V.

    If the D1's enable is controlled by the UCD, it shall not reach POWER_GOOD when its ENABLE pin is de-asserted. if you have external circuity which could make D1 reach POWER_GOOD without ASSERTING its ENABLE PIN , that the design need re-think.


    Regards
    Yihe
  • Hi,

    1)I dont want to use ENABLE pin because I just want to monitor a voltage coming to UCD from external source and depending on it sequencing ON and OFF should happen. I dont want the UCD to kick start the sequencing.

    2) I know that I can use OPERATION command to change the state of the rails.
    Is there any way to change the IDLE state of an auto enable rail ? I'm not been able to bring that rail (d1) to RAMP_UP state after its UVF shutdown. Even after clearing the faults its been the same situation. So using OPERATION command ,reset,Pin selected rail states are my options right ??

    Thanks and regards,
    Ashwath.

  • please refer section 4.7,4.8 and 4.9 of www.ti.com/.../slua815.pdf
    The only way to bring the IDEL state of a auto enable rail to ramp_up or REGULAT is to use the fault response. you have to enable re-sequensing feature in the D1 rail's fault response. so when D1 has a UV fault, it shutdown itself and r1. when both D1 and R1 are below POWER_GOOD_OFF threshold, resequencing will try to bring both D1 and R1 out of IDEL.
    Regards
    Yihe
  • Hi,

    It solved my problem.!!!

    One more question:

    Can we toggle the enable pin of a rail through PMBus command?

    Thanks and regards,
    Ashwath.

  • It is good to hear.

    if the ON/OFF CONFIG is set to OPERATION mode, you can issue OPERATION command to toggle the ENABLE Pin.

    Regards

    Yihe

  • Hi,

    I dont want to use the operation command because that will shut down the every rail that I have.

    Otherwise, polarity of the enable signal is software configurable (via PMBus commands) right?? I think changing the polarity in real time serves the purpose.

    Regards,

    Ashwath.

  • Hi,

    Is there any option to change the poarity of DMON pins? Like 0V implies LOGIC HIGH (power good) and 3.3V is LOGIC LOW.
    I can see active low and high options for GPI pins not for DMON.

    Regards,
    Ashwath.
  • No, OPERATION Command is a paged-based command. so it only turn on or off the rail you have assigned before. it will not shutdown all rails which are up to the operation command.

    OPERATION command is the way to toggle individual rails' ENABLE.
    The polarity of the DMON is not configuration.
    Regards
    yihe
  • Hi,

    I want to have a rail with auto enable.It should not depend on the turn on command to start.It should start on its own. But if at all I want to forcefully shut down the system in some extreme conditions 

    I want to give the external software to control its shutdown. 

    If I enable OPERATION command dependency it will wait for the TURN ON command to start.

    So I'm thinking of changing the polarity of the enable signal. SEQ_CONFIG does the job right?

    Thanks and regards,

    Ashwath.

  • HI,

    I have configured Pin L4 LGPO13(GPIO) as GPI fault enable. The fault on it should trigger shutdown sequence.

    When I tried to assign this functionality in the fault response I'm not been able to see LGPO13 only.

    Thanks and regards,

    Ashwath.

  • Ashwath

    do you prefer command over GPIO? how do you turn the rail back on later on?

    If i were you, i would use CONTRL_PIN( for example ACTIVE HIGH), by default CONTROL_PIN is high, so when UCD is out of reset, it wil read the CONTROL_PIN state, it will turn on all rails if it is high. there is no need for commands or other signals. under exetremey case, you can pull the CONTROL_PIN low, than the rails will be off. you can toggle CONTROL_PIN high to let UCD to turn rails back on again later.

    Regards

    Yihe

  • THe GPI #16 is not the phyiscal pin and instead it is the index of the GPI you assigned.
    Which GPI was assigned by LGPO13?
    Regards
    Yihe
  • Hi,

    But when I used TURN ON(OPERATION) in Fusion GUI all the rails started.

    Then is it like OPERATION(0xFF)?

  • Hi,

    I have configured LGPO13 as GPI fault pin.

    I want amon1 and amon2 to shutdown when GPI #1 is low. When I tried to assign that in fault response I'm not seeing any LGPO13. All that I can see are the GPI #1 to GPI #32 and all the GPIs were

    showing unassigned. 

    Now which GPI pin should I have to assign in order to get the desired result.?

    Regards,

    Ashwath. 

  • Haa,I know that way. But CNTRL pin is not PMBus command controllable right. Mannual interaction is required for that.
    So I dont want to go for that. My UCD should be controlled by external software via I2C using PMBus commands.

    and I already have a board in which we haven't routed CNTRL pin so...

    I cant enjoy CNTRL pin feature
  • Hi,

    I have configured GPIO4 as GPI fault pin. I'm controlling it using GPO MAR13.

    I have set in fault response of GPI #01 and bingo I'm getting the desired result.

    It should have been GPI #04 fault which should cause the shutdown right?

    How the GPI pins are mapped in fault response list?

    Like I have configured GPIO 4 as  GPI fault pin in hardware config.

    But I set GPI #1 in fault response. Whats actually happening here?

    I have attached the config file

    test.xml

  • Hi,

    See this config file. I have set MAR 04 pin as GPI fault pin .

    But in fault response I'm using GPI #1 and  I'm getting the result.

    3630.test1.xml

    Can u explain me how the mapping of GPIO pins are done in fault response?

    Regards,

    Ashwath.

  • Ok, you want to rail to start automatically, but you also want to have a pmbus command to control the rail.

    If that's the case, you can use PIN SELECTED RAIL STATE, which is very similiar with PMBUS_CONTRL.

    when rail's on_off_config is set to OPERATION, besides OPERATION command, applicaion can also assign up to 3 GPIs(8 state) to device rails' on/off.

    The PIN SELECTED RAIL STATE is under Global Configure.

    So when UCD is out of reset, it read the GPI to determine whether the rail shall be on  or off. if under any extremet case, you can issue operation command to turn off the rails.

    Regards

    Yihe

  • Hi,

    Can you explain me how to toggle Command controlled GPO pins via PMBus commands. I know I have to use GPIO_CONFIG command. I have toggled it in the Fusion GUI and I'm seeing this in the PMBus log

    GPIO_CONFIG_80 [MFR 43,0xFB]: wrote Static GPO [1] [Enable: True; Out_Enable: True; Out_Value: True; Status: False] [0x07] to RAM

    GPIO_CONFIG_80 [MFR 43,0xFB] is the command right.. What is the role of [0x07] being written to RAM..

    Please explain me

    Thanks and regards,

    Ashwath.

  • In order to configrue a commanded based GPIO.

    the followiing commands are need in a pari:

    1. GPIO_SELECT(0xFA). this command is to select which pin to configure. The value used with command is the Pin ID(pin index) defined in the table 11 http://www.ti.com/lit/ug/slvuaw9a/slvuaw9a.pdf

    2.GPIO_CONFIG(0xFB).this command is to configure the pin(high/low). please refer section 11.41 of http://www.ti.com/lit/ug/slvuaw9a/slvuaw9a.pdf to understand why value of 0x7is used.

    Regards

    Yihe