{{ message }}
Espruino Pico: Remove settings for DNP oscillator#4719
Merged
Conversation
Collaborator
Author
Collaborator
Yeah, I fixed the build problem with #4721. This seems to happen every time there is some updated software on the build system VPS's. |
Collaborator
|
@hierophect Could you drop an Espruino Pico build in #4714 for the OP there to test? I thought I could point to an artifact, but I don't see any artifacts. Thanks. |
Collaborator
Author
|
That's weird, don't they normally show up even when the build fails overall? Anyway yeah I can drop one over there. |
Collaborator
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
2 participants
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.
The LSE on the Espruino Pico is actually DNP, which isn't documented on the schematic. This was causing a clock failure after the 6.0 STM32 timekeeping reworks.
Resolves #4714