TPS65987D: Use I2C2 to load binfile to external spiflash

Hi James,

If you are using the flash, it might be address 0x50. Can you confirm which SPI Flash you are using or is this for EVM?

Unfortunately, I don't think we have the full code for this but I can confirm.

Thank you,

Hari

Hi Hari,

Please try your best to help get the full code or else the current sample code is sort of unusable for me.

The serial flash is M25P80. Please confirm me the I2C address. Thanks.

Hi James,

At the moment, I do not think we have the full code. I will need more time to check with our team.

For the flash, you will need to check the datasheet for that particular device for the I2C address as I am not familiar with this one.

Thank you,

Hari

Yes, please work on getting the full sample code as I'm needing it soon. Thanks.

Alright what I was experiencing is very strange:

My I2C communicates (wired) with TPS65987D over its I2C2 whose address is 0x70. However TPS65987D responds NAK. BUT, if I use the I2C1 address (0x40) , then TPS65987D responds to I2C2 lines. I feel the documentation could be mistaken between I2C1 and I2C2 for the address?

Again, please help provide the full example as I mentioned above. The source sample in slvae21 is only the .c part of it. Without full sample code, it's unusable. 

Thanks.

Hi James,

The I2C address should be according to the documentation as they are set and controlled by the default device firmware, I'll double check and confirm with you by tomorrow. 

The example in the document should be treated as sudo code. On page 6, there is a flash update execution flow chart that demonstrates the logic behind flash update over I2C. The technical reference manual (TPS987D TRM) includes all the information for 4CC commands as shown in the flow chart. We do not have a full code as that's dependent on the EC connected to the PD controller.

Regards,

Raymond Lin

Hi Raymond, did you have a chance to verify why the I2C addresses are cross-referenced as I observed?

Hi Raymond, thanks for your quick response. Above is my actual hw setup for ADCIN1 & ADCIN2 address selectors (both grounded). However, I2C2 responds to address 0x40 before loading its microcode (blank flash). And after the microcode is loaded, I2C2 then responds to address 0x70. I'm OK with this with some unnecessary extra FW logic though. However, it is very important to me to understand this behavior; especially why the address switches AFTER microcode is loaded...etc. I'd appreciate it if you could help clear this confusion. Thanks. 

Hi James,

I'm not too sure why the I2C addresses are reacting like that. Let me consult with a firmware team member and get back to you by Thursday, thank you for your patience.

Regards,

Raymond Lin