![[Image]SANEI HYTECHS](/en/shared/img/logo_w.png){kind=logo}
AUTOSAR MCAL Development
There are many achievements in the development of MCAL conforming to the AUTOSAR standard. We provide consistent services from the design process to the verification process in the development process for automotive applications.
SANEI HYTECHS is developing MCAL conforming to the AUTOSAR CP standard. Based on our past experience and achievements, we provide customers with consistent services from the design process to the verification process in the development process for automotive applications.*For information on our development process, please also refer to our approach to the functional safety standard ISO 26262.
MCAL:
MCAL (MicroController Abstraction Layer) is a "software module group responsible for microcontroller control" in the automotive standard software architecture, AUTOSAR CP (Classic Platform). MCAL operates the memory and registers of a microcontroller, and controls various peripherals.
At the higher level, it provides abstracted functions that do not depend on the microcontroller specifications, such as "initialization," "start," and "completion notification." By going through MCAL, the upper layer can achieve the desired operation while minimizing the need to be conscious of the microcontroller.
At the higher level, it provides abstracted functions that do not depend on the microcontroller specifications, such as "initialization," "start," and "completion notification." By going through MCAL, the upper layer can achieve the desired operation while minimizing the need to be conscious of the microcontroller.
List of MCAL Modules:
The following software modules have been standardized in MCAL. This includes the functions provided by the software modules, the interface with the upper layer, and configuration (please see here for the configuration mechanism).
For non-standardized microcontroller-specific constraints and functions, individual support from MCAL developers is required.
The following support methods can be considered:
The following support methods can be considered:
- Add functionality to standardized functions (the added functionality can be enabled/disabled by configuration)
- Add custom functions (the added functions can be enabled/disabled by configuration)
Implementing modules not available in MCAL (Complex Drivers implementation)
AUTOSAR CP defines a mechanism for implementing functionality not defined in the standardized software modules.
The following types of software modules can be implemented as Complex Drivers:
Like standardized software modules, Complex Drivers are defined with requirements such as the need for a hierarchical structure. However, they are defined as software modules that can be implemented freely within a certain range.
The following types of software modules can be implemented as Complex Drivers:
- Software modules for achieving extended services/protocols.
- Software modules for controlling microcontroller-specific peripherals.
- Software modules for higher responsiveness.
Like standardized software modules, Complex Drivers are defined with requirements such as the need for a hierarchical structure. However, they are defined as software modules that can be implemented freely within a certain range.
Mechanism of Configuration
In AUTOSAR CP, a mechanism is defined that allows software modules to be customized according to their usage. This customization is called configuration, and MCAL can also be configured through this mechanism. Configuration items are standardized as specifications for each software module.
For items related to constraints or features specific to a microcontroller that are not standardized, individual responses by MCAL developers are required.
Configuration involves using dedicated applications such as the ECU Configuration tool (Configurator) and the BSW Module Generator. The Configurator takes an input in the form of a list of configuration items (ECU Configuration Parameter Definition XML file) and generates a list of configuration values (ECU Configuration Value Description XML file). The Generator takes the list of configuration values as input and generates the MCAL code. Configurators are provided by BSW vendors, while generators and lists of configuration items are provided by MCAL developers.
For items related to constraints or features specific to a microcontroller that are not standardized, individual responses by MCAL developers are required.
Configuration involves using dedicated applications such as the ECU Configuration tool (Configurator) and the BSW Module Generator. The Configurator takes an input in the form of a list of configuration items (ECU Configuration Parameter Definition XML file) and generates a list of configuration values (ECU Configuration Value Description XML file). The Generator takes the list of configuration values as input and generates the MCAL code. Configurators are provided by BSW vendors, while generators and lists of configuration items are provided by MCAL developers.
How to Obtain MCAL
MCAL may be provided by various microcontroller manufacturers.
If MCAL is not available from a specific manufacturer, or if it does not meet the requirements of a customer's system, please consult us. Based on our experience and achievements, we will provide development services tailored to your needs.
If MCAL is not available from a specific manufacturer, or if it does not meet the requirements of a customer's system, please consult us. Based on our experience and achievements, we will provide development services tailored to your needs.
MCAL Development Services
We provide MCAL development services tailored to your needs. We can accommodate your requirements for expanding or reducing the functionality and configuration of MCAL, as well as comply with the AUTOSAR specification. In addition, we are capable of developing MCAL using a process based on Automotive SPICE to comply with the functional safety standard ISO26262.
If you have any concerns, please do not hesitate to contact us.
If you have any concerns, please do not hesitate to contact us.
We also provide information on the configuration mechanism we offer.
We propose an alternative method for configuration using configuration setting files (Config Files: C language files) that customers can directly edit instead of using configuration through the configuration parameter definition XML file or BSW module generator.
This can help reduce costs associated with:
Please contact us for more details.
This can help reduce costs associated with:
- Development costs for configuration parameter definition XML files or BSW module generator
- Operational testing costs with the ECU configuration tool
Please contact us for more details.
Renesas MCAL Third-Party Support
We provide various technical support related to MCAL (*) for customers using Renesas MCAL.
We have developed a large amount of software for Renesas microcontrollers to date.
We have a wide range of development experience, including peripheral control, clock/power control, and core control of microcontrollers.
To solve the challenges that customers face, our team analyzes and investigates from both software (MCAL) and hardware (microcontroller) perspectives to support customer development.
We have developed a large amount of software for Renesas microcontrollers to date.
We have a wide range of development experience, including peripheral control, clock/power control, and core control of microcontrollers.
To solve the challenges that customers face, our team analyzes and investigates from both software (MCAL) and hardware (microcontroller) perspectives to support customer development.
| Item | Description |
|---|---|
| Technical Support | We provide various support to customers who are using MCAL for the first time, helping to resolve any questions or concerns during the introduction process. Additionally, we assist in analyzing and resolving any issues customers may be facing. |
| Configuration Setting Support | We support configuration settings to achieve a configuration suitable for your system. |
| Custom Development | We respond to requests for customization, such as adding functions that are not included in the standard MCAL. |
* Targeting the MCAL for RH850/F1Kx, which is provided by Renesas as "Easy to Start". For more information, please visit Renesas' website.
Tools
In order to meet customer requests, our company provides a variety of design and verification tools, including:
- Integrated development environment MULTI
- Helix QAC, a static analysis tool for C language source code (with MISRA-C:2004, 2012, CERT-C options)
- SharedVariableChecker2, an automatic analysis tool for shared variables
- Coverage Master winAMS (with MC/DC option)
- CANalyzer, a testing tool for network and distributed systems (note: CANalyzer is a product of Vector)
- LAN circuit testing and logging tool MLT PX-10 model C2
- Traceability management tool microTRACER
Development Achievements
We have a proven track record in AUTOSAR CP R4.0.3 - R4.3.0. It is also possible to develop software for peripheral control not specified in the specifications as Complex Drivers.
- We have a proven record of success
Microcontroller Drivers
- Core Test
- MCU Driver
- Watchdog Driver
- GPT Driver
Memory Drivers
- Internal EEPROM Driver
- Internal Flash Driver
- RAM Test
- Flash Test
Communication Drivers
- Ethernet Driver
- FlexRay Driver
- CAN Driver
- LIN Driver
- SPI Handler Driver
I/O Drivers
- PORT Driver
- DIO Driver
- ADC Driver
- PWM Driver
- ICU Driver
Other Device Drivers
In addition to MCAL, our company is also able to develop device drivers based on consortium standards and customer requests.
If you have any concerns or issues with microcontroller peripheral control or device control, please don't hesitate to contact us.
If you have any concerns or issues with microcontroller peripheral control or device control, please don't hesitate to contact us.
- Clock / Power Saving Control
- Communication Systems (CAN/LIN/SPI/CXPI/Ethernet, etc.)
- Others (Flash/Timer/AD, etc.)