Reply by Mitja Nemec December 12, 20122012-12-12
On Dec 11, 10:26&#4294967295;pm, maury <maury...@core.com> wrote:

snip

> > then it gives you the available memory ranges. Log into the TI e2e forum and submit your question there.
My advice is somewhat different. Log into TI e2e forum and look for the answer. It is already there. Or you can try http://lmgtfy.com/?q=program+will+not+fit+into+available+memory Mitja
Reply by Tim Wescott December 11, 20122012-12-11
On Tue, 11 Dec 2012 15:51:13 -0500, Randy Yates wrote:

> Tim Wescott <tim@seemywebsite.please> writes: >> [...] >> I am taking the liberty to cross-post this to comp.arch.embedded, >> because it's more of an embedded programming issue than a digital >> signal processing issue. > > Tim, > > We have had this discussion before. > > Historically, from my own experience dating back to 1993, this group has > been for the discussion of digital signal processing software, hardware, > and algorithms. However the OP's question is not off-topic since the > group's description in the latest usenet newsgroup list, > > ftp://ftp.isc.org/pub/usenet/news.announce.newgroups/
Group_Lists/20121115
> > is > > Digital Signal Processing using computers. > > Newsgroups topics can overlap. There is overlap between the DSP > hardware/software portion of this group and comp.arch.embedded, so that > group is also a viable place for such a question. However, due to the > specialized nature of DSP processors ("computers"), this group is > particularly suited to the OP's question. > > Your comments seem to imply this is not the proper, or optimum, place > for such questions. I believe it is both a proper and optimum place.
Proper, yes. Optimum -- well, it _is_ a garden-variety embedded software question far more than it is a DSP-specific question. To the extent that it turns out to be a question needing a tools whiz, there's more of those over on comp.arch.embedded than there are here. Actually, I think it's an ideal candidate for cross-posting, simply because it's (a) really just an embedded question, but (b) an embedded question that deals with a chip most likely to be used by folks here. -- My liberal friends think I'm a conservative kook. My conservative friends think I'm a liberal kook. Why am I not happy that they have found common ground? Tim Wescott, Communications, Control, Circuits & Software http://www.wescottdesign.com
Reply by maury December 11, 20122012-12-11
On Tuesday, December 11, 2012 10:41:41 AM UTC-6, leomhb wrote:
> Dear Folks, I am working with Code Composer Studio v5 and TMS320F2812. I am facing with the following errors, even for Hello World sample program. Thanks, Amir ................. **** Build of configuration Release for project ssr **** C:\Program Files (x86)\TI\ccsv5\utils\bin\gmake -k all 'Building target: ssr.out' 'Invoking: C2000 Linker' "C:/Program Files (x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/bin/cl2000" -v28 -ml -mt -O2 --diag_warning=225 --display_error_number --diag_wrap=off -z -m"ssr.map" --warn_sections -i"C:/Program Files (x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/lib" -i"C:/Program Files (x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/include" --reread_libs --display_error_number --diag_wrap=off --rom_model -o "ssr.out" "./hello.obj" -l"libc.a" "../2812_RAM_lnk.cmd" <Linking> warning #10247-D: creating output section ".cio" without a SECTIONS specification warning #10247-D: creating output section ".sysmem" without a SECTIONS specification warning #10210-D: creating ".stack" section with default size of 0x400; use the -stack option to change the default size warning #10210-D: creating ".sysmem" section with default size of 0x400; use the -heap option to change the default size "../2812_RAM_lnk.cmd", line 86: error #10099-D: program will not fit into available memory. placement with alignment/blocking fails for section ".text" size 0x17ff page 0. Available memory ranges: PRAMH0 size: 0xffe unused: 0xf89 max hole: 0xf89 error #10010: errors encountered during linking; "ssr.out" not built >> Compilation failure gmake: *** [ssr.out] Error 1 gmake: Target `all' not remade because of errors. **** Build Finished ****
It's telling you: program will not fit into available memory. then it gives you the available memory ranges. Log into the TI e2e forum and submit your question there.
Reply by Randy Yates December 11, 20122012-12-11
Randy Yates <yates@digitalsignallabs.com> writes:

