1. Sysview Mainframe
2. Sysview

February 1, 2021 To: CA SYSVIEW PERFORMANCE MANAGEMENT Customers From: The Broadcom CA SYSVIEW Product Team Subject: CA SYSVIEW 16.0 Continuous Delivery Feature PTF General Availability Announcement On behalf of. Appendix D SEGGER SystemView integration instructions¶. SEGGER SystemView is a real-time recording and visualization tool that reveals the true runtime behavior of an application.

SEGGER SystemView is a real-time recording and visualization toolthat reveals the true runtime behavior of an application. To enableSystemView, follow the instructions below.

Configuring SmartSnippets™ Studio projects to support SystemView:

1. Peek at r13.5 –r13.5 –Chorus –We will start the work but there will be nothing exposed –Integration with DB2 –Right now this is using Insight for DB2 as a server and SYSVIEW as the display engine –Thresholds and Alerts –More zIIP support –JES functional consistency –Security (the.
2. The Worldwide Leader in the Design, Development, Manufacture & Distribution of Mobile Document Capture Solutions.

To enable SystemView for a specific build configuration of any SmartSnippets™ Studioproject, configure the project to build SystemView’s source files andinclude header file directories:

1. Select a project which has the OS_FREERTOS definition enabled.Bare metal projects are currently not supported.
2. Right click project’s “sdk” subfolder and go to New->Folder

3. In the pop-up window select: Advanced->'Linktoalternatelocation'->Browse… and select the<sdk_root_directory>/sdk/middleware/segger_tools folder asshown in Figure 94.

Figure 94 Select the Linker Folder

4. Right click project’s name and go to Properties->C/C++Build->Settings->ToolSettings->CrossARMCCompiler->Includes->IncludePaths(see Figure 95), add the following Workspace folders and click apply:

${workspace_loc:/${ProjName}/sdk/segger_tools/Config}

${workspace_loc:/${ProjName}/sdk/segger_tools/OS}

${workspace_loc:/${ProjName}/sdk/segger_tools/SEGGER}

5. Open the project’s config/custom_config_*.h file and add Code 44 to add and enable the System View configuration:

Note

that configTOTAL_HEAP_SIZE should be increased by``dg_configSYSTEMVIEW_STACK_OVERHEAD`` bytes for each system task. For example, if there are 8 system tasks, configTOTAL_HEAP_SIZE should be increased by: (8 * dg_configSYSTEMVIEW_STACK_OVERHEAD) bytes.

6. To call SEGGER_SYSVIEW_Conf() from application add Code 45. A goodplace to do this is inside system_init() after the configuration ofsystem clocks:

7. Build and download the application image to DA1468x. Then run theapplication either by pressing the Reset Button (Release Build) or bystart debugging the application.
8. To disable SystemView, set dg_configSYSTEMVIEW to 0 and rebuild theapplication.

Running SystemView on the Host:

1. Start the Segger System View application from SmartSnippets™.

Figure 96 System Viewer application

2. Configure the SEGGER System View as shown in Figure 97.

Sysview Mainframe

Note Drivers yulong audio sound cards & media devices.

that the address for the RTT Control Block Detection is locatedin application’s .map file. For example, for PXP reporter the .mapfile is located at pxp_reporter/DA14681-01-Release_QSPI. PressCtrl+F and search the address of the _SEGGER_RTT variable.

3. On the main SystemView window, press the upper right “Start RecordingButton” button.

4. One can Stop and Restart the recording at any time using the buttonsfrom SystemView PC Application.

Additional information:

1. The processing overhead of SystemView is not negligible and canpotentially affect system dynamics or cause assertions due to thedelays inserted from ISR monitoring. To minimize the impact on timecritical ISRs there are some configuration options that allow theuser to enable/disable the monitoring of certain aspects of thesystem, as shown below:

Sysview

2. In applications with heavy IRQ usage it is possible that thecurrently used 2kb RTT buffer cannot hold all the monitored eventsand this may cause RTT overflows which simple means that some eventsare lost. The number of lost events is visible in the System View GUIRTT overflows property.

   To avoid this SEGGER suggest:

   • Minimize the interactions of the debugger with J-Link while thetarget is running. (i.e. disable live watches)
   • Select a higher interface speed in all instances connected to J-Link.(i.e. The debugger and System Viewer)
   • Choose a larger buffer for System View. (1 - 4 kByte)
   • Run System Viewer stand-alone without a debugger.

3. System View uses sdk’s RTC, which is clocked by one of the LP clocks. For example, if the LP clock is XTAL32K each timer tic corresponds to ~31us. Events that last less than 30us will be visualized as events that last 31us.

4. Application/Device name can be set inSEGGER_SYSVIEW_Config_FreeRTOS.cSYSVIEW_APP_NAME/SYSVIEW_DEVICE_NAME definitions. At the samefile function _cbSendSystemDesc() is located which sends commaseparated IRQ names to the Host PC. Because the internal used bufferis only 128 bytes, not all IRQs are named there. One could usemultiple SEGGER_SYSVIEW_SendSysDesc() calls to name all IRQs butthis means more processing requirements. It is recommended to leavejust one packet there.

5. Memory overhead is 2Kb RAM for RTT buffers, 256 bytes heap for everythread, 256 bytes stack for the shared IRQ stack and ~5Kb rom.

6. It is possible to redirect printf messages on SystemView’s host window:

   • if CONFIG_RETARGET is defined, messages go to UART
   • if CONFIG_RTT is defined, messages go to RTT
   • if CONFIG_NO_PRINT is defined, messages are discarded
   • If nothing of the above is defined, but the dg_configSYSTEMVIEW isenabled, messages go to System View’s GUI terminal.

Currently System View supports only integer variables, so %s strings are not printed properly. printf using SystemView inserts delays (because of the temporary disabled IRQs) that may trigger assertions so it is not recommended to be used.