STM32 MCUs Wireless

Hello, I have a BLE Secure Connection implemented between an android phone and STM32WB55. Currently, using fixed key to start pairing, it takes approximately 2 seconds to get paired (after the key is sent, and devices are paired) in addition to 600ms for scan, connect, and find services.I was wondering if some can confirm and give me some pointers on how to bring the pairing time to less than 1 second.What I have tried so far.Fixed MTU size on firmware and Android to avoid MTU set/reset(this reduced 0.5 seconds)Min Advertisement Time Duration is 800ms and Max is 10.4 secondsTx Power : Set to MAX @ 6dbMEncryption is set to minimum 8 byte.There is only 1 service, with 2 Characteristics( 1 read, 1 write), and both are authenticated, and encrypted.Thanks

We have developed battery operated product using STM32WLE5CC.when device goes into deep sleep around 1.7uA current are flow normally.During Testing of product we face an issue which is described as below.During deep sleep of STM32WLE5CC, we removed battery from device so now slowly- slowly voltage gets down on STM32WLE5CC VCC-GND pin.Case 1:Voltage Down Start from 3.3V and when it reached to 1V-1.1V, we again plug battery into device and now voltage on STM32WLE5CC VCC-GND pin is 3.3V .then we press Button on EXTI on PB3 Button, which is our external wake-up source and STM32WLE5CC wake-up start working completely.Case 2:Voltage Down Start from 3.3V and when it reached to 700mV - 800mV, we again plug battery into device and now voltage on STM32WLE5CC VCC-GND pin is 3.3V.but in these condition STM32WLE5CC didn't boot again and also not react on button press on PB3 external wake-up. its goes into unknown condition.its only react now when we restart it using reset button.So, Please help us

I am using TIM16 as a one second counter on an STM32WB55. I would like to generate an interrupt after it rolls x times (as example 2). I set the TIMx_RCR to a 1. Can someone tell me what function I need to call in the HAL library and should I place that function within the "HAL_TIM_PeriodElapsedCallback" which I am using?I only see the "HAL_TIM_GenerateEvent" which to me sounds like if you want to do a software generate of an event????Thank you.

Greetings, i am developing a application that will run on a RAK3172 module and i have been attempting to use the radio End-Of-Life flag to detect when the battery supply is too depleted to operate the radio safely.The base application is the LoRaWAN_End_Node sample with modifications to make it run on a RAK3172 package mounted on a custom PCB.As the first thing upon entering the main function, i activate the end of life detection enable register with the function (HAL_PWREx_SetRadioEOL) provided to me by the sdk. Then i connected the board to a power supply to simulate different battery charge levels.To make a long story short, for some reason the EOL flag (in PWR-SR2) remains always set to 1, regardless of:-enabling or disabling of the EOL enable register-state of the radio-supply voltageUnfortunately this makes the end-of-life detector useless as i cannot discriminate whether or not the battery is sufficiently full to operate the radio safely.Thanks in advance

 I have already done it, but I want to change the code for the P-NUCLEO-LRWAN3gateway. Is it possible to share the code if you have it?I use the bin file for the gateway and the expansion code for the end-devices.Board used: https://www.st.com/en/evaluation-tools/p-nucleo-lrwan3.htmlBin: https://www.st.com/content/st_com/en/products/partner-products-and-services/embedded-software-from-partners/the-things-network-gateway-firmware.html#product-details

I have no problem to flash or debug the CM4 of the board. But when I'm trying to flash the CM0+ this error occurred : Error in final launch sequence:Failed to start GDB serverFailed to start GDB serverError in initializing ST-LINK device.Reason: (255) Unknown. Please check power and cabling to target.This informations are show on the consol : STMicroelectronics ST-LINK GDB server. Version 5.9.1Copyright (c) 2021, STMicroelectronics. All rights reserved.Starting server with the following options:    Persistent Mode      : Disabled    Logging Level       : 1    Listen Port Number     : 61234    Status Refresh Delay    : 15s    Verbose Mode        : Disabled    SWD Debug        &

