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.

How to fix this error?

Other Parts Discussed in Thread: UCD9222

Hi.

I installed FUSION Digital Power 2.0 and I connect my board to configure UCD9222 but Fusion Digital Power saw this error

Error creating device UCD9222: Failed to create device UCD9222 object at address 78: This firmware release (1.0) is no longer supported by Fusion tools; it is pre-release firmware. Please contact your Texas Instruments representative for assistance.

How to fix this error?? and I use Win10, what version Fusoin Digital Power support for?

Regards

Thanks.

  • Hello ?? nobody here??
  • I have seen the same error message when trying to start Fusion Digital Power Designer 2.0.166 if the tool 'Edit Device Scan Options' is set for IC_Device_ID.  If I change the scan option to "DEVICE_ID & DEVICE_CODE & IC_DEVICE_ID", Fusion Digital Power Designer starts without presenting the error message. 

    The full text of the error message is:

    An error occured while trying to detect a PMBus device. The error was:
    Error creating device UCD9222: Failed to create device UCD9222 object at address 78: This firmware release (1.0) is no longer supported by Fusion tools; it is pre-release firmware. Please contact your Texas Instruments representative for assistance. Full DEVICE_ID is UCD9222-48|6.4.0.12747|101215. at TIDP.PMBus.PMBusDevice.l(ai A_0, IEnumerable`1 A_1, ar A_2) at TIDP.PMBus.PMBusDevice.l(ak A_0) at TIDP.PMBus.WinForms.Forms.a.n0()
    Please check your device firmware, power, and USB connection.

    I am using a USB-TO-GPIO EVM adapter.  The available adapter firmware versions in the 'USB Adapter Firmware Download' tool include 1.0.10, 1.0.11, 1.0.13, and 1.0.14.  The adapter was received with version 1.0.10.  I upgraded to 1.0.14 but had to downgrade to 1.0.11 for other reasons.  The error message was seen while running version 1.0.11 firmware on the USB-TO-GPIO EVM adapter.


    Is IC_Device_ID simply not supported as a scan option for the UCD9222?  If the error message is valid how do I obtain the appropriate firmware for the UCD9222 ?

  • It is best to use the scanning method which includes all the possible formats. It will slow down the discovery process somewhat but you will be guaranteed to capture all TI PMBus devices supported by the Fusion Digital Power Designer GUI that are connected to the bus.

     A bit of history involved with the different scanning options.

    When the PMBus was first released there was no standard command for identifying the type of device.

    TI created a MFR_SPECIFIC command, DEVICE_ID, for its early fully digital implementation.  This was a block read command of 4 bytes which was not an issue given the memory available in this device.

    Hybrid analog/digital devices were later developed which had limited memory register resources and TI created a MFR_SPECIFIC byte command called DEVICE_CODE to identify these devices.

    In newer releases of the PMBus specification, the PMBus.org created a "standard" command called IC_DEVICE_ID for manufacturers to use to identify the device.  And this is used in the most recent PMBus devices that have been released.

    I used quotations around standard because the IC_DEVICE_ID command is defined as a block read of varying length which allows the manufacturer to use the format of their choice.  So the only thing that is truly standard is the command code.  It would be hoped that each manufacturer would have a standard definition for all parts they produce which support IC_DEVICE_ID.

  • Thank-you very much for the response.  If I understand correctly the error message that I received is valid and I should expect the UCD9222 to respond to IC_DEVICE_ID if I was using the proper firmware.  The question is how do I obtain the proper firmware?

  • I left off that the correct scanning method for the UCD9222, being a full digital implementation, would be DEVICE_ID or any of the scanning options that include DEVICE_ID. Using just IC_DEVICE_ID will result in an error in detection.

    You did indicate that the Fusion GUI opened properly when the scanning method was "DEVICE_ID & DEVICE_CODE & IC_DEVICE_ID", correct?

    Scanning all three identification types is the most versatile method (it will take an extra second or two to complete vs. running a single scan method but it would load any device which responds to any identification method)
    i.e. You could load a UCD device (DEVICE_ID), a TPS device (IC_DEVICE_ID) and a TPS device (DEVICE_CODE) which all share the same PMBus interface into the Fusion GUI at the same time.

    This scanning method also works well if you are switching between multiple projects that use different identification types. (No need to remember to change the scanning method)