When configuring the I2C peripheral in target mode with multiple own addresses (e.g., OA0, OA1), the hardware only responds to the first address (OA0). Transactions to additional addresses (OA1, OA2, OA3) are ignored, and the target does not acknowledge or respond to them.

Configure multiple own addresses in the I2C_HwAttrs for the target instance (e.g., ownTargetAddr[0]=0x10, ownTargetAddr[1]=0x20).
Open the I2C instance in target mode.
From a controller (master), send a transaction to the first address (OA0, e.g., 0x10):
The target responds as expected.
Send a transaction to the second address (OA1, e.g., 0x20):
The target does not respond (no ACK, no data exchange).
Observe that only OA0 is functional; all other addresses are ignored.