Each R5FSS supports the following features:
- Dual-core Arm Cortex-R5F
- Core revision: r1p3
- Armv7-R profile
- Dual-core and Lockstep mode support
-
- Dual-core mode:
Two independently operating cores (asymmetric multiprocessing,
no coherence)
- Lockstep mode:
One operating core (CORE0) and One lockstep core (CORE1)
- CORE0 uses TCM resources of both cores
- CORE1
caches and interrupts are unused in this mode
- Support for
switching to Dual-core mode from Lockstep mode by application
(Efuse-enabled/MMR configuration feature) - by triggering a CPU
reset. (See device specific datasheet for additional
details.)
- L1 memory system
- 16KB instruction cache per CPU
- 4x4KB
ways
- SECDED
ECC protected per 64 bits
- 16KB data cache per CPU
- 4x4KB
ways
- SECDED
ECC protected per 32 bits
- 64KB
tightly-coupled memory (TCM) per CPU]
-
- SECDED
ECC protected per 32 bits
- Readable/writable from system
- Configurable reset initialization values through the
CTRLMMR
- Split
into A and B banks (with B further splitting into B0 and
B1 interleaved banks)
- 32KB TCMA (ATCM)
- 16KB TCMB0 (B0TCM)
- 16KB TCMB1 (B1TCM)
- In Dual-Core mode, CORE0 and CORE1 each have 64KB of
TCM:
- 32KB TCMA
- 16KB TCMB0 + 16KB TCMB1
- In
Lockstep mode, TCM is 128kB in total for CORE0 of the
specific R5FSS:
- 64KB TCMA
- 32KB TCMB0 + 32KB TCMB1
- Full-precision floating point (VFPv3-D16)
- 16 region memory protection unit (MPU)
- 8 breakpoints
- 8 watchpoints
- Dynamic branch prediction with global history buffer and 4-entry return stack
- CoreSight debug access port (DAP)
- CoreSight embedded trace macrocell (ETM-R5) interface
- Performance monitoring unit (PMU)
- Interfaces
- 64-bit VBUSM initiator pair (1 read, 1 write) for
L2 memory accesses (per core)
- 64-bit VBUSM target (for both read and write) for
TCM access (per core)
- Also allows
access to cache for debug purposes
- 32-bit VBUSP initiator for peripheral access (per
core)
- 4x 32-bit VBUSP target configuration port (2x ECC
Aggregator + 1x CCMR + 1x STC)
- 32-bit VBUSP target debug port
- Allows access to
all R5FSS internal debug logic
- Synchronous clock domain crossing on all interfaces
- CPU and interface clocks run at a 2:1 frequency
ratio or 1:1 frequency ratio. Refer to the Operating Performance Points
section of the device datasheet for details on what is supported for
each device.
- Integrated vectored interrupt manager (VIM)
- 256 interrupts per core
- Only interrupts connected to R5F CORE0 are
available in Lockstep mode
- Each interrupt programmable as either IRQ or FIQ
- Each interrupt has a programmable enable mask
- Each interrupt has a programmable 4-bit priority
- Priority interrupt supported
- Vectored interrupt interface
- Compatible with R5F VIC port
- Programmable 32-bit vector address per interrupt
- Address is SECDED error protected
- Default vector addresses provided on DED
- Dual-Core or Lockstep capable
- Software interrupt generation
- Integrated ECC aggregators
- Support for error injection to all supported ECC memory blocks to test ECC functionality (add-on function from TI)
- One ECC aggregator per core to cover all RAMs and caches associated with that core
- Standard Arm CoreSight debug and trace
architecture at the R5FSS level
- Cross triggering:
Supported by cross trigger interface (CTI) (per CORE) and cross trigger
matrix (CTM) components
- Processor trace:
Supported by embedded trace macrocell (ETM) (per CORE) and advanced
trace bus (ATB) funnel components
See R5FSS Functional
Description for a functional block diagram and additional details related
to the R5FSS.