Functional Overview
www.ti.com
42
SWRU543–January 2019
Submit Documentation Feedback
Copyright © 2019, Texas Instruments Incorporated
Architecture Overview
1.3 Functional Overview
The following sections provide an overview of the main components of the CC32xx system on chip (SoC)
from a microcontroller point of view.
1.3.1 Processor Core
1.3.1.1 Arm
®
Cortex
®
-M4 Processor Core
The CC32xx application MCU subsystem is built around an Arm
®
Cortex
®
-M4 processor core, which
provides outstanding computational performance and exceptional system response to interrupts at low
power consumption, while optimizing memory footprint—making the MCU subsystem an ideal fit for
embedded applications.
Key features of an Arm
®
Cortex
®
-M4 processor core are:
• Thumb
®
-2 mixed 16-bit and 32-bit instruction set delivers the high performance expected of a 32-bit
Arm
®
core in a compact memory size – enabling richer applications within a given device memory size.
• Single-cycle multiply instruction and hardware divide
• Atomic bit manipulation (bit-banding), delivering maximum memory use and streamlined peripheral
control
• Unaligned data access, enabling data to be efficiently packed into memory
• Hardware division and fast multiplier
• Deterministic, high-performance interrupt handling for time-critical applications
• Configurable 4-pin JTAG and 2-pin (SWJ-DP) debug access
• Ultra-low-power sleep modes
• Low active power consumption
• 80-MHz operation
1.3.1.2 System Timer (SysTick)
The Arm
®
Cortex
®
-M4 processor core includes an integrated system timer, SysTick. SysTick provides a
simple, 24-bit, clear-on-write, decrementing, wrap-on-zero counter with a flexible control mechanism. The
counter is clocked on the system clock.
SysTick makes OS porting between Cortex
®
-M4 devices much easier because there is no need to change
the OS system timer code. The SysTick timer integrates with the NVIC and can generate a SysTick
exception (exception type 15). In many OSs, a hardware timer generates interrupts so that the OS can
perform task management (for example, to allow multiple tasks to run at different time slots and to ensure
that no single task can lock up the entire system). To perform this function, the timer must be able to
generate interrupts and, if possible, be protected from user tasks so that user applications cannot change
the timer behavior.
The counter can be used in several different ways:
• An RTOS tick timer that fires at a programmable rate (for example, 100 Hz) and invokes a SysTick
routine
• A high-speed alarm timer using the system clock
• A simple counter used to measure time to completion and time used
• An internal clock-source control based on missing or meeting durations
To Next Page
Loading...
