STM32 MCUs Wireless

I'm using two STM32L4xx connected to LoRa modules. The LoRa settings on both cases are:bw = 500 kHzSF = 12CR = 4/5implicit header, Crc off, low data rate optimization is on.On transmitter module, I do the following:Make sure the module is not in sleep modeSet the Tx pin high and Rx pin low.Clear the flagsSet the payload sizeSet the TxBaseAddr and AddPtr to 0x80Write 3 bytes to FiFoChange the operation mode to Transmitter.Wait until the TxDone flag is setI have read back all the registers to make sure they are properly set.On the receive side I make sure the modem is in continuous receive mode and check the flags until RxDone is set to 1. When I check the register RxNbBytes it is 1 and reading through the FiFo I can only see one of the bytes has been transferred.I've been dealing with this problem for about a week now and have tried many different things. Comparing my steps to other libraries (such as mbed os), I'm following the same steps.

STM32CubeIDE 1.3.1 - STM32-Nucleo-WB55 - with or without FreeRTOS CMSIS_V2Using PB7 STLINK_TX & PB6 STLINK_RX for UART debug traces (with a logger)BLE in initial configuration by IDE in P2P or HRS.Thank for you answers and help.

Hello! I welded the controller p-nucleo-wb55 on my board(out of debug board) and powered it how is described in the documentations, but bluetooth does not work(does not advertise). How can I solve this problem?

If the spreading factor is set to 9, messages get through. As I increase it to 10 or 11, I start to get the OnTxTimeout error. The payload I'm sending is similar to this lCrTHfXrQdM7M6ZoFrmwMxHacVtZcoBxvSvve0Pi5awSYtk=I need to increase the spreading factor to increase the range. My frequency is set to 904600000 and my bandwidth is set to 2.

Hi, I have followed the AN5247 to implement OTA flow and wondering if it is possible to put different user APP in two flash address and OTA APP could decide to boot from which one. I have tried to flash P2P server_ota in 0x08007000 and HartRate_ota in 0x0802C000(also updated linker info) and update "CFG_APP_START_SECTOR_INDEX" in BLE_Ota as 0x2C to boot from the second APP. Although the HartRate function works, Cube programmer can't even connect to nucleo. It seems something strange. Also because the 2 APPs may be put at one of assigned flash address(07 or 2C), how to handle the linker setting while compile the FW?

