AN-ISC-8-1153_ThirdPartyModuless

Third Party Modules

Figure 1 – Overview of BSWMD file of MCU

2.0  Integration in DaVinci Configurator 5
For integration of a module into a MICROSAR stack, different things have to be done.
If the module fulfills one of the following list points, check this chapter for the description.
The module:
•  has parts, generated based on the configuration (i.e. ECUC file)
•  requires the SCHM API for Exclusive Area handling
•  has cyclic MainFunction calls
•  needs access to communication PDUs

2.1  Configuration With CFG5
If the module shall be configured within the CFG5, the tool requires its modules description in a BSWMD file (basis
software module description). Also the module has to be added to the configuration.
2.1.1  Adding of BSWMD File
Provide an additional search path for BSWMD files within your configuration. The BSWMD file must end with
.arxml to be noticed by CFG5.
Open Project|Project Setting|Modules|Additional Definitions and Add the path to the module’s BSWMD file as
shown in the following screenshots.

2
Application Note AN-ISC-8-1153

Third Party Modules

Figure 2 – Modules|Additional Definitions

Figure 3 – BSWMD added

Now the CFG5 knows the module and it can be added to the configuration. But before the configuration has to be
closed and opened again.
2.1.2 Adding a Module to the Current Project
For adding the module to the current configuration, open Project|Project Settings|Modules and Add it with the
blue plus. If the path to the module is within the delivered SIP, you will find it in Select from SIP otherwise in
Select additional definition (see screenshots below).

3
Application Note AN-ISC-8-1153

Third Party Modules

Figure 4 – Module Assistant

Figure 5 – Module Definitions

Now the module is within your project, configure it using the Basic Editor.
2.2 External Generation Step
If the module has parts generated based on the configuration of the ECUC file and the generation shall be started
from the CFG5, the generation list has to be extended. The configuration of the generation steps for third-party
modules can either be done manually or by a configuration file, making it easier to reuse your module for further
projects.

4
Application Note AN-ISC-8-1153

Third Party Modules

2.2.1  Manual Set-Up
Open Project|Project Settings|Code Generation|External Generation Steps and Add the generation settings
using the blue plus.

Figure 6 – External Generation Steps

