Installation
and Setup for DSP/BIOS 5.42
This version
of DSP/BIOS is delivered as a component of Code
Composer Studio v5.3.0 (CCStudio). It is available for Microsoft Windows.
It includes support for all DSP families supported by DSP/BIOS: C28x,
C55x, and C6x.
For the
latest information about what’s new in this
release and any known issues, see the release
notes (which, in turn, has links to other documents).
This document
describes how to perform the following
tasks:
Installing
DSP/BIOS
DSP/BIOS
5.42
is installed as part of the CCSv5.3.0 installation process.
Additionally, it can be installed using the stand alone installer located on software download website.
Setting
System Variables
If
you want to build with DSP/BIOS 5.42 outside the CCSv5.3.0 environment,
follow these steps:
-
Create the
BIOS_INSTALL_DIR system
environment variable, and
set it to <install_dir>/bios_5_42_00_xx.
- Insert
the location of the BIOS 5/xdctools installation that is included within DSP/BIOS 5.42, at
the beginning of your PATH system environment variable. (Remove any
DSP/BIOS or XDCtools locations that were
put in for earlier DSP/BIOS or XDCtools installations.) For
Windows use back slashes (“\”) and a semicolon (;)
between each system environment variable you add to the PATH.
For example:
- C:\ti\bios_5_42_00_xx\xdctools;
- See the Makefiles for DSP/BIOS applications below for directions to build the examples.
Converting CCSv3.3 Projects to
CCSv5 Projects
To import a
CCSv3.3 project, choose Project
> Import Legacy CCSv3.3 Project
in CCSv5. Follow the instructions in the import wizard. For more
information about converting CCSv3.3 projects to CCSv5 projects, go to
the Code
Composer Studio Mediawiki and read the "Migration" section of
the page.
If
you are importing a project that uses DSP/BIOS, the import wizard asks
you to select the version of DSP/BIOS you want the imported project to
use. It is recommended that you select DSP/BIOS 5.42. This version of
DSP/BIOS is compatible with previous 5.x versions. If you select a
DSP/BIOS 6.x version, you will need to make changes to your source code
and configuration. If you select a DSP/BIOS version prior to 5.42, you
will not have access to the ROV tool and Real-time Analysis debugging
features.
DSP/BIOS
Examples
You can use
the following sources
for example DSP/BIOS applications:
DSP/BIOS Examples
Some DSP/BIOS examples are provided through the CCSv5.3.0 project
wizard.
The
DSP/BIOS examples come preconfigured for a variety of platforms. If you
have a platform that is not included, you should use a text editor to
modify the .tcf file for the platform that is most closely
related
to
yours. In particular, you will likely need to modify the platform named
in the utils.loadPlatform() statement and the MEM module settings. See
the DSP/BIOS Textual Configuration
(Tconf) User’s Guide(SPRU007) for more information about
platforms and .tcf files.
When building the examples for
28x or 55x it is sometimes necessary to open the
project build properties and set the appropriate values. For instance,
if using 28x or 55x and large model is set for the example it may be
neccessary to set the same model option for the compiler. If
you would like to run huge model for evm5505 and evm5515 examples then
--ptrdiff_size would need to be set from 16 to 32. These and other
runtime options can
be found under the Build Properties --> C/C++ Build -->
C5500
Compiler --> Runtime Model Options.
See the release notes
for known issues.
To create an example in CCSv5.3.0 or higher
follow these steps:
- Create
a new CCS project. Open CCSv5.3.0 and select File --> New
--> CCS project.
- This
will start the project wizard.
- In the first box, give the project a name. For example, name it
"hello_example".
- Next,
if necessary, select the project output type from the dropdown menu. The default is executable.
- Select a DSP/BIOS 5 supported device: C2000, C5500 or C6000
- You can now type in your device variant to the filter
or select it from the drop down menu. You may also use the
generic
device for your target device.
- Under Project Templates and examples, expand
the "+ DSP/BIOS v5.xx Examples" tree. Select the folder for
your
device and expand. Select the hello Example.
- There
are more examples in
<install_dir>\packages\ti\bios\examples
that are not listed in the
project wizard. It possible to create these other
examples by selecting "Empty Project" at this point and add the .c and
.tcf
files to your project manually.
- After
the example is selected, click the "Finish" pane at the bottom of the
pane.
- A project will
now show up named "hello_example" under
the "C/C++ Projects" tab in CCS.
- To build the
example, select from the CCS menu Project
--> Build Project.
Makefiles for DSP/BIOS Applications
If you do not
use CCStudio
to build your application, you can build from the command line using
gmake and
makefiles.
The best way
to create build files
for your application is to copy and revise the makefile shipped with
this product. The relevant files for the
examples shipped with DSP/BIOS 5.42 are:
- makefile_hello
in each example target directory
- config.mak
in <install_dir>\packages\ti\bios\examples\
- cNNrules.mak
in <install_dir>\packages\ti\bios\examples\
(NN
is the DSP family)
IMPORTANT:
Only
use forward slashes (“/”) in all makefiles and files included by
makefiles
regardless of the OS you are using.
Typical
things you need to
change in config.mak are:
- INSTALL_ROOT and XDCTOOLS_ROOT should
point to the location where you installed. Set them to bios_5_42_00_xx and bios_5_42_00_xx/xdctools respecitively.
- If
you want to use a version of RTDX or PSL
other than the version provided with the DSP/BIOS installation, change
the
variable for that component. For example, you might set PSL_ROOT to
C:/ti/c5500/psl.
- The
CnnX_CODEGEN_ROOT variable for your DSP
platform should point to the location of the codegen tools you want to
use.
- For
example, C6X_CODEGEN_ROOT = C:/ti/ccsv5/tools/compiler/c6000_<version>. (If you use multiple
operating systems, note that the codegen tools are OS-specific.)
- If
you are using UNIX, comment out the REMOVE
definition for Windows and uncomment the corresponding definitions for
UNIX.
Typical
things you might need to
change in cNNrules.mak
are:
- Currently all examples are built for debug (-g).
To change this, remove the “-g” from the CCNNOPTS
line.
- Change
or add any compiler, assembler, or linker
options as needed in the definitions of CCNNOPTS,
ASNNOPTS, and LDNNOPTS.
Typical
things you might need to
change in makefile
are:
- Location
of
config.mak and cNNrules.mak if they
are not in the default examples location.
- TCONFOPTS
should be the –D option for use on the
tconf command line. See the instructions for defining the
config.importPath for CCStudio and the DSP/BIOS
Textual Configuration (Tconf) User’s Guide (SPRU007H).
- CCNNFLAGS,
ASNNFLAGS, and LDNNFLAGS
allow you to specify any additional compiler, assembler,
and linker flags specific to this application.
For example, to have a map file created for the hello example, add “-m
hello.map” to LD55FLAGS. To build with the C55x large model, first
change the
configuration in the tcf file, and then add the “-ml” flag to the
C55FLAGS and
AS55FLAGS definitions in the makefile.
- PROG,
OBJS, and CMDS should reference your
source files, object files, and linker command files.
- If
the application uses CSL directly, add the
“-i” option to CCNNFLAGS to point to
the directory that contains the CSL header files.
In
order to use gmake to build using the supplied makefiles you have
to add the <Install Dir>\bios_5_42_00_xx\xdctools directory to your PATH. Once this
is
setup, you can build the hello example using the following syntax from
the command line "gmake -f makefile_hello".
Windows:
Open
the Environment Variables setting and add the XDCtools directory to the
PATH
Right
click on "My Computer" and
select properties --> Advanced --> Environment Variables
Under
"System Variables" scroll down to Path and double click on it
Scroll to
the beginning of the
line for "Variable Value" and add the XDCtools install dir followed by
a semi-colon.
Linux:
If
you are using bash on Linux, change the PATH with teh following command:
export PATH=<BIOS5_install_dir/xdctools>:$PATH
If you are using
bash on Linux, change the PATH with the following command:
Set PATH =(<BIOS5_install_dir/xdctools> $PATH)
More
Information About DSP/BIOS
See
the
following documents
available with this release and also on www.dspvillage.com
to
learn about DSP/BIOS:
Copyright © 2012, Texas Instruments
Incorporated
Code Composer Studio,
DSP/BIOS,
eXpressDSP, and TMS320 are
among the trademarks of Texas Instruments. See www.ti.com for a list of
trademarks
and registered trademarks belonging to Texas Instruments.