My understanding of "global" variables is that anything
declared outside of a function definition is allocated
in the heap at link time, and the final size of that
heap is what is reported as RAM usage. All variables
inside functions (that are not labeled static in real C)
are just names for stack
Hi Ricardo,
I'm not sure I understand your explanation. Also, I'm not entirely sure
how this works on the microcontroller. Essentially, a program consists
of a number of sections. One section is the actual program code (i.e.,
the instructions in binary form), and for the programs generated by
Thanks for the reply.
Let me get this straight, the actual occupied memory is provided as a value
for the ROM (13800). The flash memory contains the .hex file, which is then
decomposed into the ROM and RAM.
Is my understanding correct?
Regards,
--
Ricardo
On Fri, Jul 16, 2010 at 2:40 PM, Urs Hu
Hi Ricardo,
The HEX file is a text file. Every byte of the binary is written as two
characters (human readable hex values). In addition, there are
addresses, checksums and other programming or control information.
If you don't assign any value to a variable declaration, that variable
will get
Hello everyone,
I'm trying to understand the relationship between ROM and RAM .hex file
generated in the build.
It has been said here that:
>> In words few ROM includes the code and initialized data RAM and includes
>> BOTH initialized and uninitialized data (note the stack That Is Not
>> Includ
