STM32 MCUs Wireless

Hi, I am having issues reinitialising the BLE stack after waking up from sleep. I am initialising it the exact same was as normal power on. Upon waking up and calling the TL_Enable() function, a shci_notify_asynch_evt it not being received. Is there any examples on how to reinitialise after standby mode?Thanks,Daniel

I am unable to successfully put the STM32WB55 into Shutdown mode and then wakeup via either one of the WKUP pins or the RTC. I can get the WKUP pins to work if I use HAL_PWRex_DisableInternalWakeupLine, but then it won't wakeup via the RTC. If I omit DisableInternalWakeupLine, the MCU will not enter Shutdown mode at all.

Hello! PCB Antenna for STM32WB shown in AN5129 Application note where used pcb stack-up with core 711.2 μm. Exactly the same antenna used in P-NUCLEO-WB55 (MB1355) where pcb thickness is ~1500 μm. How is it possible? How changes antenna parameters when thickness substrate is increased?In AN5129 written: "The electrical parameters and performance of the PCB antenna are also determined by the substrate used, inparticular the thickness of the core and dielectric constants." But in AN5165 recommends to use this solution for different stack-up. How is it possible?

Hello,I'm developing an application based on B-L072Z_LRWAN1 hardware.If i Program my code on the evaluation board everyting works good. I can send and receive packets with LoRa.If I program it on my custom hardware (based on the evaluation board) everything works BUT the LoRa transmission.I cant receive anything and the Tx function timeout ALWAYS expires. Is there some activation procedure that has to be done to make the LoRa module work? Thank You so much.Andrea

Hi,We designed a product using STM32WB series for BLE application. In our case we didn't follow any impedance for antenna due to size constraints. Now we are facing BLE advertising problem.Is the problem with impedance or any other. Kindly guide us to overcome the BLE problem.Attached BLE antenna designed and it is verified by STM technical persons.RegardsLokesh

I'm using a WB55 Nucleo board and setting up a BLE connection with a 2nd WB55 Nucleo board using aci_gap_create_connection(). The connection succeeds and I am able to transfer data between the 2 boards. I would then like to terminate the connection. I call aci_gap_terminate_gap_proc(0x40) to do this, but I always get a return value of 0x46, which corresponds to BLE_STATUS_NOT_ALLOWED. Any ideas why the call to aci_gap_terminate_gap_proc() fails? Or is there a different recommended way to terminate the BLE connection? Thanks...

..

Hello,I have found some bugs in linker scripts generation when creating a project from CubeMX. Those bugs appears only when code is generated for STM32CubeIDE, related to linker scripts:/* Highest address of the user mode stack */ _estack = 0x20040000; /* end of "RAM" Ram type memory *//* Memories definition */ MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 256K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 1024K }_estack should be set to 0x2003000, otherwise the system goes into hard fault.RAM_SHARED section does not appear, without it the coprocessor is unreachable I guess.MAPPING_TABLE, MB_MEM1 and MB_MEM2 are not mapped to RAM_SHAREDOn the other hand, if I generate a makefile or TRUEStudio project for stm32wb55cg (1 MB of flash), the linker reports only 512 KBHope to see this fixed, thanks for your help!

In STM32CubeProgrammer I can set RDP on AA level and BB level, but in CLI mode read/write protection is constantly in BB. In CLI protection byte doesnt change, I mean I can't change itand can't write FUS or stack, and even check the fuse version.C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=usb1 -rdu     -------------------------------------------------------------------                      STM32CubeProgrammer v2.1.0     -------------------------------------------------------------------USB speed  : Full Speed (12MBit/s)Manuf. ID  : STMicroelectronicsProduct ID : DFU in FS ModeSN         : 207D308E3036FW version : 0x011aDevice ID  : unknownWarning: Device is under Read Out ProtectionDi

I have successfully uploaded stm32wb5x_FUS_fw.bin to my STM32WB55CC and the next step resulted in the error I don't know how to deal with. Here is the CMD log     ------------------------------------------------------------------                      STM32CubeProgrammer v2.1.0     ------------------------------------------------------------------USB speed  : Full Speed (12MBit/s)Manuf. ID  : STMicroelectronicsProduct ID : DFU in FS ModeSN         : 2065369C3136FW version : 0x011aDevice ID  : 0x0495Device name : STM32WBxxFlash size : 256 KBytesDevice type : MCUDevice CPU : Cortex-M0+/M4Download firmware image at address 0x80cc000 ...Memory Programming ...Opening and parsing file: stm32wb5x_BLE_Stack_fw.bin File   &nb

..

