--- On Mon, 6/22/09, David Kelly dke...@hiwaay.net wrote:
Study the include files for register definitions for a means of
controlling the absolute address of allocation.
Thank you David Kelly for your response. I will sieve through the header files
to know how to allocate a variable to a
--- On Tue, 6/23/09, Joerg Wunsch j...@uriah.heep.sax.de wrote:
The only method to not have the linker reorder your variables is to
just use a single variable (per memory section). So, put some kind of
an embracing struct around all your variables you'd like to have in
a particular order, and
On Tue, Jun 23, 2009 at 02:02:37AM -0700, Parthasaradhi Nayani wrote:
--- On Tue, 6/23/09, Joerg Wunsch j...@uriah.heep.sax.de wrote:
The only method to not have the linker reorder your variables is to
just use a single variable (per memory section).? So, put some kind of
an embracing struct
--- On Tue, 6/23/09, David Kelly dke...@hiwaay.net wrote:
Something like this might work for you:
typedef struct {
uint8_t variable;
uint16_t a, b, c, d;
uint32_t e;
} FLASH_STRUCT;
#define flash_p ((FLASH_STRUCT *)(0x8000))
Hello David Kelly,
Thanks a lot for taking time to
Hello all,
I have interfaced flash memory to my mega64 and created a section for this
memory. I have some variables and two structures which are located in this
memory. Initially I defined the variables first and then the structure. After
linking I checked the map and list files and found that
On Mon, Jun 22, 2009 at 10:17:50AM -0700, Parthasaradhi Nayani wrote:
Hello all,
I have interfaced flash memory to my mega64 and created a section for
this memory. I have some variables and two structures which are
located in this memory. Initially I defined the variables first and
then the
