BoxView IDE Quick Start: DSP56K Project

This quick start guide to BoxView IDE will provide users with steps to set up their development environment, create a simple application, define a debug session, start the simulator, and view their application output. BoxView IDE provides several other help documents (all are available through online help ). In addition, BoxView IDE is distributed with several sample projects. The Tutorial provides a walk through of the IDE using one of the sample projects. The Users Guide provides detail information including the IDE Command Reference, DebugP Menu Options, File Menu Options Project Menu Options, and Run Menu Options.

Development Environment Overview

BoxView Integrated Development Environment (IDE) features the high level language, embedded processor target debugger as part of the Eclipse software development environment. The Eclipse platform is an open, industry supported, extensible, software development platform.

Several windows are displayed, including a navigator window which shows folders containing sample projects. There are three basic types of resources that exist in the Development Environment; a resource is a collective term for the projects, folders, and files viewed in the IDE:

Files

Files in the file system

Folders

Directories on a file system. Folders are contained in projects or other folders. Folders can contain files and other folders.

Projects

Contain folders and files. Projects are used for builds, version management, sharing, and resource organization. Like folders, projects map to directories in the file system. (When you create a project, you specify a location for it in the file system.)

The directory location on your computer where the resources will be stored is called a workspace. The sample projects are stored in the default installed location. The Development Environment supports multiple workspaces.

 

Windows in BoxView IDE

The BoxView IDE contains many windows or views. A set of views is called a perspective. The IDE has 2 predefined perspectives: the Project Perspective and the Debug Perspective. The Project Perspective displays a set of windows valuable when manipulating project files. The Debug Perspective displays windows valuable when debugging a project. Users can change perspectives by choosing menu option Window->Open Perspective or by using the associated button on the IDE's button bar:

Users can add windows to any perspective by using the IDE's Window pull-down menu. Users can close windows in a perspective by selecting the window's close icon:

 

 

Create a Project

The Navigator window provides a hierarchical view of the resources in your workspace; users can open files for editing by double clicking on the filename in the navigator window.

 

 

 

The New Executable project dialog will be displayed.

 

The Navigator will now contain your new project. Use the mouse to double click on the ExampleProject project in the Navigator window. Three files are created automatically by the IDE and are contained in the project:

 

Create a Source File

Create a source file in your new project that will contain a simple program.

The New File dialog will be dispalyed.

An empty source file named simpleExample.asm has been added to the ExampleProject project. The empty source file is opened in the IDE.

Write the content of the new application.

;----------------------------------------------------------------
; simpleExample.asm
; Program clears accumulator A, and loops.
; Loop increments A, saves A (A2,A1,A0).
;-----------------------------------------------------------------

 
VALUE_A2
VALUE_A1
VALUE_A0

RESET

START

LOOP

 org x:0
dc 0
dc 0
dc 0
org p:$0000
jmp START
org p:$0100
clr a
nop
inc a
nop
move a2,x:VALUE_A2
move a1,x:VALUE_A1
move a0,x:VALUE_A0
jmp LOOP
end

; Data block starts at zero
; define storage for A2
; define storage for A2
; define storage for A0
; Program block starts at zero
; Skip over interrupt vectors
;
;Clear accumulator A
;
;Increment A by 1
;
; Save A2
; Save A1
; Save A0
; Loop to increment again

;--------------------------------------------------------------

Anytime a source file is saved, the automatic build operation will be triggered. Your simple program should assemble with no warnings or errors, so the Problems window will be empty.

Configure the Debug Session

Before the debugger can be started, establish a connection to the target hardware and configure the debug session.

 

Debugging Your Application

Once the debug session has been configured, the debugger can be started.

Many windows are populated in the Debug perspective when the application is started. In the debug window, note the application has stopped (as defined in our session configuration):

Below, the Source window shows an arrow in the margin for the Current Program Counter at the first instruction in the program. The Code Window shows the Current Program Counter by highlighting in yellow; the assembler lines representing the Selected Source Line are highlighted in green.

Below the source window shows the added breakpoint on the jmp instruction, the code window shows the breakpoint in burgundy, and the breakpoint window displays the line number of the source file associated with the breakpoint:

 

 

For more information on debug windows, review the Debug Menu Options Section of the Users Guide.