This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
manual:demos:nucleo_l152re_cubeide [2024/02/15 13:12] voorburg [EEPROM memory device support] |
manual:demos:nucleo_l152re_cubeide [2024/02/15 14:30] (current) voorburg [EEPROM memory device support] |
||
---|---|---|---|
Line 80: | Line 80: | ||
* ''NvmDoneHook()'' | * ''NvmDoneHook()'' | ||
- | The actual low-level driver for operating on the internal data EEPROM is located in the files ''memdrv.c'' and ''memdrv.h''. The implementation of the before mentioned hook-functions is such that it glues it to the function in this low-level driver. | + | The actual low-level driver for operating on the internal data EEPROM is located in the files ''memdrv.c'' and ''memdrv.h''. The implementation of the before mentioned hook-functions is such that it glues it to the functions in this low-level driver. |
+ | |||
+ | For testing purposes an extra S-record file was generated that contains random data, mapped to a location in the internal data EEPROM: | ||
+ | |||
+ | * \Target\Demo\ARMCM3_STM32L1_Nucleo_L152RE_CubeIDE\Prog\Debug\eeprom_data.srec | ||
+ | |||
+ | If you select this S-record file when starting a firmware update, its data contents will be stored in the STM32L152RE's internal data EEPROM. | ||
+ | |||
+ | Note that this S-record file with random data was generated with the ''srec_cat'' [[https://srecord.sourceforge.net/|tool]]: | ||
+ | |||
+ | <code> | ||
+ | srec_cat -generator 0x08080000 0x08080400 -repeat-data 0x00 -exclude 0x08080000 0x08080400 \ | ||
+ | -random-fill 0x08080000 0x08080400 -o eeprom_data.srec -Motorola | ||
+ | </code> | ||
+ | |||
+ | Refer to this blog article for in-depth details on how to add support for an additional memory device: | ||
+ | |||
+ | * [[https://www.feaser.com/en/blog/2024/02/additional-memory-device-in-openblt/|Additional memory device in the OpenBLT bootloader]] | ||