Usage

There are a couple of ways how SWART can be used over command line interface:

• Software analysis without using already created Project
• Software analysis using already created Project
• Reporting using specific Snapshot
• Software analysis using Tasking utility tool and Reporting with groups file provided

For every use case valid License should be active.

Flags

 -a – perform Analysis

use with one of the following options:

• m – Memory Analysis – Performs only memory analysis. Must be used with Fast Memory Report option. In other cases invalid.
• s – Snapshot Analysis
• p – Snapshot Analysis but using existing project file for inputs

Example – Perform Analysis

-a s

-elf – path to elf file

Example – Elf path

-elf "D:/pathToElfLocation/Software-Application.elf"

-hwres – path to hardware resource file

Example – Hardware Resources path

-hwres "D:/pathToHardwareResourcesLocation/aurix-tc377-resources.txt"

-al – path to project architecture layout file

Example – Architecture Layout path

-al "D:/pathToArchitectureLayout/tricore_tc3xx_layout.txt"

-arch – path to project architecture file

Example – Architecture path

-arch "D:/pathToArchitecture/tricore_tc3xx_arch.txt"

-r – reporting – hex value; need to be used with -rout flag

Option that can be used with m option for Analysis flag:

• Fast Memory Report = 1

Options that can be used with s and p options for Analysis flag:

• Hardware Memory Report = 2
• Components Memory Report = 4
• Interfaces Report = 8
• Components Memory Over Budgets = 16
• Components Overview = 32
• Components Groups Overview = 64 (NOTE: must be used with -g flag, otherwise it will not be generated)

as 4 lower nibble (defines which report to create), and:

• TXT = 1
• CSV = 2

as 4 higher nibble (defines format for reporting)

Example – Reports (Components Memory & Hardware Memory Reports in CSV format)

-r 0x20006

-rout – location where to save reports – NOTE: need to be used with -r flag

Example – Reports location

-rout "D:/pathToReports/reports/"

-o – snapshot output location

Example – Snapshot output location

-o "D:/pathToOutput/out/"

-t – temp location

Example – Temporary files location

-t "D:/pathToTempFolder/temp/"

-l – logs location

Example – Logs location

-l "D:/pathToLogs/logs/"

-n – project name – used in Architecture tag in xml

Example – Custom Project name

-n "AurixProject"

-s – snaphost image file to load – use to generate reports from a snapshot. Ignored flags: -a, -elf, -hwres, -arch, -t, -l, -n

Example – Snapshot Image location

-s "D:/pathToSnapshots/2021-08-06T10-29-05-43/2021-08-06T10-29-05-43.ssi"

-proj – project file location – used with analysis option ‘p’

Example – Project location

-proj "D:/pathToProjectFile/AurixProject.json"

-f – new project file location – used with analysis option ‘s’ to get also project file

Example – New project file location

-f "D:/pathToNewProjectFile/NewAurixProject.json"

-m – specify how much memory in MB should be allocated for JS execution (optional, if not set use default value of 10240MB)

Example – Specify memory usage for JS execution

-m 10240

-u – location of Tasking utility tool (used in fast analysis with Tasking compiler)

Example – Tasking utility tool

-u "D:/pathToBinary/hldumptc.exe"

-g – path to groups file used in reporting for components groups overview

Example – Groups file

-g "D:/pathToGroupsFile/groups.xml"

Examples

Software analysis without using already created Project

Reporting: Hardware Memory Report and Components Memory Report in csv

Analysis: Snapshot Analysis

Project name: DummyMcuProject (used as a name in Snapshot Architecture xml tag)

New Project file: NewDummy.json

Set custom paths for resources such as elf file, hardware resources file, etc etc

-r 0x20006
-rout "D:/pathToReportsOut/reports/"
-a s
-elf "D:/pathToElf/Software_Application.elf"
-hwres "D:/pathToHardwareResources/aurix-tc377-resources.txt"
-o "D:/pathToOutput/"
-t "D:/pathToTemporaryFiles/"
-l "D:/pathToLogs/"
-arch "D:/pathToArhictecture/tricore_tc3xx_arch.txt"
-n DummyMcuProject
-f "D:/pathToNewProjectFile/NewDummy.json"

Software analysis using already created Project

Reporting: Hardware Memory Report and Components Memory Report in csv

Analysis: Snapshot Analysis using existing project file

-r 0x20006
-rout "D:/pathToReportsOut/reports/"
-a p
-proj "D:/pathToProjectFile/Dummy_proj.json"

Reporting using specific Snapshot

Reporting: Hardware Memory Report and Components Memory Report in csv

Snapshot image to load: 2021-08-06T10-29-05-43.ssi

-r 0x20006
-s "D:/pathToSnapshotImage/2021-08-06T10-29-05-43/2021-08-06T10-29-05-43.ssi"
-rout "D:/pathToReportsOut/reports/"

Software analysis using Tasking utility tool and Reporting with groups file provided 

Reporting: Components Groups Overview Report and Hardware Memory Report in txt and csv

Analysis: Snapshot Analysis

Project name: DummyMcuProject (used as a name in Snapshot Architecture xml tag)

New Project file: NewDummy.json

Set custom paths for resources such as elf file, hardware resources file, etc etc

-r 0x30042
-rout "D:/pathToReportsOut/reports/"
-a s
-elf "D:/pathToElf/Software_Application.elf"
-hwres "D:/pathToHardwareResources/aurix-tc377-resources.txt"
-o "D:/pathToOutput/"
-t "D:/pathToTemporaryFiles/"
-l "D:/pathToLogs/"
-arch "D:/pathToArhictecture/tricore_tc3xx_arch.txt"
-n DummyMcuProject
-f "D:/pathToNewProjectFile/NewDummy.json"
-u "D:/pathToBinary/hldumptc.exe"
-g "D:/pathToGroupsFile/groups.xml"