INFORMATION ADVANCE

TMS320TCI6618

Communications Infrastructure KeyStone SoC

5.2 Memory Protection

Memory protection allows an operating system to define who or what is authorized to access L1D, L1P, and L2 memory. To accomplish this, the L1D, L1P, and L2 memories are divided into pages. There are 16 pages of L1P (2KB each), 16 pages of L1D (2KB each), and 32 pages of L2 (32KB each). The L1D, L1P, and L2 memory controllers in the C66x CorePac are equipped with a set of registers that specify the permissions for each memory page.

Each page may be assigned with fully orthogonal user and supervisor read, write, and execute permissions. In addition, a page may be marked as either (or both) locally accessible or globally accessible. A local access is a direct DSP access to L1D, L1P, and L2, while a global access is initiated by a DMA (either IDMA or the EDMA3) or by other system masters. Note that EDMA or IDMA transfers programmed by the DSP count as global accesses. On a secure device, pages can be restricted to secure access only (default) or opened up for public, non-secure access.

The DSP and each of the system masters on the device are all assigned a privilege ID. It is only possible to specify whether memory pages are locally or globally accessible.

The AIDx and LOCAL bits of the memory protection page attribute registers specify the memory page protection scheme, see Table 5-1.

Faults are handled by software in an interrupt (or an exception, programmable within the CorePac interrupt controller) service routine. A DSP or DMA access to a page without the proper permissions will:

•Block the access — reads return 0, writes are ignored

•Capture the initiator in a status register — ID, address, and access type are stored

•Signal event to DSP interrupt controller

The software is responsible for taking corrective action to respond to the event and resetting the error status in the memory controller. For more information on memory protection for L1D, L1P, and L2, see the C66x CorePac User Guide in ‘‘Related Documentation from Texas Instruments’’ on page 59.

TMS320TCI6618

Communications Infrastructure KeyStone SoC

5.3 Bandwidth Management

When multiple requestors contend for a single C66x CorePac resource, the conflict is resolved by granting access to the highest priority requestor. The following four resources are managed by the Bandwidth Management control hardware:

•Level 1 Program (L1P) SRAM/Cache

•Level 1 Data (L1D) SRAM/Cache

•Level 2 (L2) SRAM/Cache

•Memory-mapped registers configuration bus

The priority level for operations initiated within the C66x CorePac are declared through registers in the CorePac. These operations are:

•DSP-initiated transfers

•User-programmed cache coherency operations

•IDMA-initiated transfers

The priority level for operations initiated outside the CorePac by system peripherals is declared through the Priority Allocation Register (PRI_ALLOC), see Section 4.4 ‘‘Bus Priorities’’ on page 80. System peripherals with no fields in PRI_ALLOC have their own registers to program their priorities.

More information on the bandwidth management features of the CorePac can be found in the C66x CorePac Reference Guide (literature number SPRUGW0.)

5.4 Power-Down Control

The C66x CorePac supports the ability to power-down various parts of the CorePac. The power-down controller (PDC) of the CorePac can be used to power down L1P, the cache control hardware, the DSP, and the entire CorePac. These power-down features can be used to design systems for lower overall system power requirements.

Note—The TCI6618 does not support power-down modes for the L2 memory at this time.

More information on the power-down features of the C66x CorePac can be found in the C66x CorePac Reference Guide (literature number SPRUGW0).

5.5 CorePac Resets

Table 5-2 shows the reset types supported on the TCI6618 device and how they affect the resetting of the CorePac, either both globally or just locally.

Table 5-2 CorePac Reset (Global or Local)

For more detailed information on the global and local CorePac resets, see the C66x CorePac User Guide in ‘‘Related Documentation from Texas Instruments’’ on page 59. And for more detailed information on device resets, see Section 7.7 ‘‘Reset Controller’’ on page 149.

ADVANCE INFORMATION

INFORMATION ADVANCE

TMS320TCI6618

Communications Infrastructure KeyStone SoC

5.6 CorePac Revision

The version and revision of the C66x CorePac can be read from the CorePac Revision ID Register (MM_REVID) located at address 0181 2000h. The MM_REVID register is shown in Table 5-3 and described in Table 5-3. The C66x CorePac revision is dependant on the silicon revision being used.

Figure 5-5 Packed DMA Priority Allocation Register (PKTDMA_PRI_ALLOC)

5.7 C66x CorePac Register Descriptions

See the C66x CorePac User Guide in ‘‘Related Documentation from Texas Instruments’’ on page 59 for register offsets and definitions.