Setting up winIDEA SWAT for ETAS RTA-CAR (AUTOSAR)
In this topic:
•Step 1: Configure iTCHi Wizard
•Step 3: Integrate and rebuild the code
•Step 4: Configure winIDEA Analyzer
Introduction
This section describes how to integrate SWAT into an application and configure winIDEA Analyzer.
Setup scenario follows the workflow:
•configure iTCHi
•add observe/instrumentation points
•allocate SWAT buffer
•integrate & rebuild
•configure winIDEA
Prerequisites
1. Enable ORTI and OS hooks in RTA-CAR
a. Open ISOLAR-B and load your RTA-CAR project.
b. Open the BSW Editor for the OS.
c. Enable the ORTI file generation by setting the parameter value for Orti23Lauterbach (parameter definition: /AUTOSAR_Os/EcucModuleDefs/Os/OsRTATarget/Param/Orti23Lauterbach) to true.
d. Enable the OS hooks need to be enabled by Set the parameter value to true and thus enable the OS hooks:
•OsPreTaskHook
oparameter definition: /AUTOSAR_Os/EcucModuleDefs/Os/OsOS/OsHooks/OsPreTaskHook
•OsPostTaskHook
oparameter definition: /AUTOSAR_Os/EcucModuleDefs/Os/OsOS/OsHooks/OsPostTaskHook
•isr_lifetime_hooks
oparameter definition: /AUTOSAR_Os/EcucModuleDefs/Os/OsOS/Param/isr_lifetime_hooks
The OS can signal the start and the stop of a task or category 2 ISR execution via hook functions.
e. Invoke the OS code generator after you have applied the changes in the OS configuration.
2. Enable VFB trace hooks in RTA-CAR
a. Open ISOLAR-B, load your RTA-CAR project and open the BSW Editor for the RTE.
b. Set the RteVfbTraceEnabled (parameter definition: /AUTOSAR_Rte/EcucModuleDefs/Rte/RteGeneration/RteVfbTraceEnabled) to true.
c. For each entity configure the <entityName>_Start und <entityName>_Return function for RteVfbTraceFunction (parameter definition: /AUTOSAR_Rte/EcucModuleDefs/Rte/RteGeneration/RteVfbTraceFunction).
d. Invoke the RTE code generator after you have applied the changes in the RTE configuration.
Step 1: Configure iTCHi Wizard
a. To generate the required files, use the iTCHi Wizard and configure the following parameters:
•iTCHi Configuration file - Path to the file which is used to load/save iTCHi configuration
•ORTI file location - Path to the ORTI file generated from the ETAS RTA-OS generator (in the ETAS RTA-CAR Starter Kit (RTA-SK), the ORTI file is located in /RTA-SK/Target_specific/RTA-SK/Os/src/RTAOS.orti)
•Profiler XML file location - Path where Profiler configuration should be written into
•Commands
oEnable TASK/ISR (Thread) Tracing if you want to profile the OS - Select task_state_swat_rtacar
oEnable Runnable Tracing if you want to profile the Virtual Functional Bus (VFB) - Select runnable_swat
b.On the next page, the following parameters need to be configured:
•as described in Configure SWAT parameters in iTCHi (bare metal example).
•task_state_inst_rtacar
oetas_os_hooks_c: C file which into which iTCHi generates the OS hook implementations
•runnable_instrumentation
orte_arxml - Path to the Rte EcuC file in which the Rte configuration is stored (in the ETAS RTA-CAR Starter Kit (RTA-SK), the Rte EcuC file is located in /RTA-SK/ecu_config/rte/internal/Rte_EcucValues.arxml)
orte_stack_supplier - Needs to be set to etas.
oimpl_vfb_hooks_c - C file which into which iTCHi generates the VFB hook implementations
Step 2: Allocate SWAT buffer
Follow these steps for bare metal example.
Step 3: Integrate and rebuild the code
Follow these steps for bare metal example, except for this:
If the build environment from the ETAS RTA-CAR Starter Kit (RTA-SK) is used, the following steps are applicable to add the additional files into the build environment:
1. Add the directory name containing the SWAT target code and the generated iTCHi files in the Python script /Compiler_specific/Scripts/genCMake.py (CMakeLists.txt will be created out of it):
# List of directories to search for C files
srcDirs = ["../../RTA-SK/Target_specific/SWAT", "<other directories>"] # Please adjust the directory name according to your project needs
The build environment will consider
•all source files located in the directory and all subdirectories.
•directories containing header files as include directories.
2. Execute the script /Compiler_specific/build.bat.
Step 4: Configure winIDEA Analyzer
Follow these steps for bare metal example.
More resources
