faq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
faq [2020/02/14 12:59] voorburg |
faq [2024/02/15 14:39] voorburg |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| Bootloaders are quite tricky and are critical for the overal functioning and reliability of the system. If the bootloader is not running correctly, it could become impossible to update the user program or, even worse, no longer starts the actual user program once programmed. | Bootloaders are quite tricky and are critical for the overal functioning and reliability of the system. If the bootloader is not running correctly, it could become impossible to update the user program or, even worse, no longer starts the actual user program once programmed. | ||
| - | [[https://www.feaser.com/en/services.php|Feaser]] offers professional engineering services to integrate, customize and port OpenBLT to your specific requirements. Feel free to contact Feaser to discuss details and possibilities. | + | [[https://www.feaser.com/en/services.php|Feaser]] offers professional engineering services to integrate, customize and port OpenBLT to your specific requirements. Feel free to contact Feaser to discuss details and possibilities. If you prefer to give it a try yourself, [[https://www.feaser.com/en/blog/?p=352|this blog article]] contains detailed instructions on how to adjust the OpenBLT bootloader to your microcontroller system. |
| **__What licensing options are available?__** \\ | **__What licensing options are available?__** \\ | ||
| Line 80: | Line 80: | ||
| The OpenBLT bootloader already has several security options build-in that can be easily enabled. Together with readily available add-on modules and a few extra configuration steps, your system can be fully secured. Have a look at [[https://www.feaser.com/en/blog/?p=245|this blog article]], which lists the available security options and explains in detail how to enable them. | The OpenBLT bootloader already has several security options build-in that can be easily enabled. Together with readily available add-on modules and a few extra configuration steps, your system can be fully secured. Have a look at [[https://www.feaser.com/en/blog/?p=245|this blog article]], which lists the available security options and explains in detail how to enable them. | ||
| + | |||
| + | **__Can the OpenBLT bootloader update itself?__** \\ | ||
| + | |||
| + | Yes, this is possible. It involves the creation of a secondary OpenBLT bootloader, derived from the same source code. You can find details and step-by-step instructions in [[https://www.feaser.com/en/blog/2022/05/how-to-update-the-openblt-bootloader-itself/|this blog article]]. | ||
| + | |||
| + | Note though that updating the bootloader itself comes with a risk. If something goes wrong during this procedure (for example an unexpected power loss or communication glitch), you might be left with a system that has no bootloader at all. | ||
| **__What is the ROM footprint of the bootloader?__** \\ | **__What is the ROM footprint of the bootloader?__** \\ | ||
| Line 87: | Line 93: | ||
| Tips and tricks on further reducing the ROM footprint of the bootloader can be found in [[https://www.feaser.com/en/blog/?p=174|this blog article]]. | Tips and tricks on further reducing the ROM footprint of the bootloader can be found in [[https://www.feaser.com/en/blog/?p=174|this blog article]]. | ||
| - | **__What are the ROM footprints of the OpenBLT add-on modules??__** \\ | + | **__What are the ROM footprints of the OpenBLT add-on modules?__** \\ |
| The [[https://www.feaser.com/en/addons.php#encryption|firmware encryption]] module requires about 1800 bytes, the [[https://www.feaser.com/en/addons.php#checksum|improved checksum]] module about 700 bytes and the [[https://www.feaser.com/en/addons.php#gateway|master/slave gateway]] module about 900 bytes. We dedicated an entire [[https://www.feaser.com/en/blog/?p=347|blog article]] to this topic to give you more details. | The [[https://www.feaser.com/en/addons.php#encryption|firmware encryption]] module requires about 1800 bytes, the [[https://www.feaser.com/en/addons.php#checksum|improved checksum]] module about 700 bytes and the [[https://www.feaser.com/en/addons.php#gateway|master/slave gateway]] module about 900 bytes. We dedicated an entire [[https://www.feaser.com/en/blog/?p=347|blog article]] to this topic to give you more details. | ||
| Line 169: | 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?__** \\ | ||
faq.txt · Last modified: 2024/02/15 14:43 by voorburg
Page Tools
