The project window displays the files used in the project, and the included files, in a tree structure.
This tree structure is used to keep track of file dependency, and to recompile only the necessary files when a Make command is used.
The source window displays the current source file. In "C" mode, this is the C code or the original assembly code, if the source is in assembly language) , with the program counter values corresponding to each line displayed in the right margin. In "asm" mode, the source file displays the disassembled instructions, interspersed with the original source code, if available. If the source code is not available (when executing functions in a library, for example), only the disassembled instructions can be seen. The user can set and reset breakpoints directly in the source window.
The CPU window displayes the current values of all registers. All registers can be modified directly in this window. For convenience, the status register is also "broken down" into its different bit components, displayed in check boxes.
AQ430 User Information Window
The User Information Window displays all compiler and system messages. The other "tab" in this tab control allows the user to search for strings in the project, or, more generally in file folders.
The Watch window displays the variables and/or absolute memory locations selected by the user. Simple variables, structures, expressions can be watched.
Program Memory Window
The Program Memory Window displays the entirety of the MSP430Fxxx microcontroller. It is color coded to represent the different areas (SFR, boot, RAM, info memory and program memory). The RAM area can be modified directly. The SFR (Special Function Registers) area can be modified through the special purpose SFR window.
This window displays the current list of breakpoints. Breakpoints can be associated with a count, and also with a C expression being true (non zero). The user can define "hardware" and "software" breakpoints. When a "go" (real time run) command is received, the hardware breakpoints are given "priority"over the software breakpoints. For example, if the chip has 3 hardware breakpoints, and the user has defined 3 hardware breakpoints and 3 software breakpoints, only the 3 hardware breakpoints will be used whena "go" command is received. All 6 breakpoints would be used if a "slow run" command was received.