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. --- src/lib.rs | 3 --- 1 file changed, 3 deletions(-) (limited to 'src/lib.rs') diff --git a/src/lib.rs b/src/lib.rs index 40d2789..46963e6 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -147,9 +147,6 @@ //! domains. This seems to matter most on the 1050, which has the widest spread of bank-to-power //! domain assignment (according to AN12077). //! -//! There is no support for ECC on 1160 or 1170. The runtime assumes that OCRAM and TCM ECC -//! is disabled, and that the corresponding memory banks can be used for OCRAM. -//! //! The runtime installs a `cortex-m-rt` `pre_init` function to configure the runtime. //! You cannot also define a `pre_init` function, and this crate does not support any //! other mechanism for running code before `main()`. -- cgit v1.2.3