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.

UCD3138CC64EVM-030: PMBus message in UCD3xxx device GUI

Part Number: UCD3138CC64EVM-030
Other Parts Discussed in Thread: UCD3138PFCEVM-026

Hello,

I have downloaded the PFC firmware from here and then connected the UCD3138CC64EVM to the PC as per the steps mentioned in SLUU886A

After directly converting the firmware to .x0 using CCS and downloading the file using UCD3xxx GUI. 

I faced the following warning(in yellow) :

Why is this message showing up? user's guide does not mention any such message.


Regards,

  • All of the EVM codes have what we refer to as hardware backdoor.  

    If you start modifying a UCD code, it is very easy to lock up the device by introducing a bug which prevents you from being able to clear the checksum.  If this happens, then the IP security features of the UCD will not permit you to erase the flash and reprogram the device.

    For this reason, we strongly suggest that you don't write the checksum when downloading a code with any changes in it.  

    First download the new code without the checksum.  While the code is executing, click the command code to jump to ROM command.  

    After the code returns to ROM, click the checksum tap and click dump.  make sure that the checksum location it is reading from is correct.

    If the checksum is being cleared properly, you will see zeroes in the dumped checksum.  If you see zeroes, it should be safe to download that particular code with the checksum, or just click on the Recreate button to put in the valid checksum.  

    If the dump shows anything else, including FFs, don't write the checksum, but debug the clear checksum or zero out integrity word. code.  

    Back to the hardware backdoor.  This is some code we add to increase your chances of not locking up the checksum.  It's not a guaranteed capability, but it is helpful.

    If you look at the start of the main function in main.c, you will see the backdoor code:

    //Check to see if FAULT1 is pulled high, or flash trim checksum is bad, if yes then go to ROM. if yes then go to ROM.
    if((MiscAnalogRegs.GLBIOREAD.bit.FAULT1_IO_READ == 1) || (PMBusRegs.PMBCTRL1.bit.SLAVE_ADDR == 0x7e))
    {
    pmbus_read_write_rom_mode(PMBUS_WRITE);
    }

    Please leave the code in and just pull the fault 1 pin down with a jumper wire to disable the backdoor.  That way you may still be able to recover the chip if you mess up the checksum erase capability by pulling FAULT 1 up, but normally the backdoor will be disabled.  

  • Hello,

    I did not make any changes to the code, I created the .x0 of the firmware downloaded from the website as it is.

    I am looking to run the Classic PFC EVAL Board UCD3138PFCEVM-026 with the controller card. 

    I tried downloading the same code/.x0 file without the checksum, but still getting the same messages:

    Also as you said here  "While the code is executing, click the command code to jump to ROM command."

    Seems like it is not going from Program --> Rom

    I clicked on the "Command program to jump to Rom and Scan" option in "others" and got these other messages :

    Regards,

  • What Ian said about " click the command code to jump to ROM command" is that when the user code is exectuing. But it looks like that your code is not executing, and it stays in ROM.

    Have you checked your board on the backdoor condition? If you have the same backdoor code as below, please pull the fault 1 pin low to disable the backdoor. 

    //Check to see if FAULT1 is pulled high, or flash trim checksum is bad, if yes then go to ROM. if yes then go to ROM.
    if((MiscAnalogRegs.GLBIOREAD.bit.FAULT1_IO_READ == 1) || (PMBusRegs.PMBCTRL1.bit.SLAVE_ADDR == 0x7e))
    {
    pmbus_read_write_rom_mode(PMBUS_WRITE);
    }

    Best Regards,

    Xuemei