STM32 MCUs Wireless

When using the Custom Template option in Cube MX 5.6 for the WB55, the generated "custom_stm.c" file contains some bugs in the "Custom_STM_App_Update_Char" function. Namely, the calls to "aci_gatt_update_char_value" mistakenly pass the characteristic handles twice rather than first passing the service handle and corresponding characteristic handle. I'm hoping this will be fixed in the next update to Cube MX.Additionally, I would have expected Cube MX to generate code for the cases in the "Custom_STM_Event_Handler" function. I filled the code out for the "EVT_BLUE_GATT_ATTRIBUTE_MODIFIED" case on the material from the WB workshop video (part 4) which seems to work, but it seemed fairly standard to me so I was wondering if it could just be generated by Cube MX in the future.

HiI am trying to generate a true random number on the B-LO72Z-LRWAN1 using the HAL_RNG_GenerateRandomNumber function with the code below:uint32_t rnd_generator (void) {RNG_HandleTypeDef RngHandle;  // RNG handler declaration uint32_t rv;  RngHandle.Instance = RNG;  if (HAL_RNG_Init(&RngHandle) != HAL_OK) {    printf ("\n Error RNG_Init \n");  }  if (HAL_RNG_GenerateRandomNumber(&RngHandle, &rv) != HAL_OK) {    printf ("\n Error RNG_Generate \n");  }  HAL_RNG_DeInit(&RngHandle);  return rv;}The HAL_RNG_GenerateRandomNumber always returns an error and the generated number is always the same. I believe that I must initialize the clock for the RND module using my own version of the HAL_RNG_MspInit and HAL_RNG_MspDeInit functions.Can you provide me some help on this?BRGilberto

Hi,Can any one guide me how can i enable debug messages in BLE_HeartRateFreeRTOS demo.i have enable below macro but doesn't get any success#define CFG_DEBUGGER_SUPPORTED  1#define CFG_DEBUG_BLE_TRACE   1#define CFG_DEBUG_APP_TRACE   1#define CFG_DEBUG_TRACE_LIGHT   1Please help me what i am missing i need debug print come fromAPP_DBG_MSG and BLE_DBG_HRS_MSG.Thanks,Arjun

Hello,I successfully able to download and run the BLE_OTA example (on WB55-Nucleo platform)I had transfer the M4 FW file only, named: BLE_p2pServer_ota_reference.bin with the size of 33.6KB, The Total transfer time was: 42.02 Sec (on my Huawei p10 mobile running "ST BLE Sensor" mobile App. v4.7.1)Meaning the Transfer Rate is less then 10Kbits/SecPlease advise why the Transfer Rate is so slow? and what need to do in order to make it faster?Thanks In Advance,Micha

Greetings, I have my STM32WB55RGV6 connected to my computer through USB using the ST-LINK port on the board. When trying to flash the coprocessor to run an example application from the WB firmware package, I cannot even erase the previous firmware. Using the commands from the attached link results in an error to erase the firmware, with message FUS_STATE_ERR_UNKNOWN. I have no problems flashing the main processor with binaries using this tool or armKEIL, but for some reason I cannot get the hang of this. I have even tried following the release notes addresses for programming but nothing seemed to work. Does anybody have a solution for this issue? Thank you for your attention, I have added some screenshots below to make my issue easier to understand. 1- Initial Connection using st-link2- attempting to erase firmware3- attempting to flash FUS firmware4 and 5 - Attempting to flash BLE full stack firmwarePedro Casanova

Using STM32CubeMonitor-RF I am able to update my device via OTA with one small issue. I send the command to program my device and my application gets deleted and the device reboots into our OTA application but I have to search for my device a second time, select the device and then reinitate the programming process. It works fine as a two step process but would like for it to be a single step process.I have a BLE sniffer and I can see where the problem occurs but I have not been able to figure out what is causing it.Here's a snippet from the Nucleo board that works:Here's the snippet form our device that doesn't:The LL_TERMINATE_IND is missing from our connection but I am not sure what is causing the problem.

Hiat_master software works fine but end_node software not working I tried OTAA and ABP.

I have a project using the STM32_WB55 where I use CubeMX to setup a custom BLE template, services, characteristics, etc. I noticed that STM32Cube_FW_WB_V1.8.0 supports both BLE and FREERTOS, but when I enable FREERTOS, all my custom BLE settings are deleted. Additionally, many of the configuration tabs appear to be missing. I see there is an option to setup the heart rate sensor, but adapting this to match my initial custom BLE configuration seems to be a lot of effort compared to generating a custom template. Is there a way to use my custom template with FREERTOS in CubeMX? If not, is this something that will be supported in a future version?

..

STM32WB SoCs have radio module. I need a way to write own wireless stack but the documentation is lacking their description.So far documentation mentions 3 peripheral devices on APB3:0x6000 1000 - 0x6000 1FFF 4 KB 802.15.4 CTRL0x6000 0400 - 0x6000 07FF 1 KB Radio CTRL0x6000 0000 - 0x6000 03FF 1 KB BLE CTRLAnd 8 interrupts:BLE_BLUE_IT BLE blue controller interruptBLE_RFC_IT BLE radio control interruptBLE_RFFMS_IT BLE radio states interruptBLE_HOST_WKUP BLE host wakeup interrupt802_IT0 802.15.4 interrupt 0802_IT1 802.15.4 interrupt 1802_IT2 802.15.4 interrupt 2802_HOST_WKUP 802.15.4 host wakeup interruptThis would be great to get more information on what registers there are and how these peripherals function.Can anyone help me with that?

What could be a solution for this? Device would be a WiFi+BLE gateway, which runs Linux, and can support advertising scan for at least 300 beacons, and have Ethernet port.Something from ST?

I have followed the workshop on https://www.youtube.com/watch?v=V_qVURNbWuM&list=PLnMKNibPkDnHCD2Xc_xX-nWR7AoWBPK2Q. And the first time I went through it everything worked fine. However, when I tried it a second time it did not:I loaded the BLE_Ota_x.bin to the board using the programmer. I then use the ST BLE Sensor app to upload BLE_p2pServer_ota_x.bin into the board and set the memory allocation to 0xC000. This upload works well, but then if I want to load a new code through the app, e.g. the BLE_HeartRate_ota_x.bin, it does not work. The file does not appear as selected firmware, after tapping the SELECT FILE button and selecting the file. If instead, I tap the round button with the refresh arrow, I get a message saying "No node was found".I tried using the dongle in transparent mode as well and get an error or no response message after trying to upload the code.Thanks in advance.Cheers,Derek

Hi,I'm using CubeMX to generate the code for the STM32WB and I found a problem in the secuencer library which is automatically generated.When I register a new task in the scheduler, this places the callback function in TaskCb[0] but when I set the task to be exectued the scheduler tries to trigger it from TaskCb[1] and this leads into a HardFault error. I don't know if the problem is registering the tasks or exectuting them. Anyone else have seen this? Any ideas?Working with the vesrion: STM32Cube FW_WB V1.4.0.Regards,Diego

In P-NUCLEO-WB55 schematics, the pins are connected as shown below. I was not able to find much info from datasheet other than that its related to RF functionality. Can i leave it open if i am making a custom board with STM32WB55 controllers?

Hi there, I'm using a customized board based on B-L072Z-LRWAN1. I also use I-CUBE-LRWAN (v1.1.4), compiled on Keil uVision. Everything works fine. I can get about 2uA in Stop mode. Now I'm doing a project requiring power consumption optimized so I enable Sleep-On-Exit feature. At first, the process of initialization -> sleep (3s) -> uplink first time (enable an interrupt here) -> sleep is fine. However, after the interrupt executed, I can see it isn't back to main function but the current consumption is about 3.5mA. I figured out somehow the uC cleared the SLEEPDEEP bit in SCR register. So inside the interrupt I've set it again. And it did partially works. The current consumption is down to less 900uA but not what I want which is about 2uA or so.So far I've followed instructions in both programming manual PM0223 and reference manual RM0376 but no luck. Do you guys have any suggestion?Thanks in advance.

Does the STM32WB BLE stack support diversity antenna through an external RF switch?

What are the dimensions of package WLCSP59?

I am trying to initiate a project via cubeMx for the STM32WB55 nucleo board.I an able to initiate a simple project without the BLE middleware (STM32_WPAN).Once adding the STM32_WPAN, the generated project not compiled on both Atollic true studio and system work bench.Here is a link to a video demonstrating the issue.I am using: -CubeMX version 5.5.0 -Atollic true studio version 9.3.0 -WB package: STM32Cube_FW_WB_V1.4.0Thanks

I am experiencing an error while trying to upgrade a Nucleo-68 board from P-NUCLEO-WB55 wireless coprocessor to latest v1.7.0 firmware provided by STMicroelectronics/STM32CubeWB github repo.I already reported the issue on the githb repo here is a copy of the issue:**Describe the set-up**Host OS: Linux glibc systemBoard: P-NUCLEO-WB55 STM32WB55RG (Nucleo-68)Tools: - STM32CubeProgrammer v2.4.0 - SMT32CubeWB firmware images**Describe the bug**Trying to update the wireless coprocessor to latest v1.7.0 results in an error:```Error: failed to download Segment[0]Error: failed to download the FileError: Failed to download image!```**How To Reproduce**1. clone `https://github.com/STMicroelectronics/STM32CubeWB`2. enter the repository3. checkout tag `v1.7.0`4. cd `Projects/STM32WB_Copro_Wireless_Binaries/STM32WB5x/`5. follow instructions at `How to flash the Wireless Coprocessor Binary via USB (Command Line Interface)` in file `Release_Notes.html` using STM32CubeProgrammer v2.4.0**Addi

..

Hi,I am developing an application for custom built STM32WB55CC board. Everything seems to be fine, however I am not able to upgrade FUS from v0.5.3. I am reproducing steps from release notes attached inside 1.8.0 FW pack. Please find a log from deleting old FUS:PS C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin> .\STM32_Programmer_CLI.exe -c port=usb1 -fwdelete ------------------------------------------------------------------- STM32CubeProgrammer v2.5.0 -------------------------------------------------------------------       USB speed : Full Speed (12MBit/s) Manuf. ID : STMicroelectronics Product ID : DFU in FS Mode SN : 206A3261554D FW version : 0x011a Device ID : 0x0495 Device name : STM32WBxx Flash size : 256 KBytes Device type : MCU Device CPU : Cortex-M0+/M4     FUS state is FUS_SERVICE_ONGOING   FUS status is FUS_IMAGE_NOT_FOUND   FUS state is FUS_IDLE   FUS status is FUS_NO_ERROR Deleting firmware ...After "De

Hello ST Team, I would like to use the STM32WL in a project that ends at the end of the year.When can I expect the STM32CubeWL MCU package to be released (Q4 was mentioned in a post -> Too rough)?Would it be possible to get a preliminary (also untested) version for testing purpose?Would it be possible to get a blinking_led STMCubeIDE project for developement?Thank you very much in advance.

Dear ST,   the current version of the CMSIS OS2 wrapper (V1.8.0 for STM32WB) does not support calling the functions osTimerStart() and osTimerStop() from an ISR. However, FreeRTOS does provided the functions xTimerChangePeriodFromISR(), xTimerStopFromISR() that can be called from an ISR as an alternative to the functions xTimerChangePeriod(), xTimerStop() used in the wrapper.   Could you please support calling the mentioned functions from an ISR in a future release?   Best regards, Roman

For an R&D project we are curently designing a PCB around an stm32WB , we use the stm32W55 usb dongle as reference design for our project.But we are currently not able to source some specific components : L3 : Ferrite FCM1608KF-601T0FLT1 : band pass filter LFB182G45CGFD436 So i would like to know if ST have other substitute with the same footprints ?Best regards,Pierre

Hello,I'm using CubeMx to create a project with usb cdc serial port and BLE functionality. CubeMx generates a sequencer UTIL_SEQ_Run(~0); that runs the BLE state machine. In the code below, if I comment out UTIL_SEQ_Run(~0); the code runs fine per Workshop #3 on Youtube. Prints out the data "Hello World" to hyperterminal. As soon as I uncomment UTIL_SEQ_Run(~0); and run the app in the debugger I get a hard fault. Has anyone seen this behavior while trying to run the sequencer with usb cdc? Any thoughts as to how to debug this as far as where I should start looking?Thanks,