Automating File Management With the LabVIEW DSP Test Integration Toolkit for TI DSP

This tutorial explains how to use the LabVIEW DSP Test Integration Toolkit for TI DSP to automate routine file management tasks in Code Composer Studio.

Note: This toolkit is no longer officially supported by NI, but you can download the VIs that were included in this toolkit.

Automating Routine Tasks

The DSP Test Integration Toolkit allows you to automate the management of Code Composer Studio (CCS) files. With the toolkit you can open, close, compile and download project files. After downloading the code to the DSP device, you can run and halt the code.

After you create and save code in CCS, you can build a VI in LabVIEW that sequences each of these processes, automating the handling of the code. Figure 2 shows a VI that opens a specified project file, compiles the file, downloads the corresponding .out file to the DSP device, and then runs the .out file on the DSP device.

You can use the DSP Test Integration Toolkit VIs to create test systems that manage multiple project files. However, you must close or halt a project file on the DSP device for a second project file to execute properly.

Monitoring Project File Status

Finally, the DSP Test Integration Toolkit has built-in functionality to monitor the execution state of CCS from the front panel . To do this, simply create a string indicator on the front panel and then create a reference to the string indicator. Next, wire the reference directly to the CCS Open Project VI. The front panel string indicator displays the status of CCS as shown in Figure 3.

The attached example program is a good template for developing DSP test systems. The example program demonstrates the proper sequencing of VIs and how to use the CCS Status String.
Related Links:
Managing Code Composer Studio Files Using the LabVIEW DSP Test Integration Toolkit for TI DSP
DSP Communication Using RTDX

Reader Comments | Submit a comment »