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: Fusion finds multiple designs in a singla UCD3138

Part Number: UCD3138

Hello,

We have a fullbridge LLC firmware that we load to an UCD3138 device.

When we connect with Fusion, it prints the following. Notice the "Found **** "  lines. It claims to have found both an LLC design and a PFC design in the same IC!

Any ideas what might be going wrong?

Thanks!

22.03.2017 17:10:52

Data Flash verified!

22.03.2017 17:10:52

Writing program flash checksum 0x338B79 ...

22.03.2017 17:10:52

Validating checksum written through read back ...

22.03.2017 17:10:52

Program flash checksum AOK

22.03.2017 17:10:52

Download completed without error; 16,2 sec elapsed

22.03.2017 17:10:52

Sending ROM execute flash command (SendByte 0xF0 to address 11)

22.03.2017 17:10:54

Scanning for programs that respond to a DEVICE_ID read ...

22.03.2017 17:10:54

Looking for device in program mode ...

22.03.2017 17:10:55

Found DC-DC LLC Firmware v0.0.49.0 @ PMBus Address 89d in program mode

22.03.2017 17:10:55

Found PFC SinglePhase Shunt Firmware v0.0.49.0 @ PMBus Address 89d in program mode

22.03.2017 17:11:05

22.03.2017 17:11:05

Sending the device to ROM mode (clears program flash checksum) ...

22.03.2017 17:11:05

Waiting for ROM mode via ROM version fetch ...

22.03.2017 17:11:08

Error: Device does not appear to be in ROM mode after ENABLE_ROM_MODE command; after 3.000 msec the ROM is still not responding

22.03.2017 17:11:14

22.03.2017 17:11:14

Sending the device to ROM mode (clears program flash checksum) ...

22.03.2017 17:11:14

Waiting for ROM mode via ROM version fetch ...

22.03.2017 17:11:17

Error: Device does not appear to be in ROM mode after ENABLE_ROM_MODE command; after 3.000 msec the ROM is still not responding

  • The fact that it discovers both isn't hard to explain.  Some of our DC/DC codes are also designed to support interface to a PFC via the UART.  So I wouldn't worry about it.  Maybe you can make it go away from the GUI by taking every bit in the PFC_CMD #define and making it a zero, but I don't know exactly how the GUI figures these things out.  Here's a sample start from a PFC:

    #define CMD_PFC \

    {0x10, 0x00, \

    0x60, 0x00, \

    ....