First of all, what is the best way to see how many bytes each *.c file in my project uses when compiled? (Is this what the "text=xxx data=0 bss=0" means in the project explorer, if not, what do those mean?). My current method of determining this is looking in the output folder and see how many Kb the *.hex file is, but there must be a better way.
Second, When I include <stdlib.h> and call:
Code:
float f;
f = atoff("123.456");
Just this change causes the size of my hex file to more than double, from 39.6kb to 81.8kb, and causes me to get "code size exceeded" error!
The same thing happens when doing this to the "toggle" example project. (using double and atof, or int and atoi have same issue)
Any input appreciated! This is a student project trying to use atoff when reading serial from a GPS.
Sorry, I meant that I get the "code size exceeded" error when trying to debug with RLink (32k limit). This is because a single call to stdlib uses basically all of the 32k limit. Is there a way to reduce the size of stdlib? atoff() can't actually consume 40k of flash can it?!
Also, for the first part of my initial question, how can I see the size of the compiled *.c files?
Size information: In the Project Windows, you can display this information (push on 'Show' then select Build Information. You can also look at the MAP file (View MAP File), but only after linked.
For debugging, this the difference between the standard license (limited up to 32KB) and the Pro license (no limitation). As a workaround, you can force the relocation of some functions (done in CircleOS) in the non-debuggable part (e.g. above 08008000). I am not sure if it works, but try the linker option 'Use small printf library'. We reduced the overall code size for Printf (and the called functions). But I am not sure because I don't see why atoff would be called (except if scanf had been optimized too...).
Thanks for your responses. kubsztal, I will try your code tommorow, I have tried to relocate stdlib to new flash section, and its getting very late. Do you have an atoi function as well?
Francis :
I am not sure if it works, but try the linker option 'Use small printf library'. We reduced the overall code size for Printf (and the called functions). But I am not sure because I don't see why atoff would be called (except if scanf had been optimized too...).
This does not affect the size of my program.
Francis :
For debugging, this the difference between the standard license (limited up to 32KB) and the Pro license (no limitation). As a workaround, you can force the relocation of some functions (done in CircleOS) in the non-debuggable part (e.g. above 08008000).
I tried this, and I did as you said by putting all standard library functions in a separate memory section above 0x8008000. I thought I would still be able to debug on the first 32k (put breakpoints and view values in first 32k only). The code with my modified linker compiles fine, however, I still get the code size limit exceeded error from Rlink when trying to debug. Here is how I modified the default linker file:
/* Sections Definitions */
SECTIONS
{
/* ADDED BY ME This should catch stdlib code */
.sect2 :
{
. = ALIGN(4);
lib_a* (.text .text.* .rodata .rodata.* .glue_7 .glue_7t)
} >FLASHBIG
/* REGULAR CODE BELOW */
/* for Cortex devices, the beginning of the startup code is stored in the .isr_vector section, which goes to FLASH */
.isr_vector :
{
. = ALIGN(4);
KEEP(*(.isr_vector)) /* Startup code */
. = ALIGN(4);
} >FLASH
.............................
I've verified that the standard lib functions get put in the FLASHBIG section looking at the map file.
I would like to be able to at least debug (put breakpoints and watch variables)in the first 32k, while still being able to call the standard library functions located outside of the first 32k.
It's possible to debug, but with some limitations: youmust avoid any 'stop' in the non-debuggable area. It means that you have to go from a breakpoint to another without stopping (nor single-stepping) in the non-debuggable area. When you want to stop, set a breakpoint in the debuggable area at a location you know you will pass..
What you just described is what I would like to do.
Attached is my modified Primer Toggle Example project with my modified linker script. The stdlib functions are in the FLASH above 32Kb, the main.c functions all in the first 32Kb. It builds, programs, and runs fine, but will not debug.
I don't have such one because I created atof just during reading this forum. For atoi you need only first loop from my example, remove checking for dot and assign result of calculations to (un)signed long instead of float. Before this loop you may add checking for minus sign in order to convert negative values correctly. Then after conversion of whole string multiply result by -1. You may also add checking for boundaries of (un)signed long and for accidental ascii characters other than digits inside the string.
Thanks kubsztal, I think I will probably end up using your function and doing atoi as well.
Francis, I know you are quite busy. I would still like to know how I could debug the first 32k while having additional data in flash above 32k with the Rlink. The file in my last post above contains the toggle example, adding in a call to atoff and my customized linker script that puts stdlib functions above 32k flash, Rlink still will not let me debug.
No. you can debug the lowest part of your module as long as you don't "break" your execution in the upper part. Perhaps some old versin of RIDE7 didn't allow this mode (get the latest one from the Raisonance web site, but a new version will be released early next week...).
Francis, I'm using RIDE7 version 7.18.0903 and Rkit-ARM 1.18.0903, and I cannot perform the functionality you are describing. However, I will wait one week for the new version, try it again, and post the outcome.
Francis, I have posted a youtube video of my screen showing what I experience: http://www.youtube.com/watch?v=_VVl2lCKlLs Sorry if the framerates a bit quick (Use the pause to read titles).
