AM62X Host Descriptions¶
Introduction¶
This chapter provides information on the set of HostIDs permitted in this AM62X SoC. HostIDs uniquely identify each logically distinct high level software entity. A software entity identification number (HostID) can be assigned to an OS either native or virtualized, or a firmware/native application. The HostID is used to select the set of Secure Proxy channels for which this software entity should use to communicate with the System Firmware.
System Firmware also checks that the used HostID comes from software running on the correct core (as implied by Host Name in the below table) and with the correct security level (Security Status column) to prevent HostID spoofing.
Enumeration of Host IDs¶
| Host ID | Host Name | Security Status | Description |
|---|---|---|---|
| 0 | TIFS | Secure | Device Management and Security Control |
| 10 | A53_0 | Secure | Cortex a53 context 0 on Main island |
| 11 | A53_1 | Secure | Cortex A53 context 1 on Main island |
| 12 | A53_2 | Non Secure | Cortex A53 context 2 on Main island |
| 13 | A53_3 | Non Secure | Cortex A53 context 3 on Main island |
| 14 | A53_4 | Non Secure | Cortex A53 context 1 on Main island |
| 30 | M4_0 | Non Secure | M4 |
| 31 | GPU | Non Secure | GPU context 0 on Main island |
| 35 | MAIN_0_R5_0 | Secure | Cortex R5_0 context 0 on Main island(BOOT) |
| 36 | MAIN_0_R5_1 | Non Secure | Cortex R5_0 context 1 on Main island |
| 37 | MAIN_0_R5_2 | Secure | Cortex R5_0 context 2 on Main island |
| 38 | MAIN_0_R5_3 | Non Secure | Cortex R5_0 context 3 on Main island |
| 250 | DM2TIFS | Secure | DM to TIFS communication |
| 251 | TIFS2DM | Non Secure | TIFS to DM communication |
| 253 | HSM | Secure | HSM Controller |
| 254 | DM | Non Secure | Device Management |
Note
- Description provides an intended purpose of the host ID, though on some systems, this might be used differently, backing memory and link allocations are made with the specified purpose in mind
- Security Status provides an intended purpose for the Host context