From 2fec327652c16c0352473f9a36152493630a7f57 Mon Sep 17 00:00:00 2001 From: Ian McIntyre Date: Sat, 14 Jun 2025 14:48:59 -0400 Subject: Update cortex-m-rt to 0.7.5 There's an unreleased commit upstream to support stack painting with custom memory layouts, like ours. I eagerly defined the _stack_end symbol. Tested on hardware. --- CHANGELOG.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 0ae56f7..70c7376 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -21,6 +21,24 @@ 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. +### cortex-m-rt 0.7.5 + +Update to cortex-m-rt 0.7.5. The new runtime introduces additional build-time +features. You could enable these features yourself by depending on the same +`cortex-m-rt` package and selecting features. Here's how this runtime supports +each `cortex-m-rt` feature. + +The `paint-stack` feature is not supported. Do not enable this feature. +(Upstream commits suggest that we should be able to support stack painting in a +future release.) + +The `zero-init-ram` feature will zero the VMA region of `.data` before copying +contents from the load region. This isn't particularly useful, but it's safe to +enable. + +This package still enables `set-vtor` and `set-sp` features by default. For +convenience, this package still forwards the `device` feature. + ## [0.1.7] 2025-06-14 Introduce `RuntimeBuilder::in_flash` for creating images that can be launched -- cgit v1.2.3