Skip to main content
Associate III
Aug 20, 2025 4:05 AM UTC
Question

BLE connection fails when project is generated for IAR (works with CubeIDE) on NUCLEO-WBA55CG

I am facing an issue with BLE connection on the NUCLEO-WBA55CG board.

Using the same .ioc file:

  • When I generate the code for STM32CubeIDE, the project builds and runs fine, and I can connect to the device successfully using the ST BLE Toolbox app.

  • But when I generate the code for IAR, the project builds and runs, but the device cannot be connected. On the Android app, when I press Connect, it briefly shows Connecting and then reverts back to Connect, without establishing the connection.

So the only difference is the toolchain (CubeIDE vs IAR).

Environment:

  • STM32CubeMX 6.15

  • STM32Cube_FW_WBA 1.7.0

  • IAR Embedded Workbench (please fill in your version here)

  • STM32CubeIDE 1.19.0

  • IAR 9.60

Has anyone experienced this issue? How can I make the BLE connection work properly with IAR as well?

Kenwang_0-1755673278629.png

 

This topic has been closed for replies.

5 replies

Remy ISSALYS
ST Technical Moderator
Aug 22, 2025 12:16 PM UTC

Hello, 

Can you please share your project and not only the .ioc file?
 
Best Regards

KenwangAuthor
Associate III
Aug 29, 2025 12:55 AM UTC

@Remy ISSALYS 

Is any update ?

STTwo-32
ST Technical Moderator
Sep 22, 2025 12:27 PM UTC

Hello @Kenwang 

Do you have the same behavior using the IAR V9.20. If so, does it work with LPM turned or following the recommendations of your previous post.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
KenwangAuthor
Associate III
Aug 26, 2025 12:52 AM UTC

Attached files is my IAR project created by the ioc file.

I have disable "CFG_LPM_STDBY_SUPPORTED".

 

Kenwang_0-1756169998657.png

 

I compared the images built with CubeIDE and IAR, and observed that the image generated by IAR contains almost all 0xFF data starting from address 0x20806000. Could this be the root cause of the Bluetooth connection failure?

Kenwang_0-1756178688468.png