Specify the module generator settings (i.e. parameters to be handed over). If the module generator also supports
validation or requires a transformation of the input file, this can also be configured. For further information also see
the Help Content of CFG5.
2.2.2  Automatic Set-Up
The settings described in 2.2.1 can also be done automatically by a so-called Settings.xml. For configuration
options of the Settings.xml please refer to 3.0 Settings.xml.
2.3  Internal Behavior Description
Most AUTOSAR modules require Exclusive Area and / or MainFunction handling by the RTE. The MICROSAR
RTE reads this information from the so-called Internal Behavior description, which is a part of a BSWMD file. This
file has to be provided to the CFG5 by placing it into the folder for InternalBehavior files (default is
./Config/InternalBehavior).
The <BSW-IMPLEMENTATION> container within the BSWMD file must have a reference to the Internal Behavior
(i.e. <BEHAVIOR-REF DEST="BSW-INTERNAL-
BEHAVIOR">/VendorX/Mcu_ib_bswmd/BswModuleDescriptions/Mcu/McuBehavior</BEHAVIOR-REF>, see also Figure 1).
The RTE reads the Internal Behavior of the module from this file and provides a solving action to create an
RteBswModuleInstance with this information.
2.3.1  Example for Internal Behavior Description
The following example for an Internal Behavior description defines an exclusive area called MCU_EXCLUSIVE_AREA_0
and a MainFunction called Mcu_MainFunction, which has to be called with a cycle time of 0.01 seconds. The file
should be placed into the folder for InternalBehavior files (default is ./Config/InternalBehavior) or the content can
even be in the BSWMD file itself.

5
Application Note AN-ISC-8-1153

Third Party Modules

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<AUTOSAR xmlns="http://autosar.org/schema/r4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://autosar.org/schema/r4.0 autosar_4-0-3.xsd">
  <AR-PACKAGES>
  <AR-PACKAGE>
  <SHORT-NAME>VendorX</SHORT-NAME>
  <AR-PACKAGES>
  <AR-PACKAGE>
  <SHORT-NAME>Mcu_ib_bswmd</SHORT-NAME>
  <AR-PACKAGES>
  <AR-PACKAGE>
  <SHORT-NAME>BswModuleDescriptions</SHORT-NAME>
  <ELEMENTS>
  <BSW-MODULE-DESCRIPTION>
  <SHORT-NAME>Mcu</SHORT-NAME>
  <PROVIDED-ENTRYS>
  <BSW-MODULE-ENTRY-REF-CONDITIONAL>
  <BSW-MODULE-ENTRY-REF DEST="BSW-MODULE-
ENTRY">/VendorX/Mcu_ib_bswmd/BswModuleDescriptions/Mcu_MainFunction</BSW-MODULE-ENTRY-REF>
  </BSW-MODULE-ENTRY-REF-CONDITIONAL>
  </PROVIDED-ENTRYS>
  <INTERNAL-BEHAVIORS>
  <BSW-INTERNAL-BEHAVIOR>
  <SHORT-NAME>McuBehavior</SHORT-NAME>
   <EXCLUSIVE-AREAS>
  <EXCLUSIVE-AREA>
  <SHORT-NAME>MCU_EXCLUSIVE_AREA_0</SHORT-NAME>
  </EXCLUSIVE-AREA>
  </EXCLUSIVE-AREAS>
  <ENTITYS>
  <BSW-SCHEDULABLE-ENTITY>
  <SHORT-NAME>Mcu_MainFunction</SHORT-NAME>
  <IMPLEMENTED-ENTRY-REF DEST="BSW-MODULE-
ENTRY">/VendorX/Mcu_ib_bswmd/BswModuleDescriptions/Mcu_MainFunction</IMPLEMENTED-ENTRY-REF>
  </BSW-SCHEDULABLE-ENTITY>
  </ENTITYS>
  <EVENTS>
  <BSW-TIMING-EVENT>
  <SHORT-NAME>Mcu_MainFunctionTimingEvent0</SHORT-NAME>
  <STARTS-ON-EVENT-REF DEST="BSW-SCHEDULABLE-
ENTITY">/VendorX/Mcu_ib_bswmd/BswModuleDescriptions/Mcu/McuBehavior/Mcu_MainFunction</STARTS-ON-EVENT-REF>
  <PERIOD>0.01</PERIOD>
   </BSW-TIMING-EVENT>
  </EVENTS>
  </BSW-INTERNAL-BEHAVIOR>
  </INTERNAL-BEHAVIORS>
  </BSW-MODULE-DESCRIPTION>
  <BSW-MODULE-ENTRY>
  <SHORT-NAME>Mcu_MainFunction</SHORT-NAME>
  <CALL-TYPE>SCHEDULED</CALL-TYPE>
  <EXECUTION-CONTEXT>TASK</EXECUTION-CONTEXT>
  </BSW-MODULE-ENTRY>
  </ELEMENTS>
  </AR-PACKAGE>
  </AR-PACKAGES>
  </AR-PACKAGE>
  </AR-PACKAGES>
  </AR-PACKAGE>
  </AR-PACKAGES>
</AUTOSAR>

2.3.2  Templates for Internal Behavior Description
Some modules provided by a MICROSAR delivery are not developed by Vector and do not have an automatic
Internal Behavior creation (i.e. MCALs). For easier integration some of them provide templates for the Internal
Behavior description. If these files are available within the current delivery they are positioned at
.\Misc\InternalBehaviorTemplates. Please remove the starting ‘_’ marking the files as templates, copy them to the

6
Application Note AN-ISC-8-1153

Third Party Modules

InternalBehavior folder of your project and adapt them to your configuration (i.e. changing the cycle time of the
MainFunction).
2.4 RTE configuration
If the Internal Behavior is configured as described in 2.3 the RTE will provide a solving action to automatically
create the required RTE configuration. If a MainFunction has to be called by the RTE, perform the according Task
Mapping afterwards. The RTE will then generate the Exclusive Area and MainFunction calls as described in the
Internal Behavior.
2.5 CDD Configuration
For your own modules that need access to any PDU within the communication stack, use the so-called CDD
module (Complex Device Driver), which is part of the SIP. For adding the CDD to the current configuration, open
Project|Project Settings|Modules and Add it via the blue plus.

Figure 7 – Module Definitions CDD

In the Basic Editor you can define, where the CDD shall be placed within the communication stack.

Figure 8 – Configuring CDD

For further information how to configure the CDD, please refer to its Technical Reference
(TechnicalReference_Asr_CddCfg5.pdf).

7
Application Note AN-ISC-8-1153

Third Party Modules

3.0  Settings.xml
The Settings.xml is an open interface to the CFG5. With this file the following configuration can be done:
•  Settings for external validation and generation steps

The file shall be placed to .\DaVinciConfigurator\Generators\<Msn> (i.e.
C:\Vector\CBD1200333_D02_V85x\DaVinciConfigurator\Generators\Mcu\Settings_ExtGen_Mcu.xml) and is
automatically known at start of the CFG5.
The following example creates the same generator settings as the example in 2.2.1.

<Settings>
  
  <Settings Name="com.vector.cfg.gui.core.generators.ExtGenSteps">
  <Settings Name="ExtGenSettings_DrvMcu">
  <Setting Name="Active" Value="true"/>
  <Setting Name="CommandLine" Value="C:\Vector\CBD1200333_D01_V85x_AddOn\Mcu\Mcu.exe"/>
  <Setting Name="GenerationParameters" Value="$(GenDataFolder) $(ProcessingEcuCFile) --generate"/>
  <Setting Name="SupportsStandAloneValidation" Value="true"/>
  <Setting Name="ValidationParameters" Value="$(GenDataFolder) $(ProcessingEcuCFile) --validate"/>
  <Setting Name="TransformationRequired" Value="false"/>
  <Setting Name="TransformationXsltFile" Value=""/>
  <Setting Name="TransformationOutput" Value=""/>
  <Setting Name="WorkingDir" Value="C:\Vector\CBD1200333_D01_V85x_AddOn\Mcu"/>
  <Setting Name="SpecificAsVersionRequired" Value="true"/>
  <Setting Name="RequiredAsVersion" Value="4.0.3"/>
  </Settings>
  </Settings>
</Settings>

4.0  Integration Into the Build Project
AUTOSAR has introduced a mechanism to integrate standardized code into different µC and Compilers. To adapt
the modules into a project with specific compiler and linker settings the files MemMap.h and Compiler_Cfg.h have
been introduced. If the module that shall be integrated into a build project that makes use of those mechanisms,
these files have to be adapted.
For further information on this topic please also refer to TechnicalReference_Asr_MemoryMapping.pdf within the
SIP.

Example code for the following chapters:
#define MCU_START_SEC_VAR_INIT_8BIT
#include "MemMap.h"

VAR (uint8, MCU_INIT_DATA) Mcu_InitStatus = 0;

#define MCU_STOP_SEC_VAR_INIT_8BIT
#include "MemMap.h"

#define MCU_START_SEC_PUBLIC_CODE
#include "MemMap.h"

FUNC(void, MCU_PUBLIC_CODE) Mcu_Init (P2CONST(Mcu_ConfigType, AUTOMATIC, MCU_APPL_CONST) ConfigPtr)
{
…
}

#define MCU_STOP_SEC_PUBLIC_CODE
#include "MemMap.h"

8
Application Note AN-ISC-8-1153

Third Party Modules

4.1  Compiler_Cfg.h
Add all used compiler abstraction defines from your module to this file, even if they are defined to nothing.
Required Compiler_Cfg.h content for above given example:
#define MCU_PUBLIC_CODE
#define MCU_APPL_CONST
#define MCU_INIT_DATA
4.2  MemMap.h
Add all used memory abstraction defines from your module to this file.
Required MemMap.h content for above given example:
#ifdef MCU_START_SEC_VAR_INIT_8BIT
  #undef MCU_START_SEC_VAR_INIT_8BIT
  #define START_SEC_VAR_INIT_8BIT
#endif
#ifdef MCU_STOP_SEC_VAR_INIT_8BIT
  #undef MCU_STOP_SEC_VAR_INIT_8BIT
  #define STOP_SEC_VAR
#endif

#ifdef MCU_START_SEC_PUBLIC_CODE
  #undef MCU_START_SEC_PUBLIC_CODE
  #define START_SEC_CODE
#endif
#ifdef MCU_STOP_SEC_PUBLIC_CODE
  #undef MCU_STOP_SEC_PUBLIC_CODE
  #define STOP_SEC_CODE
#endif

9
Application Note AN-ISC-8-1153

Third Party Modules

5.0  Additional Resources
VECTOR TECHNICAL REFERENCES
TechnicalReference_Asr_MemoryMapping.pdf
TechnicalReference_Asr_CddCfg5.pdf

6.0  Contacts

Germany
France, Belgium, Luxemburg:
Sweden, Denmark, Norway,
and all countries not named below:

Finland, Iceland:

Vector Informatik GmbH
Vector France S.A.S.
VecScan AB
Ingersheimer Str. 24
168, Boulevard Camélinat
Theres Svenssons Gata 9
70499 Stuttgart
92240 Malakoff
41755 Göteborg
GERMANY
FRANCE
SWEDEN
Phone: +49 711-80670-0
Phone: +33 1 42 31 40 00
Phone: +46 31 764 76 00
Fax:  +49 711-80670-111
Fax:  +33 1 42 31 40 09
Fax:  +46 31 764 76 19
E-mail:  info@de.vector.com
E-mail:  information@fr.vector.com
E-mail:  info@se.vector.com



United Kingdom, Ireland:
China:
India:

Vector GB Ltd.
Vector Automotive Technology
Vector Informatik India Pvt. Ltd.
Rhodium, Central Boulevard
(Shanghai) Co., Ltd.
4/1/1/1, Sutar Icon, Sus Road,
Blythe Valley Park
Sunyoung Center
Pashan, Pune - 411 021
Solihull, Birmingham
Room 1701, No.398 Jiangsu Road
INDIA
West Midlands B90 8AS
Changning District

UNITED KINGDOM
Shanghai 200050

Phone: +44 121 50681-50
P.R. CHINA
Phone: +91 20 2587 2023
Fax:  +44 121 50681-69
Phone: +86 21 6432 53530
Fax:   +91 20 2587 2025

Fax:   +86 21 6432 5308

E-mail:  info@uk.vector.com
E-mail: info@cn.vector.com
E-mail: info@in.vector.com

USA, Canada, Mexico:
Japan:
Korea:

Vector CANtech, Inc.
Vector Japan Co. Ltd.
Vector Korea IT Inc.
39500 Orchard Hill Place, Suite 550
Tennozu Yusen Bldg. 16F
5F, Gomoas bldg.
Novi, MI 48375
2-2-20 Higashi-shinagawa,
12 Hannam-daero 11-gil, Yongsan-gu
USA
Shinagawa-ku,
Seoul, 140-889

Tokyo 140-0002
REPUBLIC OF KOREA

JAPAN

Phone: +1 248 449 9290
Phone: +81 3 5769 7800
Phone: +82 2 807 0600
Fax:  +1 248 449 9704
Fax:  +81 3 5769 6975
Fax:  +82 2 807 0601
E-mail:  info@us.vector.com
E-mail:  info@jp.vector.com
E-mail:  info@kr.vector.com

10
Application Note AN-ISC-8-1153

Document Outline

Last modified July 6, 2025: Initial commit (97b4320)