boards/weact/stm32wb55_core/doc/index.rst
.. zephyr:board:: weact_stm32wb55_core
Overview
The WeAct Studio STM32WB55 Core Board is a compact multi-protocol wireless and ultra-low-power development board embedding a powerful radio compliant with the Bluetooth® Low Energy (BLE) SIG specification v5.0 and with IEEE 802.15.4-2011.
Hardware
STM32WB55CGU6 is an ultra-low-power dual core Arm Cortex-M4 MCU 64 MHz, Cortex-M0+ 32MHz with 1 Mbyte of Flash memory, Bluetooth 5, 802.15.4, USB, AES-256 SoC and provides the following hardware capabilities:
Ultra-low-power with FlexPowerControl (down to 600 nA Standby mode with RTC and 32KB RAM)
Core: ARM® 32-bit Cortex®-M4 CPU with FPU, frequency up to 64 MHz
Radio:
Clock Sources:
RTC with HW calendar, alarms and calibration
Up to 24 capacitive sensing channels
16x timers:
Memories
Rich analog peripherals
SMBus/PMBus)
1x USB 2.0 FS device, crystal-less, BCD and LPM
Security and ID
More information about STM32WB55CG can be found here:
STM32WB55CG on www.st.com_STM32WB55 datasheet_STM32WB55 reference manual_.. zephyr:board-supported-hw::
IMPORTANT: The WeAct STM32WB55 Core Board ships with a "Full Stack" wireless binary pre-installed on the Cortex-M0+ coprocessor. This binary is NOT compatible with Zephyr and must be replaced with an "HCI Layer" binary before using Bluetooth functionality.
To operate Bluetooth on the WeAct STM32WB55 Core Board, the Cortex-M0+ core must
be flashed with a valid STM32WB Coprocessor HCI binary. These binaries are delivered
in STM32WB Cube packages, under Projects/STM32WB_Copro_Wireless_Binaries/STM32WB5x/
For this board, the extended HCI binary has been tested: stm32wb5x_BLE_HCILayer_extended_fw.bin
For compatibility information with the various versions of these binaries,
please check :module_file:hal_stm32:lib/stm32wb/README.rst.
The Cortex-M0+ wireless coprocessor binary requires an external debug probe and STM32CubeProgrammer to flash. DFU mode cannot be used for the M0+ coprocessor. Connect an external debug probe (ST-LINK/V2 or J-Link) to the 4-pin SWD header (P3) and use STM32CubeProgrammer to program the binary at the appropriate memory address.
The install address for STM32WB5xxG (1M variant) varies by binary type (v1.23.0):
FUS (Firmware Upgrade Services) install address (v2.1.0):
See the STM32 Wireless Coprocessor Binary Table_ for complete address information.
The WeAct STM32WB55 Core Board system clock is driven by a 32 MHz HSE crystal oscillator. By default, the system clock is configured to run at 64 MHz using the PLL with HSE as the source.
The board includes an ME6231A33M3G 3.3V LDO regulator that accepts input voltage from 3.3V to 5.5V. Power can be supplied via:
The board has 1 USART and 1 LPUART. The Zephyr console output is assigned to USART1 (PA9/PA10). Default settings are 115200 8N1.
Programming and Debugging
.. zephyr:board-supported-runners::
The WeAct STM32WB55 Core Board does not include an onboard debugger. The Cortex-M4 can be flashed via DFU mode without an external probe, however the Cortex-M0+ coprocessor requires an external debug probe (ST-LINK/V2 or J-Link) connected to the 4-pin SWD header (P3).
It is recommended to use at least v0.8 of dfu-util. The package available in
debian/ubuntu can be quite old, so you might have to build dfu-util from source.
There is also a Windows version which works, but you may have to install the
right USB drivers with a tool like Zadig.
Connect a USB Type-C cable and the board should power ON. Force the board into DFU mode by keeping the BOOT button pressed while pressing and releasing the RESET button.
The dfu-util runner is supported on this board and so a sample can be built and tested easily.
.. zephyr-app-commands:: :zephyr-app: samples/basic/blinky :board: weact_stm32wb55_core :goals: build flash
.. zephyr-app-commands:: :zephyr-app: samples/hello_world :board: weact_stm32wb55_core :goals: build flash
Alternatively, if you have an external debug probe (ST-LINK/V2 or J-Link)
connected to the SWD header (P3), STM32CubeProgrammer can also be used to flash the
Cortex-M4 application using the --runner (or -r) option:
.. code-block:: console
$ west flash --runner stm32cubeprogrammer
You need an external debugger connected to the SWD header (P3) to debug
applications on this board. You can then debug an application in the usual way.
Here is an example for the :zephyr:code-sample:blinky application.
.. zephyr-app-commands:: :zephyr-app: samples/basic/blinky :board: weact_stm32wb55_core :maybe-skip-config: :goals: debug
.. _WeAct Studio GitHub: https://github.com/WeActStudio/WeActStudio.STM32WB55CoreBoard
.. _STM32WB55CG on www.st.com: https://www.st.com/en/microcontrollers-microprocessors/stm32wb55cg.html
.. _STM32WB55 datasheet: https://www.st.com/resource/en/datasheet/stm32wb55cg.pdf
.. _STM32WB55 reference manual: https://www.st.com/resource/en/reference_manual/dm00318631.pdf
.. _dfu-util: https://dfu-util.sourceforge.net/
.. _Zadig: https://zadig.akeo.ie/
.. _STM32CubeProgrammer: https://www.st.com/en/development-tools/stm32cubeprog.html
.. _STM32 Wireless Coprocessor Binary Table: https://github.com/STMicroelectronics/STM32CubeWB/blob/master/Projects/STM32WB_Copro_Wireless_Binaries/STM32WB5x/Release_Notes.html