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.

UCD3138: UCD3138 firmware programming error

Part Number: UCD3138

Hello
I made a prototype based on the UCD3138's full-bridge hard-switch development board.

After I just burned the firmware to the prototype, everything went fine and the prototype worked fine.

I changed the output capacitance of the prototype and reported an error when burning the firmware again. As shown below:

The program displays "No devices found".

I changed the second prototype and it can burn and work normally.

I don't know why it failed when burning. Why can a prototype burn  successfully but another  prototype  fail to burn? Is the UCD3138 of the failed prototype broken?

  • I tried to re-burn the firmware, but still reported an error, as shown above.
    "No PMBus devices responded to a DEVICE_ID requset"

  • I replaced a new UCD3138 and the same error occurred when I re-programmed the program.
    I think UCD3138 should not be damaged, but I don't know what went wrong, which caused the firmware to fail to burn.
  • Please scan the device in ROM mode (Click on Scan Device in ROM, on the top side of device GUI)
    Based on your screen shot I can see that you have chosen not wrote the checksum.
    So your device may be in ROM mode.
  • In the first picture, I first clicked on "scan the device in ROM mode". When the status is normal, it shows "Found ROM V2 IC V3-UCD3138.Rev2". When I click "command rom to execute its programe", it appears. The error was "no device found".
    Very strangely, this prototype was working properly before. I just replaced the output capacitor.
    After I replaced a 330uF tantalum capacitor with a 300uF ceramic capacitor, I got an error.
    I later replaced the ceramic capacitor with a tantalum capacitor, and the prototype could be started normally.
    After that, I replaced the tantalum capacitor with a ceramic capacitor and the prototype could start up normally. Now the prototype can work normally.
    I have not changed anything except the output capacitor. I think the startup of the software should have nothing to do with the type of output capacitor, so I am wondering why the error occurred before? What are the reasons that can lead to an error?
  • The issue may be caused by something else and is intermittent.
    And it appeared like it is related to the output cap, but it is not.
    Please just make sure that the slope of the 3.3 V power up ramp time meets the UCD3138 requirement.