I'm using the necleo-wb55 board.I'm trying to increase ADC measuring speed but I found that the speed for 16-bit measurement and 12-bit measurement looks the same even though 16-bit uses 256 oversampling. I checked how many measuring cycles happen using USB debug but both systems show about 300 times per second.Because I have to use 32 channels for the mapping device, the 300 times per second is insufficient, (its frame rate becomes ~10 fps). I'm targeting 60 fps ~ 600 fps because I have to collect brain signals.Could you explain what can cause such a delay?or should I use a high-end microcontroller such as STM32H725AEI having 550 MHz clocks? In this case, I'm concerned about how to send data through wireless communication.

When you power Nucleo-WL55JC! with external 3V3 via CN6, I could see constant 120mA current consumption. Is there any way we can reduce this?

..

Hi all. I've got a problem when trying to flash the STM32WLE5J8I6.I am trying to run a simple blinky code and blink an onboard LED on my custom pcb.The program builds fine, connecting with the ST-Link (Nucleo-WL55JC1) and using SWD to connect to the STM32WLE5 works. However, when running or debugging, the program gets stuck at 97%. See picture. The following output is seen in the console:STMicroelectronics ST-LINK GDB server. Version 6.1.0 Copyright (c) 2022, STMicroelectronics. All rights reserved.   Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled   Waiting for debugger connection... Debugger connected Waiting for debugger connection... Debugger connected Waiting for debugger connection... ------------------------------------------------------------------- STM32CubeProgrammer v2.10.0 -------------------

Hello, I'm trying to connect an OLED display to my STM32WL55JC by I2C but it doesn't work...I've successfully connect it with a STM32F411RE but the I2C configuration / HAL interface seams to be different between both MCU...Here my config on the STM32F4 Here my config on th STM32WL : Does anyone know whats wrong ? Thanks so much !Hugo P.

Can you use the extended advertising and scanning found in BLE 5 somehow? I have found some references to them in the code, but cannot find any defines. Do they exist? Will they be implemented?

..

In examples I got familiar with RF low level access is controlled by some exact coprocessor firmware. Existing coprocessor binaries provide some higher level of abstraction that seems to not include forcing signal with exact characteristics. Do I missing something or is there any other approach to start continuous signal generation with specified power and frequency?

Hi, I want to use B-U585I-IOT02A as a controller for mobile robot, I use a smartphone for the remote control. For now I am using HC-05 as the bluetooth interface because I can't find out how to program the STM32WB5MMG to act similar with HC-05. Can anyone give me any guide or reference how to do it? I just need it to work as the bluetooth interface to receive serial data and send it to the STM32U585.And I use MITAppInventor 2 to create the smartphone software if anyone wondering.

I went from the v1.12.1 stack to the v1.13.3 stack and LE Privacy seems to be no longer working. It advertises, but always with the static random address, not a random resolvable address. Also, the address never changes. Anyone else seeing this? Is there some new interface I need to use to get random resolvable addresses?

Hello, Can you please point me to the factory settings of stm32wb55 pucleo board.I seem to have erased some sectors 1-192 and fiddled with some option bytes (nBOOT0) and nSWBOOT0Best Regards,D

Several BLE circuit design inquiries of the STM32WB55RG MCU.The BLE impedance requirement of this MCU is 50 ohm, and it is recommended to use LPF (MLPF-WB55-01E3). For the detailed circuit diagram, please refer to the fourth page of the attached file (20220119_Main Board(3-8).pdf), component information Elements will appear by clicking on them with the mouse.The PCB stack is 1oz CU / 0.1mm(FR4) / 1oz CU / 1.2mm (FR4) / 1oz CU / 0.1mm(FR4) / 1oz CU with a total thickness of 1.6mm.1. With the current design, the BLE signal will first pass through the LPF, and a T-type matching circuit is designed between the LPF and the antenna. Is this design OK? I read the ST document (AN5165) that the filter is placed near the antenna. , the Pi-type matching circuit is placed between the filter and the MCU.2. If it is feasible according to the current design, is there a tool to quickly calculate the component values and line width/length of the matching circuit?3. Currently discussing the line impedan

