We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I downloaded the newer version of the demo RealView Compiler (3.23) and suddenly whenever I compile a program for my LPC2103 it adds 16 KB of read only data. No matter how small and simple the program is.
It looks like they increased the debug limit from 16KB to 32KB also. That makes me think they are aware that programs are now going to be 16KB larger so they needed to expand the limits of the demo. But does anyone know why it would be using the space.
It looks like a total waste. In the map file it says that it is all (incl. padding) RO-data. Which makes me think its just empty padding. Is there some option I'm missing? Or some checkbox to check to turn off this 16KB of empty space, or some reason for it to be appearing?
I'm at a complete loss.
Andy; I really don't know why Keil did this but I can guess. They are attempting to limit the eval from running small programs that can execute in 16K. The user would not require the full purchase version for real developement. Keil did a similiar thing with the PK51 many years ago when the eval could run a 4K program. They offset the startup by 4K so you could not use the many 4K devices in real production. So, I'm guessing they attempting to offset the code by 16K. Remember, I'm just guessing at this. Bradford