SLYY228 November 2024
An eUSB2 repeater must respond to control messages, which are eUSB2 signal patterns that control the repeater state machine after configuration. With the notable exception of CM.RAP, control messages are not used in native mode. They are not meant to be forwarded to the USB 2.0 bus and are meant to be received and interpreted only by an eUSB2 repeater or peripheral.
Register Access Protocol (RAP) is an optional feature introduced in eUSB2 to further simplify implementation. CM.RAP, shown in Table 1, is the control message used to access the RAP interface. It’s common to use the I2C interface for configuration. In lieu of implementing a separate I2C interface, RAP can access the register space of an eUSB2 repeater or peripheral directly through eUSB2. This vendor-defined register space can be modified by issuing the CM.RAP command, along with the operand and target register address. RAP enables system designers to exclude components and general-purpose I/O pins typically required for I2C communication to reduce system cost and footprint.
| Control message name | Description |
|---|---|
| CM.FS | Revert to full-speed terminations |
| CM.L1 | Enter L1 power state |
| CM.L2 | Enter L2 power state |
| CM.Reset | USB 2.0 bus reset |
| CM.Test | Force-enable high-speed terminations |
| CM.RAP | Start of RAP access |
Although it is still a relatively new interface, eUSB2 hosts, devices and repeaters are only expected to grow as modern processor technology nodes continue to shrink below 7nm.