|
Surprisingly different,
surprisingly
effective
![]() |
![]() T1.accessPredictor makes it possible to detect access violations before the software runs on the target hardwareUpset 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”. ![]() ![]() Analyzing the binary rather than the source code has significant advantages.
![]() Using T1.accessPredictor is very simple; there are only a few steps to take
![]() 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 ![]() Step 5 (optional): Export the results for regression tests for subsequent software releases. Supported processors
| ![]()
|
||||||||||||
| |
|