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
What are your specific SDCC command line flags for the compiler and linker?
From: Felix Brack [mailto:fb@...]
Sent: Wednesday, April 20, 2005 11:50 AM
Subject: Re: [Sdcc-user] Preventing SDCC from initializing stack pointer
Unfortunately this would not work, since it is not just a boot loader
that gets out of the way when the user application runs. Quite much of
the work is done by the firmware which has access to the user
application by means of callbacks. Hence there is a permanent
communication between firmware and user application which live in
Any other ideas ?
Many thanks for your help, Felix
luic> Is there a way for the user application to pass control back to the
luic> bootloader? I do a similar thing with two pieces of code, but I
luic> intentionally reset the stack pointer at the beginning of the user
luic> application since control cannot pass back to the bootloader. Would a
luic> similar scheme work for your project?
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
Sdcc-user mailing list
From: Felix Brack <fb@lt...> - 2005-04-20 16:20:45
To compile I use
sdcc -c -o .\\build\\ -I..\c51lib\include --model-large --nooverlay lmos.c
and to link I use
sdcc --model-large --xram-loc 0x0000 --code-loc 0x0000 --data-loc 0x00 --idata-loc 0x00 --stack-loc 0x80 -Wl -bBSEG=0x00 --iram-size 0x100 ./build/lmos.rel ./build/async.rel ./build/flash.rel ./build/int.rel ./build/lmos.rel ./build/modem.rel ./build/seslay.rel ./build/systime.rel ./build/tsplay.rel ./build/delay.rel
Sorry for the long line, it's a copy paste from the syn editor output
window. Please note that I use an SAB80C535 with 256 bytes of RAM. The
parameters above are for the firmware. To compile the user
application, I use the same settings as for the firmware. To link the
user application I currently use the following settings:
sdcc --model-large --xram-loc 0x0800 --code-loc 0x2000 --data-loc 0x30 --idata-loc 0x30 --stack-loc 0x80 -Wl -bBSEG=0x30 --iram-size 0x100 ./build/nightrd.rel ./build/kbrd.rel ./build/aio.rel ./build/pio.rel ./build/lcd.rel ./build/dio.rel ./build/convert.rel ./build/timer.rel ./build/mnuclock.rel ./build/mnumsr.rel ./build/menu.rel ./build/vlreg.rel ./build/errorlst.rel ./build/rtc.rel ./build/lcomm.rel ./build/communic.rel ./build/mem.rel ./build/delay.rel
The setting for --stack-loc of course is 'wrong' for me. The other
settings are more or less fine but still not optimized.
luic> What are your specific SDCC command line flags for the compiler and linker?