IBIEN=B_0x0, HJEN=B_0x0, CREN=B_0x0, RSTACT=B_0x0, AS=B_0x0
I3C own device characteristics register
| DAVAL | Dynamic address is valid (when the I3C acts as target) |
| DA | 7-bit dynamic address |
| IBIEN | IBI request enable (when the I3C acts as target) 0 (B_0x0): IBI request disabled 1 (B_0x1): IBI request enabled |
| CREN | Controller-role request enable (when the I3C acts as target) 0 (B_0x0): controller-role request disabled 1 (B_0x1): controller-role request enabled |
| HJEN | Hot-join request enable (when the I3C acts as target) 0 (B_0x0): hot-join request disabled 1 (B_0x1): hot-join request enabled |
| AS | Activity state (when the I3C acts as target) 0 (B_0x0): activity state 0 1 (B_0x1): activity state 1 2 (B_0x2): activity state 2 3 (B_0x3): activity state 3 |
| RSTACT | Reset action/level on received reset pattern (when the I3C acts as target) 0 (B_0x0): no reset action 1 (B_0x1): first level of reset: the application software must either: 2 (B_0x2): second level of reset: the application software must issue a warm reset, also known as a system reset. This (see Section 21.3: RCC functional description - Reset) has the same impact as a pin reset (NRST = 0): 3 (B_0x3): no reset action |
| RSTVAL | Reset action is valid (when the I3C acts as target) |