STM32 MCUs Wireless

Hello,We are evaluating LoRa module from Murata which is having STM32L0x2 MCU in it.We would like to understand if there is any specified range limit for device identifier values read from unique device ID registers of STM32L0x2.

For baremetal coding

Hi I am testing SysTick with STM32WL55.I set the IOC file as follows.​When a break point is set in HAL_IncTick() in SysTick_Handler() and the program is executed in debug mode, the program does not stop here.In other words, the SysTick_Handler() function is not executed.​Are there any other additional settings required?How can I resolve it?​​​

Hi.I am using STM32WL55 for FSK communication.Firmware version is STM32Cube_FW_WL_V1.3.0.In the past, version 1.1.0 was used, but version 1.3.0 has changed a lot.So I'm not sure how to set it up.​​First of all, I want to set SUBGHZ_PHY, but the Enable check box is disabled as follows.And files related to SUBGHZ_PHY and Radio are not visible after [Generate Code].Could you let me know why it is disabled and how I can use it?​Please give me a procedure or method on how to set up and use FSK.​Thank you.​​

basically I'm working with a LoRaWan card that mounts your STM32WLE5CCU6 microcontroller.the problem arises from the high consumption of my product.I'm trying to program the PA8 pin of the microcontroller as an input that is always under VDD and I've soldered a 470K resistor upstream of the pin to reduce the circuit consumption as much as possible.but with this resistance the pin no longer relays the current.in practice this pin is connected to a switch (TX_ON_EVENT) can you help me or tell me someone who can help me solve the problemswitch NC and when it's Open TX_ON_EVENT

Hello, we want to use the STM32WLE55 MCU in the AI50H Module to build a Node to Node connection in a LoRa Network.So i used the STM32CubeMX Program to build an easy solution that includes only "UART", "SUBGHZ" and "SUBGHZ_PHY" modules. Goal is that i send a sensor value per UART and the STM32 sends this data over Lora.So i have several problems:STM32CubeMX told me to change the linker file because "subghz_phy" is active? what is there to change?i have (in the fresh generated file) several errors after building.. "<file_path>: Invalid Argument" and "fatal error: no input files"can someone help me what i am doing wrong? Sorry for providing not that much information, this is a totally new created project.

..

..

STM32WB5MMG�?�STMicro�?�ら�??供�?�れるLibrary,Driver,FUS_fw,BLE_Stack_full_fw,BLE_Otaを利用�?��?��?カスタムプロファイル�?�BLEを�?�載�?��?�製�?を開発�?��?��?��?��?�。�?�れを販売�?�る�?��?�?Bluetooth SIG�?証を�?��?��?��?��?�考�?��?��?��?��?�。QDID170767,160724�?�該当�?�る�?��?�?れ�?��?��?��?プロファイル サブシステム QDID 122688�?�カスタムプロファイル�?��?��?��?�も該当�?�る�?��?��?��?�分�?�り�?��?�ん。教�?��?��??�?��?��?�。

Hi everyone,I use the  STM32CubeIDE 1.6.0 and the STM32WL package 1.0.0I am trying to implement the clock synchronization feature but I cannot get the application to be built.I enabled the with the following definition#define LORAWAN_DATA_DISTRIB_MGT 1 in lorawan_conf.hBut while building the project it returns undefined reference of two functions defined in LmhpDataDistribution.hI tried to clean and build again but it doesn't workBoth files (LmhpDataDistribution.h and LmhpDataDistribution.c) are included in the project. Do I miss something?  

But we need to increase the memory for CM4, so we modified the files STM32WL55CCUX_FLASH.ld:CM0PLUSFLASH (rx) : ORIGIN = 0x08030000, LENGTH = 64KCM4FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 192KUnfortunately, it stopped working with this definition. Apparently something else needs to be adjusted or what are we doing wrong?

How can I wake up the B-L072Z-LRWAN1 STM32L072CZ PA0 pin when I want to measure the begin and end of a movement plus gathering measurements from the FIFO after one or several FIFO watermark interrupts?Ideally I want to let the STM32 go back into low power mode and let the begin/end of movement and any FIFO watermark interrupt wake up the STM32. There is no reason to not go back to lop power mode when the accelerometer gathers data for several seconds.The problem is that there is only one external wakeup pin on the STM32L072CZ which is PA0 while I want to wake up the STM32 for two different interrupts.I am sure that this is not the first time that something like this is required. There might be a solution already documented or answered before but for now I can't find them.Thanks in advance

Hi, I just found this in the guide (image)

..

I have interesting problem.Custom PCB as master role using SDK 1.15.0.Trying bonding procedure, I find an situatiotion where after ACI_GAP_PAIRING_COMPLETE_VSEVT_CODE event, waiting 100ms (as in "BLE_HeartRateFreeRTOS_ANCS" example) (Ithink it is a mistake or error using that algorithm) and starting disconnect operation calling "aci_gap_terminate()" - the FW freeze and I newer receive an "HCI_DISCONNECTION_COMPLETE_EVT_CODE" event.This log of bonding proc with trying disconnect after ACI_GAP_PAIRING_COMPLETE_VSEVT_CODE like in "BLE_HeartRateFreeRTOS_ANCS" example :-------------------------------------------------------------------------------SCAN START: 1 use white_list: 0 result: 0CONNECT BEGIN: 0 HCI_VENDOR: 0407HCI_LE_META: 0001CONNECTION_COMPLETE wit peer: 0000Bonded=0 SMode=1 SLevel 1HCI_VENDOR: 0C03HCI_LE_META: 0007HCI_VENDOR: 0C03HCI_VENDOR: 0C10HCI_ENCRYPTION_CHANGE: enabled: 0001 status: 0000HCI_VENDOR: 0802HCI_LE_META: 0003HCI_VENDOR: 0401ACI_GAP_PAIRING_COMPLETE: 0000 0

