I've submitted a bug report as requested.
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost i
To those in the know,
The code for printf (printf_large.c) is as follows. My question is,
should the space conditions be '>=' rather than just '>' ? (I did some
raw byte dumps of a __code U08 *, and the type was 0x80. And with the
change made, I get the correct output from printf!
Cheers,
Andy
I've trawled the archives, but not found a conclusive answer to this.
We have some code which Keil can compile and run happily, without using
much IRAM at all.
When I build with SDCC, the IRAM is full - see .mem below.
Since I'm using --model-large, what is it putting in IRAM? Is there a
way to f
Maarten,
Many thanks for the excellent response so far.
Please bear with the following lengthy explanation
It _IS_ a small app: the .map file shows all the code:-
Area Addr Size Decimal Bytes
(Attributes)
-
Maarten,
Many thanks for the excellent response so far.
Please bear with the following lengthy explanation
It _IS_ a small app: the .map file shows all the code:-
Area Addr Size Decimal Bytes
(Attributes)
-
Thanks a lot Maarten,
I've made sense of the extended address record. However one thing still
confuses me. If I build a small app that all fits in the common area,
the output.ihx still contains two extended address records, along the
lines of:-
:0204FA // I guess this means bank0?
..
I'm evaluating SDCC for a project, which needs code-banking (we estimate
code size >64k). Are there any examples of how to do code-banking? I
have seen and followed the instructions (see below), but I think there
is one thing I still need to know.
On our hardware, the common area is 0x4000-0x7fff,
