Clive Webster schrieb:
I've previously used WinAVR and their port of gcc has an 'enhancement' in
the avr-size which is option '-C' or '--format=avr' which also needs you to
Please notice that this mailing list is about GCC development, not about
binutils.
size is not a part of GCC. size is part of GNU binutils.
pass the chip type in '--mmcu=atmega328p' for example. This shows the total
amount of flash required (ie code + data), and RAM (ie data + bss) and
compares these against the abilities of the chip you have specified. This is
very useful in build scripts to fail code that is too big to upload to the
processor.
I'm trying to create a newer version of the AVR toolchain as WinAVR is now
quite old (January 2010!) - but need to work around this issue.
I'm not sure if it was functionality the WinAVR folk added themselves or
whether it's a 'no longer supported' option in gcc or if it originates
somewhere else!
For patches applied to the tools shipped with WinAVR, see respective
patches in your WinAVR distribution in folder ./source
For a list of files contained in your WinAVR distribution,
read ./WinAVR-manifest.log
For links to the projects, see the files ./source/SOURCE and
WinAVR-user-manual.txt in your WinAVR distribution.
Johann
