SPRUJF2A March 2026 – March 2026 AM13E23019
Table 22-11 lists the memory-mapped registers for the SPGSS_REGS registers. All register offset addresses not listed in Table 22-11 should be considered as reserved locations and the register contents should not be modified.
| Offset | Acronym | Register Name | Section |
|---|---|---|---|
| 120h | LPBK0 | Loopback across multiple UNICOMM instances. User has to ensure that the UNICOMMs looped back are contained in the same SPG and have the same underlying IP instantiated (i.e. both UART, both SPI, both I2C, etc.) | Go |
| 1C0h | PAIR0 | Pairing of UNICOMM I2C-configured instances for Multi-Master/SMBUS applications. User has to ensure that the UNICOMMs looped back are contained in the same SPG and are both in I2C modes. | Go |
Complex bit access types are encoded to fit into small table cells. Table 22-12 shows the codes that are used for access types in this section.
| Access Type | Code | Description |
|---|---|---|
| Read Type | ||
| R | R | Read |
| Write Type | ||
| W | W | Write |
| Reset or Default Value | ||
| -n | Value after reset or the default value | |
LPBK0 is shown in Figure 22-9 and described in Table 22-13.
Return to the Summary Table.
Loopback across multiple UNICOMM instances. User has to ensure that the UNICOMMs looped back are contained in the same SPG and have the same underlying IP instantiated (i.e. both UART, both SPI, both I2C, etc.)
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R/W-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| PERIPHERAL | CONTROLLER | RESERVED | EN | ||||||||||||
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | ||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | RESERVED | R/W | 0h | |
| 15-12 | PERIPHERAL | R/W | 0h | UNICOMM instance selected for loopback. The selected instance will be treated as the LPBK0 peripheral.
0h = UNICOMM0_3 : Select UNICOMM0(SPG0) or UNICOMM3(SPG1). 1h = UNICOMM1_4 : Select UNICOMM1(SPG0) or UNICOMM4(SPG1). 2h = UNICOMM2_5 : Select UNICOMM2(SPG0) or UNICOMM5(SPG1). |
| 11-8 | CONTROLLER | R/W | 0h | UNICOMM instance selected for loopback. The selected instance will be treated as the LPBK0 controller.
0h = UNICOMM0_3 : Select UNICOMM0(SPG0) or UNICOMM3(SPG1). 1h = UNICOMM1_4 : Select UNICOMM1(SPG0) or UNICOMM4(SPG1). 2h = UNICOMM2_5 : Select UNICOMM2(SPG0) or UNICOMM5(SPG1). |
| 7-1 | RESERVED | R/W | 0h | |
| 0 | EN | R/W | 0h | Loopback enable
0h = Disable 1h = Enable |
PAIR0 is shown in Figure 22-10 and described in Table 22-14.
Return to the Summary Table.
Pairing of UNICOMM I2C-configured instances for Multi-Master/SMBUS applications. User has to ensure that the UNICOMMs looped back are contained in the same SPG and are both in I2C modes.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| RESERVED | |||||||||||||||
| R/W-0h | |||||||||||||||
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| TARGET | CTL | RESERVED | EN | ||||||||||||
| R/W-0h | R/W-0h | R/W-0h | R/W-0h | ||||||||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 31-16 | RESERVED | R/W | 0h | |
| 15-12 | TARGET | R/W | 0h | UNICOMM instance selected for I2C pairing. The selected instance will be treated as the I2C PAIR0 target.
0h = UNICOMM0_3 : Select UNICOMM0(SPG0) or UNICOMM3(SPG1). 1h = UNICOMM1_4 : Select UNICOMM1(SPG0) or UNICOMM4(SPG1). 2h = UNICOMM2_5 : Select UNICOMM2(SPG0) or UNICOMM5(SPG1). |
| 11-8 | CTL | R/W | 0h | UNICOMM instance selected for I2C pairing. The selected instance will be treated as the I2C PAIR0 controller.
0h = UNICOMM0_3 : Select UNICOMM0(SPG0) or UNICOMM3(SPG1). 1h = UNICOMM1_4 : Select UNICOMM1(SPG0) or UNICOMM4(SPG1). 2h = UNICOMM2_5 : Select UNICOMM2(SPG0) or UNICOMM5(SPG1). |
| 7-1 | RESERVED | R/W | 0h | |
| 0 | EN | R/W | 0h | Enable
0h = Disable 1h = Enable |