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.

UCD9090: Is there a way to tell if the configuration file has error?

Other Parts Discussed in Thread: UCD9090

In the 8524.Configuration Programming of UCD Devices.pdf  file, section 8.4 has the following text:

When the device powers up and executes its program, it computes the checksum of the configuration section of data

flash. It compares this to the checksum section. If there is no match, this is an error condition and the device does the

following:

The device loads a default configuration into operational memory (RAM). This is the configuration that is read

and written via PMBus. This configuration is referred to as the HARDCODED PARMS configuration. The

HARDCODED PARMS config does not have any rails, fans, GPOs, or GPIs defined (UCD92xx and

UCD90xx) nor any monitors or PWMs defined (UCD90xx only).

Then from the UCD9090 manual, it says that the ECC can correct one (1) bit error.  Is there a way to tell that the configuration file has a bit error? 
Thanks.

e2e.ti.com/.../8524.Configuration-Programming-of-UCD-Devices.pdf

  • ECC is transparent to firmware. If ECC corrected an error, firmware will not see it.

  • Thank you. Is there a way for SW to read the actual configuration file from flash via the I2C interface?  I don't want to read the RAM version since there may be an error on the flash that has been corrected by ECC. 

    Basically, I want to be able to detect a singlet bit error in the configuration file in flash before it turns into multiple uncorrectable bit error via the i2C interface. Is this possible? 

  • If the configuration file has an error, the device will be able to detect it by calculating the checksum, then the device will erase the erroneous configuration and wait for new configuration to be downloaded by user. 

  • I understand that when there is a configuration file error, the device will activate the default configuration and wait for a new configuration.

    The problem is that the SW is running on a microprocessor that is powered by the UCD9090. When the device has a configuration error, the microprocessor will not be activated. This render the module useless and there is no way to update this without pulling it out of service.  I want to prevent this situation from happening. 

  • If the configuraion is lost, you have to reprogram the UCD to bring it back work. how can you preven this?
    if there is another processor who can communicate with UCD all the time, you may be able to detect this but not prevent this.
    Regards

    Yihe