Open GoogleCodeExporter opened 9 years ago
I get a similar error. Also v2.3 but with Arduino 1.0.5 on a OpenSuse Linux
In file included from Max7456.cpp:2:0:
KV_Team_OSD.h:180:40: error: variable 'item_table' must be const in order to be
put into read-only section by means of '__attribute__((progmem))'
extern PROGMEM const char *item_table[];
Original comment by bejo5...@googlemail.com
on 26 Sep 2014 at 4:06
I could solve the problem with the use of an older Arduino version 1.0.1.
I guess the error depends on the integrated gcc compiler which also has changed
the version. But it would be quite nice if the code would be adapted to the new
compiler version.
Original comment by bejo5...@googlemail.com
on 29 Sep 2014 at 1:49
Has anyone figured our how to fix this?
Original comment by ajb...@gmail.com
on 2 Apr 2015 at 4:26
Same Problem here,
Arduino: 1.6.3 (Windows 7), Board: "Arduino Pro or Pro Mini, ATmega328 (5V, 16
MHz)"
Build options changed, rebuilding all
In file included from EEPROM.cpp:5:0:
KV_Team_OSD.h:180:40: error: variable 'item_table' must be const in order to be
put into read-only section by means of '__attribute__((progmem))'
extern PROGMEM const char *item_table[];
^
Error compiling.
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
Original comment by rens.toe...@gmail.com
on 4 Apr 2015 at 1:58
[deleted comment]
Same problem here.
++++++++++++++
Arduino: 1.6.2 (Windows 7), Board: "Arduino Pro or Pro Mini, ATmega328 (5V, 16
MHz)"
Build options changed, rebuilding
allC:\Users\Alan\AppData\Roaming\Arduino15\packages\arduino\tools\avr-gcc\4.8.1-
arduino2/bin/avr-g++ -c -g -Os -w -fno-exceptions -ffunction-sections
-fdata-sections -fno-threadsafe-statics -MMD -mmcu=atmega328p -DF_CPU=16000000L
-DARDUINO=10602 -DARDUINO_AVR_PRO -DARDUINO_ARCH_AVR
-IC:\Users\Alan\AppData\Roaming\Arduino15\packages\arduino\hardware\avr\1.6.2\co
res\arduino
-IC:\Users\Alan\AppData\Roaming\Arduino15\packages\arduino\hardware\avr\1.6.2\va
riants\eightanaloginputs
C:\Users\Alan\AppData\Local\Temp\build4254549908884914337.tmp\EEPROM.cpp -o
C:\Users\Alan\AppData\Local\Temp\build4254549908884914337.tmp\EEPROM.cpp.o In
file included from
C:\Users\Alan\AppData\Local\Temp\build4254549908884914337.tmp\EEPROM.cpp:5:0:C:\
Users\Alan\AppData\Local\Temp\build4254549908884914337.tmp\KV_Team_OSD.h:180:40:
error: variable 'item_table' must be const in order to be put into read-only
section by means of '__attribute__((progmem))' extern PROGMEM const char
*item_table[]; ^Error compiling.
Original comment by alan.kub...@gmail.com
on 11 Apr 2015 at 7:31
[deleted comment]
[deleted comment]
same problem here !!!
--------------------
Arduino: 1.6.3 (Windows 8), Board: "Arduino Pro or Pro Mini, ATmega328 (5V, 16
MHz)"
C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-g++ -c -g -Os -w
-fno-exceptions -ffunction-sections -fdata-sections -fno-threadsafe-statics
-MMD -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10603 -DARDUINO_AVR_PRO
-DARDUINO_ARCH_AVR -IC:\Program Files
(x86)\Arduino\hardware\arduino\avr\cores\arduino -IC:\Program Files
(x86)\Arduino\hardware\arduino\avr\variants\eightanaloginputs
C:\Users\gg\AppData\Local\Temp\build2908002897883449585.tmp\EEPROM.cpp -o
C:\Users\gg\AppData\Local\Temp\build2908002897883449585.tmp\EEPROM.cpp.o
In file included from
C:\Users\gg\AppData\Local\Temp\build2908002897883449585.tmp\EEPROM.cpp:5:0:
C:\Users\gg\AppData\Local\Temp\build2908002897883449585.tmp\KV_Team_OSD.h:180:40
: error: variable 'item_table' must be const in order to be put into read-only
section by means of '__attribute__((progmem))'
extern PROGMEM const char *item_table[];
^
Error compiling.
Original comment by ggeorg...@gmail.com
on 14 Apr 2015 at 5:50
I get the same problem on 1.6.1
Original comment by leviticu...@gmail.com
on 21 Apr 2015 at 11:56
Here's a fix for the latest android version:
in KV_Team_OSD.h:
change this: 'extern PROGMEM const char *item_table[];'
to this: 'extern PROGMEM const char * const item_table[];'
in KV_Team_OSD.cpp:
change this: 'PROGMEM const char *item_table[] ='
to this: 'PROGMEM const char * const item_table[] ='
and everything will compile, good luck!
Original comment by MichaelT...@gmail.com
on 24 Apr 2015 at 4:41
Also here is a fork of the 2.3 build with the fix already in place:
https://github.com/slacker87/rush-osd-development/archive/master.zip
Original comment by MichaelT...@gmail.com
on 24 Apr 2015 at 4:52
ok i did eeprom clear, loaded the github rush OSD but the GUI doesnt writ to
the board and the osd displayed on the video stream is all messed up and way
far right of where it should be
Original comment by CBRrunne...@gmail.com
on 22 May 2015 at 1:15
is there a fix for the windows version?
Original comment by CBRrunne...@gmail.com
on 23 May 2015 at 5:18
i ogt the same issu please help where i neet to change the program
Original comment by r.bura...@gmail.com
on 25 May 2015 at 12:45
I used an older version of arduino
but two solutions are above #11 and #12
Original comment by ggeorg...@gmail.com
on 25 May 2015 at 12:48
Arduino: 1.6.4 (Windows 8.1), Board: "Arduino Pro or Pro Mini, ATmega328 (5V,
16 MHz)"
In file included from EEPROM.cpp:5:0:
KV_Team_OSD.h:180: error: expected unqualified-id before '\x5d3b'
'extern PROGMEM const char * const item_table[];'
^
expected unqualified-id before '\x5d3b'
This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
Original comment by r.bura...@gmail.com
on 26 May 2015 at 3:36
[deleted comment]
i just upload the firmware but my OSD look like this. any idea please
Original comment by r.bura...@gmail.com
on 26 May 2015 at 11:29
Attachments:
im getting the same as the picture above..... any ideas?
Original comment by Disp0sab...@gmail.com
on 13 Jun 2015 at 5:42
I also loaded the "master" corrected version from above, but cannot write to
the board via the GUI. I'm thinking it might has something to do with the
arduino version and compiling...I'll try with older version of Arduino IDE.
Original comment by Dreaming...@gmail.com
on 13 Jun 2015 at 4:38
Original issue reported on code.google.com by
DHDo...@gmail.com
on 18 Sep 2014 at 5:52