Skip to main content
OliM
Senior II
March 17, 2026
Solved

BLE Thread dynamic stack broken in Cube v. 1.24?

  • March 17, 2026
  • 3 replies
  • 260 views

After a long time, i started to look into using the BLE_Thread_dynamic stack image on WB55 again. First without success with my own code on my own board, which I do think to remember worked before.

But afterwards with the BLE_Thread_dyn example on a WB55 Nucleo Board and that doesn't work as well.

 

This is how the FUS Info looks

image.png
And this is where it gets stuck

Clipboard01.jpg

Any Ideas what I might be doing wrong?
I already tested with and without "Start Wireless Stack" from the programmer. Not using it, makes it stop even earlier, at hci_reset.

Starting to look into older stack images now.
Edit: I went back up to 1.18 (using the example code from 1.24, which seems to be untouched since way back) and nothing worked :thinking_face:.

Best answer by OliM

So after a lot of lost hairs and no support through the official channels (“please do like in the example”). The issue I was facing with my code look like some debug options are running as default in the Thread Stack:
I needed a TL_TRACES_Init( ); and to implement the ack on CLI send to get the Thread stack through SHCI_C2_THREAD_Init 

void TL_THREAD_CliNotReceived( TL_EvtPacket_t * Notbuffer )
{
/* ignore the data */
(void) Notbuffer;
/* Ack the send request Notify so M0 continues */
TL_THREAD_CliSendAck();
}

 

3 replies

ST Technical Moderator
March 30, 2026

Hello @OliM ,

Ensure FUS and stack versions are compatible. Always delete the previous stack before reinstalling, verify installation steps carefully and verify that the stack is correctly installed by checking the version with 'Read FUS infos' or reading OB SBRV.

Check the value of the SBRV option bytes in OB tab following this wiki article: STM32WB Firmware Upgrade Service - stm32mcu

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
OliM
OliMAuthor
Senior II
April 1, 2026

Regarding the not running example I found the issue: I did not have the WB55RX to ST link TX jumper on the Nucleo. Apparently that floating RX was completely throwing off the example.
For my own code i am still searching why I don't get a response to SHCI_C2_THREAD_Init() .

OliM
OliMAuthorBest answer
Senior II
June 17, 2026

So after a lot of lost hairs and no support through the official channels (“please do like in the example”). The issue I was facing with my code look like some debug options are running as default in the Thread Stack:
I needed a TL_TRACES_Init( ); and to implement the ack on CLI send to get the Thread stack through SHCI_C2_THREAD_Init 

void TL_THREAD_CliNotReceived( TL_EvtPacket_t * Notbuffer )
{
/* ignore the data */
(void) Notbuffer;
/* Ack the send request Notify so M0 continues */
TL_THREAD_CliSendAck();
}