Gliwa-Logo
Weisse Spuren
Surprisingly different, surprisingly effective ./design2013/header-t1-4_web.png
accPredLogo

T1.accessPredictor makes it possible to detect access violations before the software runs on the target hardware


Upset by MPU exceptions in the field? Tracking them down while the software executes can be very time consuming and costly. T1.accessPredictor allows you to check for any memory access violations before even flashing the software. Think of it as an “off-line MPU”.
binaryOnlyaccessPredictor

Analyzing the binary rather than the source code has significant advantages.

  • It is a long way from the source code to the binary and assuming that no additional accesses were injected by the compiler and linker is a critical assumption in a safety-relevant context.
  • C source analysis also omits any assembler code.
  • What’s more today’s ECUs incorporate software components from various parties. None of them has a full view on 100% of the sources so a complete analysis is impossible when performing source code analysis.

Zitat

Using T1.accessPredictor is very simple; there are only a few steps to take


Step 1: Specify the different access classes using the intuitive GUI and define in which way (Read, Write and eXecute) every class may access the other classes. “Execute” refers to code accesses such as function-calls. In the example on the right, four access-classes were defined: ASIL_A, ASIL_D, QM and Flash.

Click on image to enlarge
access predictor Step 1
Step 2: Read in the binary, the ELF file. T1.accessPredictor will disassemble the binary and perform a static analysis based on abstract interpretation. Afterwards T1.accessPredictor presents a “bi-directional” call-tree indicating a) which function calls which other functions and b) by which other functions a function gets called.
Step 3: If necessary, add annotations (manually, generated or measurement-based) to complete the call-tree.
Step 4: Analyze the results! The call-tree indicates access violations with red exclamation marks: for invalid data accesses and for invalid code accesses.

Click on image to enlarge
accPred_04

Step 5 (optional): Export the results for regression tests for subsequent software releases.


Supported processors


Silicon/IP
Vendor
Core Controller Examples
InfineonTC1.6.XTC2xx, TC3xx
NXP/STMe200z0-z4, z6, z7MPC57xx, MPC56xx, MPC55xx, SPC58, SPC57, SPC56, etc.
NXP/STMe200z2, z4, z7MPC57xx, MPC56xx, MPC55xx, SPC58, SPC57, SPC56, etc.
Newsbox Oben
HOT TOPICS
Message from our CEO
Learn what impact COVID19 has on GLIWA. And please let us know if we can help with temporary licenses for example.

Peter Gliwa message

Interviews on YouTube
Check-out the interviews with GLIWA CEO Peter Gliwa on Matrickz TV. In this one Peter talks with MATRICKZ CEO Dr. Hasan Akram about timing in automotive software develeopment and in this one about entrepreneurship.

Interview

T1 supports TC39x
Synchronized traces from 6 cores!
T1 makes it happen. Click here, to view a screenshot of T1 with 6 synchronized traces and some cross-core communications.

AURIX TC399

More details on the AURIX 2G can be found in Infineon's official press-release.
Newsbox Unten