Kurt,
Remove the --iram-size 128 so you can still use the high
internal ram for idata variables and stack. Otherwise
everything must be crammed into the first 128 bytes.
Maarten
> Maarten;
>
> Thanks. I had remembered reading that the stack used idata and could be
> mapped into the upper
Maarten;
Thanks. I had remembered reading that the stack used idata and could be
mapped into the upper 128 bytes but didn't realize data and idata were
different. I also see where data access to the upper 128 bytes maps into
the CY7C68013's SFR space.
I assume if I set iram-size to 256 I ne
Hi Kurt,
I think you misunderstand the keywords data and idata
and did not fully graps the (im)possibilities of the
8051 internal ram. Data memory is only 128 bytes big and
it shares space with the registers and bit variables. In
the upper 128 bytes you can only have idata variables
and stack
kurt.m.sanger-qa2vv93yo6iavxtiumw...@public.gmane.org wrote:
> We was compiling fine, made a few additions, and now we're out of room.
> We are using a Cypress CY7C68013 with 256 bytes of iram and don't
> believe we should be out of room.
Check the lst file for the internal ram data section. Y
We was compiling fine, made a few additions, and now we're out of room. We
are using a Cypress CY7C68013 with 256 bytes of iram and don't believe we
should be out of room.
Exact error message is "?ASlink-Error-Insufficient space in data memory. 9
bytes short."
Link command line is in a dos bat
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
hai all,
i am compiling CC2430em application using sdcc compiler, its giving
the following error: ?ASlink-Error-Could not get 407 consecutive bytes
in internal RAM for area DSEG.
can anyone inform me what is cause for it and how to rectify it.
--
