Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I use P89C51RD2 chip.
How can I define the memory size (dram) ?
With an old version 2.3.0 it works perfectly and my dram start at 0x30
With a new version SDCC :
mcs51/gbz80/z80/avr/ds390/pic14/TININative/xa51 2.3.3 (Mar 3 2003)
the dram start at 0x10 ??? It's the same program.
Anybody can help ?
From: Jesus Calvino-Fraga <JesusC@ece.ubc.ca> - 2003-03-04 18:15:40
From version 2.3.2 on, unless you tell the linker something else, it will
allocate the data region as low as possible in dram. It looks as if your
program doesn't have any bit variables and it uses only register banks 0
and 1. Therefore the next available byte is at 0x10 (a 32 byte save
compared to older versions!). You can check file .mem for a quick summary
of how memory was allocated, or the .map file for more details. If you
still want your data to be allocated at 0x30, you could use --data-loc 0x30
when linking (and the linker will warn you that so many bytes are wasted).
At 06:09 PM 3/4/03 +0100, Olivier LARRIGAUDIERE wrote:
> I use P89C51RD2 chip.
> How can I define the memory size (dram) ?
> With an old version 2.3.0 it works perfectly and my dram start at 0x30
> With a new version SDCC :
> mcs51/gbz80/z80/avr/ds390/pic14/TININative/xa51 2.3.3 (Mar 3 2003) (MING W32)
> the dram start at 0x10 ??? It's the same program.
>Anybody can help ?
>This SF.net email is sponsored by: Etnus, makers of TotalView, The
>debugger for complex code. Debugging C/C++ programs can leave you feeling
>lost and disoriented. TotalView can help you find your way. Available on
>major UNIX and Linux platforms. Try it free. http://www.etnus.com
>Sdcc-user mailing list