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.

UCD90120A: EVM can access the UCD90124 but not the UCD90120A

Part Number: UCD90120A
Other Parts Discussed in Thread: UCD90SEQ64EVM-650, UCD90124, , USB-TO-GPIO

The UCD90SEQ64EVM-650 comes with a UCD90124 installed in the socket.  I was able to access and configure the UCD90124 with no issues.

I replaced the UCD90124 with a UCD90120A but can not access the UCD90120A with the Fusion tool.  Here is the warning message:

It appears that the tool recognized the PMBUS address but could not advance any further.  Any suggestions on how to resolve this issue?

Thanks,

Phil

856-7676-7676 ext 2277

  • Please share your warning message so that we can help,

    Regards

    yihe

  • Here is the warning message:

    "Failed to create device.

    Failed to create device UCD90120A object at address 101:Error reading NUM_PAGES:NACK.

    Can not continue configuring the attached device as a UCD90120A."

    The tool was able to find the device when it completed its scan.  Before the warning message window, the tool displayed a window that stated:

    "Scanning USB Adapter #1 for devices....

    Found UCD90120A at address 101d (1 device found)"

    Thanks,

    Phil

    856-767-7676 ext 2277

  • Did you mean after you swapped the IC from 90124 to 90120A, the GUI can not access the UCD90120A?
    Could you try to enable the PEC on USB-TO-GPIO Dongle , refer setion 6.1 of www.ti.com/.../slvub51.pdf

    thank
    yihe
  • Yes, after I swapped the IC from 90124 to 90120A, the GUI could not access the UCD90120A.

    I changed the PEC (Packet Error Checking) from Disabled to Enabled and received this warning:

    "Failed to create device.

    Failed to create device UCD90120A object at address 101: Object reference not set to an instance of an object"

    I tried all 4 configuration combinations below and received the same warning message as above:

    1)    Bus Speed 100khz, PEC Disabled

    2)    Bus Speed 100khz, PEC Enabled

    3)    Bus Speed 400khz, PEC Disabled

    4)    Bus Speed 400khz, PEC Enabled

    What does this warning message mean?

    Any other suggestions on how to resolve this issue?

    Thanks,
    Phil

    856-767-7676 ext 2277

  • Is it a brand new UCD90120A? you may tried to erase the configuraiton file. please follow below:

    Please follow the image to do.

    thanks

    yihe

  • Yes, it is a brand new UCD90120A. I tried several different UCD90120As in the socket and got the same warning message.
    Per your suggestion, I tried to erase the device using the tool you recommended. I received the following error message:
    "Activity #1 of 1 produced a fatal error"
    "Could not read DEVICE_ID from address 101: NACK; it is impossible to erase data flash on a device if it's DEVICE_ID can not be read; this indicates a serious communication of firmware error must be resolved"

    I then tried to Scan for Devices and received the following message:
    "Performing DEVICE_ID reads on addresses 1 through 127, skipping 12. PMBUS_REVISION will be read on DEVICE_ID read error."
    "Address 101 read PMBUS_REVISION [0x98] returned 1.1, 1.1 - Part II: 1.1 [0x21]"
    "***Warning: expected 0x21 to be returned by PMBUS_REVISION"
    "Found 1 device(s)"

    What do you think is the root issue here? I believe the tool can find the device at address 101d. What is the next step?
    Thanks,
    Phil
  • Hi Phil

    could you try the devic GUI and click the DEVICE_ID to see whether the device is detectable?

    Also could you try to change the pull-up resistor on the same setting as PEC operation to see whether GUI can configure the device?

    Regards

    Yihe

  • I tried all the different pull-up resistor values and it did not resolve the issue.

    I opened the Device GUI tool and clicked on DEVICE_ID and got this warning message:

    What does "Failed to create device UCD90120A object at address 101: Object reference not set to an instance of an object" mean??

     

    The MFG information came up all "empty".  What is the root issue here?

    Thanks,
    Phil

     

     

  • could you try the SCAN DEVICE IN ROM Mode on the DEVICE GUI to see whether GUI can detect the device?
    Thanks
    Yihe
  • I tried but it failed. Here is the error message:
    "Error: Unable to communicate with ROM, device may be in Flash Mode."
    "No ROM Detected"
  • which Fusion GUI is usded?
    Could you follow section 6.9 www.ti.com/.../slvub51.pdf to open the tool shown on figure 6-16.
    at the read block put 0xFD into the Cmd and click send to retrieve the device _id. Please share receiving data.
    Thanks
    Yihe
  • I'm using Fusion Digital Power Designer

    Version 7.0.1 [2017-04-04]

    Here is the data received when I sent the Read Block "FD" command:

    10:40:43.505: SAA #1: BlockRead (Address 101d, Cmd 0xFD): ACK 0x5543443930313230417C322E332E342E303030307C31313036303300

    Thanks,

    Phil

  • Hi Phil

    Please download the latest Fusion GUI 7.0.11 from below.

    http://www.ti.com/tool/fusion_digital_power_designer

    Regards

    Yihe

  • Thanks the latest Fusion version resolved the issue.