MCUSW
CDD IPC Profiling Application

Introduction


This application measures the CPU cycles required for transmission, reception of N number of bytes to, from a given core. As an example communication between MCU 1 0 and MPU 1 0 will be considered (or other cores). Similar approach would be employed for other cores. Please refer (Supported Drivers) for details on core that can host MCAL

Simulates transmission and reception of messages of different length, including standard lengths of 8 bytes and 64 bytes.

SoC Host Core Remote Cores Comments
J721E MCU 1 0 MCU 2 1, MPU 1 0 MCAL could be hosted on other cores but this demo application runs only on MCU 1 0, at this point of time

Dependencies

Local Application

This application depends on multiple components and are detailed in sections below

  1. TI RTOS : Uses Task, semaphore, Interrupt Handling HWI and Profiling Utility.
  2. MCAL
    • Cdd Ipc Driver
  3. MCAL BSW Stubs Stubs at (SDK Install Directory)/mcusw/mcuss_demos/Bsw_Stubs are used.
  4. MCAL Configurations Cdd Ipc Configurations at (SDK Install Directory)/mcusw/mcuss_demos/mcal_config are used.
  5. The MCAL based profiling application is hosted on MCU 1 0 (could also be hosted on other cores in future, (Supported Drivers))

Remote Application

This application depends on multiple components and are detailed in sections below

  1. TI RTOS : Uses Task, semaphore, Interrupt Handling HWI and Swi.
  2. PDK
    • IPC Driver

Back To Top


Flow Chart

The flow chart below depicts the profiling application

  • ipc_remote_app_mpu1_0_release.xa53fg would be hosted on Remote Core (MPU 1 0)
  • cdd_ipc_profile_app_mcu1_0_release.xer5f would be hosted on Local Core (MCU 1 0)
demo_cdd_ipc_profile_flowchart.png
Cdd Ipc Profiling Application

Back To Top


Compile Time Configurations

  1. CDD_IPC_DEV_ERROR_DETECT Control checks of configurations and parameters. Turned OFF for profiling test

Back To Top


Test Setup / Configurations used

EVM

  1. Require the EVM only, as the IPC relies on built-in mailbox hardware.

Back To Top


Steps to run

  1. Build the demo application as detailed in Common Steps in User Guide, Specific Steps in
  2. Steps to run is detailed in Common Steps in User Guide, Specific Steps in

Back To Top


Document Revision History

Revision Date Author Description Status
0.1 14 Apr 2019 Sujith S Initial Version Under Review
0.2 18 Apr 2019 Sujith S Addressed Review comments Approved
0.3 16 Jul 2019 Sujith S Included updates based on J721E Approved
0.4 8 Aug 2019 Sunil M S Updates profile numbers for release 00.09.01 Approved
0.5 16 Oct 2019 Sujith S Updates profile numbers for release 01.00.00 Approved
0.6 17 Feb 2020 Sujith S Re Organized the document Approved