diff options
| author | Ian McIntyre <me@mciantyre.dev> | 2026-02-09 17:04:50 -0500 |
|---|---|---|
| committer | Ian McIntyre <me@mciantyre.dev> | 2026-03-08 14:12:21 -0400 |
| commit | 57978b04a7e141e0f34bc24088771a6fedea634e (patch) | |
| tree | 66d7baa46399d8a87414e583c4e52a937b2ef542 /CHANGELOG.md | |
| parent | 38afb9f2e22badada26ebf833a5ee48ced4ac257 (diff) | |
Restrict RAM if ECC is enabled
As of this commit, the RuntimeBuilder only limits the available OCRAM
if either ECC controller is enabled. It's misleading; however, it gives
users a chance to evaluate their firmware builds with the restricted
RAM regions. I'll add and test the controller setups in a later commit.
Existing tests still pass. New unit tests demonstrate the restricted
RAM behavior.
Diffstat (limited to 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index afae79a..d97758f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -32,6 +32,15 @@ true if you only specify the count, or if you make no choice. However, if you specify the layout, the builder guarantees that the FlexRAM banks will match that layout. +### ECC RAM for 11xx MCUs + +You may optionally enable ECC RAM on 11xx MCUs. The implementation supports + +- FlexRAM ECC for TCM and FlexRAM-managed OCRAM. +- MECC64 for dedicated OCRAM. + +See the ECC RAM documentation on `RuntimeBuilder` for more information. + ## [0.1.7] 2025-06-14 Introduce `RuntimeBuilder::in_flash` for creating images that can be launched |
