[PATCH] bsp/arm: allocate .rtemsstack on REGION_STACK instead of on REGION_WORK
Karel Gardas
karel at functional.vision
Mon May 16 09:48:46 UTC 2022
Hello,
this one seems to slip through. Nobody reviewed it nor commented yet.
I've been running with this patch here for about a month on various
STM32h7 boards without a problem.
Thanks!
Karel
On 4/7/22 21:15, Karel Gardas wrote:
> REGION_WORK may be backed by external RAM which may not be initialized
> in a time we need stack to work well. E.g. code loaded in flash,
> stack allocated on in-cpu SRAM and data (REGION_WORK) on external SDRAM.
>
> Sponsored-By: Precidata
> ---
> bsps/arm/shared/start/linkcmds.base | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bsps/arm/shared/start/linkcmds.base b/bsps/arm/shared/start/linkcmds.base
> index ec6c4e4557..10d2c54028 100644
> --- a/bsps/arm/shared/start/linkcmds.base
> +++ b/bsps/arm/shared/start/linkcmds.base
> @@ -329,7 +329,7 @@ SECTIONS {
> bsp_section_rtemsstack_begin = .;
> *(SORT_BY_ALIGNMENT (SORT_BY_NAME (.rtemsstack*)))
> bsp_section_rtemsstack_end = .;
> - } > REGION_WORK AT > REGION_WORK
> + } > REGION_STACK AT > REGION_STACK
> bsp_section_rtemsstack_size = bsp_section_rtemsstack_end - bsp_section_rtemsstack_begin;
>
> .noinit (NOLOAD) : ALIGN_WITH_INPUT {
More information about the devel
mailing list