Pass rtc_clock to MicroNMEALocationProvider in all variants #1364
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Several variants were constructing
MicroNMEALocationProviderwithout passing thertc_clockreference, even though one was available in scope. This means GPS timefixes were never synced to the RTC on those boards.
This PR adds
&rtc_clockas the second constructor argument across all 18 affectedvariants, ensuring GPS-derived time is propagated to the RTC consistently.
Changed variants
heltec_mesh_solar, heltec_tracker_v2, heltec_v3, heltec_v4, keepteen_lt1,
lilygo_tbeam_1w, lilygo_tbeam_SX1262, lilygo_tbeam_SX1276,
lilygo_tbeam_supreme_SX1262, meshadventurer, nano_g2_ultra, promicro, rak3112,
rak3401, rak4631, rak_wismesh_tag, thinknode_m3, xiao_c3
Notes
heltec_trackeris intentionally excluded — it will be addressed by Support GPS properly on Heltec Wireless Tracker v1.x #1351(heltec_wireless_tracker_gps) which supersedes the change for that variant.
, &rtc_clockto the existingMicroNMEALocationProvider(Serial1)call. No behavioral changes beyondenabling RTC sync from GPS.