T114: Allow GPS to sleep, keep Vext active only when GPS is connected #924
+13
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
T114 power usage with GPS connected is higher than necessary: Even if GPS is deactivated and not used, its still powered up. Currently Vext is toggled for GPS, but if Vext is deactivated GPS hardware wakes up.
Solution: Allow GPS to sleep by setting the GPS_WAKEUP to low and toggle it when deactivating/activating GPS. GPS_EN is therefore mapped to GPS_WAKEUP. On board init: Enable Vext and set GPS_WAKE to high to check for GPS presence. If GPS is connected we have to keep Vext on and if not Vext can be turned off.