Difference between revisions of "SystemView"

From SEGGER Wiki
Jump to: navigation, search
 
(2 intermediate revisions by 2 users not shown)
Line 15: Line 15:
   
 
[[Use SystemView UART Recorder]]
 
[[Use SystemView UART Recorder]]
  +
  +
[[How to use SystemView Heap Monitoring]]
  +
  +
[[How to use SystemView Heap Monitoring - Custom Heap]]
   
 
== Tweaking RAM usage ==
 
== Tweaking RAM usage ==
 
TBD (on targets with tight RAM constraints)
 
TBD (on targets with tight RAM constraints)
  +
  +
== Troubleshooting ==
  +
  +
* [[SystemView Overflows]]
   
 
[[Category:Software Tools]]
 
[[Category:Software Tools]]

Latest revision as of 15:29, 17 July 2023

SEGGER SystemView is a real-time recording and visualization tool for embedded systems that reveals the true runtime behavior of an application, going far deeper than the system insights provided by debuggers. This is particularly effective when developing and working with complex embedded systems comprising multiple threads and interrupts: SystemView can ensure a system performs as designed, can track down inefficiencies, and show unintended interactions and resource conflicts, with a focus on details of every single system ticks.

SystemView can record data from the embedded target system while it is running. The recorded data is analyzed and the system behavior is visualized in different views. All system information is sent by the application and is part of the recording. The information is shown in the window on the top right and includes the application name, the underlying OS, the target device and the timing information. Additional information about task switches and interrupt frequency provide a quick overview of the embedded system. With the Timeline and the Events window the whole system execution can be visually analyzed.

Target Instrumentation

FreeRTOS with SystemView

Use SystemView without RTOS

Recording Interrupts

Use SystemView UART Recorder

How to use SystemView Heap Monitoring

How to use SystemView Heap Monitoring - Custom Heap

Tweaking RAM usage

TBD (on targets with tight RAM constraints)

Troubleshooting