Part Number: PCA9557 We are using PCA9557 and want to pull up the I/O0/P0 to 1.8V. The device is powered by 3.3V in our board. I want to confirm if there is any limitation on the P0 (which is specifically open drain pin) pull up voltage since the pin…
Part Number: PCA9557 Hello expert, I have question for PCA9557's behavior regarding SMBus communication time out. My customer observed that PCA9557 hasn't happened time out even if adding more than 25ms wait between Reg addr and write data. I think SMBus…
Part Number: PCA9557 Hi dear supporting team,
I heard there is a bug on PCA9557 , and it is revised on TCA9557, may I know what the bug is?
and are these two chips fully pin2pin compatible?
Customer found PCA9557 has very high requirement on POR…
Part Number: PCA9557 Hi dear experts,
Would you please provide PCA9557 Rjt, Rjc and Rjb information to me? Datasheet only lists Rja. Plus, what is the max Junction temp of PCA9557.
Thanks very much for your reply in advance.
BR,
Joyce Li
Part Number: PCA9557 hi dear supporting team,
what's the max junction temp of PCA9557PWR? there is no information in d/s. and from calculation, the max power consumption at 3.6V is only 0.079mW, is this correct?
Part Number: PCA9557 Hi Team
My customer Zhuzhou is using PCA9557 and met some problem for reset function.
I've read the previous discussion for PCA9557 and there're 3 ways to reset the device:
1. keep VCC low longer than 100ms and Power on less…
Bobby, thanks for the reply,
I have some questions:
1. I assume that after the powerup measured in scopeshot above the IC was locked for I2C communication. Is this correct?
2. The IC was holding the SDA line low, thus preventing all communication…
Part Number: PCA9557 Hi dear supporting team,
The dataseet says If ramp conditions are outside timing allowances , POR condition can be missed, causing the device to lock up. If the device locks up, is there a possibility that the SDA signal will stay…
I have a board with one PCA9557 wired for address 1. I can now write a byte to tthe Output register, and get an ACK after each byte sent (0x32 ACK 0x01 ACK 0xFF ACK). I am having a problem with reading a byte from the Input regsister. I send 0x32 ACK…
