TM4C123 Architecture and Digital I/O ā
Learning Objectives ā
After completing this experiment, you will be able to:
- Identify the main components and subsystems of the TM4C123 microcontroller and understand their roles within an embedded system.
- Recognize the organization of the ARM Cortex-M4 core, memory map, and peripheral buses.
- Understand the role of core peripherals including NVIC, SysTick, and System Control Block (SCB).
- Configure and control digital output pins using the General-Purpose Input/Output (GPIO) module.
- Write Assembly programs to drive on-board LEDs through direct register access.
- Relate register operations to physical hardware behavior and verify functionality through observation on the LaunchPad board.
Experiment Overview ā
This experiment introduces the architecture of the TM4C123 microcontroller and its most fundamental feature ā the ability to interface with the outside world through digital I/O pins.
You will first explore the internal structure of the device, including the ARM Cortex-M4 core, core peripherals (NVIC, SysTick, SCB), buses, memory regions, and peripheral interconnect. Then, you will apply this understanding by writing Assembly programs that toggle the on-board LEDs connected to PORTF.
In this experiment, you will:
- Understand how peripheral registers are mapped into memory and accessed by the CPU.
- Learn about Cortex-M4 core peripherals and their functions.
- Learn the initialization sequence required to enable and configure GPIO ports.
- Develop Assembly programs that control LEDs using software delays.
- Form the foundation for subsequent experiments involving interrupts, timers, and analog peripherals.
By the end of this lab, you will understand the TM4C123 architecture, Cortex-M4 core peripherals, be able to configure GPIO ports for digital output, and control external hardware through register manipulation in Assembly.
Theoretical Background ā
TM4C123 Microcontroller Architecture ā
The TM4C123GH6PM microcontroller is built around the ARM Cortex-M4F processor core, implementing the ARMv7-M architecture. It integrates the CPU core, memory, peripherals, and I/O interfaces on a single chip ā a complete system-on-chip (SoC) solution for embedded applications.
Core Components ā
The TM4C123 contains the following major components:
- ARM Cortex-M4F Processor Core: 32-bit RISC processor with hardware Floating-Point Unit (FPU)
- Memory: 256 KB Flash, 32 KB SRAM, 2 KB EEPROM
- System Buses: Advanced High-Performance Bus (AHB) and Advanced Peripheral Bus (APB)
- Core Peripherals: NVIC, SysTick Timer, Memory Protection Unit (MPU), System Control Block (SCB)
- General-Purpose Timers: Six 16/32-bit and six 32/64-bit timers
- Communication Interfaces: UART, I²C, SSI (SPI), CAN
- Analog Peripherals: 12-bit ADC with 12 channels, analog comparators
- GPIO Ports: Six ports (A-F) with up to 43 programmable pins
ARM Cortex-M4 Core Peripherals ā
The ARM Cortex-M4 processor includes several core peripherals that are common across all Cortex-M4-based microcontrollers. They are tightly integrated with the CPU and provide essential system functions such as interrupt handling and timing.
Nested Vectored Interrupt Controller (NVIC) ā
The NVIC manages all interrupt and exception handling. It supports up to 240 interrupt sources (138 on the TM4C123), hardware priority levels, and automatic context saving for efficient servicing. Key features include nesting, tail-chaining, and late-arrival handling for minimal interrupt latency.
Important NVIC registers (base address 0xE000E100):
NVIC_ENxā Set-EnableNVIC_DISxā Clear-EnableNVIC_PRIxā Priority ConfigurationNVIC_ACTIVExā Active Status
SysTick Timer ā
The SysTick timer is a simple 24-bit down-counter integrated in the core. It provides a consistent time base for system delays or periodic tasks. Many operating systems use it for time-keeping or scheduling.
SysTick registers (base address 0xE000E010):
STCTRLā Control and StatusSTRELOADā Reload ValueSTCURRENTā Current Counter Value
Other core peripherals such as the System Control Block (SCB) are present but not covered in this course.
Memory Map ā
The Cortex-M4 processor uses a unified 4 GB address space for all code, data, and peripherals. Every peripheral and memory region occupies a unique address range, allowing direct access through normal load and store instructions.
| Region | Address Range | Description |
|---|---|---|
| Flash Memory | 0x00000000 - 0x0003FFFF | Program storage (256 KB) |
| SRAM | 0x20000000 - 0x20007FFF | On-chip data memory (32 KB) |
| Peripherals | 0x40000000 - 0x400FFFFF | Peripheral registers |
| GPIO Ports | 0x40004000 - 0x40025FFF | GPIO A-F registers |
| Core Peripherals | 0xE0000000 - 0xE00FFFFF | NVIC, SysTick, SCB, etc. |
Each peripheral's registers are memory-mapped, meaning they are accessed just like variables in memory. For example, writing to address 0x400253FC directly updates the GPIO Port F data register.
General-Purpose Input/Output (GPIO) ā
GPIO (General-Purpose Input/Output) ports form the primary interface between the microcontroller and external devices such as LEDs, switches, and sensors. Each pin can be configured as either an input or an output.
When a pin is an output, software drives it high or low to control external hardware (e.g., turn an LED on/off). When a pin is an input, software reads its logic level (e.g., a button press).
GPIO Ports Overview ā
The TM4C123GH6PM provides six GPIO ports (A-F), each with up to eight programmable pins. Not all pins are available on the LaunchPad, and some are reserved for debugging or special functions.
| Port | Pins Available | Notes |
|---|---|---|
| Port A | PA0-PA7 | UART0 (PA0, PA1) shared with USB debug interface |
| Port B | PB0-PB7 | I²C0, SSI2, ADC channels |
| Port C | PC0-PC7 | PC0-PC3 used for JTAG (avoid modification) |
| Port D | PD0-PD7 | PD7 requires unlock for GPIO use |
| Port E | PE0-PE5 | ADC and UART5 functionality available |
| Port F | PF0-PF4 | On-board LEDs (PF1-PF3) and switches (PF0, PF4) |
Each port exposes its own control and data registers, allowing independent configuration and operation.
Memory-Mapped GPIO Registers ā
GPIO modules are accessed via memory-mapped registers: fixed addresses that the CPU reads/writes with standard LDR/STR instructions.
Every port has a base address; key registers sit at fixed offsets from that base.
| Port | Base Address |
|---|---|
| Port A | 0x40004000 |
| Port B | 0x40005000 |
| Port C | 0x40006000 |
| Port D | 0x40007000 |
| Port E | 0x40024000 |
| Port F | 0x40025000 |
In this experiment we use Port F, so:
GPIODIR=0x40025400GPIODEN=0x4002551CGPIODATA=0x400253FC
Address Masking in GPIODATA ā
The GPIODATA register supports address masking: address bits [9:2] form a bit mask that selects which pins are affected.
- Full access: Base +
0x3FCā all 8 pins. - Masked access: Base + (
mask<< 2) ā only the pins inmask.
Example (PF1 only):
0x40025000 + (0x02 << 2) = 0x40025008This is address masking (often confused with "bit-banding"); it enables fast, selective reads/writes to individual pins.
Protected and Special-Function Pins ā
Some pins are locked or reserved at reset due to critical roles:
- PF0 doubles as the Non-Maskable Interrupt (NMI) input and is locked. To use it as GPIO, write
0x4C4F434BtoGPIO_LOCKand set the desired bits inGPIO_CR. - PC0-PC3 carry the JTAG debug interface and should not be reassigned in normal operation.
Always confirm pin availability in the datasheet before repurposing special-function pins.
Port F on the LaunchPad ā
Port F connects to the on-board RGB LEDs and user push buttons:
| Pin | Function | Connected Component | Active Level |
|---|---|---|---|
| PF1 | Output | Red LED | Active High |
| PF2 | Output | Blue LED | Active High |
| PF3 | Output | Green LED | Active High |
| PF0 | Input (locked) | SW2 (Push Button) | Active Low (enable pull-up) |
| PF4 | Input | SW1 (Push Button) | Active Low (enable pull-up) |
LEDs are active-high (write 1 to turn on). Push buttons pull to ground when pressed, so inputs read 0 when pressed and require internal pull-ups.
GPIO Configuration Workflow ā
In practice, GPIO usage has two phases:
- Initialization (setup, runs once): enable the port clock, unlock protected pins (if needed), set direction, and enable digital function.
- Runtime (operation, repeats): read inputs or write outputs by accessing
GPIODATAin the main loop or in interrupt service routines (ISRs).
A typical structure is:
; Initialization phase
BL InitGPIO ; RCGCGPIO, optional LOCK/CR, DIR, DEN
; Runtime phase
loop
; Read buttons (inputs) and/or drive LEDs (outputs)
; Optionally, some I/O is handled inside ISRs
B loopThe detailed register-level steps (clock enable, unlock, direction, digital enable, and data access) are demonstrated in the following subsections.
Step 1 ā Enable the GPIO Port Clock ā
Register: RCGCGPIO ā Run Mode Clock Gating Control for GPIO (0x400FE608)
Before accessing any GPIO port, its clock must be enabled. The RCGCGPIO register controls the clock to all GPIO modules. Each bit corresponds to a single port (A-F). Writing a '1' to a bit enables the clock to that port, while '0' disables it.
RCGCGPIO Register Layout:
| Bit 31-6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 |
|---|---|---|---|---|---|---|
| Reserved | PF | PE | PD | PC | PB | PA |
To activate Port F, bit 5 must be set to 1 as shown below.
LDR R1, =0x400FE608 ; RCGCGPIO register
LDR R0, [R1]
ORR R0, R0, #0x20 ; Set bit 5 (Port F)
STR R0, [R1]Once the clock is enabled, a short delay or status polling ensures the peripheral is ready before further configuration.
Step 2 ā Unlock Protected Pins ā
Registers: GPIO_LOCK (0x40025520), GPIO_CR (0x40025524)
Certain pins such as PF0 are protected because they share critical alternate functions (e.g., the NMI input). To modify these pins, the port must be unlocked by writing the key value 0x4C4F434B ("LOCK") into the GPIO_LOCK register. The GPIO_CR register (Commit Register) then determines which pins can be altered.
GPIO_CR Register Layout:
| Bit 31-8 | Bit 7-0 |
|---|---|
| Reserved | Commit Mask |
The following code unlocks Port F and enables modification of all pins.
LDR R1, =0x40025520 ; GPIO_LOCK
LDR R0, =0x4C4F434B ; Unlock key
STR R0, [R1]
LDR R1, =0x40025524 ; GPIO_CR
MOV R0, #0xFF ; Allow changes to all pins
STR R0, [R1]In this experiment, PF0 is not used, so unlocking is optional. After unlocking, configuration registers such as direction and digital enable can be safely modified.
Step 3 ā Configure Pin Direction ā
Register: GPIODIR (0x40025400) ā GPIO Direction Control (Port F)
The GPIODIR register determines whether each GPIO pin functions as an input or an output. Writing '0' configures the pin as an input, while '1' configures it as an output.
GPIODIR Register Layout (Port F):
| Bit 31-8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 |
|---|---|---|---|---|---|---|---|---|
| Reserved | PF7 | PF6 | PF5 | PF4 | PF3 | PF2 | PF1 | PF0 |
For the on-board RGB LED, PF1-PF3 must be configured as outputs. Bits 1-3 are therefore set to '1'.
LDR R1, =0x40025400 ; GPIODIR register (Port F)
LDR R0, [R1]
ORR R0, R0, #0x0E ; Set PF1, PF2, PF3 as outputs
STR R0, [R1]Unmodified bits remain unchanged, allowing input pins (such as PF0 or PF4) to retain their default configuration.
Step 4 ā Enable Digital Functionality ā
Register: GPIODEN (0x4002551C) ā Digital Enable Register (Port F)
Each GPIO pin can serve analog or digital functions. The GPIODEN register enables the digital circuitry for selected pins. Pins configured as digital inputs or outputs must have their corresponding bits set to '1'.
GPIODEN Register Layout (Port F):
| Bit 31-8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 |
|---|---|---|---|---|---|---|---|---|
| Reserved | PF7 | PF6 | PF5 | PF4 | PF3 | PF2 | PF1 | PF0 |
Bits 1-3 are set to enable PF1-PF3 as digital outputs for the LED.
LDR R1, =0x4002551C ; GPIODEN register (Port F)
LDR R0, [R1]
ORR R0, R0, #0x0E ; Enable PF1-PF3 as digital pins
STR R0, [R1]Failing to enable GPIODEN leaves the pins electrically inactive even if their direction is set.
Step 5 ā Write to the Data Register ā
Register: GPIODATA (0x400253FC) ā Data Input/Output Register (Port F)
The GPIODATA register reflects the current logic levels on all GPIO pins. Writing to a bit drives the corresponding output high ('1') or low ('0'). Bits 1-3 correspond to the RGB LED pins on the LaunchPad: PF1 = Red, PF2 = Blue, PF3 = Green.
GPIODATA Register Layout (Port F):
| Bit 31-8 | Bit 7 | Bit 6 | Bit 5 | Bit 4 | Bit 3 | Bit 2 | Bit 1 | Bit 0 |
|---|---|---|---|---|---|---|---|---|
| Reserved | PF7 | PF6 | PF5 | PF4 | PF3 | PF2 | PF1 | PF0 |
The example below drives PF1 (Red) and PF3 (Green) simultaneously to produce a yellow color.
LDR R1, =0x400253FC ; GPIODATA register (Port F)
MOV R0, #0x0A ; Set PF1 (Red) and PF3 (Green) = Yellow
STR R0, [R1]By writing different bit combinations, various LED colors can be generated:
| Color | Red (PF1) | Blue (PF2) | Green (PF3) | Hex | Combination |
|---|---|---|---|---|---|
| Red | š“ | ā« | ā« | 0x02 | Red only |
| Blue | ā« | šµ | ā« | 0x04 | Blue only |
| Green | ā« | ā« | š¢ | 0x08 | Green only |
| Yellow | š“ | ā« | š¢ | 0x0A | Red + Green |
| Cyan | ā« | šµ | š¢ | 0x0C | Blue + Green |
| Magenta | š“ | šµ | ā« | 0x06 | Red + Blue |
| White | š“ | šµ | š¢ | 0x0E | All on |
Procedure ā
Examples ā
The following examples illustrate the complete process of initializing Port F and controlling the on-board LEDs using Assembly language.
Example 1 ā Simple LED Blink ā
This example initializes Port F and toggles the Red LED (PF1) on and off using address masking with a software delay.
Address Masking for PF1:
0x40025000 + (0x02 << 2) = 0x40025008 AREA RESET, CODE, READONLY ; Code section
THUMB ; Use Thumb instruction set
EXPORT __main ; Export symbol
__main PROC
LDR R1, =0x400FE608 ; RCGCGPIO address
LDR R0, [R1] ; Read current value
ORR R0, R0, #0x20 ; Enable Port F clock
STR R0, [R1] ; Write back
NOP ; Small delay
NOP
LDR R1, =0x40025400 ; GPIODIR address
LDR R0, [R1] ; Read current value
ORR R0, R0, #0x02 ; Set PF1 as output
STR R0, [R1] ; Write back
LDR R1, =0x4002551C ; GPIODEN address
LDR R0, [R1] ; Read current value
ORR R0, R0, #0x02 ; Enable digital function for PF1
STR R0, [R1] ; Write back
loop LDR R1, =0x40025008 ; Masked DATA address for PF1
MOV R0, #0x02 ; Turn ON red LED (PF1)
STR R0, [R1] ; Write to GPIODATA
LDR R0, =1000000 ; Load delay count
BL DELAY ; Call delay
MOV R0, #0x00 ; Turn OFF red LED (PF1)
STR R0, [R1] ; Write to GPIODATA
LDR R0, =1000000 ; Load delay count
BL DELAY ; Call delay
B loop ; Repeat
ENDP
DELAY PROC
SUBS R0, R0, #1 ; Decrement counter
BNE DELAY ; Loop until zero
BX LR ; Return
ENDP
ENDExample 2 ā Cycle Through RGB Colors ā
This example extends the previous one by cycling through RGB LED colors (Red, Green, Blue) using a software delay.
Address Masking for PF1, PF2, PF3:
0x40025000 + ((0x02 | 0x04 | 0x08) << 2) = 0x40025038 AREA RESET, CODE, READONLY ; Code section
THUMB ; Use Thumb instruction set
EXPORT __main ; Export symbol
__main PROC
BL PF_Init ; Initialize Port F
loop
LDR R1, =0x40025038 ; Masked DATA address for PF1-PF3
MOV R0, #0x02 ; Turn ON red LED (PF1)
STR R0, [R1] ; Write to GPIODATA
LDR R0, =10000000 ; Load delay count
BL DELAY ; Call delay
MOV R0, #0x04 ; Turn ON blue LED (PF2)
STR R0, [R1]
LDR R0, =10000000
BL DELAY
MOV R0, #0x08 ; Turn ON green LED (PF3)
STR R0, [R1]
LDR R0, =10000000
BL DELAY
B loop ; Repeat
ENDP
DELAY PROC
SUBS R0, R0, #1 ; Decrement counter
BNE DELAY ; Loop until zero
BX LR ; Return
ENDP
PF_Init PROC
LDR R1, =0x400FE608 ; RCGCGPIO address
LDR R0, [R1] ; Read current value
ORR R0, R0, #0x20 ; Enable Port F clock
STR R0, [R1]
NOP ; Small delay
NOP
LDR R1, =0x40025400 ; GPIODIR address
LDR R0, [R1]
ORR R0, R0, #0x0E ; Set PF1-PF3 as outputs
STR R0, [R1]
LDR R1, =0x4002551C ; GPIODEN address
LDR R0, [R1]
ORR R0, R0, #0x0E ; Enable digital function for PF1-PF3
STR R0, [R1]
BX LR ; Return
ENDP
ENDTasks ā
Task 1 ā Adjust the Blink Rate ā
Modify the delay routine in Example 1 to change the blinking speed of the Red LED. Experiment with different delay values until the LED blinks at approximately 1 Hz (about one second ON and one second OFF).
Task 2 ā Cycle Through Multiple Colors ā
Expand Example 2 to include additional colors by combining the Red, Green, and Blue LEDs. Create a program that automatically cycles through all color combinations listed in the table above.
Hint: Use a loop to step through the color sequence repeatedly instead of writing separate code for each color.