> Historically, from my own experience dating back to 1993, this group has > been for the discussion of digital signal processing software, hardware, > and algorithms. However the OP's question is not off-topic since the > group's description in the latest usenet newsgroup list, [...]
Bad writing. Sorry. Allow me to rephrase: Historically, from my own experience dating back to 1993, this group has been for the discussion of digital signal processing software, hardware, and algorithms. MORE OBJECTIVELY, the OP's question is not off-topic since the group's description in the latest usenet newsgroup list, [...] ftp://ftp.isc.org/pub/usenet/news.announce.newgroups/Group_Lists/20121115 is Digital Signal Processing using computers. -- Randy Yates Digital Signal Labs http://www.digitalsignallabs.com
Reply by Randy Yates December 11, 20122012-12-11
Tim Wescott <tim@seemywebsite.please> writes:
> [...] > I am taking the liberty to cross-post this to comp.arch.embedded, because > it's more of an embedded programming issue than a digital signal > processing issue.
Tim, We have had this discussion before. Historically, from my own experience dating back to 1993, this group has been for the discussion of digital signal processing software, hardware, and algorithms. However the OP's question is not off-topic since the group's description in the latest usenet newsgroup list, ftp://ftp.isc.org/pub/usenet/news.announce.newgroups/Group_Lists/20121115 is Digital Signal Processing using computers. Newsgroups topics can overlap. There is overlap between the DSP hardware/software portion of this group and comp.arch.embedded, so that group is also a viable place for such a question. However, due to the specialized nature of DSP processors ("computers"), this group is particularly suited to the OP's question. Your comments seem to imply this is not the proper, or optimum, place for such questions. I believe it is both a proper and optimum place. -- Randy Yates Digital Signal Labs http://www.digitalsignallabs.com
Reply by Tim Wescott December 11, 20122012-12-11
On Tue, 11 Dec 2012 10:41:41 -0600, leomhb wrote:

> Dear Folks, > > I am working with Code Composer Studio v5 and TMS320F2812. I am facing > with the following errors, even for Hello World sample program. > > Thanks, > Amir > > ................. > > **** Build of configuration Release for project ssr **** > > C:\Program Files (x86)\TI\ccsv5\utils\bin\gmake -k all 'Building target: > ssr.out' > 'Invoking: C2000 Linker' > "C:/Program Files (x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/bin/cl2000" > -v28 -ml -mt -O2 --diag_warning=225 --display_error_number > --diag_wrap=off -z -m"ssr.map" --warn_sections -i"C:/Program Files > (x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/lib" -i"C:/Program Files > (x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/include" --reread_libs > --display_error_number --diag_wrap=off --rom_model -o "ssr.out" > "./hello.obj" -l"libc.a" "../2812_RAM_lnk.cmd" > <Linking> > warning #10247-D: creating output section ".cio" without a SECTIONS > specification warning #10247-D: creating output section ".sysmem" > without a SECTIONS specification warning #10210-D: creating ".stack" > section with default size of 0x400; use the -stack option to change the > default size warning #10210-D: creating ".sysmem" section with default > size of 0x400; use the -heap option to change the default size > "../2812_RAM_lnk.cmd", line 86: error #10099-D: program will not fit > into available memory. placement with alignment/blocking fails for > section ".text" size 0x17ff page 0. Available memory ranges: > PRAMH0 size: 0xffe unused: 0xf89 max hole: 0xf89 > > error #10010: errors encountered during linking; "ssr.out" not built > >>> Compilation failure > gmake: *** [ssr.out] Error 1 gmake: Target `all' not remade because of > errors. > > **** Build Finished ****
I am taking the liberty to cross-post this to comp.arch.embedded, because it's more of an embedded programming issue than a digital signal processing issue. It's been a long long time since I've used Code Composter, but it appears that your linker command file is not covering all the bases as far as specifying all of the sections. Either you need to call more than one command file, or your 2812_RAM_lnk.cmd is not correct for the files that you are trying to link. My suggestion, since I cannot offer something more specific, is to dig around and see if there's a pre-defined project that already works. If you find it, then strip out all of its code files and start from there. -- Tim Wescott Control system and signal processing consulting www.wescottdesign.com
Reply by leomhb December 11, 20122012-12-11
Dear Folks,

I am working with Code Composer Studio v5 and TMS320F2812. I am facing with
the following errors, even for Hello World sample program.

Thanks,
Amir

.................

**** Build of configuration Release for project ssr ****

C:\Program Files (x86)\TI\ccsv5\utils\bin\gmake -k all 
'Building target: ssr.out'
'Invoking: C2000 Linker'
"C:/Program Files (x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/bin/cl2000"
-v28 -ml -mt -O2 --diag_warning=225 --display_error_number --diag_wrap=off
-z -m"ssr.map" --warn_sections -i"C:/Program Files
(x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/lib" -i"C:/Program Files
(x86)/TI/ccsv5/tools/compiler/c2000_6.1.0/include" --reread_libs
--display_error_number --diag_wrap=off --rom_model -o "ssr.out" 
"./hello.obj" -l"libc.a" "../2812_RAM_lnk.cmd" 
<Linking>
warning #10247-D: creating output section ".cio" without a SECTIONS
specification
warning #10247-D: creating output section ".sysmem" without a SECTIONS
specification
warning #10210-D: creating ".stack" section with default size of 0x400; use
the -stack option to change the default size
warning #10210-D: creating ".sysmem" section with default size of 0x400;
use the -heap option to change the default size
"../2812_RAM_lnk.cmd", line 86: error #10099-D: program will not fit into
available memory.  placement with alignment/blocking fails for section
".text" size 0x17ff page 0.  Available memory ranges:
   PRAMH0       size: 0xffe        unused: 0xf89        max hole: 0xf89    

error #10010: errors encountered during linking; "ssr.out" not built

>> Compilation failure
gmake: *** [ssr.out] Error 1 gmake: Target `all' not remade because of errors. **** Build Finished ****