SPRADJ0 February   2025 AM2612 , AM2631 , AM2632 , AM2634 , AM263P2 , AM263P4 , AM2732 , AM2732-Q1 , AM620-Q1 , AM623 , AM625 , AM625-Q1 , AM62A3 , AM62A3-Q1 , AM62A7 , AM62A7-Q1 , AM62D-Q1 , AM62P , AM62P-Q1 , AM67 , AM68A , AM69A , DRA821U , TDA4AEN-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4VE-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VP-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Configurator
  5. 2Software Stack
    1. 2.1 Configurator Plug-in
    2. 2.2 Source Files
    3. 2.3 User Guide
    4. 2.4 Compliance Support Package (CSP)
  6. 3Utilizing the Source - Building Drivers and Examples
    1. 3.1 One-Time Setup
    2. 3.2 Build Instructions
    3. 3.3 Build Command Syntax
  7. 4Obtaining an MCAL package
  8. 5Summary
  9. 6References

1 Introduction

Table 1-1 shows acronyms and definitions.

Table 1-1 Full Form Expansions for Abbreviations and Acronyms
Acronym Definition
API Application Programming Interface
ARXML AUTOSAR XML
AUTOSAR AUTomotive Open System ARchitecture
BSW Basic Software
CDD Complex Driver Design
CSP Compliance Support Package
ECU Electronic Control Unit
FSQ Functional Safety Qualification
FuSa Functional Safety
GUI Graphical User Interface
ISO International Organization for Standardization
IRQ Interrupt ReQuest
ISR Interrupt Service Routine
MCAL Microcontroller Abstraction Layer
MCU Microcontroller Unit
MPU Microprocessor Unit
Mip Module Implementation Prefix
RTE Runtime Environment
SIL Silicon Integrity Level
SDK Software Development Kit
SRS Software Requirement Specification
SWS Software Specification
TI Texas Instruments Incorporated
XER5F

eXEcutable for R5F core

MCAL is the same as the Hardware Abstraction Layer that is responsible for providing ways to interact with the underlying hardware system comprising a processor along with memory and the peripherals through the set of drivers based on the documented interface. MCALs are one of the layers under the AUTOSAR stack.

AUTOSAR is an open standardized software framework for Automotive Development, established by a group of leading automotive industrialists in 2003. The latest release is R23-11; succeeding releases R22-11, R21-11, R20-11, R19-11, ..., R4.4.0, R4.3.1, R4.3, R4.2, R4.1, R4.0.3, R3.2, R3.1, R3, and R2 that were published in 2006. Versions were numbered as R<YY>-<MM> where <MM> is month and <YY> is year of release in two digits, starting with R17-03 and prior releases were semantically versioned as v<Major>.<minor>.<Revision> until v4.4.0 and 4.5.0. The standards organization provides specifications under the Classic Platform and Adaptive Platform architecture, out of which the Classic Platform architecture standards include MCAL under the Basic Software (BSW) layer.

Figure 1-1 shows the Classic Platform standard layer architecture is comprised of an Application Layer, Runtime Environment, BSW Layer, and a Microcontroller layer just below. The scope of the Classic Platform architecture is from Application to µC.

AM602, AM2412 AUTOSAR 4.3.1 Architecture Figure 1-1 AUTOSAR 4.3.1 Architecture

The BSW Layer sandwiched between Runtime Environment and Microcontroller has the sublayers, specifically, Services Layer, ECU Abstraction Layer, and MCAL Layer colored distinctly in Purple, Green, and Red tint, respectively. Though the Complex Drivers block is not distinctly colored, the block is another sublayer of BSW that spans entirely within BSW from the microcontroller to the RTE interaction. Figure 1-1 shows the breakdown for MCAL and Complex Drivers.

The MCAL package is meant to be run on Arm® Cortex®-R core fabricated by Texas Instruments on the multiple cores. For TI Jacinto™, Sitara™ MCU, and MPU Arm®-based device families, the Cortex-R5 core is the target core for supporting execution of the MCAL and CDD device drivers. At present, only single-core MCAL support is offered from TI on these device families.