From 57978b04a7e141e0f34bc24088771a6fedea634e Mon Sep 17 00:00:00 2001 From: Ian McIntyre Date: Mon, 9 Feb 2026 17:04:50 -0500 Subject: 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. --- CHANGELOG.md | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'CHANGELOG.md') 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 -- cgit v1.2.3