Dear all, The X-CUBE-MATTER Expansion Package is now available on our official website following this link MATTER - Matter software expansion for STM32Cube - STMicroelectronics It is a reference implementation for the demonstration of Matter on ST...
Please go and visit our wiki pages where you can find a lot of information on our wireless product families (WB, WBA, WL) and the supported protocols: BLE, Zigbee, Thread, Matter, Lora, ... To begin your technical journey, please start from this top ...
"The I-CUBE-LRWAN Expansion Package consists of a set of libraries and application examples for STM32L0, STM32L1 and STM32L4 Series microcontrollers acting as end-devices."Can i use the libraries comming with this package even if i am using a STM32F7...
How to do Programming in cmwx12zzabz-078 Lora module..?Im new for STM32 controller. I purchased cmwx12zzabz-078 Lora module which is integration of STM32L082 and SX1276 module. when i connect this module its showing in device manages as "STM device ...
And description of the scheduler used in application of "Cable Replacement"
Is there some kind of example of using stm32WB in the same way as HM-10 BLE. I need to communicate between controller and mobile phone. The simplest solution seems to be serial communication. Maybe someone have any example How to read and write valu...
It looks like ST only provides bin file to controls Radio, even reference manual also doesn't mention too much on the Radio system. I am wondering if there is any way to log all PHY payload of a PAN coordinator? Does anybody have experience on this?T...
Hi Team,We are using STM32L072 Discovery kit LoRa module for reading CCS811 sensor over I2C peropheral. The Hardware Id (Deivce id) of the sensor is not able to read as the data line does not contain ACK signal at the end. We are using HAL_I2C_Master...
B-L072Z-LRWAN1 discovery kitMTCAP Multitech conduit I-CUBE-LRWAN end-node sample code
I am facing a challenge with the System event response codes. Digging into the FW I find the FW is looking for the status in the wrong part of CPU2's SystemCmdBuffer. It seems CPU2 respects the 8 byte header, whereas FW (with comments) says the evtse...