Dhakshinamoorthy, Soundararajan schrieb:
Hi all,
Can someone advise a way to support device specific linker scripts in
binutils for our AVR port. Currently bintuils is based on device
architecture and not device as i understand.
This is a reasonable approach. Just imagine what a device-specific
approach would men in the ARM world, not taking into account different
RAM and flash configurations...
I am trying to update the linker scripts, with the start address of
boot section, which is different for each device (or atleast i don't
seem to find a way to compute it based on the information available
in binutils )
If such linker scripts shall become the default linker scripts then you
need 200+ emulations to support the 200+ devices.
Maybe you can have a look at how the tools handle different RAM start:
The compiler just calls the linker with Tdata to provide the
information. This you could add a new column to
./gcc/config/avr/avr-mcus.def and use that information appropriately.
Johann
:)
Thanks, Soundararajan
------------------------------------------------------------------------
_______________________________________________ AVR-GCC-list mailing
list AVR-GCC-list@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
_______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
