QUICK
Board Support Packages
Board support packages are pre-customized platforms used to build ROM files for certain boards. Each version of TALON has out-of-the-box support for a variety of hardware. This includes makefiles, samples, and host connectivity tools. The host tools
enable communication to the host (via parallel port, USB, PCI, etc.) for a terminal interface (PTY) and PC file system access (HVFSD) from the DSP target program.
For example, the C6211 DSK example uses the hardware’s on-board parallel port as the
host communication channel. Your hardware and other boards may be different.
Blackhawk can customize TALON for your hardware under our BSP service. Contact
us for more information. These host interface features are not necessary to run TALON
on your target hardware. They are provided as tools to ease initial development.
Host Utilities
The terminal and file system utilities allow a users PC to communicate with TALON as it
is running on the DSK. The steps for using it with the TI C6211 DSK are shown below.
>cd blackhawk\talon6xx\build\board\dsk6211\bin
>hvfsd_UNI hdsk6211.dll
>pty hdsk6211 0
The hvfsd command starts the host virtual file system service to connect to the target
board (via parallel port on the C6211 DSK). The pty command starts a psuedo terminal
connection to the target on port 0 across the same parallel port interface as hvfsd.
All TALON BSPs can support two terminal windows (0 & 1) running simultaneously. The
typical application running during debug builds in this window is an embedded shell
(esh) command line interpreter ($ - prompt).
START
GUIDE
Blackhawk™
TALON™
Operating
System
EVAL
System Requirements
Software
• Windows® 95/98/ME/NT/2000/XP Operating System
• Adobe® Acrobat Reader
Hardware
• CD-ROM Drive
• PC compatible with the minimum requirements for running Code Com•
poser™ or Code Composer Studio™
TI EVM/DSK board or custom hardware
TI Software Tools
• Code Composer Studio™ v2.1 or
• Code Composer™ v4.1x
Target Specific Files
The src directory of each BSP contains specific startup code for the EVM or DSK. This
information is included in the following files. Examples exist in any BSP folder.
custom.c
This file contains hardware specific boot commands and information for the DSP
and board configuration. It is the first routines run by the TALON kernel during the
power-on/reset boot sequence.
init.c
This file contains the environment configuration for the main process of TALON. It
is the location for code that opens the debug terminals and mounts all file systems
(ROM and host) prior to starting the main process application. This is where you will
specify your application executable(s) to start.
Where to go Now
Please refer to the TALON Programming Guide for more detailed information, as this guide is only meant to give an overview on what is necessary to install and build TALON for a TI TMS320 DSP target.
Blackhawk
123 Gaither Drive
Mt. Laurel, NJ 08054-1701 USA
+1-856-234-2629
www.blackhawk-dsp.com
4
Blackhawk and TALON are registered trademarks of EWA Technologies, Inc.
TalonEval-QS-01
Software Installation
The default installation will use the typical setup
and create two base directories under the
TALON version’s main folder selected during
setup. A sample layout is shown in figure 1 to
the right using the TALON 6000 OS.
CD-ROM Distribution
Insert the distribution CD-ROM into the computer’s CD-ROM drive and follow the installation
setup wizard. If the setup does not start, run the
setup.exe located in the directory X:\setup
(where X: is the drive mapping for the CD-ROM).
ZIP/EXE Distribution
If your distribution is via web download or email
distribution, run the setup.exe included in the
package and follow the installation wizard.
September 2003
Figure 1–Typical TALON
Directory Layout
1
TALON Overview
Each TALON operating system distribution is broken into two sections (OS and BUILD),
under the main directory as shown for the TALON 6000 OS in figure 1.
OS
The OS folder is designated as read-only that contains header files used during compilation and library files needed during linking. It also contains documentation and online
HTML-based help references.
\DOCS
Documentation for TALON is located under the OS\DOCS folder after installation. If you
received a distribution CD-ROM it can be viewed from the Browse Documents section.
BUILD
The BUILD folder is an area to build your application. It includes specific target board
support packages (BSP), host and target code, drivers and utilities, and pre-built default target executables.
\BOARD
The BUILD\BOARD subfolder of the BUILD directory contains BSP examples for typical
EVM and DSK boards. This section contains the files relative to your target hardware in
which the OS and application is being built to run.
You will model your application project after the board example that fits your target DSP.
For example, if you were designing a project around a C64x device, you would model
your board’s build area after the TEB6416 folder.
Compiling and Linking
The TALON build tools use the standard UNIX & Linux makefile format and require certain environment variables to locate all necessary files. These requirements are listed
below including an example build process to set these correctly for a supported DSK
board.
PATH
The PATH environment variable must contain several location needed by TALON including the os\bin folder and TI compiler tools (i.e. ti\c6000\cgtools\bin).
MAKEFILE
The following environment variables are needed by the TALON make utility, make.exe.
Please note that the make utility requires that these environment variables use the forward slash (/) to separate folders rather than the expected backslash (\).
BLACKHAWK_HOME
Root directory of the TALON installation
BLACKHAWK_SRC
Root directory of the open source installation
BLACKHAWK_TARGET
Name of the target board directory
TIDIR
Directory containing TALON provided TI files
TI
The default TI compiler and assembler environment variables, C_DIR and A_DIR, need
be set to the correct locations for linking with the provided TALON headers and link
library files.
2
Example Build
The following is a command file example based on the TALON 6000 OS installation for
the TI C6211 DSK target board showing the setting for needed environment variables.
Sample BATCH Command File
Rem
Set path to Ti tools and environment.
SET PATH=C:\TI\C6000\CGTools\Bin;%PATH%;
SET C_DIR=C:\Blackhawk\Talon6xx\os\Ti\Lib;C:\Blackhawk\Talon6xx\os\Ti\Include
SET A_DIR=C:\Blackhawk\Talon6xx\os\Ti\Lib
Rem
SET
SET
SET
SET
Blackhawk Build Evironment Variables
PATH=C:\Blackhawk\Talon6xx\os\bin;%PATH%
BLACKHAWK_HOME=C:/Blackhawk/Talon6xx/os
BLACKHAWK_SRC=C:/Blackhawk/Talon6xx/build
BLACKHAWK_TARGET=dsk6211
Rem
Modified TI source and library files
SET TIDIR=C:/Blackhawk/Talon6xx/os/Ti
Rem
Change folder to default board config area.
CD C:\Blackhawk\Talon6xx\build\board\dsk6211\config
Building a ROM Image File
A typical compilation sequence on how to build TALON is listed below under each
board area of the build folder from a command line window.
>cd blackhawk\talon6xx\build\drv\pty
>make
>cd blackhawk\talon6xx\build\board\dsk6211\config
>make
>cd blackhawk\talon6xx\build\board\dsk6211\host
>make
>cd blackhawk\talon6xx\build\board\dsk6211\src
>make
The \src folder contains the information needed to build the OS run-time image for the
target board. The makefile produces a ROM Image File (ROM.OUT) in this directory,
which is the executable TALON image for the DSP target that is loaded with Code Composer or Code Composer Studio.
This is also where you will start investigating how to build TALON. For more detailed
information please refer to the TALON Programming Guide.
ROM Image File
The ROM Image file is created by the system building utility makerom. This file contains
the ROM File System and possibly the operating system kernel, which together represent the operating environment of the target embedded system.
The format of the ROM Image file is exactly a COFF2 (Common Object Format) file of the
type produced by the Texas Instruments linker tool. This file may be loaded using a
loader into a target system and debugged using a symbolic debugger. The format of the
ROM Image file can be found on the TALON Programming Guide (the COFF file format
can be found in TI documentation).
3