FPGA Central

Hey guys,

Is there any way to tell the code composer studio to make
a chunk in off-chip ram CE0, and just put 2 arrays in it?
I dont want to put all my data variables in it, since it
is slower than IRAM and this is a real-time DSP app.

Thanks
Dave

"Dave F" <[email protected]> wrote in message
news:LN%Ka.518$[email protected]..
> Hey guys,
>
> Is there any way to tell the code composer studio to make
> a chunk in off-chip ram CE0, and just put 2 arrays in it?
> I dont want to put all my data variables in it, since it
> is slower than IRAM and this is a real-time DSP app.
>
> Thanks
> Dave

This is relatively easy to do.

1) Use the #pragmas to place specified variables into certain sections.
2) Add a section to your .cmd to put the section into the desired memory
block.

/*
Put this at the top of your C code.
Make sure you don't include an extern to this variable above the #pragma
statement. (Sometimes happens if you include a header file.)
*/
#pragma DATA_SECTION(sine_table, "tables")
COMPLEX sine_table[N]; // Stores cosine and sine values for lookup.

/*
Linker.cmd.
*/
SECTIONS {
coeff_sect > SARAM_A
samples >SARAM
tables > SARAM_B
}

On Sun, 29 Jun 2003 23:30:05 -0500, "Jerry J. Trantow"
<[email protected]> wrote:

>/*
> Put this at the top of your C code.
> Make sure you don't include an extern to this variable above the #pragma
>statement. (Sometimes happens if you include a header file.)
>*/
>#pragma DATA_SECTION(sine_table, "tables")
>COMPLEX sine_table[N]; // Stores cosine and sine values for lookup.

Note that pragma DATA_SECTION has a slightly different syntax if
you're using C++! In C++ the pragma is not qualified with an object
name, and is applicable to only the object immediately following the
pragma. So, for the above, you would just have:

#pragma DATA_SECTION("tables")
COMPLEX sine_table[N]; // Stores cosine and sine values for lookup.


Best Regards
John McCabe

To reply by email replace 'nospam' with 'assen'