Protection
205
SPRUH82C – April 2013 – Revised September 2016
Copyright © 2013–2016, Texas Instruments Incorporated
System Configuration (SYSCFG) Module
10.2.2 Kicker Mechanism Protection
NOTE:
The Kick registers are disabled in silicon revision 2 and later. The SYSCFG registers are
always unlocked and writes to the Kick registers have no functional effect.
The Kick registers (KICK0R and KICK1R) can only be accessed in privileged mode (the host
needs to be in Supervisor mode). Any number of accesses may be performed to the
SYSCFG module, while the module is unlocked.
The SYSCFG module remains unlocked after the unlock sequence, until locked again.
Locking the module is accomplished by writing any value other then the key values to either
KICK0R or KICK1R.
To access any registers in the SYSCFG module, it is required to follow a special sequence of writes to the
Kick registers (KICK0R and KICK1R) with correct key values. Writing the correct key value to the kick
registers unlocks the registers in the SYSCFG memory-map. In order to access the SYSCFG registers,
the following unlock sequence needs to be executed in software:
1. Write the key value of 83E7 0B13h to KICK0R.
2. Write the key value of 95A4 F1E0h to KICK1R.
After steps 1 and 2, the SYSCFG module registers are accessible and can be configured as per the
application requirements.
10.3 Master Priority Control
The on-chip peripherals/modules are essentially divided into two broad categories, masters and slaves.
The master peripherals are typically capable of initiating their own read/write data access requests, this
includes the ARM, EDMA3 transfer controllers, and peripherals that do not rely on the CPU or EDMA3 for
initiating the data transfer to/from them. In order to determine allowed connection between masters and
slave, each master request source must have a unique master ID (mstid) associated with it. The master ID
is shown in
. See the device-specific data manual to determine the masters present on your
device.
Each switched central resource (SCR) performs prioritization based on priority level of the master that
sends the read/write requests. For all peripherals/ports classified as masters on the device, the priority is
programmed in the master priority registers (MSTPRI0-3) in the SYSCFG modules. The default priority
levels for each bus master is shown in
. Application software is expected to modify these values
to obtain the desired performance.
Table 10-1. Master IDs
Master ID
Peripheral
0
ARM - Instruction
1
ARM - Data
2-7
Reserved
8
PRU0
9
PRU1
10
EDMA3_0_CC0
11
EDMA3_1_CC0
12-15
Reserved
16
EDMA3_0_TC0 - read
17
EDMA3_0_TC0 - write
18
EDMA3_0_TC1 - read
19
EDMA3_0_TC1 - write
20
EDMA3_1_TC0 – read
21
EDMA3_1_TC0 – write
22-33
Reserved