STM32WBA52CGU6 Advertisement Issue: Discoverable in iOS/Windows not in Android

[rajdeep_01]

Hi Concerned Team,

Need valuable support:
1. Advertisement Issue: Discoverable in iOS/Windows not in Android
- Board: NUCLEO-STM32WBA52
- MCU: STM32WBA52CGUX
- SDK: 1.14.0
- Due to unavailability of out of box any BLE example code for STM32WBA52 series,
  Used base code for STM32WBA55 series and converted firmware for STM32WBA52,
  Tried examples: peer_to_peer_server_ota, heartrate_ota and beacon.
- Found strange case for all three examples that:
  Device advertisement found in iOS(BLE5.3) and Windows(BLE5.0), with good RSSI around -26dBm to -34dBm,
  even able to connect, read, write and notify perfectly,
  But device advertisement not found in Android phones:
  MI-11X(Android-V13, BLE5.1), Nokia-G42-5G(Android-V13, BLE5.1)
- peer_to_peer_sever_ota (STM32CubeIDE) advertisement found in windows and iOS related screenshots attached here.
Ref: Windows discovered advertisement
- Related peer_to_peer_server_ota firmware attached here for reference(7zip need to extract same).
- Related sniffer based packet info:

 

 2. SDK has not a single STM32WBA52 BLE examples.

[STTwo-32]

Hello @rajdeep_01 

Do you have the same behavior if you use one of the examples available for the STM32WBA52 Nucleo Board (Just download the version 1.1.0 of the STM32CubeWBA unzip it and open one of the examples available on this version using the STM32CubeIDE, compile and upload it). If you still have the same issue please report. I'm not able to reproduce the same issue on my side.

Best Regards.

STTwo-32

[rajdeep_01]

Hi @STTwo-32 

Thanks for update,
After initiated query in forum, already tried with different SDKs,
Facing same issue with below SDKs:
V1.4.0, V1.3.1, V1.3.0 and V1.2.0
Got success and everything working fine in below SDK:
V1.1.1.

As a workaround, can go with SDK V1.1.0 (4 Sep 2023 released),
but It will be great, if found fix to use latest SDK also.

Regards,
Rajdeep

[STTwo-32]

As you can see on the release note for the projects of the STM32CubeWBA V1.4.1:

• Connectivity applications are not supported on this release for NUCLEO-WBA52CG board.

Best Regards.

STTwo-32

[rajdeep_01]

Hi @STTwo-32 ,

Thanks for update,
but main concern is facing issue with latest release (or all release after V1.1.1),
that issue is still not fixed with these SDKs.

Request STM-Team to either fix the issue or provide tested proven example code, at least one with BLE support for related STM board NUCLEO-WBA52CG.

Thanks,
Rajdeep

[STTwo-32]

Hello @rajdeep_01 

The NUCLEO-WBA52CG is an obsolete product now. We suggest replacing it with the NUCLEO-WBA55CG. On the SDK side, the connectivity will not be supported for the NUCLEO-WBA52CG in any of the coming versions.

Best Regards.

STTwo-32

[rajdeep_01]

Hi @STTwo-32

Thanks for information, but main concern is related to MCU STM32WBA52CGU6 facing issue when incorporate SDK released after V1.1.1. Request STM-Team to fix the issue.

Note that STM claims that MCU STM32WBA52CGU6 has 10 year production support, I am assuming that STM will also support SDK releases during this timeline. Mark if any correction is there. It's strange that NUCLEO-WBA52CG has become overnight obsolete, even used MCU STM32WBA52CGU6 has 10 year production support.

Waiting for issue fix.

Regards,
Rajdeep

[STTwo-32]

Hello @rajdeep_01 

For the STM32WBA52 MCUs, they are available, and you can use them since they are supported by the Current SDK version. The only think is that Connectivity applications are not supported on this SDK release for NUCLEO-WBA52CG board. 

This product is obsolete, but you still can use the STM32WBA52 MCUs (As you already said, STM32WBA52 MCUs has 10-year production support). 

Best Regards.

STTwo-32

[rajdeep_01]

Hi @STTwo-32 

Thanks for quick reply, gained many information since ticket raised, but unfortunately looks like neither main issue is not properly addressed nor issue fix action initiated.

Let's focus on particular main concern:
STM32WBA52CGU6 Advertisement Issue: Discoverable in iOS/Windows not in Android.

Hope STM team will address main concern, proactive initiate action to fix issue and provide solution.

Regards,
Rajdeep

[STTwo-32]

On my side, I'm not able to reproduce that issue for both Nucleo-WB55CG and even on the Nucleo-WB52CG. Could you please Create a new post with more details (test it using a Nucleo-WB55CG if possible, precise the changes you have done on the original example,..).

Best Regards.

STTwo-32