This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: PROCESSOR-SDK-DRA8X-TDA4X
What are the different layers that go into AUTOSAR, what is the functionality of each layer, and how does MCAL relate to the framework as a whole?
AUTOSAR architecture has three major software layers: Application, Runtime Environment and Basic Software, which run on our Microcontroller (going from top to bottom to hardware).The Basic Software Layer (BSW) is horizontally divided into Services, ECU Abstractions, Microcontroller Abstraction (MCAL) and Complex Drivers layers. The sub-layers of BSW are vertically grouped into functional services such as System, Memory and Communication.
MCAL is the lowest software layer in BSW, and closest to the microcontroller. It includes internal drivers, so it has direct access to the microcontroller's internal peripherals. The main purpose of MCAL is to allow the higher software layers to be independent of the hardware. Therefore, MCAL software modules are hardware dependent, while higher layers are independent.
The next layer above MCAL is the ECU Abstraction Layer. This acts as the interface for the drivers in MCAL and provides the APIs that allow access to peripherals and devices.
Services layer is the highest in BSW and offers basic services for applications and basic software modules.
The AUTOSAR Runtime Environment (RTE) provides communication services to application software and ensures that AUTOSAR software components stay independent from mapping to specific ECU.
Furthermore, going into MCAL details: MCAL acts as an interface/abstraction layer between the hardware and above software layers. Since it can make actual and direct calls to memory and can transmit information to external destinations, MCAL needs to be provided by the SoC provider. Texas Instruments provides MCAL software drivers for Jacinto 7.
To read more about AUTOSAR and its layers, please refer here.
To start looking into the software package that Texas Instruments provides, please refer Processor SDK RTOS Automotive package, and its documentation.
After installing the Processor SDK RTOS Automotive package, MCU software can be found in "mcusw" directory. Please refer to the MCU Software User Guide and the MCU Software Release Notes.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.