Forums

[newbie] how to build DSP prototype board

Started by Unknown November 6, 2004
Hi all,

Suppose I've got well working algorithm (IIR filter) developed in Code
Composer Studio along with DSP Starter Kit, say C5510. I've got a built COFF
file (*.out) that loads into DSP through DSK and works there like a charm.
Now what. I want to have that code to work on a standalone prototype board
that I'll build.
Please, tell me what are the steps to be taken in order to transfer my code
into standalone DSP board, and what elements should that board contain (DSP,
ADC/DAC, memory?, do I have to transfer my code into eeprom - how do I do
that, how do I tell the DSP to load program from eeprom and run it
automatically, etc.).


Thanks for your help,
Melonaski


Melonaski wrote:

> Hi all, > > Suppose I've got well working algorithm (IIR filter) developed in Code > Composer Studio along with DSP Starter Kit, say C5510. I've got a built COFF > file (*.out) that loads into DSP through DSK and works there like a charm. > Now what. I want to have that code to work on a standalone prototype board > that I'll build. > Please, tell me what are the steps to be taken in order to transfer my code > into standalone DSP board, and what elements should that board contain (DSP, > ADC/DAC, memory?, do I have to transfer my code into eeprom - how do I do > that, how do I tell the DSP to load program from eeprom and run it > automatically, etc.). > > > Thanks for your help, > Melonaski
Code that works in RAM won't necessarily work in ROM, although the chances are good that you aren't using any self-modifying code. Your code uses variables. Those need to be in RAM. Their addresses, and the addresses of jump targets in the code will all need to match the memory map of your standalone board. You will need startup code that initializes the state of the processor, as well as the C run-time package. You can copy all that from what the DSK loads (with appropriate memory-map alterations), but you better understand it rather than copy blindly. C does its best to insulate the programmer from the hardware. You have to find a way to get back to it. HLLs have many advantages, including portability. But each processor and peripheral combination needs a scaffold to support the HLL. CCS provides that scaffold for the particular DSK. I find that assembly is the simplest way to code for a relatively simple one-off. Jerry -- Engineering is the art of making what you want from things you can get. �����������������������������������������������������������������������
Jerry Avins wrote:
> Melonaski wrote: > > >>Hi all, >> >>Suppose I've got well working algorithm (IIR filter) developed in Code >>Composer Studio along with DSP Starter Kit, say C5510. I've got a built COFF >>file (*.out) that loads into DSP through DSK and works there like a charm. >>Now what. I want to have that code to work on a standalone prototype board >>that I'll build. >>Please, tell me what are the steps to be taken in order to transfer my code >>into standalone DSP board, and what elements should that board contain (DSP, >>ADC/DAC, memory?, do I have to transfer my code into eeprom - how do I do >>that, how do I tell the DSP to load program from eeprom and run it >>automatically, etc.). >> >> >>Thanks for your help, >>Melonaski > > > Code that works in RAM won't necessarily work in ROM, although the > chances are good that you aren't using any self-modifying code. > > Your code uses variables. Those need to be in RAM. Their addresses, and > the addresses of jump targets in the code will all need to match the > memory map of your standalone board. > > You will need startup code that initializes the state of the processor, > as well as the C run-time package. You can copy all that from what the > DSK loads (with appropriate memory-map alterations), but you better > understand it rather than copy blindly. > > C does its best to insulate the programmer from the hardware. You have > to find a way to get back to it. HLLs have many advantages, including > portability. But each processor and peripheral combination needs a > scaffold to support the HLL. CCS provides that scaffold for the > particular DSK. I find that assembly is the simplest way to code for a > relatively simple one-off. > > Jerry
On the 2812 with Code Composter and the Spectrum Digital eval board you can move a few jumpers on the load a program into processor flash, where it executes fine. Once this is done the load process onto a production board is the same -- you need to bring out the processor's JTAG emulator pins to an appropriate header, and you need to spend $$$ for TI's JTAG debugging pod. -- Tim Wescott Wescott Design Services http://www.wescottdesign.com
> Please, tell me what are the steps to be taken in order to transfer my
code
> into standalone DSP board, and what elements should that board contain
(DSP,
> ADC/DAC, memory?, do I have to transfer my code into eeprom - how do I do > that, how do I tell the DSP to load program from eeprom and run it > automatically, etc.). >
Thank you all, for your inputs. But could someone write a simple instruction (something like: 1. Using this tool do that... 2. Buy that to do that... Etc.) Melonaski
Melonaski wrote:

>>Please, tell me what are the steps to be taken in order to transfer my > > code > >>into standalone DSP board, and what elements should that board contain > > (DSP, > >>ADC/DAC, memory?, do I have to transfer my code into eeprom - how do I do >>that, how do I tell the DSP to load program from eeprom and run it >>automatically, etc.). >> > > > Thank you all, for your inputs. But could someone write a simple instruction > (something like: > 1. Using this tool do that... > 2. Buy that to do that... > Etc.) > > Melonaski > > >
Not in a reasonably sized post, unless you luck into someone with experience with your processor and eval board. If it's a halfway decent eval board you should be able to load the flash on the uP on the board, and the board documentation should tell you how. Really, everyone has to struggle with this whenever they adopt new technology. It's just part of the experience. -- Tim Wescott Wescott Design Services http://www.wescottdesign.com
Hi

You can this task using several way. For instance, you can use one or
more of EEPROM, HPI boot, parallel boot methods... etc. Please read
TI's bootloader manual to find yours best method.

"Melonaski" <sedaka@NIESPAMUJgo2.pl> wrote in message news:<cmirts$bpc$1@news.onet.pl>...
> Hi all, > > Suppose I've got well working algorithm (IIR filter) developed in Code > Composer Studio along with DSP Starter Kit, say C5510. I've got a built COFF > file (*.out) that loads into DSP through DSK and works there like a charm. > Now what. I want to have that code to work on a standalone prototype board > that I'll build. > Please, tell me what are the steps to be taken in order to transfer my code > into standalone DSP board, and what elements should that board contain (DSP, > ADC/DAC, memory?, do I have to transfer my code into eeprom - how do I do > that, how do I tell the DSP to load program from eeprom and run it > automatically, etc.). > > > Thanks for your help, > Melonaski
Melonaski,

As Tim pointed out you will need an XDS510 JTAG emulator (~$1400-$1800) in 
order to do emulation on your own custom-built board.  I think a better 
first step will be to program the flash on the 5510 DSK so that the DSK 
functions as a stand-alone system.

Here's an application note on using the 5510 boot loader:

http://focus.ti.com/docs/apps/catalog/resources/appnoteabstract.jhtml?abstractName=spra763c

Also, here's a quick overview of what you'll need to do:
1)  Use the hex conversion utility (documented in spru280) to take your .out 
file and create a boot table that you will burn into the flash.
2)  Use Flashburn to actually write the table into the flash.

Brad


"Melonaski" <sedaka@NIESPAMUJgo2.pl> wrote in message 
news:cmjgnn$p4a$1@news.onet.pl...
>> Please, tell me what are the steps to be taken in order to transfer my > code >> into standalone DSP board, and what elements should that board contain > (DSP, >> ADC/DAC, memory?, do I have to transfer my code into eeprom - how do I do >> that, how do I tell the DSP to load program from eeprom and run it >> automatically, etc.). >> > > Thank you all, for your inputs. But could someone write a simple > instruction > (something like: > 1. Using this tool do that... > 2. Buy that to do that... > Etc.) > > Melonaski > > >