Kernel Awareness for various RTOS

If kernel awareness for an RTOS (Real-time Operating System) is added to HiTOP, the Display objects functionality is brought in.

However, the additional functionality also depends on the RTOS in question and the functionality of the debug system.

This functionality gives you information about the objects of the RTOS and their attributes. Tasks are a good example for objects, because they are normally found in every RTOS. The attributes of task objects are normally at least priority and state (e.g. running, ready, suspended). However, the attributes of a task and the values of the attributes will differ from RTOS to RTOS. For example, one RTOS might have additional attributes like scheduling strategy while another might name the task states differently and still another might have no suspended state at all. This shows that the information given by a display object's functionality depends heavily on the RTOS in question. However, you can expect Hitex RTOS Debug Support to display all objects and all their attributes, even if this requires multiple windows. Additional RTOS Objects may be semaphores, memory regions, alarms, counters, queues, messages, etc.

Display object functionality requires only the most basic features of a debug system, i.e. to read from memory. Display object functionality is therefore present in all RTOS support from Hitex.

This general explanation of Hitex RTOS Debug Support also applies to Hitex OSEK/VDX Debug Support.