Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

IAR Kickstart Code Size Limitation?

IAR Kickstart Code Size Limitation?

2004-12-12 by tkreyche

Hi Group,
I recently got the IAR Kickstart Kit for LPC210x and have read all 
the docs and compiled and run sample apps -- everything works fine.

I'm confused by the code size limitation of the kit, the docs 
say "The kit also comes with a 32K code-limited version of IAR's 
Embedded Workbench."

When I compile the sample program runninglights, the output of the 
linker (ARM mode generating debug code) says:

 1168 bytes of CODE  memory (goes to 7k in Thumb mode)
 8456 bytes of DATA  memory
   12 bytes of CONST memory

The size of the on-disk image for RunningLights.d79 is 31.0 KB 
(31,806 bytes).

So is the limit based on the "CODE memory" size or the on-disk size 
or ? The 1.1k seems about right but IAR has nothing I can find in the 
docs or web site to clarify. I can ping them Monday but somebody must 
have run into this.

thanks, Tom

Re: IAR Kickstart Code Size Limitation?

2004-12-12 by tkreyche

--- In lpc2000@yahoogroups.com, "tkreyche" <tkreyche@w...> wrote:
......................
> 
> I'm confused by the code size limitation of the kit, the docs 
> say "The kit also comes with a 32K code-limited version of IAR's 
> Embedded Workbench."
> 
> ....................................................... 

> So is the limit based on the "CODE memory" size or the on-disk size 
> or ? The 1.1k seems about right but IAR has nothing I can find in 
the docs or web site to clarify. 

Never mind. I ran a test by generating a lot of floating point code.

One of the modules size was 26 976 bytes of CODE memory 
and when the linker added a couple others it went over 32k.

Fatal Error[e89]: Too much object code produced (more than 0x8000 
bytes) for this package. Fatal! Execution terminated...
Total number of errors: 1


Tom

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.