1# BTstack port for STM32WB55 Nucleo Boards using FreeRTOS 2 3This port supports the Nucleo68 and the USB dongle of the [P-NUCLEO-WB55 kit](https://www.st.com/en/evaluation-tools/p-nucleo-wb55.html). Both have 1 MB of Flash memory. 4 5The STM32Cube_FW_WB_V1.3.0 provides the HAL and WPAN, and initializes the device and the initial Makefile. 6For easy development, Ozone project files are generated as well. 7 8## Hardware 9 10In this port, the Nucelo68 or the USB Dongle from the P-NUCLEO-WB55 can be used. 11Development was done using FUS v1.0.1 and v1.0.2 and Full BLE Stack v1.3.1. 12See STM32Cube_FW_WB_V1.3.0/Projects/STM32WB_Copro_Wireless_Binaries/Release_Notes.html for update instructions. 13 14Note: Segger RTT currently doesn't work as output stops after CPU2 (radio controller) has started up. 15 16### Nucleo68 17 18The debug output is sent over USART1 and is available via the ST-Link v2. 19 20### USB Dongle 21 22To flash the dongle, SWD can be used via the lower 6 pins on CN1: 23 - 3V3 24 - PB3 - SWO (semi hosting not used) 25 - PA14 - SCLK 26 - PA13 - SWDIO 27 - NRST 28 - GND 29 30The debug output is sent over USART1 and is available via PB6. 31 32## Software 33 34FreeRTOS V10.2.0 is used to run stack, you can get this example version by checking out official repo: 35 36 $ cd Middlewares 37 $ git submodule add https://github.com/aws/amazon-freertos.git 38 $ git submodule update 39 & cd amazon-freertos && git checkout v1.4.8 40 41Or by specifying path to FreeRTOS 42 43 $ make FREERTOS_ROOT=path_to_freertos 44 45To build all examples, run make 46 47 $ make 48 49All examples and the .jedbug Ozone project files are placed in the 'build' folder. 50 51## Flash And Run The Examples 52 53The Makefile builds different versions: 54- example.elf: .elf file with all debug information 55- example.bin: .bin file that can be used for flashing 56 57### Nucleo68 58 59There are different options to flash and debug the Nucleo68 board. The Nucleo68 boards comes with an on-board [ST-Link programmer and debugger](https://www.st.com/en/development-tools/st-link-v2.html). As an alternative, the ST-Link programmer can be replaced by an [SEGGER J-Link OB](https://www.segger.com/products/debug-probes/j-link/models/other-j-links/st-link-on-board/). Finally, the STM32 can be programmed with any ARM Cortex JTAG or SWD programmer via the SWD jumper. 60 61### USB Dongle 62 63Please use any ARM Cortex SWD programmer via the SWD interface desribed in the hardware section. 64 65## Run Example Project using Ozone 66 67When using an external J-Link programmer or after installing J-Link OB on the Nucleo68 board, you can flash and debug using the cross-platform [SEGGER Ozone Debugger](https://www.segger.com/products/development-tools/ozone-j-link-debugger/). It is included in some J-Link programmers or can be used for free for evaluation usage. 68 69Just start Ozone and open the .jdebug file in the build folder. When compiled with "ENABLE_SEGGER_RTT", the debug output shows up in the Terminal window of Ozone. Note: as mentioned before, Segger RTT currently stops working when CPU2 has started up. 70 71## Debug output 72 73All debug output can be either send via SEGGER RTT or via USART1. To get the console from USART1, simply connect your board under STLink-v2 to your PC or connect PB6 (USART1 TX) of the Nucleo board to an USB-2-UART adapter and open a terminal at 115200. 74 75In src/btstack_config.h resp. in example/btstack_config.h of the generated projects, additional debug information can be enabled by uncommenting ENABLE_LOG_INFO. 76 77Also, the full packet log can be enabled in src/btstack_port.c by uncommenting the hci_dump_open(..) line. The console output can then be converted into .pklg files for OS X PacketLogger or WireShark by running tool/create_packet_log.py 78 79## GATT Database 80In BTstack, the GATT Database is defined via the .gatt file in the example folder. During the build, the .gatt file is converted into a .h file with a binary representation of the GATT Database and useful defines for the application. 81