SPRADN1 August   2025 F28E120SC , F29H850TU , F29H859TU-Q1 , TMS320F2800132 , TMS320F2800133 , TMS320F2800135 , TMS320F2800137 , TMS320F2800152-Q1 , TMS320F2800153-Q1 , TMS320F2800154-Q1 , TMS320F2800155 , TMS320F2800155-Q1 , TMS320F2800156-Q1 , TMS320F2800157 , TMS320F2800157-Q1 , TMS320F280021 , TMS320F280021-Q1 , TMS320F280023 , TMS320F280023-Q1 , TMS320F280023C , TMS320F280025 , TMS320F280025-Q1 , TMS320F280025C , TMS320F280025C-Q1 , TMS320F280033 , TMS320F280034 , TMS320F280034-Q1 , TMS320F280036-Q1 , TMS320F280036C-Q1 , TMS320F280037 , TMS320F280037-Q1 , TMS320F280037C , TMS320F280037C-Q1 , TMS320F280038-Q1 , TMS320F280038C-Q1 , TMS320F280039 , TMS320F280039-Q1 , TMS320F280039C , TMS320F280039C-Q1 , TMS320F280040-Q1 , TMS320F280040C-Q1 , TMS320F280041 , TMS320F280041-Q1 , TMS320F280041C , TMS320F280041C-Q1 , TMS320F280045 , TMS320F280048-Q1 , TMS320F280048C-Q1 , TMS320F280049 , TMS320F280049-Q1 , TMS320F280049C , TMS320F280049C-Q1 , TMS320F28075 , TMS320F28075-Q1 , TMS320F28374D , TMS320F28374S , TMS320F28375D , TMS320F28375S , TMS320F28375S-Q1 , TMS320F28376D , TMS320F28376S , TMS320F28377D , TMS320F28377D-EP , TMS320F28377D-Q1 , TMS320F28377S , TMS320F28377S-Q1 , TMS320F28379D , TMS320F28379D-Q1 , TMS320F28379S , TMS320F28384D , TMS320F28384S , TMS320F28386D , TMS320F28386S , TMS320F28388D , TMS320F28388S , TMS320F28P550SG , TMS320F28P550SJ , TMS320F28P559SG-Q1 , TMS320F28P559SJ-Q1 , TMS320F28P650DH , TMS320F28P650DK , TMS320F28P650SH , TMS320F28P650SK , TMS320F28P659DH-Q1 , TMS320F28P659DK-Q1 , TMS320F28P659SH-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Features
    1. 2.1 Software Setup
    2. 2.2 Hardware Setup
  6. 3Running the C2000ware Example
  7. 4Adding Signal Sight to a Project
    1. 4.1 SysConfig Steps
    2. 4.2 Target Application Steps
    3. 4.3 CCS Steps
  8. 5Navigating the Signal Sight GUI
    1. 5.1 Verifying Target Connection
    2. 5.2 Enabling Data Streaming
    3. 5.3 Adjusting Plot View
    4. 5.4 Menu Bar Actions and Hotkeys
    5. 5.5 Advanced Features
      1. 5.5.1 Waveform Analyzer
      2. 5.5.2 Scope Settings
      3. 5.5.3 Data Export
  9. 6About the Tool
  10. 7Troubleshooting Guide
  11. 8Summary
  12. 9References

2.1 Software Setup

MCU Signal Sight support can be added to any existing C2000 project that has SysConfig support and uses a C2000ware version of 5.05.000 or newer. The GUI and necessary library files can be fully generated and interfaced with through the integrated CCS environment. Optionally, a standalone version of the MCU Signal Sight GUI can also be downloaded and run independent of a CCS installation.

Signal Sight Software DiagramFigure 2-1 Signal Sight Software Diagram

After adding the MCU Signal Sight module in the user's SysConfig (.syscfg) file, the SysConfig tool autogenerates library files for use by the target application, and creates the integrated GUI Composer application with the virtual oscilloscope component.

Signal Sight Software Flow DiagramFigure 2-2 Signal Sight Software Flow Diagram

The library files generate three top-level functions inside the library files for use by the target application, which are described below. To access the functions in the user's application, make sure to include the signalsight.h header file with the line: #include <signalsight/signalsight.h>

  • SIGNALSIGHT_INIT() - Signal Sight Initialization Function
    • Call this function once in the initialization code after device initializations, interrupt initializations, and SysConfig initializations (Board_init()), but before enabling interrupts globally.
  • SIGNALSIGHT_sendPlotData() - Signal Sight Capture Plot Data Function
    • Call this function at the part of the application code where data needs to be sampled. The value of the plot variable is saved in a memory buffer for transmission in the subsequent call of SIGNALSIGHT_sendPlotData(). Generally this is called from a periodic timer or ISR interrupt.
  • SIGNALSIGHT_capturePlotData() - Signal Sight Send Data Function
    • Call this function in the application where the device sends the buffered data to the GUI by the SCI peripheral. This function is recommended to be placed in a low priority location of the application code, for example, in the main loop of the code, since the CPU can be blocked waiting in this function until there is enough space in the SCI TX FIFO.