AVR doper firmware compile issue
Posted: Mon Apr 07, 2008 8:18 am
Hi,
in order to change the AVR-Doper firmware version number I had to recompile the firmware. While doing so, I encountered a few problems:
When compiling with WinAVR20080402RC1 I get a few warnings:
../hardware.h:50:1: warning: "F_CPU" redefined
=> can be removed by commenting out the lines
../stk500protocol.c:137: warning: pointer targets in passing argument 1 of 'strcpy_P' differ in signedness
=> serious???
Anyway, when I flash the generated code ignoring the warnings, everything worked at first sight, but when I use AVR-Doper in HV-Mode, it looses USB connection during the flashing process. The originally provided hex works fine, though.
I also have installed an old version WinAVR20060421
here I get a different warning:
../timer.h:44: warning: comparison is always false due to limited range of data type
=> haven't tested the generated code on AVR doper.
Question:
-Which compiler version is the originally provided hex built with?
-Can the firmware successfully and functionally be built with new WinAVR versions? If so, how?
Thanks, Tom
in order to change the AVR-Doper firmware version number I had to recompile the firmware. While doing so, I encountered a few problems:
When compiling with WinAVR20080402RC1 I get a few warnings:
../hardware.h:50:1: warning: "F_CPU" redefined
=> can be removed by commenting out the lines
../stk500protocol.c:137: warning: pointer targets in passing argument 1 of 'strcpy_P' differ in signedness
=> serious???
Anyway, when I flash the generated code ignoring the warnings, everything worked at first sight, but when I use AVR-Doper in HV-Mode, it looses USB connection during the flashing process. The originally provided hex works fine, though.
I also have installed an old version WinAVR20060421
here I get a different warning:
../timer.h:44: warning: comparison is always false due to limited range of data type
=> haven't tested the generated code on AVR doper.
Question:
-Which compiler version is the originally provided hex built with?
-Can the firmware successfully and functionally be built with new WinAVR versions? If so, how?
Thanks, Tom