| OSEK/VDX - Open systems and the corresponding interfaces for automotive electronics |
The goal of the OSEK/VDX initiative is to establish an standard for the architecture of distributed control units in the automotive area.
Hitex is member of the Technical Committee of OSEK/VDX. Hitex actively takes part in the specification of an OSEK/VDX Debug Interface by contributing to the relevant OSEK/VDX Working Group.
The official home of OSEK/VDX is http://www.osek-vdx.org.
OSEK/VDX Debug Support by Hitex
From the very beginning, Hitex participated in the work for a standardized method to debug OSEK/VDX-compliant operating systems from different vendors. Resulting from that, HiTOP from Hitex was the first debugger featuring kernel awareness for an OSEK/VDX-compliant operating system based on a method using a file, the so-called ORTI file. Currently, this method is the de-facto standard for OSEK/VDX debugging and faces its standardization by the OSEK/VDX Debug Interface Working Group. Since Hitex is participating in that working group, Hitex will always be on the edge of development and conform to the latest specifications.
OSEK/VDX Debug Support by Hitex gives you basically the same features (Display Objects, Event Trace and Task Specific Breakpoints) as for the usual RTOS Debug Support by Hitex. However, since memory usage in OSEK/VDX systems is always a theme, special features allow for checking the spare stack memory.
