Differences

This shows you the differences between two versions of the page.

--- faq [2018/08/22 11:40]
voorburg
+++ faq [2019/09/24 22:02]
127.0.0.1 external edit
@@ Line 1: / Line 1: @@
 ====== Frequently Asked Questions ======
+**__What is the history of the OpenBLT bootloader project?__** \\
+The OpenBLT project started out as a hobby project that Frank Voorburg developed on the side in his spare time. Not long after publishing the project as open source at [[https://sourceforge.net/projects/openblt/|SourceForge]], companies contracted him to perform bootloader integrations and customizations for them.
+Interest in the OpenBLT project grew consistently and continuously over the following years, resulting in a switch to a [[https://www.feaser.com/en/openblt.php#licensing|dual licensing model]] and Frank Voorburg reorganizing his company Feaser. Feaser is now fully dedicated to providing professional engineering services and commercial licenses around the OpenBLT bootloader. More details about the history of the OpenBLT project is available in [[https://www.feaser.com/en/blog/?p=11|this blog article]].
+One of the main factors contributing to the success of the OpenBLT project is the synergy between the company Feaser on the one hand and the open source OpenBLT project on the other hand. The OpenBLT project generates income for Feaser, which makes it possible for Feaser to fully sponsor the development and maintenance efforts of the OpenBLT project. [[https://www.feaser.com/en/blog/?p=256|This blog article]] contains more information about the relationship between Feaser and the OpenBLT project.
 **__Why should I use the OpenBLT bootloader?__** \\
@@ Line 13: / Line 21: @@
   * On-site integration
   * Training
-  * Technical support by phone/e-mail
+  * Technical support by e-mail
 Feel free to contact [[http://www.feaser.com|Feaser]] to discuss your support needs.
@@ Line 62: / Line 70: @@
 More details about the release schedule and bootloader version numbers can be found in [[https://www.feaser.com/en/blog/?p=81|this blog article]].
+**__What security options are available in the bootloader?__**  \\
+From the context of a bootloader, security options are meant to prevent unwanted third parties from
+  * Making firmware updates on your product.
+  * Capturing your firmware data while it is communicated to your product during a firmware update.
+  * Reading out your firmware data after it was programmed onto your product.
+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.
 **__What is the ROM footprint of the bootloader?__**  \\
@@ Line 98: / Line 116: @@
 At the end of a programming session, the bootloader stores a program specific 32-bit checksum in non-volatile memory. When the bootloader is about to start the user program, this checksum is first verified and based on the results of this verification, the bootloader determines if it's safe to start the user program.
+Note that this 32-bit checksum is calculated over only a small portion of your software program, typically a part of the interrupt vector table. It is meant as a signature that helps the bootloader to determine if a software program is present or not. To have a checksum verification over the entire contents of your software program, Feaser offers the [[https://www.feaser.com/en/addons.php#checksum|improved checksum]] add-on module.
 **__How do I debug my own firmware, when the bootloader is also present in flash?__**  \\

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools