Skip to content

Release v1.3.0
Compare
Choose a tag to compare
@firmwareguru firmwareguru released this 18 Nov 23:46
· 18 commits to main since this release
v1.3.0
1233b3b

We are pleased to bring you the STM32 Secure Patching Bootloader Release v1.3.0

Now works with STM32CubeIDE 1.9.0 and greater.

New features:

  • Simplifies application integration process by removing the need to link with a library for access to SE_PATCH (in-application firmware update) APIs. Now, the SE_PATCH engine APIs are available to all applications by default.
  • Adds new platform support for STM32L4+ and DISCO-L4R9I and B-L4S5I-IOT01A boards.
  • Adds new platform support for STM32L5 and the DISCO-L562E board.
  • Updated Quick Start Guide with instructions to generate per-project security keys (easy to do, but step was missing).

Notes:

  • Still works with prior versions of CubeIDE. Method of calling the Secure Engine APIs is more universal now.

Errata:

  • [1] SE_PATCH_Data API will fail with error code 3 Invalid image - firmware image header checksum failed or not present unless CRC hardware peripheral's power is explicitly enabled by the user application prior to calling SE_PATCH_XXXX APIs. Workaround: call __HAL_RCC_CRC_CLK_ENABLE(); during application initialization.
  • [2] SE_PATCH_Data API will fail with error code 11 (SECTION_WRITE_FAILURE) if presented with a full-image update file (.sfb) data buffer length that is not a multiple of the platform's flash write size: typically 8 bytes (doubleword). Workaround is to ensure that the API is called with an 8-byte-multiple length buffer.
    Note: this is not necessary for .sfbp (patch) files, and having it in place won't affect .sfbp updates.

Product customization for your board is available with product registration. Contact us.

Assets 2
Loading