UCD90160A: Reading checksum via GUI

Hi

Please ignore the checksum shown in the snapshot, it is not useful.

If you want to confirm the programming is successful or not, please refer section 3.2 of www.ti.com/.../slua815b.pdf.

if you want to compare the data flash hex file, please refer section 3.3 of www.ti.com/.../slua815b.pdf.

Regards

yihe

Hi Yihe,

Not understand.

First, if Hardcoded Parms didn't red light, that means successful programming?

Second, section 3.3 not write how to compare data flash hex file.

BR

Eric

Hello

If HARDCODE_PARMS is not set, it means that device has a valid configuration in place. if you have set the different MFR_REVISION for each configuration, your can read the back the MFR_REVISION to confirm whether this is a new or older configuration.

Data flash hex is a text file, you can export the file from GUI and compare the files using any edit tool which support compare function.

Please refer below video to learn how to export file;

https://training.ti.com/fusion-power-designer-import-and-export-data-flash-hex-files?context=1136655-1139495-1136589

Regards

Yihe

Hi Yihe,

Can I use Data Flash Script.csv to compare tool?

BR

Eric

Hello

Do you want to compare the data flash data from the chip with the csv file? you can read the MFR_REVSION as mentioned in the early post, it is the quickest way to confirm whether the data matches or not?

for the csv file, it can do the compare but since it also contain the fault/peak log which will be different cross the devices. it is not a good way to do.

You can refer section 3.3 of

Regards

Yihe

Hi Yihe,

So Ti recommend to use data flash file to export and import to device? not .csv file?

BR

Eric

Hello Eric

There are two types csv file: pmbus write script and data flash script. Data flash script or data flash hex file are the recommended format to program the device.

Regards

Yihe

Hi Yihe,

Our SW think we can use MFR_ID control version.

But when I change to "01", read value was 0x30 0x31 0x6b

And I try change to "001", read value was 0x30 0x30 0x31 0x82

Why value can not meet setting?

BR

Eric

Hi Yihe,

I find PEC data means Packet Error Checking?

If yes, the PEC data will change according to value by my setting?

If I want to make sure version when manufacture, can I ignore PEC data? or should I check including PEC data?

BR

Eric

Hi Yihe,

If I want to make sure I2C signal is good, that means I must check PEC data to prevent any issue?

BR

Eric

Hi Yihe,

OK, I understood.

One more question, if I programming via socket from development board, chip still create PEC data?

BR

Eric