Package: gcc-avr
Version: 1:4.9.2+Atmel3.5.0-1
Severity: normal
Dear Maintainer,
Dear Maintainer,
I get erratic behaviour on my embedded device when I compile with the latest
version.
* What led up to the situation?
I updated the gcc-avr package to 1:1.8.0+Atmel3.5 and compiled my app
* What exactly did you do (or not do) that was effective (or
ineffective)?
First I get linker errors regarding the EEPROM library:
undefined reference to `eeprom_update_block'
Then I add the library for my device AT90CAN128 (this library is new in this
package, it seems)
avr-gcc -D__AVR_AT90CAN128__ -o myapp -std=gnu99 -mmcu=avr51 *.o -lprintf_flt
-lm -lat90can128
* What was the outcome of this action?
This compiles but when I upload it I get completely erratic behaviour, the
display flickers, TTL ports go up and down...
* What outcome did you expect instead?
The app should work as with the previous package version. Or maybe I'm doing
something wrong? Shouldn't it find the correct library by itself somehow?
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gcc-avr depends on:
ii binutils-avr 2.25+Atmel3.5.0-2
ii libc6 2.21-7
ii libgmp10 2:6.1.0+dfsg-2
ii libmpc3 1.0.3-1
ii libmpfr4 3.1.3-2
ii zlib1g 1:1.2.8.dfsg-2+b1
gcc-avr recommends no packages.
Versions of packages gcc-avr suggests:
ii avr-libc 1:1.8.0+Atmel3.5.0-1
ii gcc 4:5.3.1-1
pn gcc-doc <none>
pn task-c-devel <none>
-- no debconf information
