Skip to main content
S
Sprak.11
Visitor II
January 13, 2020
Solved

Whats the use of System memory & flash memory

  • January 13, 2020
  • 2 replies
  • 4537 views

Please any one help how to differentiate the system memory & flash memory in STM32MCUs,

Whats the use of the both memory?

Where we need to store the user code & where we need to store the customized setting?

How to store FAT(File Allocation Table)?

How we get the EEPROM in STM32MCUs, through which Emulating Software?

    This topic has been closed for replies.
    Best answer by waclawek.jan

    System memory is read-only (ROM), containing the default bootloader and calibration values etc.

    You store code in FLASH.

    You can store some user data in FLASH, but note that unless you have on of the dual-bank STM32 models, program execution from FLASH waits while any other part of FLASH is being erased/programmed. Some STM32 models have a dedicated EEPROM area in FLASH, which can be erased in small pieces, in contrast to normal FLASH which is erased in relatively large chunks.

    FAT is one particular file system, in most cases it's not appropriate to run a file system in the internal FLASH.

    JW

    2 replies

    W
    waclawek.janAnswer
    Super User
    January 13, 2020

    System memory is read-only (ROM), containing the default bootloader and calibration values etc.

    You store code in FLASH.

    You can store some user data in FLASH, but note that unless you have on of the dual-bank STM32 models, program execution from FLASH waits while any other part of FLASH is being erased/programmed. Some STM32 models have a dedicated EEPROM area in FLASH, which can be erased in small pieces, in contrast to normal FLASH which is erased in relatively large chunks.

    FAT is one particular file system, in most cases it's not appropriate to run a file system in the internal FLASH.

    JW

    B
    berendi
    Visitor II
    January 13, 2020

    Flash organization depends on the MCU series and sometimes on the exact part number. It is documented in the reference manual.

    Mind the erase and write timings and the supported number of erase cycles in the datasheet. Also note that program execution might be stopped for an extended duration (up to a couple of seconds on some models) even when using EEPROM emulation. This applies to MCUs with internal EEPROM too, because that's just as well an emulation, in hardware.

    Terms & ConditionsAccessibility statement