1. The SysConfig tool autogenerates a bat file (called gui_setup.bat) that copies the autogenerated GUI composer files to the correct location in the CCS installation so that the MCU Signal Sight GUI can be launched from the CCS menu as a plugin. To run this bat file automatically every time to build the project, follow the steps below:
   1. Right-click on the project name and select Properties.
   2. Navigate to General → Variables.
   3. Click (+) and add a variable called GUI_SUPPORT and set the value to 1. The Type can be left as String.
      Figure 4-9 Add GUI_SUPPORT User_Defined Variable
   4. Navigate in the Properties menu to Build → Steps.
   5. Add an entry with the following line:

      if ${GUI_SUPPORT} == 1 ${BuildDirectory}\syscfg\gui_setup.bat

      Figure 4-10 Add Post-Build Step
2. At this point, users are ready to build the project with the MCU Signal Sight support added. Right-click on the project name in CCS and select Build Projects.
   Figure 4-11 Build the CCS Project
3. Once the project build is complete, do a refresh of CCS by navigating to Help → Reload Window. This updates the plugins populated in the View → Plugins folder of CCS.
   Figure 4-12 Reload the CCS Window
4. Load the application code onto the device by doing either right-click → Debug Project (starting a CCS debug session) or Run → Flash Project (loading the program without starting a debug session).
5. Navigate to View → Plugins → {GUI Name set in 3} to launch the MCU Signal Sight GUI.
6. Click the SELECT COM PORT button and follow the steps below.
   1. Select the COM port from the Port drop-down menu that matches the COM port used by the user's board in the PC Device Manager (Enter Device Manager into the PC Search bar). For most LaunchPads and controlCARDs, the COM port number is under the name Ports (COM & LPT) → XDS110 Class Application/User UART (COM#).
      Figure 4-13 COM Port Number From Device Manager
   2. Select or input the Baud Rate matching the input chosen in 2.
   3. Click OK.
7. Click CONNECT in the GUI and wait a few seconds for the initial communication handshake to take place.
8. Toggle on a channel and see the data begin plotting in the window.
   Note: If any data being plotted in the window, then check the trigger settings and verify that the values of the variables in the code are actively changing.

See Section 7 if there are any issues with these steps.