Embedded UML Target Debugger

The Embedded UML Target Debugger is a product developed by Willert Software Tools GmbH. It allows you to analyze the software behavior on target. This is similar to a conventional high level language debugger, but on UML level. This includes:

live animation of sequence diagrams to trace the event order and state changes on target
live animation of embedded timing diagrams showing the events and state changes on a tick timer granularity timeline
see which instances of your reactive objects (with a statechart) have been created and destroyed
navigate through a model element tree to show attributes or the current state of a statechart for any instance
display the current values of the highwatermarks when used with the OORTX
inject events from the host-side and track the reaction of the target (currently only events without arguments are supported)
see timeouts events which have elapsed on target in the diagrams
monitor the elapsed time-ticks between two events

It consists of a Windows application which let you control the debugging and see the feedback from target and a monitor solution which is part of the executable on target.

The Embedded UML Target Debugger has been designed with a minimal overhead in footprint and disturbance of the behaviour of your model in mind. Therefore, most of the work is done at runtime on your PC and as little as possible on your target. On the PC, you can view an animated sequence diagram of your target live. The target only sends very short messages when objects are created, destroyed or events are being send. It also can react to commands from the host. The messages and commands never contain symbolic data, but only memory addresses or identification codes to keep the data size small. This requires:

Information used at startup of the Embedded UML Target Debugger on your PC. This information is stored in an XML file called XMLData.xml. This file is created at the end of the building process in your IDE. It uses the map file (to resolve memory addresses for the target) and Rhapsody generated source files (which objects, attributes and states are used).
Information send from the target, like which object has been created or destroyed, which event is send etc. For sending information and receiving commands from the Embedded UML Target Debugger on the PC, we need some interface. This can be a serial interface but also CAN, JTAG or whatever I/O interface can be used. For this example, we are working with a serial interface. but other interfaces are available and you are free to implement whatever I/O you like.