SBSFU on STM32WB with changes in SFSA

[HRadt.1]

Currently when using SBSFU (1-Image in our case) one defines the application/download region.

Usually this region goes up to the wireless stack install address to utilize the space most efficiently.

My issue now is: What happens when due to a wireless stack update with a potentially larger size, the new SFSA address is lower, ranging into the application/download area.

Shouldn't SBSFU be SFSA aware? To calculate the size of the application area with respect to SFSA?

The BLE_STACK_Full didn't see size increases in its recent releases, but the light stack indeed did. Would you reccommend to decrease the size of the application space just in case a future stack update would be larger in size? But if so, how much space should be reserved?

Ignoring this would potentially block future stack updates (specificially security related updates) if the stack size would increase.

[Christophe Arnal]

​Hello,

Generally speaking, the application should plan some spare sectors to support future update. This is true for flash and SRAM2 in case you plan to store some data there.

The light stack  has been recently significantly increased because there was missing a feature that was most of the time needed ( even for a ligth stack).

It should be now stable and I would not expect much increase in future update ( similarly to the BLE_STACK_Full).

Regards.