Hi, I’m looking into whether we can use the MPQ5031 in our new design. We will connect up to 4 MPQ5031s in slave mode on the same I2C bus. The problem I see is that they all come with the same I2C address, and the only way to change the address is by I2C!! (Am I missing something, or did someone not think this through?)
I was thinking, “Ok, I’ll just pull the RESET/ENABLE on the others,” but there is no RESET nor ENABLE pin.
How am I supposed to give them a new address if they all listen on the same I2C address? Normally, one or two I2C address bits are configured through hardware to avoid this scenario.
I must be missing something. How is this supposed to be done? This chip seems perfect for our product, but if we can’t solve this simple issue, it’s useless to us.
Hi and thank you for the answer.
We have no test setup, I’m in the stage of collecting candidates based on their data sheets and user manuals.
However our requirements are 4 USB-PD ports with configurable PDO:s over I2C or SPI. We want a simple API (register map), no FW loading as so many other chip has.
The USB-PD chips will be on the same I2C bus and mounted at the same time in production. To have different versions (order number) on for the same part, just to get different I2C addresses is a logistic nightmare. If you only had a chip select pin or a reset pin, this wouldn’t bee a problem and you wouldn’t need to have a range of suffix for the some chip. Win-Win for everyone.
If this is the only way, and you don’t have anything else that can do the same with our requirement in mind, I will have to remove you as a candidate.