-
Notifications
You must be signed in to change notification settings - Fork 114
Update stm32h7 #185
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
Update stm32h7 #185
Conversation
Hmm, some DAC changes as well. |
Thanks for this! I'll finish off the DAC changes, in this case adding new type parameters in the right place can get a bit tricky.. |
Hmm, when building the RTIC examples we end up with both cortex-m 0.6 (from RTIC) and cortex-m 0.7 (everything else) in the tree, and the compiler sees types from each version as distinct. Potentially this can be resolved by tweaking the examples |
The newer releases of cortex-m 0.6 re-export the types from cortex-m 0.7, so you should be able to just call |
3671b7e
to
bd43bcd
Compare
Some changes, mostly to H7B3
* DAC peripheral on rm0433/rm0399 parts is still called "DAC12" to match reference manual naming. We keep this, even though it is now quite confusing considering the existance of two separate DACs on rm0455 parts * Complete the HAL upgrade to support two DACs. We need to add the peripheral as a generic type on the Channel type, because we need different codegen for Cx on DAC2 compared Cx on DAC1. Add the REC type as an associated type for DacExt implementations. * 2nd DAC peripheral on rm0455 parts is actually capable of "autonomous mode" operation (srd/d3), but the D3AMR/SRDAMR register still needs some work in stm32-rs
cebae9a
to
77ece78
Compare
I see now that stm32 0.6 is not fully forward compatible: rust-embedded/cortex-m#333 |
Looks good, I added a little more explanation in the changelog. bors r+ |
Incorrect since stm32-rs#185
stm32h7 should have a release soon. Preparing for that.