STDA048 September   2026 MSPM33C321A-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2MCAL and AUTOSAR Basics
    1. 2.1 What are MCAL and AUTOSAR?
    2. 2.2 MCAL Applications
    3. 2.3 AUTOSAR Applications
  6. 3MCAL Package for MSP Microcontrollers
    1. 3.1 Licensing Model
    2. 3.2 Support Model
  7. 4MSP Scalability and Ecosystem
    1. 4.1 Platform Scalability
    2. 4.2 Software Ecosystem and Integration
  8. 5Getting Started
    1. 5.1 Installation and Setup
    2. 5.2 Implementation Tips
  9.   Resources

Support Model

TI provides comprehensive direct technical support for the MCAL layer through the MCAL-to-BSW integration boundary. Within this scope, TI covers MCAL driver functionality per AUTOSAR 4.3.1 specifications, configuration through EB tresosĀ® plugins, API compliance with AUTOSAR SWS documents, bug fixes, device-specific errata workarounds, performance optimization, and memory footprint guidance for MCAL configuration. TI also provides a level of best-effort guidance for integration of TI MCAL drivers into major third-party BSW stacks, providing customers with flexibility in their choice of AUTOSAR stack while maintaining a well-supported integration path.

Support beyond the MCAL-to-BSW integration boundary is explicitly outside TI's scope. BSW module development and support (for example, CanIf, ComM, NvM, DEM, DCM) are the responsibility of the chosen AUTOSAR BSW vendor or integrator. RTE generation and configuration, application software development, and overall system integration, validation, and ISO 26262 system certification remain the responsibility of the end-developer.