Hi Johann,
Hopefully my detailed reply to your beautiful explanatory example and
description of requirements, sent yesterday, has arrived. (Although it
still hasn't appeared on list. I'll post it there again, if it doesn't
show up after a full 24 hrs. I sent a copy to Jan, so he doesn't have to
wa
Erik Christiansen schrieb:
Hi Johann,
Hopefully my detailed reply to your beautiful explanatory example and
description of requirements, sent yesterday, has arrived. (Although it
still hasn't appeared on list. I'll post it there again, if it doesn't
show up after a full 24 hrs. I sent a copy to
Erik Christiansen schrieb:
Warning: Alternative solutions are offered for some of the sub-problems.
Choices are clearer at the end.
The best choice depends mostly on whether one default linker
script should handle all the use cases mooted here.
The reply
The first attempt to handle __flashN seems to be achieving what I
understand to be the requirements, as far as basic testing shows.
Please try to rip its arms off, so we can give it the robustness which
users need. (Also, what have I plain missed. ;-)
Here are two test cases based on one source co
Erik Christiansen schrieb:
Here are two test cases based on one source code example compared with
Johann's requirements for the script behaviour.
Here is more torture. Assemble with, e.g.
$ avr-gcc flash.sx -o flash.elf -DSTUBS=10 -DP1=0x200 -DTEXT=0x2
-mmcu=atmega2560 -Wl,-Map,flash.ma
