AM275 FreeRTOS SDK  10.01.00
•All Data Structures Files Functions Variables Typedefs Enumerations Enumerator Macros Modules Pages
Flash an example application

Table of Contents

Attention
Flashing a application will overwrite the SOC init application that was flashed earlier. So if you want to load and run from CCS again, you will need to do the SOC init steps again.
As the wake-up R5 is the device manager, it needs to be started by the SBL. So it can not be loaded through CCS. It should be flashed and booted through SBL.
Note
See also Flashing Tools for more details on the flashing tools.

Introduction

In this step we will flash the application that we have build and run using CCS to the EVM flash. We can then boot this application without being connected to CCS via JTAG.

Getting ready to flash the application

  • A quick recap of steps done so far that are needed for the flashing to work
    • Make sure the UART port used for terminal is identified as mentioned in Setup UART Terminal
    • Make sure python3 is installed as mentioned in Python3
    • Make sure you have the EVM power cable and UART cable connected as shown in Cable Connections
  • Build the hello world application as mentioned in Build a Hello World example
  • As part of the build process in the final step a file with extension .mcelf.hs_fs is generated. This is the file we need to flash.
    • When building with makefiles and single-core projects, this file can be found here (shown for hello world example),
      • For R5 
         ${SDK_INSTALL_PATH}/examples/hello_world/am275x-evm/r5fss0-0_freertos/ti-arm-clang/hello_world.release.mcelf.hs_fs
      • For DM R5F (WKUP R5F) 
         ${SDK_INSTALL_PATH}/examples/hello_world/am275x-evm/wkup-r5fss0-0_freertos/ti-arm-clang/hello_world.release.hs_fs.tiimage
      • For c75 
         ${SDK_INSTALL_PATH}/examples/hello_world/am275x-evm/c75ss0-0_freertos/ti-c7000/hello_world.release.mcelf.hs_fs
    • When building with CCS projects, this file can be found here (shown for hello world example),
      • For R5F 
        ${CCS_WORKSPACE_PATH}/hello_world_am275x-evm_r5fss0-0_freertos_ti-arm-clang/Release/hello_world_am275x-evm_r5fss0-0_freertos_ti-arm-clang.appimage.hs_fs
      • For C75 ${CCS_WORKSPACE_PATH}/hello_world_am275x-evm_c75ss0-0_freertos_ti-c7000/Release/hello_world_am275x-evm_c75ss0-0_freertos_ti-c7000.appimage.hs_fs
    • NOTE: The folder name and file name in path can have "release", "Release" or "debug", "Debug" based on the profile that the application is built with.
  • Next, we need to list the files to flash in a flash configuration file. A default configuration file can be found at below path. You can edit this file directly or take a copy and edit this file. 
      ${SDK_INSTALL_PATH}/tools/boot/sbl_prebuilt/am275x-evm/sbl_ospi_hs_fs.cfg
    Note
    For HS-SE device, use sbl_ospi_hs.cfg as the cfg file.
    For HS-FS device, use sbl_ospi_hs_fs.cfg as the cfg file.
  • Edit below lines in the config file to point to your application .mcelf file. Give the absolute path to the .mcelf file or path relative to ${SDK_INSTALL_PATH}/tools/boot. Make sure to use forward slash / in the filename path.
    • For R5F_0-0 
      --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs --operation=flash --flash-offset=0xC00000
    • For R5F_0-1 
      --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss0-1_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs --operation=flash --flash-offset=0x1000000
    • For R5F_1-0 
      --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss1-0_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs --operation=flash --flash-offset=0x1400000
    • For R5F_1-1 
      --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss1-1_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs --operation=flash --flash-offset=0x1800000
    • For C751_0 
      --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/c75ss0-0_freertos/ti-c7000/ipc_rpmsg_echo.release.mcelf.hs_fs --operation=flash --flash-offset=0x400000
    • For C751_1 
      --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/c75ss1-0_freertos/ti-c7000/ipc_rpmsg_echo.release.mcelf.hs_fs --operation=flash --flash-offset=0x800000
  • This file will additionally also list the flashing application that is run on the EVM and a OSPI flash bootloader that also needs to be flashed. You can keep this unchanged if you have not modified these applications.
  • Save and close the config file.

Flashing the application

  • Build all the binaries
    • For Linux
      make DEVICE=am275x -sj
    • For Windows
      gmake DEVICE=am275x -sj
  • POWER-OFF the EVM
  • Set boot mode to UART BOOTMODE as shown in below image

