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

 

  1.   Trademarks
  2. 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. Target Audience
  4. MCU1_0 Role in Jacinto7 SDK V7.1+
  5. 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. 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. AUTOSAR TISCI Client
    1. 6.1 TISCI Client Registration in AUTOSAR
  8. 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. 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. 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

Memory Layout for Cortex-R5F

Table 11-1 shows the ATCM and BTCM in the Cortex-R5F.

Table 11-1 ATCM and BTCM in the Cortex-R5F
Region Name Start Address End Address Size
ARMSS_ATCM 0x0000 0000 0x0000 7FFF 32KB
ARMSS_BTCM 0x4101 0000 0x4101 7FFF 32KB

There are several check points for running AUTOSAR on Cortex-R5F.

  • ATCM usage: R5 SPL does not enable MCU1_0’s ATCM by default and, hence, if the AutoSAR application is being booted on MCU1_0 core from R5 SPL then ATCM shouldn’t be used in the memory layout.
    • Startup_Code should be placed to BTCM in that case.
  • Startup_Code alignment: should be 256 bytes aligned.

Example is shown below:

MEMORY
{
  OCMCRAM_Common : ORIGIN = 0x41C50000 , LENGTH = 0x00004000 /* 48 KiB */
  OCMCRAM_Common_NonCache : ORIGIN = 0x41C54000 , LENGTH = 0x00000400 /* 1024 Byte */
  OCMCRAM_Core0 : ORIGIN = 0x41C54400 , LENGTH = 0x00000800 /* 2048 Byte */
  OCMCRAM_Core1 : ORIGIN = 0x41C54C00 , LENGTH = 0x00000400 /* 1024 Byte */
  OCMCRAM_Core2 : ORIGIN = 0x41C55000 , LENGTH = 0x00000400 /* 1024 Byte */
  OCMCRAM_Core3 : ORIGIN = 0x41C55400 , LENGTH = 0x00000400 /* 1024 Byte */
  OCMCRAM_Core4 : ORIGIN = 0x41C55800 , LENGTH = 0x00000400 /* 1024 Byte */
  OCMCRAM_Core5 : ORIGIN = 0x41010000 , LENGTH = 0x00000400 /* 1024 Byte */
  DDR0 : ORIGIN = 0x41C55C00 , LENGTH = 0xA5000 /* 16 MiB */
}

  .Startup_Code : ALIGN(256)
  {
    _Startup_Code_START = .;
    *(.brsStartup)
    . = ALIGN(256);
    _Startup_Code_END = . - 1;
    _Startup_Code_LIMIT = .;
  } > OCMCRAM_Core5