From c4ee315a20e41c234d2d0f7ca3ed7e37a09b9d32 Mon Sep 17 00:00:00 2001 From: Ian McIntyre Date: Sun, 9 Nov 2025 11:53:17 -0500 Subject: Add builder API for FlexRAM bank layout The layout, or assignment of FlexRAM banks to memory regions, is more precise than the count. When a user specifies the count, we still apply the same layout as we always have. But now, by default, we prefer the fuse layout for users who have made no choice. This commit supports RAM loading with probe-rs. After probe-rs resets the MCU and uses the fuse FlexRAM layout, firmware can perfectly match that layout without disrupting the data already copied into RAM by the debugger. --- CHANGELOG.md | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 7e59f3a..5dd5d73 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,16 @@ Establish a 32 byte reservation at the start of ITCM where instructions are never placed. This reduces the total capacity of ITCM by 32 bytes on nearly all MCUs, except the 1180. +### FlexRAM bank layouts + +The runtime builder lets users specify the _layout_, or assignment, of FlexRAM +banks. This is more precise than the _count_ of banks. + +By default, the layout remains an implementation detail of the builder. This is +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. + ## [0.1.7] 2025-06-14 Introduce `RuntimeBuilder::in_flash` for creating images that can be launched -- cgit v1.2.3