- Note
- For quick start tutorial on MCU+SDK under 10 minutes, please watch Getting started with AM26x microcontrollers and MCU PLUS SDK
Application Execution Flow
Build, load and run application
Building an application
- Note
- SDK supports building applications via both Makefile and CCS.
makefile_ccs_bootimage_gen
file present inside a CCS project will have steps involved in building an application via CCS.
makefile
present inside each example folder consists of the steps involved in building the application via make.
-
Refer Build a Hello World example for an example of CCS and Makefile based build.
- Building a particular example project compiles all source files present in drivers, examples and sysconfig, links them, then generates a .out binary.
- Using the .out, we generate .appimage / .mcelf images.
- Once a multicore application image is built, we can load it into memory.
- .out file can be directly loaded into CCS. Refer Load and run example binaries in CCS
For detailed information on building visit Building an Application
Loading an application
- Loading is when an application is written into RAM/Flash memory.
- There are 3 ways to load a binary:
- via CCS
- via TI Uniflash tool
- via Python scripts
- Once the application is loaded, we can run it.
For detailed information on loading visit Loading an Application
Running an application
- Bootloaders are responsible for reading the loaded application and running it on the respective CPU.
- Depending on the boot media, there are different types of SBLs that can be used.
- If application is found in the address specified to bootloader, it parses the file, loads into respective CPUs and releases core from reset.
- Booting an RPRC image: Booting RPRC application
- Booting an MCELF image: Booting MCELF application
For detailed information on loading visit Running an Application