Why does the OTA firmware file end up in position 0x0800c000 instead of 0x08007000 as the application document says? ( https://www.st.com/content/ccc/resource/technical/document/application_note/group1/47/71/00/8f/f8/ef/45/4b/DM00556294/files/DM00556294.pdf/jcr:content/translations/en.DM00556294.pdf) . Is it posible to start user App in different memory position than 0x08007000? or to save more than one Flash memory sector for User data? (default i guess its from 0x08006000 to 0x08007000Best regardsAlvaro

I'm trying to advertise with Scan Response, as I need to advertise more data than 31 bytes (Advertisement limitation).as I understand the way to publish more data before connecting/pairing, is by using Scan Response.there is an example with the STM32WB55 Evaluation Board?Thanks,Lior

Hi all: i am a newer to the Nucleo board .Recently, i try to upgrade firmware to Nucleo board by Stm32CubeProgrammer. i click the button Firmware delete at first. after that, i choose the wireless stack or stm32wb5x_FUS_fw.bin and i want to upgrade the firmware,but it alway go wrong with the message i had search for the solution,and they didn't work for me,can anyone know what is happening and what should i do to fix that? i have tried to download the BLE_p2pServer application,but the light didn't blink as before.it has bother me few days, can anyone have solution?

Issue with following STM32WB MOOC Workshop 4: After enabling custom template CubeMX often hangs at code generation, and app_ble.c has error.I have updated CubeMX to latest version (5.6.1), as well as the firmware package for the STM32WB55 (v1.6.0). Attached please see my IOC file and the app_ble.c file in question. These cause me not being able to compile the project.Note: the code snippet start at line ~363 in attached app_ble.c file.I know the MOOC material is outdated, but I was not expecting the CubeMX to freeze like this. /**   * Advertising Data   */   uint8_t ad_data[16] = {   2, AD_TYPE_TX_POWER_LEVEL, 0x18 /* -0.15dBm */, //Transmission Power   valueNotSetted, AD_TYPE_SHORTENED_LOCAL_NAME , '0', '1', 'S', 'T', //Shortened name   3, AD_TYPE_APPEARANCE, 0x00, 0x00 /* UNKNOWN_APPEARANCE */,   3, AD_TYPE_ADVERTISING_INTERVAL, 0xA0, 0x   Expression res[2] is undefined on line 902, column 176 in stm32_wpan_ble_app_ble_c.ftl.   The p

I wanted to use the P-Nuceo-LRWAN1kit (STM32L073RZT6+SX1272) as a way to send Lora messages.On the back the kit, thare is a message about I-CUBE-LRWAN, That uses AT commands to send Lora messages.But wen i look voor I-CUBE-LRWAN software I canot find it working with my setup (can't find any reference of a SX1272 driver in the code as wel).So, now I start to wonder of I-CUBE-LRWAN is only for the master side and not te slave side?yours truly,Jos Terra

Hello.I need the STM32WB55 Nucleo board to read the BLE-beacons. Are there any ready-made examples or description of how to implement this?

I'm developing an application starting from your project BLE_p2pServer, using the demo board STM32WB55 Nucleo. I need to use the BLE only when the final user asks to use it, by pressing a button, so I need to switch off the CPU or put it in shutdown mode. How can I do it? Thanks.

Hi, I've decided to use some free time to explore LoRaWan. I have experience of ST devices and have a few nucleo boards, (F303 and L433). I bought two lora shields with which to experiment; a I-NUCLEO-LRWAN1 and a SX1272MB2DAS. I've down loaded the lora software and can see a number of examples, however the target boards/devices are different from mine. Yes I could buy the relevant board, but I noted statements that it is "easy" to migrate code between device families and devices within families. My first question is "how do you port the LoRa firmware to either of the target boards I have?" A lot of Googling and reading some guides suggests that porting is not as "easy" as some suggest!? The second question is " Is there a tutorial or video that explains in a step by step fashion how to create a Lora device from scratch?" I ask this, because while it is nice to have a ready-made project to use, I would prefer to be able to understand the implementation/problems/issues/requirements of a

I want to use external PA (SKY66118-11) with STM32WB55. Shall i connect RF pin of STM32WB55 to RFIN pin of SKY66118-11 directly or i have to connect it through matching and/or 50ohm balun.

Hello,I have a question about the STM LoRa example.While I was testing the LoRa communication using the b-l072z-lrwan1 board and the I-CUBE-LRWAN example, I found the abnormal behavior.After the "PHY txDone" message, Rx Callback did not work, the RTC timer was alive, but LoRa did not work anymore.The action also occurred after the first Tx and 1 hour after and 3 days later.The settings are as follows.KR920OTAAClass Apublic network: privateconfirmation: confirmed msgTx cycle: 60 secondsThe used version is 3 versions of 1.2.1 / 1.2.3 / 1.3.1.I found the same behavior in the two versions except 1.2.1.Payload : 0 ff 4f Tx Count : 79 236347s770: PHY txDone 236349s032: PHY rxTimeOut 236350s032: PHY rxTimeOut 236353s454: PHY txDone 236355s636: PHY rxDone Payload : 0 ff 50 Tx Count : 80 236357s770: PHY txDone 236359s953: PHY rxDone Payload : 0 ff 51 Tx Count : 81 236367s770: PHY txDone 236369s953: PHY rxDone Payload : 0 ff 52 Tx Count : 82 236377s770: PHY txDone 236379s953: PHY rxDone Payl

Hello,I have a board with stm32wb55. I can't enter to shutdown mode or can't to exit form shutdown.I want to exit from this mode via wakeup pin 1 PA0. I use this codeif( (LL_PWR_IsActiveFlag_C1SB() == 0) || (LL_PWR_IsActiveFlag_C2SB() == 0) ) { /* Set the lowest low-power mode for CPU2: shutdown mode */ LL_C2_PWR_SetPowerMode(LL_PWR_MODE_SHUTDOWN); }   HAL_PWREx_EnableGPIOPullUp(PWR_GPIO_A, PWR_GPIO_BIT_0);   HAL_PWREx_EnablePullUpPullDownConfig(); /* Disable used wakeup source: PWR_WAKEUP_PIN1 */   HAL_PWR_DisableWakeUpPin(PWR_WAKEUP_PIN1);   HAL_PWR_DisableWakeUpPin(PWR_WAKEUP_PIN2);   HAL_PWR_DisableWakeUpPin(PWR_WAKEUP_PIN3);   HAL_PWR_DisableWakeUpPin(PWR_WAKEUP_PIN4);   HAL_PWR_DisableWakeUpPin(PWR_WAKEUP_PIN5); /* Clear all related wakeup flags */   __HAL_PWR_CLEAR_FLAG(PWR_FLAG_WUF1);   HAL_PWR_EnableWakeUpPin(PWR_WAKEUP_PIN1_LOW); HAL_PWREx_DisableInternalWakeUpLine(); /* enter shutdown */   HAL_PWREx_Ente

Please clarify on example app support for this MCU BLE operation.Regards,Shri

Hi,I want to know whether the ​above mentioned stm32wb5x series support whitelist feature or not.​If no then I want to know the part number ​, which supports whitelist.

I just got myself this kit - https://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/stm32-nucleo-expansion-boards/p-nucleo-lrwan3.html#overview (433/470 Mhz version; just asserting the frequencies here..)to play with. I'm interested to use the gateway from this kit with other nodes, not from this kit or non ST ones.In particular I'm interested in using a bunch of breakout kits with this module:https://www.hoperf.com/modules/lora/RFM96.htmlWill I have any real problems with them & the gateway from the P-NUCLEO kit? That gateway is based on RisingHF chip. Now, I had experience with neither or, of those. (I'm asking of there major incompatibility issues, or if one lacks support for such & such that wont' make it usable with the other ; and not if there are different software stacks that you will need to get used to, or dev envs & configurations, etc.)

Hi,I want to generate .bin file of BLE_OTA example.i have added below command in post-build steps AC6 IDE.arm-none-eabi-objcopy -O binary "${BuildArtifactFileBaseName}.elf" "${BuildArtifactFileBaseName}.bin"It generate binary successfully but it's size is too larger than .elf and .hex, Please help me to resolve the above issueFiles sizeProduction.bin 385MProduction.hex 43KProduction.elf 2.0MThanks,Arjun

Hi,Is there an existing infrastructure for OTA custom firmware flashing of an STM32F7 MCU using (preferably) STM32WB of SPWF04?we have an already written application for our STM32F7 which takes more than 512KB.I went through the resources and found only STM32WB and SPWF04 self programming.

I designed new board with STM32WB55CGU6 based on MB1993C (P-NUCLEO-USBDongle). You can see my schematic attached(I uploaded both P-nucleo schematic and my schematic). But I can't connect to my MCU through SWD pins (DIO,CLK,NRST). I use st-link, I can connect to P-nucleo usbdongle with these 3 pins, but I can't connect to my MCU. ST-Link can't find MCU. Unfortunately one of the crystals in my design (which is connected to pins number 23 and 24) has wrong footprint, but at least I should be able to connect to the MCU. does anyone know what is the problem?

I’m using the nucleo board, and I’ve got SPI working correctly (mostly) with default settings using CubeIDE. However, the data sheets stated that SPI can run at 32 Mbps, and I’m only getting half that rate.The SPI Prescaler is set to the minimum value of /2, so I’m guessing I need to change my clock configurations to get up to the max rate? What do I need to do to get the max SPI rate; because I’m not getting with default settings?

Hi,I am working with OTA on STM32wb55 wireless MCU,I have tested BLE OTA from android app mentioned in AN5247 and it worked well.Now i need to create a python app doing the same.In order to do that i followed Flow given in the same AN5247 at Figure 9- OTA data flowMy setup is as per below:-1.STM32wb55 - P2P OTA flashed in 0x7000 location2. Linux MPU - python2.7, Gatt tool and bluez-5.50 , hciconfig hci0 up and runningMy MCU is flashed with P2P ota service and I m able to provide reboot request from my Linux device using below command on handle provided by UUID- 0000FE11-8e22-4541-9d4c-21edae82ed19char-write-cmd 0x0013 010706It issues reboot in stm32wb and puts mcu in STM_OTA mode.(Same as in Android app)At this stage my UUID and its handles are as per below,handle: 0x0001, uuid: 00002800-0000-1000-8000-00805f9b34fb handle: 0x0002, uuid: 00002803-0000-1000-8000-00805f9b34fb handle: 0x0003, uuid: 00002a05-0000-1000-8000-00805f9b34fb handle: 0x0004, uuid: 00002902-0000-1000-8000-00805f9b3

I test it on P-NUCLEO-WB55 kit board which without any other devices connected on it with the official examples "PWR_STOP2_RTC" ,and I did test it as the readme.txt file tell me（remove all jumpers on JP5, and test the current on the JP2）, but the result is near 116uA.​Also I have test the standby mode with the "PWR_STANDBY_RTC" examples, the result is about 0.2uA which is ok.​So what's the matter would it be with the STOP2 mode about the big current?Looking forward to your ​reply.Thanks.xiaodong.zhao