cancel
Showing results for 
Search instead for 
Did you mean: 

STM32WB5MMG: Cube Monitor RF refuses to connect

vishalkeshavamurthy
Associate III

We are using an STM32WB5MMG in a product, We needed to run a few BLE tests for compliance needs and came across the BLE transparent mode to help with BLE tests. 

In accordance with the ReadMe under BLE_TransparentMode inside STM32WB5MM-DK, we have undertaken the following steps 

  • Updated FUS to stm32wb5x_FUS_fw.bin at 0x080EE000
  • Updated soft device with stm32wb5x_BLE_Stack_full_extended_fw.bin to 0x080C7000
  • Modified BLE transparent Mode to change USART pins being used to PA9 and PA10 though Cube MX

vishalkeshavamurthy_1-1753783537554.png

Updated FUS and Stack 

vishalkeshavamurthy_2-1753783634962.png

Updated VCP_TX and VCP_RX

 

The CubeMonitor-RF software refuses to connect with the device however 

 

vishalkeshavamurthy_0-1753783507320.png

Unable to connect 

No changes are done to the transparent mode example with the exception of UART pin update. ioc file PDF attached 

 

 

2 REPLIES 2
FilipKremen
ST Employee

Hello,

could you please share the modified project, so I could try to reproduce it on my side?

Thank you.

 

Best regards,

ST support

Hello @FilipKremen 

Appreciate the offer to help thanks! 

I am using the project as is from the latest (V1.23.0) release of Cube Repo [[LINK]]

Specifically I am building the STM32WB5MM-DK/Applications/BLE/BLE_TransparentMode project with 1 modification, changing of default USART pins to PA9 and PA10 to fit my custom board. Original GIT link here [[LINK]]. Also attached is the ICO file where the pin change is done for regenerating the project 

I have already attached a screenshot of the CubeProgrammer window in the thread above, showing my FUS and BLE stack updated correctly. 

Please note that I had to update both the FUS and stack as instructed, the other example projects also did not seem to be advertising as expected, I ran out of time today to investigate further 

 

Also, can the FUS not be downgraded once upgraded? I was unable to downgrade and retest the board with our known functioning FW