Skip to content

v0.6.1

Compare
Choose a tag to compare
@arntsonl arntsonl released this 13 Feb 18:52
· 696 commits to main since this release

This is the GP2040-CE v0.6.1 firmware release.

This release focuses on a number of bug fixes and back end code cleanup as well as improvements to the web-configuration ui.


  • The PicoAnn pinout has been added as a dedicated configuration | by @TheTrainGoes in #37
  • Board LEDs have been fixed to account for all inputs with raw input state | by @deeebug in #40
  • Fixed warnings caused by CFG_TUD_NET | by @deeebug in #43
  • PicoAnn has been added to the cmake deploy file | by @arntsonl in #42
  • Dual Directional’s SOCD logic has been updated Issue#24 | by @arntsonl in #41
  • The switch int values to proper absolute_time_t has been updated | by @deeebug in #47
  • Fixed multiple compiler warnings | by @mthiesen in #51
  • Fixed multiple debug build issues in FlashPROM | by @mthiesen in #50
  • Fixed bug #18 which now looks at current D-Pad mode | by @mthiesen in #45
  • Configs for normal and mirrored Fightboard v3 have needed added | by @thnikk in #46
  • Auto-detecting of SH1106 OLED displays has been implemented | by @mthiesen in #57
  • Added some missing #include guards | by @mthiesen in #64
  • Added buttons to preview the splash display and button layout in web-config | by @deeebug in #54
  • Implement of an add-on to set BOOTSEL as a usable button button (see note) | by @deeebug in #56
  • Implemented a memory report endpoint | by @mthiesen in #65
  • Added the ability to configure analog from web-config | by @deeebug in #61
  • Various README.md updates | by @TheTrainGoes in #69
  • A Fightboard LED theme was added | by @thnikk in #62
  • Fightboard display layouts have been added | by @thnikk in #63
  • A memory report has been added to the web-config | by @deeebug in #70
  • Updated some names in the code to generic names | by @deeebug in #72
  • Updated to the Fightboard booardconfigs for #56 | by @thnikk in #74
  • Added an OLED display saver feature | by @rafaelcruzpb in #44
  • Added HTTP response headers to webconfig API requests | by @mthiesen in #76
  • Fixed an issued cased by multi-chunk POST requests | by @mthiesen in #77
  • Fixed an issue where slider pins default value were changed | by @deeebug in #79
  • Added the ability to switch to webconfig mode without a hardware reset | by @mthiesen in #73
  • Code change to make requests for setSplashImage atomic | by @deeebug in #78
  • Added a delay startup for slow crystals and updated the build system (see note) | by @Fortinbra in #81
  • Added a reboot button to web configurator | by @deeebug in #86
  • Changed permissions to make makefsdata executable | by @thnikk in #87
  • General addon backend enhancements | by @arntsonl in #89
  • Updated the dual directional add-on to allow for single pin assignment | by @arntsonl in #91
  • Reenabled the buzzer add-on (see note) | by @deeebug in #92
  • Consolidation of the splash screen options in the web-ui | by @arntsonl in #94

Notes:



A new add-on allows the BootSel button on the official Raspberry Pi Pico to be used as a normal button. Please note that enabling this may cause displays and LEDs to stop working. This should be used only to test things on the Pico. This can be turned off via the web-ui to return other functionality.



We have added a startup delay to all configurations to account for growing reports of crystal issues. The default startup delay on the Raspberry Pi Pico is 47 which is roughly 1ms. We have updated this to 64 which is roughly 1.5ms. This allows lower quality crystals the ability to start up properly. This mainly affected Flatbox units that were assembled by JLCPCB but we have seen a few reports of it affecting the Waveshare RP2040 Zero units as well. You may have been affected by this if you loaded firmware onto a device and it worked until the first time it was unplugged and replugged in, which would result in a unit that appeared dead until put back into BootSel mode.


The buzzer add-on has been reenabled. We incorrectly thought this was causing issues on the M1 Mac. Those issues were actually addressed via #77.


---

New Contributors

Full Changelog: v0.6.0...v0.6.1