Select View → Process Control to display the Process Control pane if it is not visible in your Code window. The following sections describe the OS marker details:
If HSD or RSD is enabled, the Process tab contains the OS marker, shown in Figure 15.14. This is the initial state with no image loaded.
In this state, neither the Thread tab nor the Cycle Threads button is available.
With an RTOS-enabled image loaded (thr_demo.axf)
but not running, the Process tab contains
the OS marker, shown in Figure 15.15.
Figure 15.15 shows a debug target where RealView Debugger has located the RTOS using the RTOS plugin. Although a suitable RTOS-enabled image has been loaded to the target, RealView Debugger has not detected that the RTOS has started.
In this state, neither the Thread tab nor the Cycle Threads button is available.
Figure 15.16 shows a running target where RealView Debugger has detected that a suitable RTOS-enabled image has been loaded to the target and threads are being rescheduled.
In this state, the Thread tab is available and the Cycle Threads button is enabled on the Connect toolbar.
Table 15.1 describes OS marker status in the Process Control pane.
Table 15.1. OS marker status in the Process Control pane
| Status | Meaning |
|---|---|
| NOT INITIALIZED | HSD or RSD is enabled but the triggering event
that loads the plugin, the *.dll file, has
not occurred. |
| HSD (PENDING) | The plugin has been loaded and RealView Debugger is waiting for it to determine that the RTOS has been found. |
| HSD (PENDING OS) | The plugin has found the RTOS but the process is not yet in a state where threads are being rescheduled. |
| HSD | HSD is fully operational. |
| HSD (RUNNING) | The system is running when RSD is disabled. This means that no up-to-date information about the RTOS can be shown. This value is never shown when RSD is enabled. |
| RSD (PENDING DA) | RealView Debugger is waiting for notification that a Debug Agent has been found. |
| RSD | RSD is fully operational. |
| HSD (RSD STOPPED) | RealView Debugger has changed from RSD to HSD debugging mode. This is usually because an HSD breakpoint or processor stop command has been performed. HSD is now available. |
| HSD (RSD INACTIVE) | RSD was operational or pending but is now disabled. This occurs only by a user request. HSD is now available. |
| HSD (RSD DEAD) | RSD was operational but is now disabled. This is usually because the Debug Agent is not responding to commands or the RTOS has crashed. HSD is now available. |
| RSD DEAD | RSD was operational but is now disabled. The debug target is still running. HSD is not available. |
| RSD (PENDING SYMBOLS) | RSD is operational, contact to the Debug Agent has been established but no symbols have been loaded. This means that RSD only works partially until the symbol table is loaded. This usually occurs after connecting to a debug target that is already running the Debug Agent. |
The OS marker is usually shown in black text in the Process tab. Where the marker is shown in red, either RTOS support is not ready, as shown in Figure 15.15, or there has been an error.
Right-click on the OS marker to see the context menu where you can control RSD:
- Disable RSD
Depending on the current mode, this option enables or disables RSD. For more details on how to control RSD, see the RSD menu described in Resource Viewer window interface components.
The initial state depends on the
RSDsetting in theRTOSgroup in the board file, or.bcdfile where available. See Configuring an RTOS-enabled connection without a vendor-supplied .bcd file for details.- Stop Target Processor
Stops the target processor and suspends RSD. Depending on your configuration settings, click the Go button to start execution and restart RSD.
- Properties
Select this option to see details about the Debug Agent. This includes the status of the RSD module, settings as specified in your board file (or
.bcdfile where available), and RSD breakpoints. For an example, see More on breakpoints.
PDF version