Proffie 2.2 Verify Error Messdage

I am using Proffie 6.7 on 2.2 board. I just received a new saber that I am trying to program. I have programmed previously (successfully), but I am by no means an expert. I used the video from Absolute Sabers to program, following step by step. On previous sabers, had no issues. On this one, I get an error when I try to verify after placing in my config file. I have tried this about 5-6 times and keep getting errors. Not sure what is going wrong. here is the error message I get when verifying:

Arduino: 1.8.19 (Windows Store 1.8.57.0) (Windows 10), Board: “Proffieboard V2, Serial + Mass Storage + WebUSB, SDCARD (SPI), 80 MHz, Smallest Code”

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

cc1.exe: warning: command line option ‘-felide-constructors’ is valid for C++/ObjC++ but not for C

c:/users/hawkf/onedrive/documents/arduinodata/packages/proffieboard/tools/arm-none-eabi-gcc/9-2020-q2-update/bin/…/lib/gcc/arm-none-eabi/9.3.1/…/…/…/…/arm-none-eabi/bin/ld.exe:C:\Users\hawkf\OneDrive\Documents\ArduinoData\packages\proffieboard\hardware\stm32l4\4.6.0\variants\STM32L433CC-ProffieboardV2/linker_scripts/STM32L433CC_FLASH.ld:224: warning: memory region `SRAM2’ not declared

lto1.exe: internal compiler error: compressed stream: data error

Please submit a full bug report,

with preprocessed source if appropriate.

See https://gcc.gnu.org/bugs/ for instructions.

lto-wrapper.exe: fatal error: C:\Users\hawkf\OneDrive\Documents\ArduinoData\packages\proffieboard\tools\arm-none-eabi-gcc\9-2020-q2-update/bin/arm-none-eabi-gcc returned 1 exit status

compilation terminated.

c:/users/hawkf/onedrive/documents/arduinodata/packages/proffieboard/tools/arm-none-eabi-gcc/9-2020-q2-update/bin/…/lib/gcc/arm-none-eabi/9.3.1/…/…/…/…/arm-none-eabi/bin/ld.exe: error: lto-wrapper failed

collect2.exe: error: ld returned 1 exit status

exit status 1

Error compiling for board Proffieboard V2.

This report would have more information with
“Show verbose output during compilation”
option enabled in File → Preferences.

Have you tried reinstalling the Arduino Proffieboard plugin under menu Tools>Board>Boards Manager?

Also, to post your error, please use 3 back ticks on the line before and after (it makes it much easier for us to read the code) like this:

```
your error code (or your config) here
```

BTW, you also might want to post your config (same as above). But if it is too big, post your config on:

and copy/paste the link here.

Sorry for the delay in responding - been tied up at work. Here is a link to the config file:

Vader Saber Config - Pastebin.com

With regards to the 3 backticks for the error code message…the whole thing is in red, and looks like multiple errors…wasn’t sure what is an error, and what is extraneous, so I posted what came up.

With regards to Arduino - yes, I did reinstall it. Still error messages.

I have tried going at this multiple ways and multiple times, but keep hitting a brick wall. Much appreciated with your responses and any help you can give!!!

At your own pace is fine. No worries.

So in File, Preferences, you can set compiler warning to: none (I think that should get rid of all the cc1.exe: warning(s))

For the rest, you config compiles for me:

C:/../AppData/Local/Arduino15/packages/proffieboard/tools/arm-none-eabi-gcc/14-2-rel1-xpack/bin/../lib/gcc/arm-none-eabi/14.2.1/../../../../arm-none-eabi/bin/ld.exe:C:\..\AppData\Local\Arduino15\packages\proffieboard\hardware\stm32l4\4.6\variants\STM32L433CC-ProffieboardV2/linker_scripts/STM32L433CC_FLASH.ld:224: warning: memory region `SRAM2' not declared
lto-wrapper.exe: warning: using serial compilation of 8 LTRANS jobs
lto-wrapper.exe: note: see the '-flto' option documentation for more information
Sketch uses 244912 bytes (93%) of program storage space. Maximum is 262144 bytes.

So the problem is not in your config.

Sorry, I can’t be more help.

There are some funky characters in the later presets (the defaults). I don’t know if that’s a cut-n-paste thing but it could need to be cleaned up, although the double slash should be enough.

