To use SystemView the SystemView target module has to be included in the target application and the OS needs to be instrumented. SystemView can also be used with a non-instrumented OS or without any OS at all.
For a detailed description of the target implementation, please refer to the SystemView User Manual UM08027.
SEGGER embOS (V4.12a and later) can generate trace events for SystemView and other recording implementations when profiling is enabled. Profiling is enabled in the OS_LIBMODE_SP, OS_LIBMODE_DP and OS_LIBMODE_DT embOS library configurations (For detailed information refer to the embOS User Manual UM01001).
In addition to the SystemView and RTT core module, SEGGER_SYSVIEW_Config_embOS.c needs to be included in the application. This file allows configuration to fit the target system, like defines for the application name, the target device and the target core frequency. It initializes the SystemView module and configures embOS to send trace events to SystemView.
At the start of the application, at main, after the target is initialized, SEGGER_SYSVIEW_Conf() has to be called to enable SystemView.
Now, when the application is running, connect the SystemView App to the target and start recording events. All task, interrupt, and OS Scheduler activity as well as embOS API calls are recorded when SystemView is connected or SEGGER_SYSVIEW_Start() has been called.
For a detailed description on how to configure embOS for SystemView, please refer to the SystemView User Manual.
SystemView can be used without any instrumented OS at all, to record interrupt activity and user events. Integrating SystemView in such an application is as simple as adding three lines of code.
For a detailed description on how to configure the application and how to record interrupts, please refer to the SystemView User Manual.