-->
USB-UART : monitor
- Using this method for accessing targets variables allows a simple way of creating a GUI Composer Application by specifying global variables in widget bindings.
- The main difference is that there is no special HW support required to enable this data exchange mode. This is the only option for MSP430 devices if you would like to use global variables to specify widget bindings.
- The main downside is that your program needs to be adjusted to include UART peripheral support and simple monitor that implements a memory read/write protocol. GUI Composer will translate symbol information
entered in widget bindings to a memory address and then request the monitor to perform that read and send results back to the host PC. This monitor will require some cycles to be able to provide data to GC app.
Overhead is difficult to quantify as it depends on how much data your GC application will pull from the target to update widgets.
- In Target Programming page you must select the device that you are working with and upload a program. This is the output of building your CCS Project in CCS Desktop or CCS Cloud. GUI Composer will
use symbols contained in that file to obtain memory addresses on the device. In majority of cases the program should already be programmed on your device.
Energia library monitor
- You may use an Energia Library that implements target monitor to get started quickly with GUI Composer and an Energia based program.
- In this case you Energia program includes monitor library and then you can start binding variables to widgets.
- Please see Energia Monitor tutorial more information.
Barebones monitor
- In this example you will need to take source code implementation of target monitor and integrate it with your program.
- This is best suited if you already have a program and you would like to add monitor based GUI Composer data exchange.
You will need to also need to add support for UART peripheral which target monitor will use to complete GUI Composer memory read/write requests.