here is no need to remove all the spill locations, you
just need to keep the number small enough that your code builds and runs.
--Mark Swayne
Jesse Lackey wrote:
> Hi - I'm using the large data model, and as I understand it all globals
> are in external RAM. And isn't idata th
e the number of extra bytes
> it allocated. It is recommended that this option NOT be used, #pragma
> nogcse can be used to turn off
> global subexpression elimination for a given function only."
>
> Would it help to use this option, maybe as a test?
>
> Bobby
>
> Ma
I don't have any ideas specific to Timer 1 and SDCC. But I do have a
suggestion.
Are your ISRs being run? You need to make sure that your ISRs are
defined when your main() routine is compiled, otherwise null, stand-in
ISRs will be used instead.
I have my ISRs defined in various, device speci
Dennis,
I have another thought as to what may be the problem. Do you see any
linker warnings when you build the sample from Keil with SDCC?
If you use the source from the keil site, the code will not work since
there is no putchar() function defined in the sdcc stdio.h. The
function is decla
using the large model. Several optimizations are
disabled when the program is compiled using
the large model, it is therefore recommended that the small model be
used unless absolutely required.
Thanks,
--Mark Swayne
Andy,
The records you posted are extended linear address records. Each one
specifies the upper 16 bits of the address, creating a full 32 bit address.
Each address prefix will last until a new prefix is declared.
:0204FA
:02 - Bytes in record
- address field - always 0 for this t
this instead:
foo = 3;
foo *= bar;
foo += baz;
* Avoid generic pointers.
* Break complex subroutines into smaller pieces.
I hope this helps.
--Mark Swayne
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Fra
I feel like I must be missing something super-obvious, but I'll ask anyway.
With SDCC installed via the installer, how do I rebuild my device libraries?
I've downloaded a recent snapshot, and I'd like to experiment with the
new huge memory model for 8051, but I need to compile the libraries in
>> With SDCC installed via the installer, how do I rebuild my device libraries?
>>
>
> Actually you can't since the Makefiles are (still) missing. You have to
> download the source package and build the libraries from there.
>
> Borut
Thanks for the reply. It leads to a few more (dumb?) que
ith 32 bit values.
The first 4 bytes passed to a function are free. So, if you are
careful to keep your API simple you will need to burn very little
memory for this issue.
I hope this information is useful.
Good night,
Mark Swayne
Maarten Brock wrote:
> Mark,
>
>
>> So, if I build a Linux compatible SDCC on Linux, can I use it to compile
>> the libraries and drop them into my windows environment?
> No, it should work ok.
>
This works perfectly.
>> What ./configure options do I need to use to enable the huge mode
>>
Thanks to Maarten and Borut's help I was able to get --model-huge code
working on my system.
I did run into one issue: if my code contains a _sdcc_external_startup
routine, the stack gets blown up on return.
As far as I can tell, what happens is this:
1. We jump to _sdcc_gsinit_startup
2. _sd
I am continuing to experiment with the new --model-huge option.
When I try to link files that exceed 64 of code, I get an insufficient
memory error from the linker:
?ASlink-Error-Insufficient ROM/EPROM/FLASH memory.
I assume that I will need to modify the linker script and manually link
th
After some research, I found Anthony Asterisk's post from December 2009
- how to: mcs51 bank switching on cc2430
http://sourceforge.net/mailarchive/forum.php?thread_name=4B2FC8D2.8090807%40gmail.com&forum_name=sdcc-user
Once I added the "-Wl-r" switch to my link flags, the code linked
Sorry for the cross post, but this discussion is taking place in at least two fora.Here are the issues with different licenses:1. LGPL protects the libraries, but static linking make it's terms identical to the GPL, thus it is unsuitable for our use.2. BSD license is almost like public domain, an
Lloyd Sargent wrote:
> Mark Swayne <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> wrote:
>
>> Here are the issues with different licenses:
>>
>>
>> 1. LGPL protects the libraries, but static linking make it's terms
>>
>> identica
Try:
#define XTAL 11059200
#define TICK_PERIOD20 /* 1/TIME_TICK */
#define RELOAD_VALUE -( XTAL/ (12 * PERIOD) )
TL0 = ( unsigned char ) ( RELOAD_VALUE );
TH0 = ( unsigned char ) ( RELOAD_VALUE >> 8 );
or:
#define XTAL 11.0592e6
#define TIME_TICK50e-3
#def
George M. Gallant, Jr. wrote:
> On Wed, 2006-07-12 at 19:52 -0700, Mark Swayne wrote:
>> Try:
>>
>> #define XTAL 11059200
>> #define TICK_PERIOD20 /* 1/TIME_TICK */
>> #define RELOAD_VALUE -( XTAL/ (12 * PERIOD) )
>>
>
I've seen an error like this when the directory I am trying to compile
to doesn't exist.
In your example, does the directory 'abc' exist? It could be that your
IDE is using an unexpected directory as its working directory.
Abhishek / TRI Technosolutions Pvt. Ltd. wrote:
>
>
>
>
> Hi
> i m dev
Somunaidu Boddu,
You are using all your direct memory.
Try either moving your variables into xdata or compile with --model-large.
--Mark
somunaidu boddu wrote:
> hai all,
> i am compiling CC2430em application using sdcc compiler, its giving
> the following error: ?ASlink-Error-Could not get 407
Another debugger file.
amazing-blinker.ihx Intel hex file.
amazing-blinker.map A listing of what is assigned where. Very useful to
learn to read.
amazing-blinker.mem A memory allocation overview. Easy to read, and
important too.
IIRC there's a something the User's Guide abo
ch files, and Microsoft NMAKE.
SDCC is UNIX and Linux software.
In my experience, SDCC is also Windows software.
--Mark Swayne
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coole
22 matches
Mail list logo