Like:

 { "TeenysSF", "tracks/mercury.wav",//23   ---2022.7.25Ìí¼Ó 

Since you are reprogramming, you could also do an update to your styles and OS. Takes a little time but solves a lot of issues. I use Fett263’s library for the most part, which has all of your links handy.

The header on your config also says it’s several things that are odd like

// This saber has:
//   o Proffieboard V1 hardware.
//   o Two buttons
//   o An XP-E2 RGB LED star on LED 4-5-6
//   o A neopixel blade on LED 1-2-3 and neopixel data 1.

Looking at your blade array, you really have a neopixel blade on LED 2-3 and data1 and no RGB LED star.

Still, it does compile on my mac but I’m using:
Arduino 2.3.4
Plugin 4.6
ProffieOS7.14

So you could try just upgrading all or any of those components.

So this error either means that your compiler installation is broken, or that you have mixed files, meaning some were compiled with version 3.6.0 of the arduino plugin and others with 4.6.0.

If you enable verbose compilation and post your full error message, I might be able to discern if there are some cached files you can delete to possibly fix the problem.

Well, I’ve tried several things, none of which worked…I tried installing 4 different versions of Arduino, after uninstalling what was on my PC…currently using 1.8.3. Tried different versions of Proffie. This latest try was with 7.14 (or maybe 7.15 - becoming a blur). I removed some of the extraneous verbiage mentioned earlier. I just installed Windows 11 - I was on Windows 10 - still, nothing working. I am so confused…I have been able to upload revised config files at least a half a dozen times before now without and issues. Here is a link to the current error message I get when I try to verify it…I would be much obliged if anyone can give jme some suggestions to try…otherwise, i may just turn this into a non-working display hilt. Much appreciated!!!

1. lto1.exe: internal compiler error: compressed stream: data error

This is a compiler error that happens when you mix up files from different version of the arduino-proffiieboard plugin.

Normally this shouldn’t happen, but arduino sometimes gets confused.

Try deleting C:\\Users\\hawkf\\AppData\\Local\\Temp\\arduino_*, restart arduino and try again.
If that doesn’t work, try re-installing the arduino-proffieboard plugin.

ALso, Arduino 1.8.3 is ancient. Either use 2.x or the last 1.x version (which I think is 1.8.19)

I know there are Youtube videos that say “do not use Arduino IDE v2.xx because …” but that has been solved in the mean time. I have been using IDE 2.3.4 and 2.3.5 when it was released and never had an issue, yet!

Sorry I can’t remember the details, but it has been fixed.

Well to be fair, it is still what your website recommends… I’ve seen several times now people will look at your website and go off of that.

1 Like

Fixed now.

2 Likes

Goooooood

Thanks! :slight_smile:

Success!!! Well, sort of…I deleted everything related to Arduino in the Temp folder. I then used Revo Uninstaller to completely remove Arduino. I downloaded 1.8.1.9 (I tried the latest version, but I could not follow the new format) and reinstalled it. I went back in and made sure all of the settings were correct, added my config, ran “verify” and no error messages. Then I uploaded it to the board, and it worked.

Except for 1 issue - this is my 5th saber. My first 2 were automatically “seen” by my PC when I plugged the board in to the USB port, and I was able to modify/add styles through the “Easy ProffieOS Customization” site (I think you refer to it as the “Workbench”) . With my 3rd, 4th, and now this saber, that site did not recognize my board until I re-uploaded the config file onto the board, making sure to select Tools: USBType: “Serial + Mass Storage + WebUSB” and DOSFS: “SDCard (SPI)”. On the 3rd and 4th sabers, after I uploaded the config to the board, I went to the Easy ProffieOS site, selected the “Here” link to go to the Workbench, and then a popup came up to select Proffie (the first time, and then it was always recognized thereafter). However, on this current one, a message comes up saying “No WEBUSB Found” Any ideas how to get this enabled from here? It feels like I’m really close - maybe just missed a step or something? Does this have anything to do with needing to install Zadig? Didn’t need to do that with Windows 10, but maybe now that I just updated to Windows 11? Thanks again for the help and getting me this far!!

That’s just weird. I mean, they are programmed the same right?

As far as I can tell, yes. Unless you have other thoughts, I think I will try uploading again…stranger things have happened with programming - maybe just a glitch that will be fixed by trying again.

So, windows is weird…

Some people end up in this situation where different boards get different drivers, and they have to run zadig every time to make it work. I’m not saying you should run zadig to fix your problem, I’m just saying that sometimes, windows decides that the serial number of the board matters when deciding which driver(s) to use. I don’t know why.

Whatever the reason is, this may provide an explanation as to why different boards behave differently - or not. Maybe they are not actually programmed the same somehow?