What is “T1 for POSIX”?
T1 version 3.2 introduced the support of POSIX operating systems through the add-on product
T1.posix as an extension to T1.timing.
Many operating systems for high-performance computing as well as the AUTOSAR AP standard are based on POSIX.
Key benefits of using T1 for the analysis of posix based systems
Live streaming of scheduling data from the target ECU
The T1-TARGET-SW traces at run-time and transmits the trace data via Ethernet to the
T1-HOST-SW. T1.timing in combinatio with T1.streaming and T1.posix offers the
- The analysis and trace data visualization takes place simultaneously to streaming/recording
data from the target ECU
- Higher resource efficiency due to avoidance of costly file accesses
- Traces of arbitrary lengths
T1 addresses the needs of the automotive
industry by supporting
- Well-known timing results (e.g. CET, DT, RT, ...)
- Visualization of AUTOSAR Deterministic Client Cycles
- Combined and synchronized tracing of AUTOSAR CP/AP ECUs networks
- Synchronized visualization and analysis of both system types in parallel and in the same view
- Event chains (host-side)
- Constraints (host-side)
Unique advantages of the T1 Timing suite compared to other solutions
- Huge benefit in total cost of ownership because of single tooling for AUTOSAR CP/AP ECUs networks
- No need to learn new tools since T1 is widely established in the automotive industry
- One intuitive GUI covers all functionalities of T1.timing, T1.streaming and T1.posix
- Flexible extension of T1 according to customer specific needs through dedicated engineering projects
- Single point of contact for all questions around timing and resource analysis
Features of T1.timing V3.2 with add-on product T1.posixClick on image to enlarge
Live streaming of scheduling data
- zoom in to see... ... detailed state information Graph view: CPU-load, CETs, RTs, DTs etc.Detailed view: colors indicating states of Processes and Threads over time
For POSIX-based projects: what is supported by T1?
For RTOS-based projects, see T1.timing
Supported processors, compilers
Each row in the table below represents one set of T1 libraries specific to a certain processor core and a certain compiler.
| Core || Compiler || Availability|
| Controller Examples|
|Arm||ARMv8-A: Cortex-A5x, Cortex-A7x||GCC||On Request (POSIX)|
|NVIDIA Tegra, NXP S32, TI TDAx, etc.|
|Intel||x86 64-bit||GCC||On Request (POSIX)|
|Intel Atom Denverton, etc.|
|Elektrobit||EB corbos Linux|
|Various Vendors||Embedded Linux (e.g. Yocto), Kernel >= 4.14|
Supported target interfaces
| Target Interface || Comment |
|Ethernet (IP/UDP)||UDP is used, IP-address and port can be configured.|
Requirements regarding the host PC
- Intel i7 or compatible CPU
- SSD drive
- 16GB RAM
Requirements for synchronized traces
- Common (accessible) time-base for all relevant ECUs
- T1 integrated on all relevant ECUs
Features released summer 2020
- Synchronized AP/CP traces
- Host-side constraints
- Host-side event-chains
- Reports generation
- Memory information related to processes/threads
- Message flow analysis (e.g. for QNX)
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.
Interviews on YouTube
Check-out the interviews with GLIWA CEO Peter Gliwa on Matrickz TV. In this
Peter talks with MATRICKZ
CEO Dr. Hasan Akram about timing in automotive software develeopment and in this
one about entrepreneurship.
T1 supports TC39x
Synchronized traces from 6 cores!
T1 makes it happen. Click
, to view a screenshot of T1 with 6 synchronized traces and some cross-core communications.
More details on the AURIX 2G can be found in Infineon's official press-release