Arctic Studio BSW Builder

From Arctic Core - the open source AUTOSAR embedded platform

Installing

To install BSWBuilder, to your Arctic Studio see http://www.arccore.com/products/request-trials/

Activation

In order to use the BSW Builder you need to activate the software. The first time you open a BSW Builder editor (after Creating an ECU Configuration below) you will get to the Registration page. The instructions on that page will tell you how to send a registration request mail, in order to receive your activation license key. When you receive the key you return to the Registration page to install it. After a re-start of Arctic Studio, your BSW Builder is activated.

Getting started

Getting Arctic Core Source Code

See Clone Arctic Core for instructions on cloning the Arctic Core repository.

Creating a Project

To create a new project connected to the Arctic Core build system, please follow the steps below:

Select File --> New --> C Project.
Enter a Project name.
In Project type, select Empty Arctic Core Project
In Toolchains, select Arctic Studio Cygwin Toolchain and click Next.
Set Arctic Core source path to point at the root of your Arctic Core source tree in your workspace, and click Finish.

Creating an ECU Configuration

To create a new configuration file and open the BSW Builder, please follow these steps:

Select File --> New --> Other....
Select New Ecu Configuration and click Next.
Enter a Configuration name and select a Parent folder.
Select the MCU type that this configuration is for. (Selecting Undefined MCU will let you configure HW-independent modules without having to select a HW platform)
Click Finish.

BSW Builder Basics

This section will let you get started creating configurations.

Opening a ECU Configuration .arxml file brings up the BSW Builder and shows the ECU Configuration Overview page. This page contains configuration information such as revision, author, copyright, selected MCU and code generator output directory. It also has an overview of the modules contained in the configuration.

Populating the Configuration

To add modules click Add... and select one or more modules to add.
To edit the configuration for a module just double-click it in the Modules Overview. This brings up the configuration page for the specific module.
The list of modules is also accessable in the Arctic Studio Outline view.
Most modules have one or a few sections for global properties, and one section for defining module entities (PDUs, Controllers, Pins etc.). To add module entities, use the links to the right of the entities tree view or right click in the view to access the context menu. The entities are often collected in groups and many can have children. The editor shows which entities can be added where by enabling/disabling the corresponding add links.
To edit the properties of an entity, just select it in the tree view and its details are shown on the right.

Validation

Whenever a value is changed or a new entity is created, the entire configuration is checked for errors.
When an erroneous value is detected, its control on the page is marked with an error marker.
Configuration problems for each module are shown in the title-bar on the corresponding module page, and a complete list of problems is available in the title-bar of the ECU Configuration Overview.
Configuration problems are also available in the Arctic Studio Problems view.

Code Generation

Code generation of configuration .c and .h files is initiated by clicking the Generate button located in the top right corner on all pages. From the ECU Configuration Overview you can run code generation for the entire ECU configuration, and from each module page you have the additional option to generate only the configuration for the current module.
No errors may exist in the configuration for the code generation to proceed.
Files are generated into the directory selected in Generator output directory on the ECU Configuration Overview page.
Validation and generation can be disabled on module basis using the check-boxes in the Modules overview on the ECU Configuration Overview page.

Tips & Tricks

Compare models

The standard diff tool is not very well suited for comparing data in xml format such as the ECU configuration arxml files. The situation arises for instance whenever you are merging updates from versioning systems, or just want to compare the contents of two local files. To enable a better way for comparing these files, called EMF Compare, that comes bundled with BSW Builder, just follow these steps:

Go to the Arctic Studio preferences via Window --> Preferences
Go to the page General/Content Types
Under the Content type EMF Compare, click Add...
Enter *.arxml and click OK

Now EMF Compare will open as your default compare editor for arxml files. To try it out, right-click an arxml file in your Project Explorer and click Compare With --> Local History...