On 12.03.13 12:53, Thomas, George wrote:
> When I checked the linker scripts, all __flashN's are going into the same
> location.
...
>
> Are there any issues in fixing these in the linker scripts ?
No, handling of __flashN's in a highly flexible and user-friendly manner
has been available for so
On 12.03.13 12:53, Thomas, George wrote:
>
> const int __memx *ramVar = &k;
...
> When I checked the linker scripts, all __flashN's are going into the same
> location.
Oh-oh, I'd up till now only read the text, not the code snippet.
We handle explicit __flashN's in the new linker script, but la
Hi Erik,
Thank You for sending down the patch.
Some of the doubts about the patch are :
1. If __flash5 is used then for placing the code we get only 0x5
to the rest of the flash for storing code (.text) . How can we make use
of the space before in a case where __flash1 - 4 are absent ?
2
I am implementing a boot-loader for the Xmega. Actually I have a working
boot-loader, but I had to do some ugly things that I am sure there are
proper ways to do if I were not so ignorant.
Pointers to FAQ, samples or replies appreciated. I did find the libc FAQ
and the gnu documentation on thi