UART BOOT MODE
  • Switch the MMC0_SELECT switch(SW9) to OFF position

MMC INTERFACE SELECT
  • POWER-ON the EVM
  • You should see character "C" getting printed on the UART terminal every 2-3 seconds as shown below

UART output in UART BOOT MODE
  • Close the UART terminal as shown below. This is important, else the UART script in next step wont be able to connect to the UART port.

Close UART terminal
Note
For HS-SE device, use default_sbl_ospi_nand_linux_hs.cfg as the cfg file.
For HS-FS device, use default_sbl_ospi_nand_linux_hs_fs.cfg as the cfg file.
  • Open a command prompt and run the below command to flash the SOC initialization binary to the EVM. 
      cd ${SDK_INSTALL_PATH}/tools/boot
  python uart_uniflash.py -p COM14 --cfg=sbl_prebuilt/am275x-evm/sbl_ospi_hs_fs.cfg
    • Here COM14 is the port name of the identified UART port in Windows.
    • On Linux,
      • The name for UART port is typically something like /dev/ttyACM0
      • On some Linux systems, one needs to use python3 to invoke python3.x, just python command may invoke python 2.x which will not work with the flashing script.
  • When the flashing is in progress you will see something like below

Flash in progress
  • After all the flashing is done, you will see something like below 
      Parsing config file ...
  Parsing config file ... SUCCESS. Found 9 command(s) !!!

  Executing command 1 of 9 ...
  Found flash writer ... sending sbl_prebuilt/am275x-evm/sbl_uart_uniflash.release.hs_fs.tiimage
  Sent flashwriter sbl_prebuilt/am275x-evm/sbl_uart_uniflash.release.hs_fs.tiimage of size 390201 bytes in 36.75s.

  Executing command 2 of 9 ...
  Command arguments : --operation=flash-phy-tuning-data
  Sent flash phy tuning data in 3.58s.
  [STATUS] SUCCESS !!!

  Executing command 3 of 9 ...
  Command arguments : --file=sbl_prebuilt/am275x-evm/sbl_ospi.release.hs_fs.tiimage --operation=flash --flash-offset=0x0
  Sent sbl_prebuilt/am275x-evm/sbl_ospi.release.hs_fs.tiimage of size 453689 bytes in 43.25s.
  [STATUS] SUCCESS !!!

  Executing command 4 of 9 ...
  Command arguments : --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/c75ss0-0_freertos/ti-c7000/ipc_rpmsg_echo.debug.mcelf.hs_fs --operation=flash --flash-offset=0x400000
  Sent ../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/c75ss0-0_freertos/ti-c7000/ipc_rpmsg_echo.release.mcelf.hs_fs of size 142562 bytes in 15.66s.
  [STATUS] SUCCESS !!!

  Executing command 5 of 9 ...
  Command arguments : --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/c75ss1-0_freertos/ti-c7000/ipc_rpmsg_echo.debug.mcelf.hs_fs --operation=flash --flash-offset=0x800000
  Sent ../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/c75ss1-0_freertos/ti-c7000/ipc_rpmsg_echo.release.mcelf.hs_fs of size 151218 bytes in 16.4s.
  [STATUS] SUCCESS !!!

  Executing command 6 of 9 ...
  Command arguments : --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo.debug.mcelf.hs_fs --operation=flash --flash-offset=0xC00000
  Sent ../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs of size 74730 bytes in 9.68s.
  [STATUS] SUCCESS !!!

  Executing command 7 of 9 ...
  Command arguments : --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss0-1_freertos/ti-arm-clang/ipc_rpmsg_echo.debug.mcelf.hs_fs --operation=flash --flash-offset=0x1000000
  Sent ../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss0-1_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs of size 65346 bytes in 8.78s.
  [STATUS] SUCCESS !!!

  Executing command 8 of 9 ...
  Command arguments : --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss1-0_freertos/ti-arm-clang/ipc_rpmsg_echo.debug.mcelf.hs_fs --operation=flash --flash-offset=0x1400000
  Sent ../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss1-0_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs of size 65346 bytes in 8.78s.
  [STATUS] SUCCESS !!!

  Executing command 9 of 9 ...
  Command arguments : --file=../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss1-1_freertos/ti-arm-clang/ipc_rpmsg_echo.debug.mcelf.hs_fs --operation=flash --flash-offset=0x1800000
  Sent ../../examples/drivers/ipc/ipc_rpmsg_echo/am275x-evm/r5fss1-1_freertos/ti-arm-clang/ipc_rpmsg_echo.release.mcelf.hs_fs of size 65378 bytes in 8.77s.
  [STATUS] SUCCESS !!!

  All commands from config file are executed !!
  • If flashing has failed, see Flash tool error messages and solutions, and resolve the errors.
  • If flashing is successful, do the next steps ...

