This post describes how the OSS-ECAL architecture is being developed with AUTOSAR in mind.
OSS-ECAL architecture in line with AUTOSAR
OSS-ECAL is developed considering AUTOSAR’s ECU Layer and MCAL in order to improve the compatibility with AUTOSAR and SDV.
By using OSS-ECAL, ECU design engineers can avoid the time and effort of creating AUTOSAR-compliant software requirement specifications based on the data sheets of each IC. In addition, software engineers with little experience with ECU Layer and MCAL can easily incorporate them.
In response to your requests, we will gradually expand OSS-ECAL to support AUTOSAR (SDV) in consultation with electronic component manufacturers.

Standardized API
The OSS-ECAL API is aware of the part model number.However, the API can be standardized with #define.
Example: How to minimize application impact
Example: Application registration for temperature sensor ABC1
/* Temperature ABC1 read function*/
etSTS oABC1_READ( float32* );
#define TEMPERATURE_READ oABC1_READ
etSTS TEMPERATURE_READ( float32* rlt )
Where to change the application when changing temperature sensor ABC1 to temperature sensor ABC2.The OSS-ECAL file should be replaced with the ABC2 file.
/* Temperature ABC2 read function*/
etSTS oABC2_READ( float32* );
#define TEMPERATURE_READ oABC2_READ
etSTS TEMPERATURE_READ( float32* rlt )
Reference: AUTOSAR
AUTOSAR defines the software layer from the hardware layer as follows, defining a corresponding software component for each hardware component. Similarly, OSS-ECAL assigns a software component to each electronic component.

