Changes Include:
- Updated compiler: arm-gcc 14.2
- Serial interrupt priority fix.
- added menu for changing pclk, allows for 40Mhz SPI
- Support for output-only SPI
- SPI3 dma fix on V3 boards (collides with audio dma)
Most of these changes will be completely invisible unless you are trying out the new color display stuff in ProffieOS 8.
Next time you start up Arduino, it should notify that there is an update available, and you will be able to install this version from there.
Note that on Linux and Mac you need Arduino 2.x to install this version. On Windows, zip files are still used, which means a bigger download, but it might still be installable from Arduino 1.x. After installation, the new arduino-proffieboard plugin should work with both Arduino 1.x and 2.x.
4 Likes
I’ve been having issues with button combinations causing the board to crash with a screech. I can’t tell for sure if it’s the plugin that’s changed, or my buttons being flaky. Could you give me some help in diagnosing/testing?
I’m using the Fett263 prop and it’s controls such as volume menu (hold power + press aux) or voice battery level (hold aux + press power) that seem to trigger.
So, the best way to find squee-of-doom errors is to use a debugger, here are some old instructions for how: Running a debugger
If you can’t set up a debugger, the second easiest way is to figure out exactly what causes the crash, then have someone who does have a debugger try it.
Even if you don’t have a debugger, if you know exactly which key combination causes it, then it narrows down the amount of code we have to look through to search for the problem.
Also, if you suspect that the compiler is part of the problem, then please try an older version and see if it has the same problem or not.
I accepted the update and I received the following errors while compiling:
lto-wrapper: warning: using serial compilation of 20 LTRANS jobs
lto-wrapper: note: see the ‘-flto’ option documentation for more information
I believe that it will allow me to install my config onto the saber, but I have not done this yet. I am just checking to make sure that these are not critical errors before I upload to my saber using 4.6.
Thanks
There’s no problem there you can ignore it just crack on with the upload
This is a warning, you can safely ignore it.