-
Notifications
You must be signed in to change notification settings - Fork 17
Closed
Labels
Description
RTK Everywhere version: v2.1-Feb 20 2025
Board: RTK Postcard
Using the serial config menu, selection of the option u) Update to new firmware
fails with Unknown choice: u
.
SparkPNT RTK Postcard v2.1-Feb 20 2025
** Bluetooth SPP and BLE broadcasting as: Postcard Base-E626 **
Menu: Main
1) Configure GNSS Receiver
2) Configure GNSS Messages
3) Configure Base
4) Configure Ports
5) Configure Logging
6) Configure WiFi
7) Configure TCP/UDP
f) Firmware Update
i) Configure Corrections Priorities
p) Configure PointPerfect
r) Configure Radios
s) Configure System
u) Configure User Profiles
+) Enter Command line mode
x) Exit
f
Menu: Firmware Update
Current firmware: v2.1-Feb 20 2025
a) Automatic firmware updates: Disabled
c) Check SparkFun for device firmware: Not requested
e) Allow Beta Firmware: Enabled
u) Update to new firmware: v2.2-Mar 10 2025 - Not requested
x) Exit
u
Unknown choice: u
Menu: Firmware Update
Current firmware: v2.1-Feb 20 2025
a) Automatic firmware updates: Disabled
c) Check SparkFun for device firmware: Not requested
e) Allow Beta Firmware: Enabled
u) Update to new firmware: v2.2-Mar 10 2025 - Not requested
x) Exit
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
PaulZC commentedon Mar 24, 2025
Hi Andrew (@aceat64 ),
Thanks for reporting this.
The root cause appears to be that
newOTAFirmwareAvailable
is never set totrue
. This line is the critical one. @nseidle was restructuring the code around the time of this commit. Looks like we missed something.While we fix this, there is a work-around:
Open the "Debug Software" menu (s d). Set option "60) Print firmware update states" to "Enabled".
Exit the menus.
Re-open the Firmware Update menu.
Ensure you have "Allow Beta Firmware" set to "Enabled", and you should be able to update.
Best wishes,
Paul
[-][Bug] [RTK Postcard] Can't start OTA Update via serial, Unknown choice: u[/-][+][Bug] Can't start OTA Update via serial, Unknown choice: u[/+][-][Bug] Can't start OTA Update via serial, Unknown choice: u[/-][+]Can't start OTA Update via serial, Unknown choice: u[/+]nseidle commentedon May 21, 2025
I believe this is no longer an issue in the RC. To test it, I overwrote the prefix to 'v' in firmwareVersionFormat() and manually set the firmware version in firmwareVersionGet()
With the above version set to 2.0 I get the following output:
A successful update commences. This is expected behavior because the emulated version number is lower that the production release version.
With the above version set to 2.1 I get the following output:
An update successfully commences. This is expected behavior, the production release is the same, but an RC is available.
I'm going to remove some of the FIRMWARE_VERSION_MAJOR == 99 checks and rely on the settings.debugFirmwareUpdate override for our own testing purposes.
Remove FIRMWARE_VERSION_MAJOR checks during firmware update