Skip to content

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 119 commits into from
Jul 23, 2020

Conversation

stephenf7072
Copy link
Owner

No description provided.

stephenf7072 and others added 30 commits March 23, 2020 17:01
Not very well tested.

(TX1 on Pad 10 does not work)
fix extern declaration of analog channel and config maps
contributions are tracked by commit history and contributors are acknowledged in the ACKNOWLEDGEMENTS.md file
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
adamgarbo and others added 29 commits June 3, 2020 11:03
use correct AP3_WireN_IOM macros
Fix for sequential PWM pin setting
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.
@stephenf7072 stephenf7072 merged commit 0af5eb0 into stephenf7072:master Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants