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.

UCD90160: UCD90160 not seen anymore after NVM write failed

Part Number: UCD90160

We have a new board designed with UCD90160 power sequencer device, and we need some help for one board where the device suddenly stopped being seen on I²C after writing is configuration in NVM with Fusion Digital Power Designer.

The device was working well before that and we are using it with the same configuration on other boards without issues, maybe the power supply was turned off too soon after or during process of NVM writing.

 

We tried with the UCD90xxx device guide but the "scan device in ROM Mode" function gives nothing => no device found.

Could you please give us the procedure to recover it from I²C and/or JTAG? Is there any way to force the device to go in ROM mode?

  • Hi

    What kind of data do you program? if you just update the configuration, the failure due to power loss shall not let the device enter ROM mode, you will most likely lose all the configuration. but you shall still be able to reprogram the part.

    What does the UCD90xxx device guide tell if you use san DEVICE_ID?

    Regards

    Yihe

  • Hi, yes I was only updating the configuration with Fusion Digital Power Designer => configure device => Write to hardware => Store RAM to Flash

    And then after power cycling the board, I can't scan the UCD90160 anymore on I²C (worked perfectly before and with other boards too).

    Sorry I meant UCD90xxx device GUI (not guide):

    Looking in this forum I found this and then suspected the device was maybe in "rom mode"??

     https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/959727/ucd90160-can-not-find-ucd90160

  • Hi

    What kind of change do you made? could you track to see whether the change can cause any problem for the system. I assumed that this is on your own system board. 

    have you probed the V33A/V33D/BPCAP/RESET to ensure they are good?

    What does UCD90xxx Device GUI report when scan DEVICE_ID? Did reset or power cycle help?

    Regards

    Yihe

  • Thanks for your help, I finally understand what happened. The configuration loaded had an issue with circular dependancy of two power rails. I think the UCD90160 was stuck in a software loop because of that and was unable to process I²C requests anymore

    I removed the input fuses for the second stage voltages managed by the UCD to kill this software loop and was able to reload a correct configuration.

    Now everything looks fine!