I2C fixes and tweaks
- GPIO pins are now color-coded with respect to their I2C lane - I2C0 pin pairs are colored blue, and I2C1 pin pairs are colored orange.
- When mapping I2C functions (either Camera SDA/SCL or Peripheral SDA/SCL), the current pin layout is checked to ensure that a Camera function isn't mapped in the same lane as a Peripheral function, or that the Camera/Peripheral partner of a pair (Data or Clock) aren't already mapped to the opposite lane; if either condition aren't met, the offending pin is unmapped with an appropriate message printed in the status bar.
- Changes to NeoPixel settings will appropriately notify that a reboot might be required to see changes properly reflected, as it's a limitation of how the NeoPixel library handles pixel strand remapping.
- Raspberry Pi Pico (W) and Arduino Nano RP2040 Connect default layouts now properly reflect a default Temperature Sensor mapping that was added in the last released OpenFIRE Firmware.
- App now correctly parses version numbers with alphanumeric characters, e.g. git hashes attached from firmware GitHub artifacts.
Installation
For Windows users, extract to wherever is most convenient. Run OpenFIREApp.exe
For Linux users, Arch Linux has an AUR PKGBUILD available @ openfireapp, installable using your favorite terminal/AUR helper. For other distros, use OpenFIRE_App-x86_64.AppImage.
Your user should be a part of the dialout library to be able to access serial ports--the app will alert you and provide the command to copy-paste into a terminal to add your user to said group. For other distros or architectures (i.e. Raspberry Pi/ARM systems), refer to the README for build instructions for your system.
At the moment, a microcontroller running OpenFIRE needs to be plugged in before starting! Hopefully this will change in a future app update.