STUSB1600

[EOF]

Hello,

I have questions about the STUSB1600:

1. Mouser marks the device as "obsolete". What is the EOL of the STUSB1600 and what alternative is recommended (STUSB1700?)?

2. The STUSB1600 is connected to the MP1 via I2C. I need to program the NVM "in system" with custom values but did not find / missed the information (in the datasheet) on how to do so. Any Idea (apart from the external programming with this NUCLEO board)?

[RobK1]

Re. 1: You mean this one? STUSB1600AQTR STMicroelectronics, the same one that ST marks as "active"? STUSB1600 - USB Type-C controller (with short-to-VBUS protection) - STMicroelectronics

[EOF]

Yes, exactly. I Wonder why Mouser sets it to obsolete....

[EOF]

Ah I see: The STUSB1600QTR is "obsolete" but the "STUSB1600AQTR" is not!

Thank you for the clarification!

[RobK1]

But I linked to the AQTR version. There's the difference.

[NBALL]

Hello

1- STUSB1600AQTR is the valid reference (stusb1600qtr has been replaced by this one since long time). This is the reference used on MP1 board.

2- To program STUSB1600 in system, stsw-stusb004 can be used as example.

Best regards

Nathalie

[EOF · Accepted solution]

Thank you for the feedback.

I was hoping to make the configuration persistent by issuing some commands via I2C from the MP1 to the STUSB1600 like for example "0x42: Writes the content of the configuration into NVM".

I guess this possibility does not exist.

[NBALL]

There is flow to follow to write the NVM: it is not possible to access unitary bit: it needs to be access by 'bank'

Unitary bit can be access thru I2C only

[EOF]

How does the "bank" writing work? Is there a (protocol) description somewhere?

[NBALL]

Please use code example from stsw-stusb004