Skip to content

Commit 0812bdc

Browse files
mairasclaude
andcommitted
docs: update GNSS section for every-boot reconfiguration
The MAX-M8Q is ROM-based with no flash memory. Settings are saved to BBR only and may be lost on power cycles. Update docs to reflect that HaLOS reconfigures the receiver on every boot, and remove the now-obsolete "Late Installation" section. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent 15e75c9 commit 0812bdc

1 file changed

Lines changed: 3 additions & 14 deletions

File tree

docs/user-guide/interfaces.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -103,28 +103,17 @@ For u-blox receivers (such as the Max-M8Q), HaLOS Marine images additionally pro
103103

104104
### Auto-Configuration (u-blox receivers)
105105

106-
On HaLOS Marine images, a systemd service (`configure-gnss-marine`) automatically detects and configures u-blox receivers on first boot:
106+
On HaLOS Marine images, a systemd service (`configure-ublox-marine`) automatically detects and configures u-blox receivers on every boot:
107107

108108
| Parameter | Value |
109109
|:----------|:------|
110110
| Baud rate | 115200 bps (factory default: 9600) |
111111
| Update rate | 10 Hz (100 ms) |
112112
| Dynamic model | Sea (optimized for marine use) |
113113

114-
The configuration is saved to the receiver's flash memory, so it persists across power cycles.
114+
The configuration runs on every boot because ROM-based u-blox modules (such as the MAX-M8Q) have no flash memory. Settings are saved to Battery-Backed RAM (BBR), which may be lost when backup battery power is interrupted — for example, when the device is unpowered for an extended period. The reconfiguration is transparent and adds approximately 2 seconds to gpsd startup.
115115

116-
The auto-configuration service probes for the receiver on up to three consecutive boots. If no receiver is detected after three attempts, the service stops retrying. This accommodates manufacturing and testing workflows where the HAT may not be attached during initial device setup.
117-
118-
### Late Installation
119-
120-
If the GNSS HAT is installed after the auto-configuration window has passed, reset the service manually:
121-
122-
```bash
123-
sudo rm -f /var/lib/halos/gnss-marine-configured /var/lib/halos/gnss-marine-attempts
124-
sudo reboot
125-
```
126-
127-
The service will run again on the next boot and configure the receiver.
116+
If no receiver is detected, the service exits silently. A newly installed GNSS HAT will be configured automatically on the next reboot.
128117

129118
### Data Access
130119

0 commit comments

Comments
 (0)