TPS53688: IOUT_CAL_OFFSET setting is lost after power cycle

Hi Neo, 

We would have to figure out if it is a GUI reporting issue or a device issue. To do this, we will be reading from the low-level GUI. 

1) You can do this by going to Tools > SMBus_I2C_SAA_ tool.

2) Once you go into the tool, try to use Read Word and Write Word to read and write using this command. The details of the command are given below. First write word to 39h with the value you want. 

3) Then you are going to store to NVM using the lower-level GUI. To do this, send byte to 11h. Pictures below are shown. 

4) Then read back from the device. To do this, read word from 39h. Check if the value that it reports is the same as what you want. 

5) If the value is the same, then we will check what happens when power-cycling the device. To do that, follow Step #2 and #3. Then power-cycle the device. Then follow Step #4 and record the value to see if it is the same as what you wrote to the device. 

Let me know what values you get from the GUI and if they are the same when you read back or not. 

Thank you, 

Dhanya Prem

Hi Dhanya,

Followed you instruction. here is write/read before power cycled. Write/Read is ok with new value 1.25A/E80A.

here is the read after power cycled. Value goes back to default 0A/E800.

We need to release the power image soon, please advise how to proceed.

Thanks

Neo

Hi Neo, 

Do you notice this happening only to this command or does this happen to all commands where it gets reset to the original value?

Thank you, 

Dhanya Prem

Hi Dhanya,

So far i see issue with this command only.

Can you please verify this issue on your demo board and provide a solution on this?

Thanks

Neo

Hi

Dhanya is sick and she will support once back to office

Regards

Yihe

Hi Dhanya
Confirmed this issue happened on Rail#2 only. I can write changes to NVM for RAIL#1 and not lost even after power cycle.

Thanks

Hi Neo, 

Let me try it on my test board and get back to you. 

Thank you, 

Dhanya Prem

Hi Neo,

Sorry for the delay in getting back to you. We would need to do a little bit of low-level GUI debugging. So the PAGE and PHASE behavior could have some sort of issues with this. 

Can you do one more sanity check for me? Do all of this in lower-level GUI. Make sure to turn polling off. 

1) In the lower-level GUI, (Tools > SMBus_I2C_SAA_ tool), make sure you have the right device in. We are going to do the sanity check for Rail B. 

2) Set Page (00h) = 0x01 (Rail B) (Use Write Byte/Read Byte, not Write/Read Block) 

3) Set Phase (04h) = 0x00 (Phase 1) (Use Write Byte/Read Byte field, not Write/Read Block) 

4) Program IOUT_CAL_OFFSET the same way as I described in the last post. 

5) Store the NVM (described in the previous post) 

Let me know what you get for all these values. 

Thank you, 

Dhanya Prem

Hi Dhanya,

Here is the snapshots.

Device 96d, 1+1 config. and the issue occurs on RAIL-B only.

RAIL-A: write-read

RAIL-A: Write-read after power cycle

RAIL-B: Write-read

RAIL-B Wirt-read after power cycle

Hi Neo, 

Thank you! I will reach out to our FW team about this. Is there a good email to reach out so that we can support through email?

Thanks, 

Dhanya Prem

Hi Dhanya,

I have request friend with you, please accept. Will send email address privately to you.

Thanks

Got your request, will loop you in the reply that I get from the firmware team. 

Best Regards, 

Dhanya Prem