Skip to main content
PADAM.1
PADAM.1
Associate III
September 28, 2020
Question

Bug: generated code from STM32CubeIDE(MX) for STM32WB55 Nucleo "BLE P2P Router" not working

  • September 28, 2020
  • 1 reply
  • 639 views

Hello

the code generated by STM32CubeIDE version 1.4 with FW package STM32WB 1.8 for BLE application "Router profile" and "Router mode enabled" does not work: It cannot be scanned and connected by smartphone application.

The reason (to my opinion after some investigation) is that the default clock configuration when creating new project does not work. I changed it as in distributed sample code to:

  • RTC/LCD Source Mux -> LSE
  • RFWKP Clock Mux -> LSE
  • SMPS Clock Mux -> HSE

With these changes, the device can be connected.

In addition, there are many differences of distributed sample code "BLE_p2pRouteur" (french word ;) which also does not contain the sub directory with binary reference as other sample projects.

STMicroelectronics should change the code generator, so that the code work "just in time".

Also there should be no difference (e.g.: detected by meld, diff or other tools) between generated and distributed code.

Best regards

Paul

This topic has been closed for replies.

1 reply

Remi QUINTIN
Remi QUINTIN
Technical Moderator
October 9, 2020

STM32WB FW package does not contain .ioc files defined by CubeMX. So when you go through CubeMX to configure your system, you have to define the clock tree you want as you can select other clock sources than those proposed by default. The defaut clock configuration may not be the correct one for all projects. The generated .ioc file keeps the complete configuration of your system. Then you generate the code and debug it with CubeIDE.

Terms & ConditionsAccessibility statement