Your linker call is missing the -mmcu option.
That's why no startup code has been scheduled to link against.
OMG, thank you, it works :)
___
AVR-libc-dev mailing list
AVR-libc-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
As avr-libc-devel wrote:
> >Seems like a strange compiler build.
> In my opinion, the problem at the link stage: the object file after
> compilation looks OK
Yes, but the linker is driven by the compiler.
> 2.$ avr-gcc blink.o -v -o blink.elf
Your linker call is missing the -mmcu option.
That'
Seems like a strange compiler build.
If this can be useful, I will provide an user account in Debian 9.7,
where I try to compile the project — you can try your thoughts on this
installation, if you wish.
___
AVR-libc-dev mailing list
AVR-libc-dev@non
Seems like a strange compiler build.
In my opinion, the problem at the link stage: the object file after
compilation looks OK
Command line to compile the project:
$ avr-gcc -iquote . -Os -pipe -mmcu=attiny2313 -mint8 -g -c -o blink.o
blink.c
While I would not recommend using -mint8 (it has b
As avr-libc-devel wrote:
> Can anyone comment on what is going on?
Seems like a strange compiler build.
> Command line to compile the project:
> $ avr-gcc -iquote . -Os -pipe -mmcu=attiny2313 -mint8 -g -c -o blink.o
> blink.c
While I would not recommend using -mint8 (it has been deprecated for
Hello friends.
A long time ago, more than 10 years ago, I used avr-gcc + avr-binutils +
avr-libc on Linux.
Today I had to compile a test project with a modern installation of
avr-gcc, avr-binutils, avr-libc.
And I noticed a strange assembler code in the listing: there is no
initialization of th
