Run the code by going to Run → Resume or clicking the Resume button in the tool bar. The project can now run and the variables display in the Expressions window. Check the following to confirm the application and hardware set up are working:

• The green power LEDs on the gate-drive boards must be on. If the gate-drivers are initialized without faults, none of the red, nFault LEDs are on. Gate drive initialization status can be checked through the tripFlagDMC.fault.UCC5880_status variable.
• Similarly other variables in the tripFlagDMC struct show the status of other faults. If no fault flags are set, to run the test motor, the runMotor can be set to RUN_MOTOR. Your variables need to appear similar to what is shown in Figure 3-17.
• If no faults are detected, the motor1.isrCount must increment continuously.
• Check the calibration offsets of the motor inverter board. The offset values of the motor phase current sensing values must be equal to approximately half of the scale current of ADC.
• The PWM output for motor drive can also be probed with an oscilloscope.

Figure 3-17 Runtime Control and Debug through Expressions View

You can halt the CPU by first clicking the Suspend button on the toolbar or by selecting Target → Suspend. To run the application from the start again, reset the controller by clicking on the CPU Reset tool bar button or clicking Run → Reset → CPU Reset and then clicking on the Restart button or Run → Restart. You can close the CCS debug session by clicking the Terminate button or by clicking Run → Terminate. This will halt the program and disconnect CCS from the controller.

Note that it is not necessary to terminate the debug session each time you change the code. Instead you can go to Run → Load → Load Program... (or Reload Program... if it is the same file). CCS will also automatically prompts to ask if you want to reload your executable if it detects you have rebuilt it.