You've now found yourself exactly where I did. I wanted to bury a
software part number at
0x100 in the flash so a 'universal' programming 'pod' could look in
this specific location of
the hex file and determine if the target was valid for an upgrade
regardless of what AVR
was implemented on the
Thanks for the links, but that is not exactly what I am looking for. Using this
document I was able to create output like this:
0x-0x008F .vectors
0x0090-0x03FF gap
0x0400-0x041F my section
0x0420- rest of the .text section
The gap is empty - it's waste of the flash space. I have not
Yes, that will place the .length segment between .vectors and .progmem. But
you
are unable to place it to some exact address. That will place it to address
that is
offset_of(.vectors)+length_of(.vectors). That can be different for some cpus.
So what? You are able to reference the location
Yes, that's exactly what I need. And yes, I'm used to IAR and others, where
this is possible. I wanted to find out if it is possible to do this with gcc, I
really did not expect any problem with this. I thought that I just have not
found the right documentation... :-(
_
From: [EMAIL
Hi All,
It's finally here, just in time for the holidays! WinAVR 20071221.
Very Special Thanks to all the contributors and all the toolchain
maintainers: Joerg Wunsch, Anatoly Sokolov, Dmitry Xmelkov, Denis
Chertykov, Marek Michalkiewicz, and anyone else I may have forgotten.
Because we're