STM32WB55RGV6 connects ADS1299 by spi. And I choose spi2. There are three signas miso\ mosi and sck. SPI2 has two alternative: GPIO_AF3_SP2 and GPIO_AF5_SPI2.① STM32CUBEMX automatically generated miso(GPIO_AF3_SP2), mosi and sck(GPIO_AF5_SPI2).Initialization is ok, but no data.② All ​GPIO_AF3_SP2. Initialization is failed and application crash.③​ All ​GPIO_AF5_SP2. Successfully.Although the result is good, I do not understand why:sad_but_relieved_face:

I was trying to use the time server for a project on STM32WB55. I tried to use it in an empty project. When I tried to debug, this window pops up:The curious part of the problem is that this error seems to happen with the time cluster only: using another cluster such as the on/off one doesn't create any problem.I will attach to this message the .ioc that I am using: I did not modify the STM32CubeMX output.What can I do?Thanks in advance.P.S. Another thing I tried to do was removing and putting back single lines of code in order to understand which part of the program caused the problem. I figured out that the whole thing runs without encountering this specific problem when I remove this line:/* file: app_zigbee.c */ zigbee_app_info.time_server_1 = ZbZclTimeServerAlloc(zigbee_app_info.zb, SW1_ENDPOINT, &TimeServerCallbacks_1, NULL);

The STM32CubeMX generate:```#define LCD_SPI_Send_DMA(rd, ln)           BSP_ERROR_FEATURE_NOT_SUPPORTED```instead if I modify the generated DISPLAY/Target/lcd_conf.h with`#define LCD_SPI_Send_DMA BSP_SPI1_Send_DMA`seems work correctly.I am using:Nucleo WB55RGGFX01M1STM32CubeIDE 1.9X Cube Display 2.1.0 (in the package 2.0.0 was correctly defined)Is this only a STM32CubeMX bug or I can't use SPI + DMA+ Display?Thanks for the support

Hi, I use the nucleoWL (STM32WL which is based on STM32L4). I want to use LPWAN to communicate some measurements each day. I use I2C between MCU and sensors. If I try the Sigfox Push Button exemple, I have 2uA in stop2 mode but if I add I2C1 (thanks to cubeMX) (with any sensor yet) I have around 500uA in stop2 mode: That is too high...I think that is due to internal pull-up resistors. Is it true ? How to avoid this in stop2 mode ?In the I2C_WakeUpFromStop2 example : the current drawn my the uC is around 1uA that is good for me. I think the pins are not pull up internallyI don't need a non-blocking mode for I2C communication because it's only one time per day, polling mode can be ok but I need a low consumption in stop2 mode. I will disconnect sensors during stop2 mode to avoid the sleep current of the sensors and the current in the external pull-up resistors.How to do it in the Sigfox Push button exemple (for example) ? (do it = achieve a low consumption in stop2 with I2C pins empty)Th

I'm using verion 1.1.5 of the I-CUBE-LRWAN software and reading a few I2C sensors using the HAL_I2C functions. No issues when sensors are functioning properly; however, I have run into periodic sensor failure issues while testing, either permanent or temporary, where one of the I2C lines may be held low or enter the wrong state. In these cases, once the HAL TX enters the I2C_WaitOnFlagUntilTimeout() function, timeout is never reached and the entire application hangs until the board is reset.Has anyone encountered a similar issue or have an advice on this problem?In the real world there are bound to be issues here and there with defects and bad communication once in a while, ideally this should not freeze the entire application if the STM32 fails to communicate with a slave device properly during a single read.Code snippet below:In a failed scenario, I2C_FLAG_BUSY remains set and it appears HAL_GetTick() never exceeds Tickstart to generate the HAL_TIMEOUT return.static HAL_StatusTypeDef

..

In order to achieve minimum power drain on the B-L072Z-LRWAN1 discovery board, it is necessary to remove some solder bridgesSee: https://community.st.com/s/question/0D50X00009XkbSOSAZ/excess-current-consumption-running-bl072zlrwan1-from-batteryAnd:https://community.st.com/s/question/0D50X00009q4M1zSAE/cant-power-bl072zlrwan1-with-batteryTo be able to use the onboard ST-Link again, these connections need to be restored:NRST: link CN4.3 to CN12.5;SWD: fit two links on CN8;VCOM: link CN5.1,2 to JP6. Rather than have to mess about with 2 separate links for the SWD, a single-row 4-pin header can be adapted: