- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm trying to enlarging the SRAM usage of my application by replacing STM32F417 to STM32F437.
Is there any modification required for utilizing the full SRAM space (256 kbytes) of STM32F437? Except modification on the file 'platforms/BCM943341WCD1/BCM943341WCD1.mk'?
HOST_MCU_VARIANT := STM32F437
HOST_MCU_PART_NUMBER := STM32F437IGH6
From the platform linker configuration /platform/MCU/STM32F4xx/GCC/*, I don't see the difference between STM32F417 and STM32F437.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
memory.ld in 437 directory still uses 128K as LENGTH of SRAM section.
I don't know it's enough. But needs to be modified at least.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
memory.ld in 437 directory still uses 128K as LENGTH of SRAM section.
I don't know it's enough. But needs to be modified at least.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are currently using the STM32F427 (this also has 256K SRAM), it is important to note that not all 256K is the same. You have 192K at 0x20000000 which is regular SRAM, then you have 64K at 0x10000000 which is Core Coupled memory. It is possible to use the 64K, but I do not think you can add them to the STACK/HEAP.
We use the 64K as a cache, but this is managed outside the STACK/HEAP.
Is it critical for you to be able to use the 64K?
-René Josefsen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi renejos and dmiya,
Thanks!
Modification on *.ld of STM32F437 is working now for accessing the 192K SRAM.
CCM 64K is not yet my urgency to use it.