SPRACY6 July   2021 DRA821U , DRA829J , DRA829V , TDA4VM-Q1

 

  1.   Trademarks
  2. 1 Introduction
    1. 1.1 SYSFW
    2. 1.2 TISCI
    3. 1.3 TISCI Client or SciClient
    4. 1.4 TISCI Server or SciServer
    5. 1.5 Acronyms Used in This Document
  3. 2 Target Audience
  4. 3 MCU1_0 Role in Jacinto7 SDK V7.1+
  5. 4 TISCI Client and Server on TI-RTOS
    1. 4.1 J7 SDK Download
    2. 4.2 SciClient Driver Location
    3. 4.3 TISCI Server Initialization Example
    4. 4.4 Integration Guide
      1. 4.4.1 Semaphore
      2. 4.4.2 Interrupts Registration
      3. 4.4.3 Interrupts Handling
      4. 4.4.4 User Tasks Registration
      5. 4.4.5 User Tasks Processing
  6. 5 Configurations in DaVinci
    1. 5.1 DaVinci Developer
    2. 5.2 DaVinci Configurator Pro
    3. 5.3 Resource
    4. 5.4 Events
      1. 5.4.1 Event for High Priority Requests
      2. 5.4.2 Event for Normal Priority Requests
    5. 5.5 SciServer User Tasks
      1. 5.5.1 High Priority User Task
      2. 5.5.2 Normal Priority UserTask
    6. 5.6 Synchronization Between Sciserver User Tasks
      1. 5.6.1 Configure the Resource for High Priority User Task
      2. 5.6.2 Configure the Resource for Normal Priority User Task
    7. 5.7 Sciserver Interrupts
      1. 5.7.1 MCU Domain Navigation System High Priority Interrupts
      2. 5.7.2 Main Domain Navigation System High Priority Interrupts
      3. 5.7.3 MCU Domain Navigation System Normal Priority Interrupts
      4. 5.7.4 Main Domain Navigation System Normal Priority Interrupts
  7. 6 AUTOSAR TISCI Client
    1. 6.1 TISCI Client Registration in AUTOSAR
  8. 7 AUTOSAR TISCI Interrupts Handling
    1. 7.1 MCU Domain Navigation System High Priority Interrupts
    2. 7.2 Main Domain Navigation System High Priority Interrupts
    3. 7.3 MCU Domain Navigation System Normal Priority Interrupts
    4. 7.4 Main Domain Navigation System Normal Priority Interrupts
  9. 8 AUTOSAR TISCI User Tasks Processing
    1. 8.1 High Priority User Task Initialization
    2. 8.2 High Priority User Task Runnable
    3. 8.3 Normal Priority User Task Initialization
    4. 8.4 Normal Priority User Task Runnable
  10. 9 TISCI Server Validation in AUTOSAR
    1. 9.1 Boot App
    2. 9.2 Boot Task Configuration
    3. 9.3 Boot App in AUTOSAR
      1. 9.3.1 Boot App Launch
      2. 9.3.2 Boot App Implementation
  11. 10PDK Libraries Used in AUTOSAR
  12. 11R5F Configurations Needed for AUTOSAR
    1. 11.1 Memory Layout for Cortex-R5F
    2. 11.2 R5F Cache Configuration

2 Target Audience

SYSFW executes on the Security Manager and Device Manager Core. On J7 devices, the DMSC subsystem is the Security Manager Core (Arm® Cortex®-M3) in the SoC. The Device Manager (DM) core however can be on the DMSC itself or the MCU R5F. The choice of whether this runs on the DMSC or the MCU R5F is based on the kind of applications the device is targeting.

For devices that do not need a dedicated security island or HSM, the device manager runs on the DMSC. If the device is targeting applications, where there is a need for a dedicated HSM, the Device manager core is independent of the DMSC (which is exclusively kept for Security functions).

Table 2-1 Missing Title
Category Device TIFS Core Dedicated Security Island or HSM? 3rd Party HSM/SHE Stack Core RM/PM (DM) core
1 DRA829/TDA4VM DMSC (M3) NO NA DMSC (M3)
2 DRA829/TDA4VM DMSC (M3) YES DMSC (Cortex-M3) Library on MCU R5F

The intention of this application report is to cater to the second category mentioned above.