This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
faq [2022/05/09 11:12] voorburg |
faq [2024/02/15 14:39] voorburg |
||
---|---|---|---|
Line 175: | Line 175: | ||
**__Can I add functionality for programming an extra non-volatile memory device?__** \\ | **__Can I add functionality for programming an extra non-volatile memory device?__** \\ | ||
- | Yes, absolutely. By default OpenBLT contains a driver to operate on the internal non-volatile memory, which is flash EEPROM in most cases. Through hooks functions that are activated by setting the BOOT_NVM_HOOKS_ENABLE configurable to 1 (blt_conf.h), support can be added for 1 or more additional non-volatile memory devices, such as external flash EEPROM and serial EEPROMs. [[http://www.feaser.com|Feaser]] offers engineering services to add support for additional non-volatile memory devices. | + | Yes, absolutely. By default OpenBLT contains a driver to operate on the internal non-volatile memory, which is flash EEPROM in most cases. Through hooks functions that are activated by setting the ''BOOT_NVM_HOOKS_ENABLE'' configurable to ''1'' (blt_conf.h), support can be added for 1 or more additional non-volatile memory devices, such as external flash EEPROM and serial EEPROMs. |
+ | |||
+ | An in-depth tutorial on how to enabled support for an additional memory device is [[https://www.feaser.com/en/blog/2024/02/additional-memory-device-in-openblt/|available on the blog]]. For a fully working example, refer to the [[https://www.feaser.com/openblt/doku.php?id=manual:demos:nucleo_l152re_cubeide#eeprom_memory_device_support|Nucleo-L152RE demo bootloader]]. | ||
+ | |||
+ | Note that [[http://www.feaser.com|Feaser]] offers engineering services to develop support for additional non-volatile memory devices for you. | ||
**__Is the bootloader robust over power failures or loss of communication during firmware updates?__** \\ | **__Is the bootloader robust over power failures or loss of communication during firmware updates?__** \\ |