Skip to content

Home

Jump to bottom
Evan Ross edited this page Jan 2, 2023 · 2 revisions

Welcome to the stm32-secure-patching-bootloader wiki!

FAQ

Q: "I just came across your git repository of the stm32 patch bootloader. I have read in detail the document you have on the git. You are using the STM32 X-CUBE-SBSFU Bootloader (with some modification) but with a different name such as stm32 secure patching bootloader not disclosing the source code but compiled .bin file for user app. Can you please explain how your bootloader is different from the STM32 x-cube-SBSFU? which is available here https://www.st.com/en/embedded-software/x-cube-sbsfu.html"

A: The stm32-secure-patching-bootloader product is based on X-CUBE-SBSFU but has a few key changes and additions. The stm32-secure-patching-bootloader targets SMEs that don't have time, money and/or expertise to allocate to getting X-CUBE-SBSFU integrated and ready to ship with their product firmware, or for SMEs that want the additional features that are not available with X-CUBE-SBSFU.

The key differences of stm32-secure-patching-bootloader are:

  1. Ready-to-go binary means customer does not need integration and maintenance of additional bootloader projects "SBSFU" and "SECoreBin" into application project workspace as X-CUBE-SBSFU does.
  2. Supports firmware difference patching while X-CUBE-SBSFU does not. With firmware patching capability built into the tooling and the bootloader core, a small change to a 200K firmware binary can be delivered OTA as a 2K patch instead.
  3. Supports TouchGFX large application firmware update, treating application content (GUI assets) that are placed onto external flash as part of one single binary using the same firmware image signing and patching capability. Customers using TouchGFX need this feature to deliver a firmware update as one file. X-CUBE-SBSFU does not have this capability.
  4. USB flash drive update built into bootloader for products that have USB OTG host. Your customers can put firmware onto a USB flash stick and plug it into your product to update the firmware. X-CUBE-SBSFU does not have this capability.
  5. The stm32-secure-patching-bootloader understands the needs of customers shipping real products. The stm32-secure-patching-bootloader core has been locked down and stable for over 3 years and is not tinkered with. The same core has been deployed to 7 STM32 families (L0, L4, L5, F4, F7, WL, G0) and to shipping products worldwide. In contrast, X-CUBE-SBSFU is a constantly evolving product and there might be unpleasant surprises waiting in the latest releases.
  6. The stm32-secure-patching-bootloader is backed by an experienced firmware and product development expert who will work with you to ensure the solution meets your needs.

All of these features could be developed by experienced personnel but the cost and time to do so would be far far greater than getting the stm32-secure-patching-bootloader, a tested, stable and ready-to-ship solution now, for just $5000 CAD. The business case is obvious.

Clone this wiki locally