Document:
SHARKY - User’s Guide
2020/07/20
8.
Firmware Upload
The STM32WB SoC inside the Sharky module has 2 cores that share the same FLASH and
SRAM addresses:
● M0+ core for embedded communication stack
● M4 core for user application
The module is delivered with BLE communication stack firmware installed on M0+ core and
Transparent VCP firmware on M4 core. This configuration allows testing the module with
STM32CubeMonitor-RF application from ST that can be downloaded from:
https://www.st.com/en/development-tools/stm32cubemonrf.html
Thread and other stacks can be installed by the user.
8.1.
FW upload to M4 core
The GUI application for flashing firmware is STM32CubeProgrammer, available for
Windows, Linux and MacOS operating systems. It can be downloaded from ST at:
https://www.st.com/en/development-tools/stm32cubeprog.html
The firmware for the M4 CPU can be uploaded:
● Using an STLink V2 or V3 device connected to the SWD interface
● Using the embedded ROM Bootloader that is selected by rising the BOOT0 pin on
reset. In this case the firmware can be uploaded via USB or UART
8.2.
FW upload to M0+ core
The M0+ firmware cannot be uploaded using STLink programmer, only the internal
bootloader is allowed to update the firmware.
ST
provides
the
en.stm32cubewb.zip
package
(download
from:
https://www.st.com/en/embedded-software/stm32cubewb.html
)
With the following compiled communication staks:
● stm32wb5x_BLE_Stack_fw.bin
○ Full BLE Stack 5.0 certified : Link Layer, HCI, L2CAP, ATT, SM, GAP and
GATT database
○ BT SIG Certification listing :
● stm32wb5x_BLE_HCILayer_fw.bin
○ HCI Layer only mode 5.0 certified : Link Layer, HCI
○ BT SIG Certification listing :
● stm32wb5x_Thread_FTD_fw.bin
○ Full Thread Device certified v1.1
Doc: UG_MDX-STWBx, Rev 1.6
pag. 52 of 57
