Introduction
Scope
In this guide we will show you to multiple ways you can configure ISOLAR to be able to run any executable or script either from an accessible location in ISOLAR or how to integrate the tool into the existing RTA-CAR workflow.
Definitions and Abbreviations
BSW: AUTOSAR Basic Software, Hardware independent service layer
RTE: AUTOSAR Run-Time Environment
OS: AUTOSAR Operating System
Confgen: BSW Configuration Generation
Toolchain
It is assumed you are using the RTA-CAR 9.2.1 toolchain
| Tool | Version |
|---|---|
| ISOLAR-AB | v 9.2.1 |
| RTA-RTE | v 7.5.3 |
| RTA-BSW | v 6.1.3 |
| RTA-OS | v 6.2.0 |
It is also expected you are using RTA-OS VRTA port on version 3.0.46. Other versions may be similar but not the same.
For the workflow section of this guide it will be assumed you are working on the latest version of the standard VRTA starterkit: RTA-SK_VRTA_GCC_Standard_9.2.1_R1.
Prerequisites
It is assumed that the reader has good knowledge of AUTOSAR Methodology and Architecture.
External tools Explained
Sometimes, when developing software, tools from multiple vendors and providers are required. The tool "ISOLAR A/B" already provides an environment where you can configure and run all of the tools within the RTA-CAR package, but it also provides methods and workflows to configure and run other tools from other sources.
There are 2 main ways to do this, depending on how you want to integrate the tools into your workflow:
- Configure the tool to be run manually.
- Configure the tool to run automatically as a hook function either before or after the running of an existing RTA-CAR tool. (Version 9.2.0+ only)
Manual Tool Method
Step 1.
Go to Run → External Tools → External Tools Configurations:
Step 2.
Create a new "Program" configuration and configure the Location, Working Directory and Arguments.
Variables
Use the "Variables" button to reuse variables that already exist that describe the project such as the ${PROJ_LOC} variable that stores the absolute location of the current project.
Step 3.
Explore other options that may be useful e.g. refreshing the project after completion. (You will want to use this if your script or executable edits any of the files in the project.)
Hook Function Method
Limitation of RTA-CAR versions
This option is not available for versions before RTA-CAR v9.2.0.
Also, in RTA-CAR v9.2.0, POST_HOOK actions on Confgen are not functional.
Step 1.
Open your projects "Properties" menu.
Step 2.
Navigate to RTA-CAR → User Hooks:
Step 3.
Add a new user hook using the Plus button then configure the Executable Path, Command line arguments, and Environment Variables.
You must configure the hook to be either before or after (PRE_HOOK or POST_HOOK) one of the existing RTA-CAR tools able to be run from ISOLAR.
Hook functions will be seamlessly called either before or after another tool is run, effectively changing what happens when you use the existing functions of ISOLAR. If this is not what you want to happen, please refer to the manual method above.
Be careful that when you configure an external tool to be called from a hook function like this that it is clear to the next person who works on your project that this is what is occurring.
Note that here you cannot use the predefined "Variables" such as ${PROJ_LOC}.
Also note that because the project refreshes after every call of any of the tools, the project will effectively refresh every time the hook is run.