I am trying to reconfigure the BLE_HID application to the smallest STM32WBCC processor.The linker script for BLE_Hid example with STM32WBRG which look like this ( stm32wb55xx_flash_cm4.ld) /* Highest address of the user mode stack */_estack = 0x20030000;  /* end of RAM */ /* Generate a link error if heap and stack don't fit into RAM */_Min_Heap_Size = 0x400;   /* required amount of heap */_Min_Stack_Size = 0x1000; /* required amount of stack *//* Specify the memory areas */MEMORY{FLASH (rx)         : ORIGIN = 0x08000000, LENGTH = 512KRAM1 (xrw)         : ORIGIN = 0x20000004, LENGTH = 0x2FFFCRAM_SHARED (xrw)      : ORIGIN = 0x20030000, LENGTH = 10K}_______________________________________________________________I tried this (STM32WBCC has SRAM1=64KB ) /* Highest address of the user mode stack */_estack = 0x20010000;  /* end of RA

When programming a binary file stm32wb5x_FUS_fw into the STM32WB55CC, after the line "RSS Status is RSS_IMAGE_IS_NOT_AUTHENTIC" appears a line "Error: fireware not authentic" in red. Why could an error like that happen and why it is impossible to proigram that file on any PC (I tried different!)? Any advice would be highly appreciated.

Try to get demo firmware sources for USB dongle MB1293C. Also a .hex file will be useful.I am trying to use STM32Cube utility to generate code from the .ioc file but the code generated does not support the usb driver properly. Any hints to how to get usb driver code working will be useful to me.

The original version of STM32WB Ble stack is 1.0.0.3/e, Other releases include 1.0.0, 1.1.0, 1.1.1, 1.2.0. What are the differences between these versions? Can you provide detailed documentation?In addition, I'm going to buy some STM32WB . Are these chips manufactured with Ble stacks installed?​

You can find it here : http://risinghf.com/#/product-details?product_id=26&lang=en

I see that cubemx shows x-cube-ble1 as an available sw package for a stm32wb55 project. Is it possible to use the x-cube-ble1 stack on the wb series? I'm having a hard time in getting the flow of how a ble app is configured on the wb, in this forum someone suggested me to read the ble1 and ble2 programming guidelines and they seem clearer and better explained than the wb wireless application notes. Sorry for the basic questio, thanks!

I'm developing a custom board with STM32WB55CGU6 with firmware based on Cable Replacement example. Trying changing the advertised name, I can not put more than 5 chars, the BLE stops working. I know the standard advertising supports until 7 chars. What I have to configure to have a bigger advertised name ?

​FLASH_CR:

So we update the FUS following the steps specificed in the release note, the process went ok and the FSU was upgradedUSB speed : Full Speed (12MBit/s) Manuf. ID : STMicroelectronics Product ID : DFU in FS Mode SN : 206936933136 FW version : 0x011a Device ID : 0x0495 Device name : STM32WBxx Flash size : 256 KBytes Device type : MCU Device CPU : Cortex-M0+/M4     RSS state is RSS_ERROR   RSS status is RSS_UFB_CORRUPT   RSS state is RSS_IDLE   RSS status is RSS_NO_ERROR Deleting firmware ... Firmware delete finished fwdelete command execution finished   hoel@iMac-de-Hoel-7 / $ /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin/STM32_Programmer_CLI -c port=usb1 -r32 0x20030030 1 ------------------------------------------------------------------- STM32CubeProgrammer v2.1.0 -------------------------------------------------------------------       USB speed : Full Speed (12MBit/s) Manuf. ID

In application note AN5289 page 35 it is written that you need to wait for the connection to be established and then call aci_gap_set_pairing_req(). I call this function when connection established event happens, but when I do this return status is 0x46 -> BLE_STATUS_NOT_ALLOWED. My question is if this is the right time to call this function, should I call any other function before or this status flag has to do something with wrong settings before the function call?Do you happen to have an example of how security pairing is established, or maybe an application note that I missed?Thank you in advance,Jaka

I have WB55 Dongle board that someone may have programmed previously. I am trying to start it fresh and make sure it is up to date using all files from  from STM32Cube_FW_WB_V1.2.0I followed the procedure to install new FUS and BLE Stack:STM32_Programmer_CLI.exe" -c port=usb1 -fwdeleteSTM32_Programmer_CLI.exe"  -c port=usb1 -fwupgrade stm32wb5x_FUS_fw.bin 0x080EC000 firstinstall=0STM32_Programmer_CLI.exe"  -c port=usb1 -fwupgrade "stm32wb5x_BLE_Stack_fw.bin" 0x080CC000 firstinstall=1Then I used the Programmer in USB mode to download BLE_TransparentModeVCP_reference.hexAll that seems to work fine. But when I set the switch back to normal boot and plug it in, there are no lights, and no COM port is recognized. Ironically, before I did this, the device did show up on COM3, but it was also unresponsive. What did I do wrong, or how can I figure what is wrong?

The STM32WB55xx devices embed an Arm ®(a) CPU1 Cortex ® -M4 core.I use this chip manual.I operate strictly according to the chip manual, but all of them have errors in reading, writing and erasing a sector.the flash meomory address range:​0x0800 000-0x080f ffff,But when I use burning tool to burn, there is an error in this address 0x080f 6000, reading and writing all report this address error, the following areas can not read and write, using mass erase also report errors; when using j-link burning, erase blank chiperase, erase sector succeeds, erase chip error.

Hi Sir/Madam,Here i need calculate the current required to operate the STM32WB55REvx. I downloaded the datasheet of this MCU. In the datasheet should i need to consider the operating conditions or absolute characteristics to calculate the current required to drive the STM32WB55REvx.Thanks & Regards,

FLASH address: 0x0800 0000~0x080F 5FFF, CPU1 (cortex-M4) can read and write to its normal access, address 0x080F 6000~0x080F FFFF is protected by CPU2 （cortex-M0）and read and write.