AM62x MCU+ SDK  08.06.00

Welcome to MCU+ SDK for AM62X. This SDK contains examples, libraries and tools to develop RTOS and no-RTOS based applications for ARM M4F CPU, AMR R5F CPU and related peripherals.

This SDK also contains examples to interface these ARM M4F applications with Processor SDK Linux based Cortex-A applications.

Getting Started

To get started, see Getting Started

Block Diagram

Given below is a block diagram of the SW modules in this SDK,

Software Block Diagram

The main software components in the block diagram are described below

Software Components Documentation Page Description
OS Kernel
No RTOS NO RTOS Contains modules which implement no-RTOS execution environment consisting of timers, ISR, main thread. Allows software on top to run in bare metal mode.
FreeRTOS Kernel FreeRTOS FreeRTOS Kernel, provides a execution environment consisting of tasks, semaphores, timers, see
FreeRTOS POSIX FreeRTOS Limited POSIX APIs with FreeRTOS underneath, provides pthreads, mqueue, semaphore, see
Driver Porting Layer (DPL) Driver Porting Layer (DPL) APIs used by drivers to abstract the OS environment. Example, Semaphore, HW interrupts, mutex, clock.
Device Drivers and HAL (Hardware Abstraction Layer)
SOC Peripheral Drivers SOC Peripheral Drivers Device Drivers library and APIs for peripherals within the SOC. Example, I2C, GPIO, UART.
Board Peripheral Drivers Board Peripheral Drivers Device Drivers library and APIs for peripherals on the board or EVM. Example, Flash.
Examples Examples and Demos Examples showing usage of different SW libraries and APIs
Tools (used on host machine)
Code Composer Studio (CCS) Using SDK with CCS Projects IDE used to build projects, debug programs.
TI CLANG Compiler Toolchain TI CLANG Homepage CLANG based ARM compiler from TI for ARM R5F and M4F
SysConfig Using SDK with SysConfig System configuration tool, used to configure peripherals, pinmux, clocks and generate system initialization code
TI Resource Explorer (TIREX) Using SDK with TI Resource Explorer Web broswer based tool to explore the SDK, select, import and run the examples
SDK Tools and Utilities Tools and Utilities Additional tools and utilities, like flashing tools, booting tools, CCS loading scripts used with the SDK development flow

Directory Structure

Given below is a overview of the directory structure to help you navigate the SDK and related tools.

Folder/Files Description
README_FIRST_AM62X.html Open this file in a web browser to reach this user guide
makefile Top level makefile to build the whole SDK using "make"
imports.mak Top level makefile to list paths to dependent tools
docs/ Offline browseable HTML documentation
examples/ Example applications for AM62X, across multiple boards, CPUs, NO-RTOS, RTOS
source/ Device drivers, middleware libraries and APIs
tools/ Tools and utilities like CCS loading scripts, initialization scripts.
board/ Board peripheral device drivers. Currently no board peripheral drivers are supported. More drivers will be added in the future.
drivers/ Soc peripheral device drivers. Currently only IPC_RPMessage supported. More drivers will be added in the future.
kernel/ NO RTOS and RTOS kernel and Driver Porting layer (DPL) for these environments.
drivers/ SOC and board level focused device drivers examples. The examples are based on both NO-RTOS and RTOS
kernel/ NO RTOS and RTOS kernel focused examples

Given below are the paths where the different tools needed outside the SDK, like CCS, SysConfig are installed by default in Windows. In Linux, the tools are installed by default in ${HOME}/ti.

Folder/Files Description
C:/ti/ccs1220 Code Composer Studio
C:/ti/sysconfig_1.15.0 SysConfig. NOTE, SysConfig is also installed as part of CCS at ${CCS_INSTALL_PATH}/ccs/utils/sysconfig_x.x.x
C:/ti/ti-cgt-armllvm_2.1.2.LTS TI ARM CLANG compiler tool chain


The licensing information of this SDK, as well as any third-party components included which are made available under a number of other open-source licenses are enumerated as part of the manifest. A complete manifest along with export control information is detailed here [LINK]

Help and Support

For additional help and support, see

Documentation Credits

This user guide is generated using doxygen, v1.8.20. See