2025-09-29 12:00 AM
Using a STUSB4500. I am attempting to request 9V @1A from a USBC wall wart. The wall wart is capable of delivering 9V @3A.
If the device cold boots,(remove all power from the system) the request is a success and stays fixed at 9V.
If I remove the USBC connector and plug it back in it will not go back to 9V, It sticks to 5V. It will not go back to 9V unless I remove power and cold boot again.
Here is the I2C traffic to the device:
write to 0x2B ack data: 0x2F
read to 0x2B ack data: 0x25
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x4B 0x00 0x00 0x00
write to 0x2B ack data: 0x89 0x4B 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x4B 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x8D
read to 0x2B ack data: 0x00 0x01 0x00 0x00
write to 0x2B ack data: 0x8D 0x00 0xD1 0x02 0x00
write to 0x2B ack data: 0x8D
read to 0x2B ack data: 0x00 0xD1 0x02 0x00
write to 0x2B ack data: 0x8D 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x70 0x03
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x70 0x02
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x51 0x0D
write to 0x2B ack data: 0x1A 0x26
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x70 0x02
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x51 0x0D
write to 0x2B ack data: 0x1A 0x26
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x70 0x02
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x51 0x0D
write to 0x2B ack data: 0x1A 0x26
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x70 0x02
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89
read to 0x2B ack data: 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x89 0x64 0xD0 0x02 0x00
write to 0x2B ack data: 0x51 0x0D
write to 0x2B ack data: 0x1A 0x26
Attached is the schematic for the design.
The power supply is a official R-Pi4 USBC adapter.
Any hints why this is the case?