I'm trying to check the dependence of BLE data rate with respect to distance from the board. I runned the BLE_DataThroughput example but I'm having a hard time to interpret the info on the gatt_server terminal (I'm using a nucleo board with a smartphone).1) here I sent the word hello** data error ** N= 4 DataThroughput = 5 bytes/s lost = 116762973 what does lost = 116762973 mean?2) I expected to see a roughly constant value of bytes/s (and higher of course) but it seems that the software just counts out the amount of characters that I send from the smartphone. DataThroughput = 22 bytes/s lost = 0 DataThroughput = 70 bytes/s lost = 0 in this case https://community.st.com/s/question/0D53W00000ElwrQSAR/stm32wb-data-throughput-issues someone got higher throughputs.How to understand this behavior? Thanks in advance.

Beside the MB1791 BOM doubt, there is PCB Layer Stack doubt too.About MB1791 PCB & Gerber Files, there is no Signal copper layout in the Middle Layer-1 (G1 Layer) & Middle Layer-2 (G2 Layer). Why the setting applied 4-layers PCB instead of 2-layers PCB ? Info referring --> STM32WL55CC - Sub-GHz Wireless Microcontrollers. Dual-core Arm Cortex-M4/M0+ @48 MHz with 256 Kbytes of Flash memory, 64 Kbytes of SRAM. LoRa, (G)FSK, (G)MSK, BPSK modulations. AES 256-bit. Multiprotocol System-on-Chip. - STMicroelectronicsPls advise.

Hello all....New to the STM32WL world and trying to understand some things:Could someone point me to the appropriate applications, within the STM32WL Library package framework, for creating a remote control hub that could send a user defined packet structure to various nodes (network would be either simplex or half duplex (call / response)? (I want to use the LoRa phy but not have the restrictions of the LoRaWan protocol as this is a self contained intranet ---- no internet required)Thank you

Hello I bought the P-NUCLEO-LRWAN3 developer board to use as a gateway for lorawan.Only to realise that its meant for 433MHz, and I need 868MHz.As far as can see there is little difference between the 2 versions.Its the same PCB, so I was wondering if I could modify the LRWAN_GS_LF1 to become a LRWAN_GS_HF1.I would just buy the P-NUCLEO-LRWAN2 but its sold out everywhere.Morten, Denmark

The WL product has been around for a while now and I still only see one FCC approved RF module (Seeed )......I had heard that ST was going to produce an FCC module with the WL55 product. Can anyone from ST validate any truth to this and comment on the time frame that we can expect a SoM? I am surprised, that only Seeed has produced modules for sale at this point. Thank you

..

Hi,Now I am working on I2C sensor (BH1750 sensor) integration with LoRaWAN base firmware(STM32cube_FW_WL_V1.0.0) in RAK module. The controller specification is STM32WLE5JCI had configured the I2C peripheral initialization as mentioned below document.I had configured the I2C sensor data reading function(I2C transmit & receive) as mentioned below document.While I am integrating, I am getting my I2C sensor's data(BH1750's LUX value) by calling the I2C data reading function after the immediate initialization of I2C peripheral.That means, it needs I2C peripheral initialization for every I2C data reading function while integrating I2C with LoRaWAN Stack.But in Embedded program, without LoRaWAN stack, I2C peripheral integration with the RAK module is working fine with the same I2C configuration.I have attached the I2C configuration details & What are all the changes I did for this I2C integration in the below mentioned document.Kindly, Do find the attachment and go-through it once.Kin

Hi All, I am evaluating the usage of the WL55 on a legacy system. Our legacy system is a 2-gfsk with whitening; it relies on 0xAAAAAA preamble frame, but it is detected as 0x555555 by the semtech submodule. This leads to a shift in the sync word and the following payload. Is there a way to change the preamble frame word? K.R.Luca.

Hi Team,I'm facing some trap in the STM32WLE5 device during RTC init, some time RTC initialization works, some time it hangs in generated function "HAL_RTC_MspInit()" during HAL_NVIC_EnableIRQ(RTC_Alarm_IRQn). if any one faced this issue kindly let me know tow it was resolved.Thanks in Advance.

Hi everyone,​EDIT: This is on the NUCLEO-WB55RG development boardWas using the board last week without any problems. Started using it this morning and the board boots up, but it cannot connect to the computer to dump code. The chip under the removable shield (I'm not sure whether its the M0 or the M4 chip, I think its the M4) is getting very hot.​All the components/soldering/traces look fine so I'm leaning towards internal failure of the chip under the shield. Is there any way I can verify whether this board is broken for good?​The LED boot sequence is different (I have two boards), the working board boots as follows:Plug USB in via computer - board powers onLED 6 turns red ONLED 5 turns ONProgram starts and all is fineHowever, the suspicious board boots like so:Plug USB in via computer - board powers onLED 6 turns red ONLEDs 4 & 5 flash on then off x2LED 6 turns red OFF and green ONLED 6 turns green OFF and red ONLEDs 4 & 5 turns ONMCU under shield becomes very hot and cannot