Add RAMECC registers across the H7 family #353
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
|
Can we just define RAMECC1 and have 2 and 3 derive from that, rather than redefining the registers for each one? |
RAMECC was 'added' to the single core parts in RM0433 Rev 7. For the dual core parts there are definitions, but they are so terrible it's worth starting over. (there's registers with the wrong address and wrong fields) The RAMECC2 and RAMECC3 registers are derived from RAMECC1. RAMECC3 only has two useful monitor channels, but there seems to be no harm in accessing the remaining channels. For a use case, there is at least one set of commercial spaceflight hardware using the H7: (no affiliation, no endorsement intended) - [Nanoavionics OBC](https://nanoavionics.com/cubesat-components/cubesat-on-board-computer-main-bus-unit-satbus-3c2/)
|
Yup, done. RAMECC3 only has two monitors connected, but I assume its safe to access the remaining monitor registers.. |
|
On a real target (H747), RAMECC3.M[3-5]CR locations are not really registers (they don't read what was just written to them). I think the easiest solution to only keep RAMECC3.M[1-2]* is to keep the separate |
RAMECC3 only has two monitoring units
bors bot
added a commit
that referenced
this pull request
Mar 28, 2020
353: Add RAMECC registers across the H7 family r=adamgreig a=richardeoin RAMECC was 'added' to the single core parts in RM0433 Rev 7. For the dual core parts there are definitions in the SVD, but they are so terrible it's worth starting over (there are registers with the wrong address, and the wrong fields) For a use case, there is at least one set of commercial spaceflight hardware using the H7: (no affiliation, no endorsement intended) - [Nanoavionics OBC](https://nanoavionics.com/cubesat-components/cubesat-on-board-computer-main-bus-unit-satbus-3c2/) Co-authored-by: Richard Meadows <962920+richardeoin@users.noreply.github.com>
Timed out |
|
bors retry |
Build succeeded
|
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.
RAMECC was 'added' to the single core parts in RM0433 Rev 7. For the dual core parts there are definitions in the SVD, but they are so terrible it's worth starting over (there are registers with the wrong address, and the wrong fields)
For a use case, there is at least one set of commercial spaceflight hardware using the H7:
(no affiliation, no endorsement intended)