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.

UCD90124A: During the upgrade process, the UCD did not respond.

Part Number: UCD90124A

Tool/software:

Hi 

We have many platforms using the UCD90124A.

Currently, one platform encounters an issue where the UCD does not respond during an x86 online update. After this, our online update process powers off and restarts. At this point, the UCD is in an erased state and empty. Since two PSU_PWR_OK signals are also connected to the UCD, it gets pulled low by the UCD.

As a result, our system cannot power up again.

Could you please help identify the cause of the UCD not responding halfway through the update? And is there any solution to this problem?

We have tried resetting the UCD and attempting the update again when it doesn't respond, but the issue still occurs intermittently. This causes the online equipment to potentially fail to power up again.

Thanks

Bruce

  • Hi

    How do you update UCD90124A, write to the data flash directly or change the RAM value then store to FALSH?

    You may have some kind of interference from the I2C resulting in the failure.

    Have you tried to use TI USB dongle and Fusion GUI to upgrade to see whether the problem is still present?

    Regards

    Yihe 

  • Hi

    How do you update UCD90124A, write to the data flash directly or change the RAM value then store to FALSH? 
    ->We use the i2c write command write to the data flash directly           

    You may have some kind of interference from the I2C resulting in the failure.     
    ->Before update UCD, we will switch the mux to x86 to  update UCD from x86, but will not execute i2cdetect command. What kind of i2c interference do you mean by?   

    Have you tried to use TI USB dongle and Fusion GUI to upgrade to see whether the problem is still present?   
    ->We have tried to use the programmer directly perform the burning action for the UCD PIN, it may also have the probability not detect UCD device(each platform), do you have any ideas?

    Thanks

    Bruce

  • Hi Bruce,

    Yihe is out of office today. Please expect an answer by tomorrow.

    Regards,

    Maha

  • Hi

    in the middle of configuration update, device can be bricked if the update is interrupted due to whatever reason: power loss, I2C signal integrity.

    I am not sure what kind of interference. Maybe some kind of I2C signal integrity. 

    Please share the log when using TI USB dongle and GUI to see the failure

    Regards

    Yihe

  • Hi Yihe :

    Please see the pic below to check using TI USB dongle failure

    We have made sure that the burner is indeed connected to the device.

    Please give some advices, we have also use the i2c logic analyzer to inspect the UCD90124A  behavior. It was observed that when writing an i2c command to UCD90124A at a certain times, the command was sent but the device did not receive it,. If you need the i2c analyzer log, I can share to you.

  • HI

    Did you try to upgrade TI's own firmware? That's something you shall avoid.

    Customer shall only touch data flash section instead of program flash.

    Program flash contains TI pre-loaded firmware and if firmware is broken, fusion can not detect the device anymore.

    Please follow this doc

    8228.recover UCD90124A from ROM mode.pdf

    Regards

    Yihe

  • Hi Yihe :

    1. We usually use the TI GUI to read the UCD default configuration first and only do the GPIO setting through GUI and have the bin file. We will burn this bin file into the device. Can you help to justify that the firmware generated by TI GUI is suitable to burn to the UCD90124A device?

    2. I think the doc that you offered to us is the pure burner procedure. We usually use the TI GUI that can do the configuration setting. The burning procedure may have some different. 

    3.We will use the TI GUI to make some settings to meet our needs and have the final bin file, I am not sure that burn the bin file into device will damage TI pre-loaded firmware or not, can you confirm?

    4. We usually update UCD online using i2c write command. The procedure is below :

    4.1. Erase the UCD flash

    4.2. Use i2c write command to burn the bin file image into UCD flash

    4.3. Verify the flash contents are same as image contents or not

    We use the i2c analyzer inspect the last step will failed because UCD does not respond after the UCD flash is erased, the i2c write command can not write into UCD, so the flash is empty, after that we will do psu reset, and the machine will not power on again.

    5. I think the online upgrade procedure is belong to program flash and the procedure may erase TI pre-loaded firmware. Can you help to confirm that if the TI pre-loaded firmware is erased, is there a probability that will make UCD90124A not response?

    6. If there is a probability that will make UCD90124A not response after TI pre-loaded firmware is erased. Can you share the TI pre-loaded firmware region in UCD90124A, we will enhance the update procedure to not programming this part and only program data flash part.

     

    Thanks

  • Hi

    Please follow the doc and report back the result.

    Regards

    Yihe

  • Hi Yihe :

    Our purpose is not to check using Programmer can detect device or not. We want to have some advices to inspect why online upgrade UCD90124A will encounter the UCD no response.

    Thanks

  • Hi

    Please follow my instructions and report back.

    Regards

    Yihe

  • Hi Yihe :

    We don't have the pure burning programmer in our side, so can not follow your doc to do the procedure and report back. Do you have others advices or instructions?

    Thanks

  • Hi

    I do not get what you mean. you do have the capacity to connect fusion GUI with TI dongle. 

    It is sufficient to run my test

    Regards

    Yihe 

  • Hi Yihe :

    Please refer the results below for the success log and failed log

    Success log :

    Failed log :

    The success log and failed log are using different platform but the UCD device is same which is UCD90124A.

    Our TI fusion GUI please refer below :

    https://www.ti.com/lit/ml/sllu093/sllu093.pdf?ts=1742198985913&ref_url=https%253A%252F%252Fwww.google.com%252F

    Hope you have some advices.

    Thanks

  • HI

    I was asking to run the ROM recovery checking test.

    Regards

    Yihe

  • Hi Yihe:

    How do we run the ROM recovery checking test through our TI fusion GUI? Do you have the SOP or others doc that can share to us? Our TI fusion GUI will scan the device first, if the device is not found, the ROM recovery checking test can not be continued.

    Thanks

  • Hi

    The instruction was provided in the previous reply. please see below.

    ...

    Regards

    Yihe

  • Hi Vincent

    The instructions was provided in the past,

    ...

    Regards

    Yihe

  • Hi Yihe

    As I mentioned before, the doc that you offered to us can not be continued through our TI fusion GUI. The first step will failed due to the device is not found.

    Thanks

  • Hi Yihe

    • As I mentioned before, the instruction that you provided to us previously can not be continued through our TI fusion GUI due to the device is not found. The first step is failed, so the others step can not be continued.
  • Hi

    Which button gave your correct response? Please provide the snapshot

    Regards

    Yihe