Error compiling 3.1.4 final (Solved)
I'm trying to compile the latest Mk2.5 firmware and it fails with an "unrecognizable insn" error. Using Arduino IDE 1.8.5 on Windows 10, all libraries fully updated, and Rambo board added from https://raw.githubusercontent.com/ultimachine/ArduinoAddons/master/package_ultimachine_index.json . Previous firmware versions will compile. This one fails in mesh_bed_calibration.cpp (something with the new XYZ calibration). Also happens running the IDE in Ubuntu.
Google lead me Here, but I'm not sure if it's related. Is this happening for anyone else, or is it a problem with my Arduino IDE?
Full error:
Arduino: 1.8.5 (Windows 10), Board: "RAMBo"
sketch\mesh_bed_calibration.cpp: In function 'find_bed_offset_and_skew.constprop':
mesh_bed_calibration.cpp:2308: error: unrecognizable insn:
}
^
(insn 1420 1419 1421 80 (set (reg:QI 2128)
(subreg:QI (mem/v/c:SI (plus:HI (reg/f:HI 2127)
(const_int 8 [0x8])) [3 count_position+8 S4 A8]) 3)) sketch\xyzcal.cpp:766 -1
(nil))
sketch\mesh_bed_calibration.cpp:2308:1: internal compiler error: in extract_insn, at recog.c:2202
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See < http://gcc.gnu.org/bugs.html> for instructions.
lto-wrapper: C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avr-gcc returned 1 exit status
c:/program files (x86)/arduino/hardware/tools/avr/bin/../lib/gcc/avr/4.9.2/../../../../avr/bin/ld.exe: error: lto-wrapper failed
collect2.exe: error: ld returned 1 exit status
exit status 1
unrecognizable insn:
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
Edit: Solved the problem by using Arduino IDE 1.6.8
Re: Error compiling 3.1.4 final (Solved)
I'm getting the same error with 3.2.0-RC2. How did you fix it?
EDIT: Actually, I just saw that you went back to an older version of Arduino. Why would that fix the problem?
Re: Error compiling 3.1.4 final (Solved)
I also had this issue.
My fix was to re-install the "Arduino Addons"; seems like the Rambo stuff has changed.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: Error compiling 3.1.4 final (Solved)
I'm getting the same error with 3.2.0-RC2. How did you fix it?
EDIT: Actually, I just saw that you went back to an older version of Arduino. Why would that fix the problem?
1.6.8 is the version used for the Prusa firmware - check GitHub. Other versions have various issues, 1.6.8 is the one the devs say to use -
install "Arduino Software IDE" for your preferred operating system
https://www.arduino.cc -> Software->Downloads
it is strongly recommended to use older version "1.6.8", by which we can assure correct compilation results
note: in versions 1.7.x and 1.8.x there are known some C/C++ compilator disasters, which disallow correct source code compilation (you can obtain "... internal compiler error: in extract_insn, at ..." error message, for example); we are not able to affect this situation afraid
Re: Error compiling 3.1.4 final (Solved)
I'm having similar issues to all those before me, It won't compile the firmware for MK2.5. I have tried many different versions, 3.1.3, 3.1.4, 3.2.1 I am running Arduino 1.6.8 and have installed the Rambo board in the preferences from https://raw.githubusercontent.com/ultimachine/ArduinoAddons/master/package_ultimachine_index.json
I have tried uninstalling everything and reinstalling, with no change.
I have loaded a slightly older variant for the MK2s and it compiles just fine.
Any thoughts would be appreciated.
Leif
Re: Error compiling 3.1.4 final (Solved)
I have now been able to compile the MK2.5 with the new xyz calibration. After successfully uploading this it will run the Z calibration but will not run the first layer calibration. When a print is tried it runs the Z calibration and then stops. there is a message on the screen showing "STOPPED" it will not respond to commands sent through the USB even though it is connected.
The saga continues.