If any strapping pins for separating two static slave address to avoid conflict in the beginning. or do you mean there won't be a problem if I3C mater can assigns the slave dynamic address for these two RT595 that can skip this issue?
The very first task an I3C master has to accomplish when setting up the network is to allocate dynamic addresses to the slaves in the network. To do so, the master must be able to uniquely identify each and every slave present trhough the static address of the device, the static address is what we call the "I2C address".
If connect to two RT595s(as devices) with our Master, will there be a conflict and STOP communication due to the same static address in beginning, or it will switch to dynamic address automatically for further communication?
There could be an issue so you need to assign different static address to the RT500 slave devices. The dynamic address is given by the master so it is neede the communication of both.
Yes, RT500 supports I3C as slave role. The I3C slave has an static address which is set in the mcu registers and it is used to communicate with I2C. It is only after the I3C master assigns the slave a dynamic address that this I3C-capable slave device can benefit from improvements that the I3C interface introduces.
