forked from sparkfun/Arduino_Apollo3
-
Notifications
You must be signed in to change notification settings - Fork 0
Bringing up to date with release1.1.2 #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
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
Not very well tested. (TX1 on Pad 10 does not work)
fixes #143 but can't explain exactly why
fix extern declaration of analog channel and config maps
contributions are tracked by commit history and contributors are acknowledged in the ACKNOWLEDGEMENTS.md file
Updated uart pad mapping
I think these were pre-development for the Apollo3 Plus
this includes several commented-out sections for modules that do not have corresponding definitions for the Apollo3. Reached out to Arpit at Ambiq Micro to address this
The full duplex direction enumeration was removed in SDK 2.4.2. Need to find out if this functionality is still supported or not.
The support is good enough to not warrant such strongly worded advice
This keeps our additional functionallity avaialble in our own source code so that the HAL can be easily updated later w/o worrying about undoing the configuration work.
Add variable I2C clock speed support
Corrected the pads for SDA2 and SCL2 on the Nano
this ensures that (when the timer is running) at least one pulse is emitted at each desired setting this removes concerns about calling analogWrite too often and changing the duty cycle the tradeoff is that analogWrite is now a blocking function that could take up to one whole timer period
Improve analogWrite
use correct AP3_WireN_IOM macros
Fix for sequential PWM pin setting
Create keywords.txt
In v1.x.x we are using (hh, mm, ss, hund, dom, mon, year) Planning to change api in v2.0.0 to (hund, mm, ss, hh, dom, mon, year)
…Time This allows the user to immediately access correct internal values (myRTC.weekday, myRTC.minute, etc...) ``` myRTC.setTime(23, 59, 59, 99, myRTC.dayOfMonth, myRTC.month, myRTC.year); previousDay = myRTC.weekday; ``` Updated Example3 to make use of this feature
This allows the user to see that the alarm fired 'exactly' when they wanted it to.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.