• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 64 subscribers
  • Views 140 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

UCD9081: Parts stopped reponding on PMBUS

CHAD GRANSTAFF
Prodigy 10 points
Part Number: UCD9081
Other Parts Discussed in Thread: USB-TO-GPIO2,

I believe I have parts that were corrupted during programming because of greater that 32 byte block size and/or not programming complete device.  These parts had prviously been reconized with the tools but do not now.

Is there anyway to recover these devices?

The hardware is working since I still have one that programs / verifies on the same bus.

Using:

USB-TO-GPIO2

TI-Fusion-Digital-Power-Designer-7.10.1 Script Runner and SMBus / I2C / SAA Tool

  • 0
    TI__Guru 60800 points

    Hi

    Fusion GUI does not support UCD9081.

    Please use the below GUI and ensure that the speed of USB-TO-GPIO2 is set to 100KHz and PEC is disable

    https://www.ti.com/tool/download/UCD9081-EVM-GUI 

    Regards

    Yihe 

  • 0 in reply to yihe
    Prodigy 10 points

    I am using the UCD9081-EVM-GUI tool also.  It will only discover the device that is still working.  It will not discover the others on the bus.

    The script runner and smbus / i2c / saa tool is working. Does using it corrupt the devices?

  • 0 in reply to CHAD GRANSTAFF
    TI__Guru 60800 points

    Hi 

    What kind of script do you run by script runner? The Smbus i2c/saa is low level tool which can be used to communicate any I2C device.

    I won't expect that the programming can brick the device.

    But UCD9081's I2C is software-based. if the device is too buy to process fault, you may not get the i2c response.

    Have you tried the USB-TO-GPIO instead of USB-TO-GPIO2?

    Regards

    Yihe

  • 0 in reply to yihe
    Prodigy 10 points

    I'm using a CSV batch generated from the SMBusI2CScriptForm. 

    I2CWrite,0xC02E02
    I2CWrite,0xC0308010
    I2CWrite,0xC032DCBA
    I2CWrite,0xC0308010
    I2CWrite,0xC0322020202020202020202020202020202020202020202020202020202020202020
    I2CWrite,0xC030A010
    I2CWrite,0xC0322020202020202020202020202020202020202020202020202020202020202020
    ....

    I2CWrite,0xC03000E0
    I2CWrite,0xC032DCBA
    I2CWrite,0xC03000E0
    I2CWrite,0xC0320000000000000000000000000000000000000000000000000000000000000000
    I2CWrite,0xC03020E0
    I2CWrite,0xC0320000000000000000000000000000000000000000000000000000000000000000
    ....

    I2CWrite,0xC02E00

    I don't think "too busy" is the issue but how would I know if I can never communicate with it?

    I read in datasheet that segment size must range between 2 and 32 bytes at one time and a multiple of two.  If not done the device is in an unknown state.

    However, the Programming Guide suggests the device supports blocks or 2 bytes to 512 bytes.  My initial attempts batch/scripts used blocks larger than 32.

    Can you speak about this unknown state and if there is a way to recover?  I believe this could be the issue I have.

    The script I'm using now only has 32-byte blocks.

    Don't have access to a USB-TO_GPIO.

  • +1 in reply to CHAD GRANSTAFF
    TI__Guru 60800 points

    Hi

    You may have to replace the IC

    Regards

    Yihe