Skip to content

arch/arm/stm32: set F412 SRAM1_END to 256KiB - #20039

Merged
xiaoxiang781216 merged 1 commit into
apache:masterfrom
dakejahl:dakejahl/stm32f412-sram
Sep 2, 2026
Merged

arch/arm/stm32: set F412 SRAM1_END to 256KiB#20039
xiaoxiang781216 merged 1 commit into
apache:masterfrom
dakejahl:dakejahl/stm32f412-sram

Conversation

@dakejahl

@dakejahl dakejahl commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Summary

The STM32F412 has 256 KiB of system SRAM at 0x20000000 and no CCM. The F2/F4 heap map never named it, so SRAM1_END fell through to the 128 KiB default at 0x20020000 and the upper half was left out of the heap.

Impact

  • New feature: NO
  • Impact on user: YES, F412 boards get the upper 128 KiB of SRAM in the heap.
  • Impact on build: NO
  • Impact on hardware: NO
  • Impact on documentation: NO
  • Impact on security: NO
  • Impact on compatibility: NO

Testing

nxstyle clean on arch/arm/src/common/stm32/stm32_allocateheap_m3m4_v1.c. PX4 carry is PX4/NuttX (10.3) and a matching 12.12 backport; those rebuild ark_can-flow-mr_canbootloader / ark_cannode_canbootloader with CONFIG_ARCH_CHIP_STM32F412VG / CG.

The F412 has 256KiB of system SRAM at 0x20000000 and no CCM. The F2/F4
heap map had no F412 entry, so it used the 128KiB default at
0x20020000 and left the upper half unused.

Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
@github-actions github-actions Bot added Arch: arm Issues related to ARM (32-bit) architecture Size: XS The size of the change in this PR is very small labels Sep 1, 2026
@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown

MemBrowse Memory Report

No memory changes detected for:

@xiaoxiang781216
xiaoxiang781216 merged commit 65d0b3f into apache:master Sep 2, 2026
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Arch: arm Issues related to ARM (32-bit) architecture Size: XS The size of the change in this PR is very small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants