aiT for TriCore statically computes tight bounds for the worst-case
execution time (WCET) of tasks in real-time systems. It directly analyzes
binary executables and takes the intrinsic cache and pipeline behavior
- aiT-computed bounds are extremely tight
and thus reflect the actual performance of your system.
Ensuring deadline adherence is not done at the expense of hardware resources.
- aiT-computed bounds are valid for all inputs and
each execution of a task. Extensive timing testing is a thing of the past.
- aiT directly analyzes binary executables. It is widely independent of
the compiler and source code language used. This means no modification
of your toolchain or the system’s operational behavior and performance
- TASKING C Compiler
- HighTec GCC
- NEW: Diab (WindRiver)
Supported processor derivates
- TriCore 1197
- TriCore 1767
- TriCore 1782
- TriCore 1784
- TriCore 1796
- TriCore 1797
- AURIX: TC275 and TC277
- NEW: AURIX 2nd GEN: TriCore 367, 377, 387, 389, and 397
- Windows: 64-bit Windows 7 SP1 or newer
- Linux: 64-bit CentOS/RHEL 7 or compatible
- 4 GB of RAM (16 GB recommended)
- 4 GB of disk space
- The Linux version requires the
libxcb-* family of libraries to be installed
- Support for macOS High Sierra 10.13 or newer is possible on request for a surcharge
Integration with ASCET
aiT for TriCore supports tight integration with ASCET,
the state-of-the-art model-based ECU software development environment from ETAS.
You can start aiT directly from the ASCET project editor menu
to perform a WCET analysis of the automatically generated ECU code.
Free trial versions are available for TriCore microcontrollers with
the ERCOSEK or RTA-OSEK operating systems.