Part Number: TDA4VH-Q1
What are the steps to integrate SDL with AUTOSAR OS? Is there any userguide available?
Hi,
SDL is designed to be OS-agnostic. It supports executing Baremetal or with an OS. TI expectation is that SDL which is ASIL-D assessed is run in the context of a Safety OS. SDL is delivered as a baremetal library – OSAL and interrupts can be integrated based on Autosar guidelines.
It is suggested that you use the baremetal OS type as you are using Autosar as the operating system and not RTOS. SDL is provided as a baremetal library that can be integrated into the user's Autosar application. It uses OS resources like interrupt handlers and memory translation through function pointers that are provided by the application. So you will have to configure the OSAL interface to use Autosar implementations with a baremetal application.
The SDL uses it's own version of OSAL (sdl\osal\src\sdl_osal.*) to abstract the OS API calls. This can be used as reference to port to your application OS. The general approach for integration would be to use the configurator to set up the interrupts for ESM instances. When the interrupt handler runs, it shall call the function pointer provided to the application through SDL_OSAL_registerInterrupt(). When starting the application, call SDL_OSAL_init() and provide the pointers to the required OSAL functions.
For example, the interrupt registration for corresponding interrupt numbers used in SDL should be done via Davinci configurator instead of Osal_RegsiterInterrupt API's. Even the tasks and runnables need to be created in davinvi configurator itself as done for sciserver - https://www.ti.com/lit/an/spracy6/spracy6.pdf. (Note -This document is not present on SDLTI IPC (CDD IPC or PDK IPC) has nothing to do with SDL.) There are no specific considerations that come to mind to make the current SDL Autosar compliant. The validation steps remain the same as running the SDL examples.
Regards,
Josiitaa
