Next: 3 What is a Command Program Up: Appnotes Index Previous:1 Executive Summary

RASSP Autocoding for DSP Control Application Note

2.0 Introduction

This Application Note will present a simple, layered architecture for the Command Program (CP) and discuss how commercially available autocoding tools and products may be used on all but one of the layers. Particular focus will be placed on autocoding the one layer, known as the Application Specific Interface (ASI) layer, where commercial support is not currently available. It will show how this layer bridges the gap between Signal Processing Program (SPP) domain concepts, such as graphs, queues and the data flow paradigm, and the CP domain concepts such as application state or mode. It will also show how this layer exploits the standardized architecture presented by the autocoded SPP. Finally, the paper will discuss the software development process in light of the use of autocoding tools for both the SPP and CP.

The Autocoding for DSP Control application note is organized in sections or chapters as follows:

Section 3.0

Section 4.0, "Top Level Program Architecture", proposes a simple, layered software architecture for command programs.

Section 5.0, "Building the Application Specific Interface", describes how a prototype tool, the Application Specific Interface Builder (AIB), is used to generatethe one layer of the software architecture for which commercial tools are not available.

Section 6.0, "Autocoding Tool Evaluations", reviews tools that could be used for the upper layers of the software architecture.

Section 7.0, "Software Develop Process", presents a software development process for building command programs.

Section 8.0, "Application Experience", describes the results of utilizing the ideas, tools and processes presented in the previous sections on three RASSP benchmark projects.

Next: 3 What is a Command Program Up: Appnotes Index Previous:1 Executive Summary

Approved for Public Release; Distribution Unlimited Dennis Basara