In article <4639e621$0$47133$892e0abb@auth.newsreader.octanews.com>,
Thad Smith <ThadSmith@acm.org> writes
>Gavin Brewer wrote:
>
>> Upon using SDCC for compiling the skeleton firmware provided by
>>Friess and McNeill (2005), I get the following cryptic linker error:
>> "Error-Could not get 5 consecutive bytes in internal RAM for area
>>DSEG."
>> What is going on here?
>
>It looks like you ran out of RAM space.
This is why I keep saying that it is often better to use the eval
version of a proper 8051 compiler than some of the free ones.
Most commercial 8051 compilers aggressively overlay the data in data
space. This is where the main bottle neck occurs for a lot of 51
programs.
--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ chris@phaedsys.org www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Reply by Joe G (Home)●May 3, 20072007-05-03
Ah... Yes... C can "abstract" you from the SRAM volitle memory locations and
placement of variables... and not tell you you have run out of SRAM space.
Have a look the map files and other files that are generated.
try reducing the number of variables or arrays and see if the error goes
away.
One of the SDCC command line settings may help
Joe
"Gavin Brewer" <gb@axicon.com> wrote in message
news:1178197207.23206.0@proxy02.news.clara.net...
> Folks,
>
> Upon using SDCC for compiling the skeleton firmware provided by Friess and
> McNeill (2005), I get the following cryptic linker error:
>
> "Error-Could not get 5 consecutive bytes in internal RAM for area DSEG."
>
> What is going on here?
>
>
> Please write directly to my mailbox.
>
> Thank you,
> Gavin Brewer.
>
> PS. For more information see:
>
> http://pages.cpsc.ucalgary.ca/~walpole/525/FRIESS%20and%20MCNEIL/code/USB-Skel/readme.pdf
Reply by Thad Smith●May 3, 20072007-05-03
Gavin Brewer wrote:
> Upon using SDCC for compiling the skeleton firmware provided by Friess
> and McNeill (2005), I get the following cryptic linker error:
>
> "Error-Could not get 5 consecutive bytes in internal RAM for area DSEG."
>
> What is going on here?
It looks like you ran out of RAM space.
> Please write directly to my mailbox.
Post here, read here. Answers and discussions benefit everyone.
--
Thad
Reply by Gavin Brewer●May 3, 20072007-05-03
Folks,
Upon using SDCC for compiling the skeleton firmware provided by Friess
and McNeill (2005), I get the following cryptic linker error:
"Error-Could not get 5 consecutive bytes in internal RAM for area DSEG."
What is going on here?
Please write directly to my mailbox.
Thank you,
Gavin Brewer.
PS. For more information see:
http://pages.cpsc.ucalgary.ca/~walpole/525/FRIESS%20and%20MCNEIL/code/USB-Skel/readme.pdf