Exercise 9 now acquires satellites, more to do for this exercise, e.g. logging and RTC time setting
This commit is contained in:
parent
0077381546
commit
21825c09c6
3 changed files with 73 additions and 14 deletions
|
|
@ -2,10 +2,17 @@
|
|||
|
||||
This exercise boots the T-Beam Supreme and verifies GPS behavior at startup.
|
||||
|
||||
Important sequence note:
|
||||
|
||||
- Exercise 10 (`10_Simple_GPS`) should be completed before this exercise.
|
||||
- Exercise 10 README contains the detailed pin-configuration explanation and troubleshooting rationale for why explicit GPS pin mapping is critical on this hardware.
|
||||
- If GPS behavior is unexpected here, review Exercise 10 README first, then return to Exercise 9.
|
||||
|
||||
Implemented behavior:
|
||||
|
||||
1. Initializes PMU, OLED, and SD startup watcher (same startup SD path used in Exercise 08).
|
||||
2. Probes GPS at startup for NMEA traffic, module identity, satellite count, and UTC time availability.
|
||||
- Uses explicit GPS UART pins and an active startup probe (multi-baud + common GPS query commands), aligned with the approach validated in Exercise 10.
|
||||
3. If L76K is detected, normal GPS-time flow continues.
|
||||
4. If L76K is not detected and Quectel-style module text is detected, OLED shows a hard TODO error:
|
||||
- Quectel detected
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue