Skip to main content
MIMBE
Associate II
June 4, 2021
Solved

Loading STUSB4500 NVM config into STUSB4500L chip doesn't allow expected PD contracts. I am running on STSW-STUSB002 V1.09. Will upgrade to V1.1.1 allow for proper config of STUSB4500L? Thank you.

  • June 4, 2021
  • 13 replies
  • 3717 views

..

This topic has been closed for replies.
Best answer by Gregory Go.

Hello,

Be careful that there are 2 different versions of the chip:

  • STUSB4500L (Light version) : USB-C controller, 5V only (up to 15W)
  • STUSB4500   (Full version) : USB PD controller, up to 20V/5A (up to 100W)

The STUSB4500L doesn’t support the USB-PD protocol, so you cannot request a voltage higher than 5V, and it doesn’t have any PDOs.

You cannot reprogram the NVM of STUSB4500L to transform it into STUSB4500 (non-L). It doesn’t work as you noticed in your experiment.

If your application needs to accept PD contracts >5V, then you cannot use STUSB4500_L, but you need to use instead the STUSB4500 (non-L).

To bring a little more confusion, be careful that STUSB4500 and STUSB4500L have the same DEVICE_ID = 0x25. But they do not have the same features set.

13 replies

Gregory Go.
Gregory Go.Best answer
Senior III
June 10, 2021

Hello,

Be careful that there are 2 different versions of the chip:

  • STUSB4500L (Light version) : USB-C controller, 5V only (up to 15W)
  • STUSB4500   (Full version) : USB PD controller, up to 20V/5A (up to 100W)

The STUSB4500L doesn’t support the USB-PD protocol, so you cannot request a voltage higher than 5V, and it doesn’t have any PDOs.

You cannot reprogram the NVM of STUSB4500L to transform it into STUSB4500 (non-L). It doesn’t work as you noticed in your experiment.

If your application needs to accept PD contracts >5V, then you cannot use STUSB4500_L, but you need to use instead the STUSB4500 (non-L).

To bring a little more confusion, be careful that STUSB4500 and STUSB4500L have the same DEVICE_ID = 0x25. But they do not have the same features set.

MIMBE
MIMBEAuthor
Associate II
June 11, 2021

Hello Gregory,

Thank you for your answer. I've already been warned of that point by your colleagues.

Best Regards.

Matt