Hi Kevin We don't use the General Call command. The master always ask a command of 64 bytes data from PSU#1. The 0x00 data are piece of the 64 bytes. An unexpected signal happen on the PUS#2 to cause a Start Bit and then PSU#2 see the 0x00 data on the I2C bus. 1. 0x00 data are piece of PSU#1(address 0x40) send to Master. 2. The unexpected signal to cause the Start bit on PSU#2(address 0x41) Actually, we have a hotswap IC(PCA9512A) after the PSU. Then the I2C parallel together after the hotswap IC. We notice the unexpected signal(caused the start bit) seems to be pulled up by the hotswap IC on the PSU#2(before it, it's a small glitch). From the Waveform the PSU#1 does not see this signal, but it appear on the PSU#2. By the way, we only expected the master communicate with PSU#1. At the same time of PSU#1 send 64 byte data back to master, PSU#2 see the General Call and then it response to I2C BUS. This cause the I2C bus to be confused. . Because the master only communicate with PSU#1. We don't want PSU#2 to response to General Call command which caused by (Hotswap IC unexpected behavior Do you advise any firmware solutions that PSU#2 will not affect the I2C bus(Master is communicating with PSU#1)?
↧