Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
Hello,Is CORE_CM0PLUS support FREERTOS ?Thank you,
Can only be duplicated using LPTIM2, enabling interrupts for LPTIM1 works fine.Hard Fault can be resolved by only re-locating the VTOR to a 512-byte boundary.
..
HelloSTM32CubeWB has two demo applicationsBLE_Peripheral_LiteCDC_Standalone (USB)It seems impossible to run the BLE with USB. I added the CDC part to the BLE app and they don't work together (if you disable one, the other works fine).What is the conflict here? The USB demo is not useful if it breaks the wireless part of a wireless MCU.Thanks
Hello,I develop an application with SUBGHZ in transmitting and receiving mode.I have initialized the hardware and configured the SUBGHZ peripheral.I use the switch (PC3, PC4, PC5) to change between Tx and Rx mode, but i steel receiving data from RF even I am in Tx mode, and I cannot send data!It is normal to receive data after switching to TxAnd why I cannot transmit data !Any body have suggestions to resolve this problem ?Thank you,Sincerely.
I bought the NUCLEO-WL55JC1 and installed the STM32CubeIDE1.9.0 on my work computer (and I also this it in my home computer, both are Window 10). The IDE automaticlly installed some STLink drivers during the softare installation, in addition to the STLink-server. This are the installed components:Segger (jlink) USB (08/02/2018 2.70.08.0)Segger (jlinkCDC) Ports (06/06/2019 1.34.0.44950)Segger (jlinkCDC_x64) Ports (08/02/2018 6.0.2601.5)Segger Microcontroller GmbH (WinUSB) USBDevice (06/14/2019 3.00.00.000)STMicroelectronics stlink-serverWhen I did this intallation process in my home computer, everything worked smoothly. Once I connected the NUCLEO to the PC through the USB port I could see the COM port named: "STMicrolelectronics STlink Virtual COM port" in the Device Manager. I went to "Help-->ST Link Upgrade" and the device was found in the device list, so I could upgrade it. I opened an example project and I could debug the NUCLEO board without any problem.However, then I did this
Sample code includes a 50ms delay "TCXO_WORKAROUND_TIME_MARGIN" in addition to the Radio.GetWakeupTime() when moving from RX to TX. Is this a necessary delay, and if so, why? Higher data-rate LoRa configurations are significantly bottlenecked by this delay.
Hi!We are developing an ultralight, ultra low power IoT device and the STM32WL seems like a great fit.We have chosen the STM32WLE5CCU variant (M4 MCU, 256kB, UFQFPN-48) because we don’t need the extra processor core. When designing the board, I ran into a couple issues.No matter how hard I looked, there seem to be no dev boards or even reference designs for the STM32WLE variant whatsoever. So far I’m following the STDES-U4S reference design. Is this correct? Is all the clock and RF stuff the same?Looking at the reference schematic, there is a lot of RF related components. Our application needs to reduce component count as much as possible because of size. Previously, we have used a Semtech SX1276 LoRa transreceiver. There, we dramatically reduced the component count by using the FI168B0845D9-T bandpass filter in a single ceramic package. I’m trying to see where could I place this.Looking at the reference schematic, this section seems to be the bandpass filter, is it possible to replace
Hello,I would like to transfer data between two P-NUCLEO-WB55 boards. I took a look at the p2p-Server/Client example and I think this is just what I need. I used the project templates from CubeIDE and created two own versions. For this I followed this tutorial and got both server and client running. For the server I managed to change the attribute value. Now I would like to establish a connection between both boards. How can I establish a connection and maybe filter for specific devices in my application?
I've been using a WB55 for a BLE Router but supply shortages have meant we need to switch to using a WB10CC. I noticed that there is no example from ST for this chipset. My initial attempts to adapt the WB55 example haven't been productive.
Hello, I am using ST ble sensor app's latest ios version to perform my firmware update on the stm32wb55 device. But the app doesn't work properly. When I try to connect a device from the home page, it shows connecting message for a long time. sometimes it shows an interface and that doesn't help in updating the firmware.. Is there any alternative to ST ble sensor app that helps to do the OTA firmware update
Hello,I asked this question once, but I feel that I explained the problem inadequately.I am attempting to write to internal flash memory and am following the (UNLOCK, ERASE, WRITE, LOCK) approach. Everything writes fine in the simple code I have written until I introduce TIM16. void StartDefaultTask(void *argument) { /* USER CODE BEGIN 5 */ static FLASH_EraseInitTypeDef EraseInitStruct; uint32_t PAGEError; int programIterator; HAL_StatusTypeDef statusErase; HAL_StatusTypeDef statusProgram; uint64_t bufferToWrite[64]; //HAL_TIM_PWM_Start(&htim16, TIM_CHANNEL_1); /* Enable the flash control register access */ HAL_FLASH_Unlock(); /* Erase the user Flash area*/ uint32_t addressToWrite = (0X08080000); /* Fill EraseInit structure*/ EraseInitStruct.TypeErase = FLASH_TYPEERASE_PAGES; EraseInitStruct.Page = 128; EraseInitStruct.NbPages = 1; PAGEError = 0; statusErase = HAL_FLASHEx_Erase(&EraseInitStruct, &PAGEError); if (statusErase != H
#define APPBLE_GAP_DEVICE_NAME_LENGTH 7 #define BD_ADDR_SIZE_LOCAL 6 #if OOB_DEMO != 0 #define LED_ON_TIMEOUT (0.005*1000*1000/CFG_TS_TICK_VAL) /**< 5ms */ #endif PLACE_IN_SECTION("MB_MEM1") ALIGN(4) static TL_CmdPacket_t BleCmdBuffer; static const uint8_t M_bd_addr[BD_ADDR_SIZE_LOCAL] = { (uint8_t)((CFG_ADV_BD_ADDRESS & 0x0000000000FF)), (uint8_t)((CFG_ADV_BD_ADDRESS & 0x00000000FF00) >> 8), (uint8_t)((CFG_ADV_BD_ADDRESS & 0x000000FF0000) >> 16), (uint8_t)((CFG_ADV_BD_ADDRESS & 0x0000FF000000) >> 24), (uint8_t)((CFG_ADV_BD_ADDRESS & 0x00FF00000000) >> 32), (uint8_t)((CFG_ADV_BD_ADDRESS & 0xFF0000000000) >> 40) }; static uint8_t bd_addr_udn[BD_ADDR_SIZE_LOCAL]; static const uint8_t BLE_CFG_IR_VALUE[16] = CFG_BLE_IRK; static const uint8_t BLE_CFG_ER_VALUE[16] = CFG_BLE_ERK; tBDAddr SERVER_REMOTE_BDADDR; P2PC_APP_ConnHandle_Not_evt_t handleNotification; PLACE_IN_SECTION("BLE_APP_CONTEXT") static BleApplicationContext_t Bl
Hello,I'm using STM32WB to scan bel beacons, i started from p2p_client example and modified it to scan all types of beacons it shows all close devices, their MAC address and RSSI power, but i want to show more beacons info like beacon name, type, beacon temperture, etc.Can anyone please tell me what to add in my code so that i can get all the beacons information?static void BLE_UserEvtRx( void * pPayload ); static void Ble_Hci_Gap_Gatt_Init(void); static const uint8_t* BleGetBdAddress( void ); void Scan_Request( void ); void APP_BLE_Init( void ) { Ble_Tl_Init( ); UTIL_LPM_SetOffMode(1 << CFG_LPM_APP_BLE, UTIL_LPM_DISABLE); UTIL_SEQ_RegTask( 1<<CFG_TASK_HCI_ASYNCH_EVT_ID, UTIL_SEQ_RFU,hci_user_evt_proc); if (SHCI_C2_BLE_Init( &ble_init_cmd_packet ) != SHCI_Success) { Error_Handler(); } Ble_Hci_Gap_Gatt_Init(); SVCCTL_Init(); BleApplicationContext.Device_Connection_Status = APP_BLE_IDLE; P2PC_APP_Init(); return; } SVCCTL_UserEvtFlowStatus_t SVCCTL_App_Noti
Hey there, i have a problem with the Nucleo STM32WL55 Board, i'm trying to reduce the current of the board in the LoRaWAN_EndNode application. When the uc is running i got something between 160uA, but in the datasheet it says that the typical current in stop2 is ~2uA. I tried it to reduce it with the SMPS. I added the resistor of zero OHM to R33 and the pinheader. I also changed the software the define DCDC_IS_SUPPORTED to zero. In Sys_conf.h i changed the the defines to no debug, trace Level to off. The only changes that are visible are that the current durring sending is raised from 25mA to 40mA. But the stop2 is still between 160-170uA. After i put the Jumper on the VLXSMPS header i got weird current measuring, like in the third picture descripted. Is there something i don't see ? I'm measuring with the X-Nucleo_LPM01A, i put the GND line to GND and the Aref+ to AVDD. Please help me, i don't get any further with it.
Hello,With the Nucleo-WB55 evaluation kit. We plugged in a CODEC to play audio.For this we need an audio player, but we cannot find an audio player provided by ST for the STM32WB55.Can you provide me with a link if there is one?Is it possible to implement an audio player on the STM32WB55?thank you in advance
I have a STM32WB35CEU7A. Vref doesn't provide a pin out, it's tied to Vdda internally. On my PCB Vdda is connected to Vdd. The question is: The ADC will take into account the internal Vref or Vdda ? I suppose the latter please verify. If that is the case can the internal Vref (Vrefbuf) still be read to offset the error from Vdda ?Thanks in advance
I'm working with STM32WL (Nucleo board). I connect it to a sensor via I2C and everything goes fine until I try to call the communication function via Sequencer. Using the Sequencer I get an error from HAL_I2C_Master_Transmit. The error is a timeout from I2C_WaitOnTXISFlagUntilTimeout.
Hello,In SUBGHZ generic pack FSK, how can I configure CRC to ITU-T CRC8 : X8+X2+X+1the only information I have find was in the datasheet of Semtech SX1261/2, and it was just about IBM CRC and CCIT CRC.What about other configurations ?
During debugging of a dual core application everything works fine for the CM4 core debug config and afterwards starting the program. As soon as I try to add the debug config for CM0+ the following error occurs: 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 : 61235 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled Error in initializing ST-LINK device. Reason: ST-LINK: Could not verify ST device! Abort connection.I can reproduce the error using Nucleo-WL55JC1 with example dual core projects, so it is at least not my code. Tried onboard ST-link v3 and external STLINK V3SET.I verified my config following this tutorial.CubeMonitor and CubeProgrammer can connect without any issues.
I took an example code from the CubeWL packet, specifically PingPong, and it works fine out of the box.After than I starded to work on the code to adapt it to my need. Specifically I opened CubeMX and added the I2C periferal. After the code generator finished I noted that the folder arrangement was changed and that I had to redo the coding done before. In this process also code from the example was lost and I had to fix that too.At this point I was able to upload the code to the boards but they showed bad signal transmission.I can't figure out what difference is causing the different performance results, the lora parameters a re basically identical.
I recently bought a NUCLEO-WL55JC1 to try. I ran a very simple Mbed OS6 program (with serial output and an LED flashing), I had previously been running on an F411, which ran fine. I then changed a single variable (ms for LED flashing), and when I attempted to redeploy the modified code, it won't run. I have tried vanilla "blinky" code, and the "mbed-os-example-lorawan", but nothing runs. The STLINK flasher LED flickers green/red, as expected, to indicate a programme flash, but no activity thereafter. I have tried upgrading the firmware to V3.J9.M3, but still no luck. Debugging also will not connect and it "actively refused".Any ideas why this might be happening?Thanks in advance.
Hello,Does anybody know how I can implement SUBGHZ_Phy library:without: HAL library, sequencer, advance trace and debuggerthank you,Sincerely.
Hi, I am using STM32WB55RG microcontroller for my project. I am using BLE as part of my application. I want to disable ( turn off) RF sub system when I am not using. I cant use any low power mode because I have to use 64MHz as CPU1 frequency. I would appreciate any help on this matter.
WATCH ON-DEMAND | STM32 Summit 2026
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.