Skip to main content
JUker
JUker
Associate II
August 14, 2019
Solved

Bluetooth classic profiles (SPP / A2DP) on STM32WB

  • August 14, 2019
  • 13 replies
  • 7772 views

Hello,

I have experience using Bluetooth classic profiles: SPP and A2DP.

Started using STM32WB and I understand it doesn't support these two above profiles, it only has a stack for BLE. Is this correct?

Can I use STM32WB with SPP and/or A2DP, if yes - how? if no - what profiles supported by the STM32WB do you recommend (to replace SPP and A2DP)?

In addition, I've noticed ST has Bluetooth devices of series BlueNRG and SPBTLE: what is the difference between these two and the STM32WB?

Do they support SPP and A2DP

Thanks,

Jig

This topic has been closed for replies.
Best answer by Christophe Arnal

Hello,

The STM32WB does only implement a BLE stack. Therefore, SPP and A2DP which are BT profiles cannot be supported.

However, there are two BLE applications which are implemented that will provide similar feature.

SPP may be replaced with the BLE_CableReplacement application which is delivered in the STM32WBCube_FW package available on the ST website.

A2DP may be replaced by a voice application based on STM32WB which is delivered in a another package found at this link

These two application share the same FW architecture so it should be easy to merge them into one single application.

BlueNRG and SPBTLE are provided by another ST division.

These two products have a specific HW and FW architecture.

The STM32WB is a product part of the STM32 families. Therefore, it shares the same HW and FW architecture than all STM32 product. An already running application on STM32 that would require a BLE connectivity may be moved easily to the STM32WB.

You may create a new post to request details on either BlueNRG and SPBTLE so that relevant people may answer you. As far as I know, BlueNRG is only a BLE product as well and I think that is the same for SPBTLE.

Regards.

13 replies

Anonymous
August 14, 2019

Hi.

Pay attention to your phrase "classic profiles". The listed profiles apply only to classic Bluetooth, and BLE does not support classic profiles.

That chip support only BLE and you cannot use him with any classic profiles.

SPP can be replaced "BLE_CableReplacement" example.

A2DP - can not be replaced.

Regards,

Vyacheslav

Christophe Arnal
ST Employee
August 14, 2019

Hello,

You are correct.

When I said " can be replaced", I meant that from an application point of view, it could be possible to provide a similar feature.

So, the Voice Demo cannot replace exactly the A2DP profile and for sure will not be compatible but I believe an application built upon the Voice Demo on STM32WB may provide to the end user a similar feature than a BT device implementing A2DP.

Regards.

JUker
JUkerAuthor
Associate II
August 14, 2019

Thank you for your reply!

Where can I find the "BLE_CableReplacement" example?

I've installed CubeMX with STM32WB package version 1.2.0

Anonymous
August 14, 2019

in folder:

CUBE_REPOSITORY\STM32Cube_FW_WB_V1.2.0\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_CableReplacement

Christophe ArnalBest answer
ST Employee
August 14, 2019

Hello,

The STM32WB does only implement a BLE stack. Therefore, SPP and A2DP which are BT profiles cannot be supported.

However, there are two BLE applications which are implemented that will provide similar feature.

SPP may be replaced with the BLE_CableReplacement application which is delivered in the STM32WBCube_FW package available on the ST website.

A2DP may be replaced by a voice application based on STM32WB which is delivered in a another package found at this link

These two application share the same FW architecture so it should be easy to merge them into one single application.

BlueNRG and SPBTLE are provided by another ST division.

These two products have a specific HW and FW architecture.

The STM32WB is a product part of the STM32 families. Therefore, it shares the same HW and FW architecture than all STM32 product. An already running application on STM32 that would require a BLE connectivity may be moved easily to the STM32WB.

You may create a new post to request details on either BlueNRG and SPBTLE so that relevant people may answer you. As far as I know, BlueNRG is only a BLE product as well and I think that is the same for SPBTLE.

Regards.

JUker
JUkerAuthor
Associate II
August 14, 2019

Thank you!

JUker
JUkerAuthor
Associate II
August 21, 2019

I've loaded the BLE_CableReplacemet project to two STM32WB55 Nucleo boards, using STM2CubeIDE.

One with GATT_CLIENT set to "1" the other set to "0".

Any VT100 terminal you recommend using?

Any video, instructions, etc?

I've tried using "Putty" with instructions in the readme.txt found in the BLE_CableReplacement folder.

Help needed please!

I don't know what else to try and do... :\

Javier1
Javier1
Principal
September 7, 2021

Same issue , same feeling, one would think propper support and documentation could be done in 2 years but apparently no.

https://community.st.com/s/question/0D53W000013pMSvSAM/blecablereplacement-doesnt-work-for-me-pnucleowb55

hit me up in https://www.linkedin.com/in/javiermuñoz/
EMECH
EMECH
ST Employee
August 22, 2019

Hello,

Here is the configuration for Tera Term VT terminal:

After a reset of the Client board and a switch off the blue LED you should see on each terminal window the following screen:

On each terminal, written characters are sent after each hit of the "enter" key.

Best regards.

EMECH
EMECH
ST Employee
August 22, 2019

Houps,

Better with the associated pictures:

0690X00000AA60qQAD.jpg

EMECH
EMECH
ST Employee
August 22, 2019

Serial Port configuration:

0690X00000AA63VQAT.jpg

EMECH
EMECH
ST Employee
August 22, 2019

And the Terminal screen:

0690X00000AA61ZQAT.jpg

Best regards.

ptagh.1
ptagh.1
Associate
May 5, 2022

Hello guys,

I wanna implement the BLE_CableReplacement example on the Nucleo board.

But I don't know which application/example should be programmed on Dongle.

I need to have a full-duplex communication between Dongle & Nucleo (Stream of data).

Terms & ConditionsAccessibility statement