Ask questions and discuss STM32 wireless solutions and their implementation for running Bluetooth LE, Zigbee, LoRaWAN applications.
Most recent activity
Hi allI am trying to test and implement a multicast LoRa network using the STM32WL.I have been going through the thread: https://community.st.com/s/question/0D53W00001JCdeESAT/has-anyone-managed-to-make-a-working-lorawan-multicast-with-stm32wl-if-so-howHowever I am still lost as to the setup of multicast. Our application does not require FOTA, it only requires to decode a broadcast message. In this scenario whether I still need include and define (LmhpRemoteMcastSetup.c). LmHandlerPackageRegister (PACKAGE_ID_REMOTE_MCAST_SETUP, NULL), if so, where in the init of the project should it be called?can the multicast key be be setup directly through the end node API as opposed to MAC command? (it would be fixed/hardcoded in this case)if the MC keys can be set through the API, would it mean that the MC group setup could be done manually, as opposed to MAC commands? is it possible to be part of more than one MC group ?Kind regards Xarion
I am trying to use as little power as possible, I want my board to wake up every 30 seconds or so, check if battery has been sufficiently charged, if not, go back to sleep, if it has then turn off rtc and do a function. Is it possible to disable rtc whilst running?
Hi Team,I'm using STM32WLE5 MUC for Lora communication (SubGHz_Phy), I want to know is there a way to use Systick instead of timer ?This is because I used RTC to some other use case. kindly share me the way for the same.Thanks,
..
In STM32WB55 the LSF must be 32KHz or it can be others like 42KHz etc. as well? Thanks.
I want to know maximun number of pairing device information can the STM32WB save.Is regard to device's flash capacity?
Kind folks,STM32Cube IDE newbie here, so please forgive the simple questions.Context:I'm trying to create a multi-vendor testbed and diagnostic environment for Matter networks. In the case of ST Micro products, the thought occurs that the two Thread-capable boards in the P-NUCLEO-WB55 pack could form a minimal Thread network, just chatting back and forth between themselves to provide some RF traffic. Idea is to use the demo Thread_FTD_Coap_Multicast application from the STM32CubeWB firmware (v 1.5.0) sample projects, modified to send a packet to its twin based on a timer (instead of user button input).Questions:Is this a good approach? Can you suggest a better one?The firmware library provides STMCube IDE projects for both boards, under folders labeled P-NUCLEO-WB55.Nucleo and P-NUCLEO-WB55.USBDongle.The former contains an .ioc configuration project, loads and builds easily in the IDE. Can be written to the board's flash from the IDE or the STM32CubeProgrammer. So far so good.But the f
Is it possible to create a project in CubeMX for a concurrent BLE & Thread application for the STM32WB55?My attempts so far only allow for either a BLE or a Thread project (not both together).Thanks
When I create a new project using STM32CubeMX with my board (NUCLEO-WL55JC1), neither defines for PIN labels will be generated in main.h nor is there a BSP folder in the Drivers folder with a xxxnucleo.h containing definitions as I have seen in the examples. I have tried with another board configuration (NUCLEO-C031C6) where label defines were populated in main.h as expected....
Hello,I am trying NUCLEO-WB55RG Matter device over thread example with apple home pod mini (support thread border router and matter) but it fails to commission and connect.I have already flashed "STM32WB_Copro_Wireless_Binaries/STM32WB5x/stm32wb5x_BLE_Thread_ForMatter_fw.bin" on board from repository.Below are versions and git repo I am using.IOS 16.3.1 , iPhone XSGitHub - GitHub - stm32-hotspot/stm32wb-matter-device-over-thread: Matter device over thread for STM32WBI am able to scan QR code and finish all process but at last iPhone shows "Unable to add accessory."I am attaching logs from Nucelo board here. Please letme know if you need anything to help on this.Thank you
While reverse engineering a demo application from ST / Seeed ( Seeed-Studio/LoRaWan-E5-Node at qian (github.com)), I started monitoring all commands and register access from the MCU to the embedded SX126.I see there are writes to register:WR [08E2]:0CWR [08E5]:20Those registers are not mentioned in the datasheet from Semtech, nor the STM32WLE5 datasheet from ST…What is the purpose of those registers ?Why is the SW writing those values ?Why is this not in the datasheet ???
Ive seen this issue in various different forms over the last 2 years and it seems like CPU2 is corrupting the TL_RefTable structure while configuring advertising. We are using v1.15.0 of the stack on a STM32WB55. This happens every few hours in the following sequence.aci_gap_set_non_discoverable(); // Wait 40 seconds aci_hal_set_tx_power_level(1, powLevel); aci_gap_set_discoverable(ADV_IND, RateMin, RateMax, addrType, NO_WHITE_LIST_USE, 0, NULL, 0, NULL, 0, 0); aci_gap_update_adv_data(Manufacturing specific type) aci_gap_update_adv_data(Name) aci_gap_delete_ad_type(AD_TYPE_TX_POWER_LEVEL) // Wait 20 secondsThen the sequence repeats over and over until we get a connection. If I just let it run (over night for example) TL_RefTable gets corrupted and triggers an MPU fault on the next advertising sequence. Why is this happening? What can I do to stop it?
Hi! I have a peripheral that callsaci_gap_terminate(BleApplicationContext.BleApplicationContext_legacy.connectionHandle, HCI_AUTHENTICATION_FAILURE_ERR_CODE)aci_gap_terminate(BleApplicationContext.BleApplicationContext_legacy.connectionHandle, HCI_AUTHENTICATION_FAILURE_ERR_CODE)itself it receives the HCI_CONNECTION_TERMINATED_BY_LOCAL_HOST_ERR_CODE reason in disconnect which I guess makes sense.But the central that it disconnects from will always receive the HCI_REMOTE_USER_TERMINATED_CONNECTION_ERR_CODE 0x13 case HCI_DISCONNECTION_COMPLETE_EVT_CODE: { /* USER CODE BEGIN EVT_DISCONN_COMPLETE */ cc = (hci_disconnection_complete_event_rp0 *) event_pckt->data; /* USER CODE END EVT_DISCONN_COMPLETE */ handleNotification.Reason = cc->Reason; APP_DBG_MSG("\r\n\r** DISCONNECTION EVENT WITH SERVER reason: %x status: %x \n\r", cc->Reason, cc->Status); }Reason will always be 0x13 and status 0x00The devices are flashed with the latest ble binariesstm32wb1x_BLE_Stack_full
The new STM32WBA series comes to complete the STM32 Wireless MCUs portfolio. The STM32WBA series is brings designers the performance, efficiency, and security required for Bluetooth® Low Energy 5.3-enabled applications. Certified for Bluetooth® Low Energy 5.3 protocol, this product series allows non-expert developers to easily add wireless communication to their device, at an affordable cost. Based on the Arm® Cortex®-M33 core featuring TrustZone® technology, the STM32WBA series provides a high level of security, protecting data, customer IP, keys and preventing hacks or device cloning. The STM32WBA wireless MCU embeds 1 Mbyte of Flash memory and 128 Kbytes of RAM. Leveraging the STM32U5 architecture, the STM32WBA series offers the same digital and analog peripherals, suitable for many applications, from industrial, to smart home and consumer markets. STM32WBA enabling features · Support for latest protocol · En
Can you point me to any wireless module out there (WiFi, Bluetooth, Zigbee, whatever).Requirements:Has easy integration with any stm32 MCU with examples in STM32CubeIDE and preferably some community support. I need the chosen protocol to offer certificated industrial gateways with the capability to communicate to an MQTT Broker.I would love the protocol to be WiFi but since ST doesn't support it officially, this way is pretty much burned.Looking forward to your replyGeorge
I have NUCLEO-WB%55RG the VREF+ and VDDA are connected together. Can I use the 2.5V internal VREF for the ADC please?
I am working with an older version of CubeMx 6.4.0 with a STM32WB55 for a legacy project. We are trying to avoid upgrading CubeMX if we can. I am looking at the Battery Charging option in the USB settings under connectivity. When I enable the option, it generates code that does not link with my existing code. Even if I tweak the generated code to compile by commenting out the empty function that is causing a linker error, it does not appear that there is anything in the code calling HAL_PCDEx_BCD_VBUSDetect. Is there something else that needs to be configured in CubeMX for this option to work properly, or is this something I need to upgrade to a newer version of CubeMX to fix?
Hello, I'm using the SubGhz_Phy_PingPong example to transfer data via Lora from a NUCLEO stm32WL to another, but I can't figure out how I can send a data array in the main.c file to the other board.Following the example, it has the main calling the MX_SubGHz_Phy_Process() function, that's in the app_subghz_phy.c file. However, the code that occurs the transaction between boards is in the subghz_phy_app.c, in the PingPong_Process() function.How do I take the array that I want from main, and send it all the way to that last function to send it?
I am trying to use the WL55 with a legacy 2-gfsk system that relies on CC1120 chip. The major issue here is related to de-whitening of the received data. I am editing the subghz ping pong example. Band, AWG and datarate are coherent with the legacy system, but the data I receive is waaaaay too long compared to the expected (and transmitted) one. First issue: I'd like to receive all the data over the air, preamble and sync word included. I am not sure I am receiving it because the data does not look like the sync word (that is 0xAA in the CC1120 and 0x55 on the WL55). I am relying on the variable-length packet format BTW.Second issue: in Variable length packet format the whitening is applied both in tx and rx ALSO to the legth byte hence the data I receive is arbitrarly long. Third issue: the PN9 algorythm in CC1120 and in WL55 are different, something related to IBM vs CCITT, hence the only solution I can figure is to receive whitened packets and de-white them in software. I don't thin
I am checking the below example code given in RAK3172 low level development folder.C:\en.stm32cubewl\STM32Cube_FW_WL_V1.0.0\Projects\NUCLEO-WL55JC\Examples_LL\LPUART\LPUART_WakeUpFromStop_InitThe only change I made here is for LED2 , GPIO pin changed from 9 to 6.(In RAK3172 evaluation board,LED2 connected from 6th pin)But,LED2 is not litting as excepted.Kindly advise me in this regard.
I cannot get the Phy_802_15_4_Cli example project working on our custom board (as part of certification). Seems like there is something wrong with the CM0 / CPU2 core, but I have no idea what the return codes mean.Only things I have changed in the example project are:UART parametersUsing LPUART1 as CLI interface insteadEnabled the relevant clocksCFG_DEBUG_TRACE = 0 CFG_FULL_LOW_POWER = 0CFG_LPM_SUPPORTED = 0CFG_LED_SUPPORTED = 0CFG_BUTTON_SUPPORTED = 0Changed the various GPIO pin mappingsGPIO_TX_PINGPIO_HARD_FAULT_PINGPIO_MCO_PINI need to get this to work with CubeMonitorRF, but it is also running into the same issues.================================= (STM32WB55) RF 802_15_4 LLDs test ================================= Trace is de-activated M0 FW Type : 802.15.4 and radio PHY validation CLI (v1.16.0) for Target WB55 802.15.4 driver version : v2.2.0 HW/system info : CUT 2.1 - Dev ID 0x00000495 - Package info 0x0A - UID64 0x0186C461 0x0080E126 802.15.4 valid cli > InitLLD Execute co
One of the biggest offenders is shown in the image below. All of the USB device types from usbd_def.h are not getting recognized by the compiler, even though usbd_def.h is in the include list at the top of the file in this image, and I can control-click to any of these structure definitions to go right to the defnition in usbd_def.h. I'm stumped about how to fix this. I have tried refresh, clean project and restart the IDE.
Hello, to get a lower power consumption in my application i would like to go in stop mode 2 and wake up shortly to receive some characters on the LPUART. But unfortunately my mcu does not wake up. I can see with the debugger that the send Byte is in the DR of the LPUART and after leaving the stop mode I also end up in the LPUART_ISR. It seems to me that I forget something or do something wrong. Therefore I am looking for help here.Currently I set the following registers before entering stop mode 2in LPUART1->CR1 USART_CR1_UESM in LPUART1->CR3 USART_CR3_WUFIEin LPUART1->ICR USART_CR3_WUCFLSE is running and propagated and selected for LPART1 by 9600 Baud
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.