Running the flashed application

  • POWER-OFF the EVM
  • Switch the EVM boot mode to OSPI NOR mode as shown below,
  • Switch the MMC0_SELECT switch(SW9) to OFF position

OSPI BOOT MODE

MMC INTERFACE SELECT
  • Re-connect the UART terminal in CCS window as shown in Setup UART Terminal
  • POWER-ON the EVM
  • You should see the SBL & DM output in WKUP UART terminal as below 
      Sciserver Testapp Built On: Nov 26 2024 10:52:59
  Sciserver Version: v2023.11.0.0REL.MCUSDK.MM.NN.PP.bb
  RM_PM_HAL Version: vMM.NN.PP
  Starting Sciserver..... PASSED

  Starting OSPI Bootloader ...

  SYSFW Firmware Version 10.0.8--w2024.02-am275x (Fiery
  SYSFW Firmware revision 0xa
  SYSFW ABI revision 4.0

  [BOOTLOADER_PROFILE] Boot Media       : FLASH
  [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz
  [BOOTLOADER_PROFILE] Boot Image Size  : 539 KB
  [BOOTLOADER_PROFILE] Cores present    :
  [BOOTLOADER PROFILE] TIFS init                        :        706us
  [BOOTLOADER PROFILE] System_init                      :       5506us
  [BOOTLOADER PROFILE] Board_init                       :          4us
  [BOOTLOADER PROFILE] FreeRtosTask Create              :        263us
  [BOOTLOADER PROFILE] Drivers_open                     :        143us
  [BOOTLOADER PROFILE] Board_driversOpen                :          1us
  [BOOTLOADER PROFILE] sciServer_init                   :      15284us
  [BOOTLOADER PROFILE] SBL Drivers_open                 :       3198us
  [BOOTLOADER PROFILE] SBL Board_driversOpen            :        135us
  [BOOTLOADER PROFILE] Sciclient Get Version            :      10350us
  [BOOTLOADER PROFILE] DSP 0 Image Load                 :      19790us
  [BOOTLOADER PROFILE] DSP 1 Image Load                 :      19817us
  [BOOTLOADER PROFILE] R5FSS0_0 Image Load              :       6158us
  [BOOTLOADER PROFILE] R5FSS0_1 Image Load              :       6012us
  [BOOTLOADER PROFILE] R5FSS1_0 Image Load              :       6025us
  [BOOTLOADER PROFILE] R5FSS1_1 Image Load              :       6008us
  [BOOTLOADER_PROFILE] SBL Total Time Taken             :      99406us

  Image loading done...
  Starting RTOS/Baremetal applications
  • You should see the following application output on the main UART terminal as below. 
      [r5f0-1]     0.003012s : [IPC RPMSG ECHO] Remote Core waiting for messages from main core ... !!!
  [r5f1-0]     0.003012s : [IPC RPMSG ECHO] Remote Core waiting for messages from main core ... !!!
  [r5f1-1]     0.003012s : [IPC RPMSG ECHO] Remote Core waiting for messages from main core ... !!!
  [c75ss0-0]     0.003008s : [IPC RPMSG ECHO] Remote Core waiting for messages from main core ... !!!
  [c75ss1-0]     0.001336s : [IPC RPMSG ECHO] Remote Core waiting for messages from main core ... !!!
  [IPC RPMSG ECHO] Message exchange started by main core !!!
  [IPC RPMSG ECHO] All echoed messages received by main core from 5 remote cores !!!
  [IPC RPMSG ECHO] Messages sent to each core = 10
  [IPC RPMSG ECHO] Number of remote cores = 5
  [IPC RPMSG ECHO] Total execution time = 492 usecs
  [IPC RPMSG ECHO] One way message latency = 4920 nsec
  All tests have passed!!
  • Congratulations now the EVM is flashed with your application and you don't need CCS anymore to run the application.