Druid System Debugger

System Level Debugging
SCIOPTA DRUID is a debugger on system level and is used in addition to a source-lever debugger. It is not replacing the source-level debugger as DRUID gives you another view into a SCIOPTA system on a higher level.

System level debugging with DRUID allows the user to get module and process information, analyse message pools, trace SCIOPTA messages and other kernel events, set watch- and breakpoints on system events and to get other system information from the target system.

DRUID connects to the target system over a separate channel which can be a simple serial line, a TCP/IP ethernet link, a USB interface or a transparent channel of the source-level debugger.

Display Module
Processes can be grouped in SCIOPTA modules, which allows you to design a very modular system.

Module status and information can be displayed in DRUID showing information about the number of processes and message pools and module memory map.

Display Processes
Information about processes in each module can be displayed. This includes address of the PCB (process control block), name, ID, type, state and priority of the processes.
Also information about the stack of all processes is available. Number of bytes of ever used stack, the addresses of the stack, size and the stack pointer are shown.

Display Message Pool
SCIOPTA messages are maintained and managed in message pools. There can be up to 128 pools per module.
DRUID allows to display important information of each message pool. This includes name, pool ID, creator process, start address, pool pointer address, size and unused memory of the pool.

You can also display information about the messages in a specific pool. This includes status, address, message ID, owner, sender, receiver, size and content of all messages in a pool.


Message Trace
Message trace is a strong feature of DRUID. The user can configure target memory to be reserved for message trace. You can setup trace-start and trace-stop conditions and DRUID will trace selected messages between start and stop.

There is a Trace Option List where the user defines what messages to trace. For a receiver or a sender the module or process can be defined. The message ID can be given as a further option.

Running Modes
DRUID can be used when the target system is stopped or even in running target systems.