STM32 MCUs Wireless

Hello.I am trying to do single-channel touch-sensing without using the TSC. For that, I put a weak pull-up on that pin. In a cyclic process, I make the pin OUTPUT-LOW, then release it and measure the rise time through Input Capture. It's a very basic test application, and I have successfully done it on many other controllers including BlueNRG-2. Unfortunately, I am not able to do the same in this.Through various measures, I have confirmed that the user application loses control of the pin as soon as the corresponding timer (associated to the pin for Input Capture) is enabled, no matter what Pin-Timer combination I use.Does anyone have any idea how to bring the control back to the user application with the Input-Capture enabled?Please note, I am configuring the controller and all its peripherals, including the Input-Capture Timer, through the latest version of STM32CubeMX.Any suggestions on how to resolve this is h

I want to use the OpenThread UDP API. So far I implemented the UDP datagram reception without any problems. Sending a datagram using the CLI works fine. When it comes to sending a datagram via the API I always get either OT_ERROR_INVALID_SOURCE_ADDRESS or OT_ERROR_DROP when I call the otUdpSend function.The invalid source address seems to be a problem with the otIp6GetUnicastAddresses and otThreadGetLinkLocalIp6Address functions. Both of them are returning addresses like "::" instead of the Link-Local or other valid addresses. Are those functions correctly implemented?Can someone please provide a fully working example how to send a UDP datagram using the OpenThread API on an STM32WBxx? Thank you very much.Currently used STM32CubeWB is 1.4

Is there any place I can find the source code for OpenOCD bundled with current release of STM32CubeIDE? I'm asking because I think source for this should be provided as it is under GPL, I'm asking since STM32WB is not supported in source available on SF and I want to compile everything from scratch.

Hi, I want to connect my cellphone to a speaker through STM32WB using Bluetooth.

Good morning everyone,I'm coding with Atollic Truestudio and CubeMX.I would like to ask for some helps concerning a function called "arm_bitreversal_32" in the "arm_cfft_f32.c".Here is my problem.I'm trying to use the function "arm_cfft_f32(x,x,x,x)" from the "arm_cfft_f32.c" file. And I got this error in this C file:undefined reference to `arm_bitreversal_32' I'm not sure if some files are missed or I should implement it by myself because the function "arm_bitreversal_32()" is declare externally (extern void arm_bitreversal_32()). I thank everyone who will try to help me to resolve my error.arm_cfft_f32.c":#include "arm_math.h" #include "arm_common_tables.h"   extern void arm_radix8_butterfly_f32( float32_t * pSrc, uint16_t fftLen, const float32_t * pCoef, uint16_t twidCoefModifier);   extern void arm_bitreversal_32( uint32_t * pSrc, const uint16_t bitRevLen, cons

Hi, I have in hand a customer board with a STM32WB55CEU6 MCU. I was able to program CPU1 (M4) firmware but it seem that CPU2 (M0+) didn't have any firmware programmed.I have found that I need to program stm32wb5x_BLE_Stack_fw.bin into CPI2. Did you have a simple procedure to do that?Board only have jtag interface SWCLK, SWDIO line, no uart or USB connector, BOOT0 line is available but NC for now.Any help will be greatly appreciated.Regards,Marc Drouin

We are currently working on STM32WBCC. Let's say my device name is DEVA. Have the following questions:1. DEVA needs any ability to connect to another BLE device DEVB.2. DEVA needs to maintain the lowest possible power when having the connection in tact with DEVB. What power state should my DEVA be in.3. I need to get a theoritical calculation on how much my device would consume in this state, also what would the entire connection cycle look like in terms of current consumption.

can anyone help me out on how to configure these devices and code them. thank you

i have been Using STM32WB55 Nucleo Board , and have successfully implemented BLE examples from repository and its Working fine, but suddenly now my board is not executing any BLE Applications , so i have updated M0 Cortex firmware i.e BLE stack From repository (stm32wb5x_BLE_Stack_fw.bin) in bootloader mode using USB . Still its not working .Also in Debug mode i am able to go into APP_BLE_Init(), which means my BLE get initialized.please help me with the query .Is it in the Firmware or there may be Hardware issue Also?

How i can do it?

Hello,I'm working on a product that integrates Murata's CMWX1ZZABZ-078 to do either LoRa or Sigfox (in different configurations, with different firmwares). I've tested it with ST-provided example applications for LoRa (AT_Slave and PingPong), and it works fine. But using the Sigfox ModemAT example, with its precompiled library objects, it appears I can't emit on the radio.First I've built the software using GCC and GNU Make, with a homemade Makefile and small alterations to the code and linker script. Then I've gotten my hands on an IAR EWARM trial version to build the code as provided by ST.I don't have credentials to access the Sigfox network yet, so I'm testing radio with the command "AT$CW=868". I can see no wave being emitted, and the device seems frozen after the command.I then tried the same steps on my B-L072Z-LRWAN1, and got the same result, except an additional SFX_ERR_INT_GET_DEVICE_INFO on startup (code 0x0099, no m

Is it possible to connect an USB HID to STM32WB Nucleo Board ? Thank you in advice!Stanislav

What's the anticipated availability of this part?

I am currently working on STM32CubeExpansion_LRWAN_V1.3.1 projects. I am using STM32l073 mcu. In End-Node project, the LSE clock is used as RTC source. But I want to use the LSI clock as RTC source instead of LSE. So far I could not be succesful.Could you help me about this issue? How can I implement the LSI clock correctly as RTC source in LRWAN project?

I've been trying to make connection with STM32F0 Discovery and hc-06 bluetooth module via USART2. I've configured Discovery as shown on figure below. Additionally there is an nvic interruption. Hc-06 is configured the same way as Discovery.uint8_t bluetooth_recive = 1; HAL_UART_Receive_IT(&huart2, &bluetooth_recive, 1);I've checked hc-06 if it's passing values sended form app on smartphone. App I was using was Bluetooth terminal HC-05. I was sending ASCII code. Connected hc-06 via usb_uart converterwas passing values to computer's application Realterm.So my question is if there is a configuration problem or something else..

I wonder why are all ACI commands, that imply using pointer-to-const parameters actually use non-const ones? Is there any reason? Will it ever be fixed?For example:tBleStatus aci_gatt_add_service(uint8_t Service_UUID_Type, Service_UUID_t *Service_UUID, uint8_t Service_Type, uint8_t Max_Attribute_Records, uint16_t *Service_Handle) { <...> Osal_MemCpy((void *) &cp0->Service_UUID, (const void *) Service_UUID, size); <...> }

I am running the above mentioned board about 3 meters away from two gateways, a TTIG and a RAK7258. I made two modifications to the stock End Node application - I modified Commissioning.h with the EUI, etc. for one of the gateways (have tried both), and changed the preprocessor define from REGION_EU868 to REGION_US915.I monitor packets on both gateways. After resetting the B-L072Z-LRWAN1 board, it will join whichever gateway I have it configured for, but it takes it anywhere from 2 to 6 attempts. After that the uplink packets appear intermittently on both gateway traces with RSSI values that vary wildly. For some packets, the RSSI is around -28, with an SNR of 8 to 14. These packets show up on both traces. Other packets either never show up, or show up on only one gateway with RSSI around -120 and SNR of -11. Most of the time I am missing 50% or more of the packets. Every once in a while things will straighten up and I receive 100% of the packets for hours.

We were planning to replace our STM32WB55 design with an STM32WB50CG, unfortunately we saw the errata document DM00625356.In particular we need to operate with LSI2 for the Bluetooth and cannot add an LSE crystal.When will there be a silicon revision to STM32WB50 that fixes this issue?

In the linker scripts for BLE_p2pServer_ota in CubeWB1.3.0, the ld script puts the OTA_TAG at 0x08007178:/* Specify the memory areas */ MEMORY { FLASH (rx) : ORIGIN = 0x08007000, LENGTH = 1k RAM1 (xrw) : ORIGIN = 0x20000004, LENGTH = 191k RAM_SHARED (xrw) : ORIGIN = 0x20030000, LENGTH = 10k OTA_TAG (rx) : ORIGIN = 0x08007178 , LENGTH = 599k }However, the BLE_ota example checks a COMPLETELY different address in CheckFwAppValidity:static uint8_t CheckFwAppValidity( void ) { uint8_t status; uint32_t magic_keyword_address; uint32_t last_user_flash_address;   magic_keyword_address = *(uint32_t*)(FLASH_BASE + (CFG_APP_START_SECTOR_INDEX * 0x1000 + 0x140)); last_user_flash_address = (((READ_BIT(FLASH->SFR, FLASH_SFR_SFSA) >> FLASH_SFR_SFSA_Pos) << 12) + FLASH_BASE) - 4; if( (magic_keyword_address < FLASH_BASE) || (magic_keyword_address > last_user_flash_address) ) {In particular the line:

I think I have discovered a bug in the way CubeMX behaves when both SPI and DMA are enabled. I am using the P-NUCLEO-WB55 board. If you look at the SPI_FullDuplex_ComDMA_Master example application, this runs fine on the P-NUCLEO-WB55 with a jumper between MISO and MOSI. However, if you exchange two lines in main.c so that we have:MX_GPIO_Init(); MX_SPI1_Init(); MX_DMA_Init();instead of:MX_GPIO_Init(); MX_DMA_Init(); MX_SPI1_Init();then the example fails. However, this is exactly what CubeMX does if we follow these steps:Create a new project for the P-NUCLEO-WB55-Nucleo (do not initialize peripherals in default mode)Enable SPI1 as full duplex master with SPI1_SCK on PA6Save and generate codeAdd SPI1_RX and SPI1_TX DMA requestsSave and generate codeThe problem does not occur if we don't save and generate code after enabling SPI1, i.e.:

Stack versions: LRWAN_V1.3.0, LRWAN_V1.2.3, LRWAN_V1.2.2Hardware: B-L072Z Murata moduleWe are registering duplicate frames sent by the End Nodes. Doesn't happen frequent: 1% of all frames, may be less.It happens on over all of our LoRa gateways so it doesn’t appear to be related to a specific brand of gateway hardware.

In AN5289, clause 12.4.5, I found, that "Low power feature is not supported". I'm wondering what actually doesn't support low power here: application example for MAC 802.15.4, the wireless stack or neither. Also, if it's the case with the wireless stack, what can be the reason of that: is this feature simply not implemented (yet?) or is it somehow entirely impossible to use low power modes with this stack on this chip?Does anybody know anything about that?

Hello, previously I used the  I-CUBE-LRWAN LoRa v1.2.0 with region AS923 no prob it can join and send data. I dropped in the newer v1.3.1  I-CUBE-LRWAN LoRa with same compile define/same region etc... it cannot join the LORA network (same APPKEY/same DEUI etc...). I can see with debug level 2 that the transmit frequencies are good (923.2/923.4Mhz for Join command), but I cannot get any JOINED return (join success) and the MCU is stuck there. Please anyone had the same issue, any suggestions?

I have a Nucleo Pack with two STM32WB55 discovery boards. One of the boards has a 64 pin micro controller, while the other board is USB dongle with a 48 pin microcontroller.I flashed the binary file from an example project called "BLE_p2pServer" found here onto the 64 pin micro controller using "STM32CubeProgrammer" and the board communicated just fine with an app called "ST BLE Sensor" as suggested in

I have an STM32WB55 Nucleo Pack and I am trying to set it up with my machine (Ubuntu 18.04.3 LTS) to run some sample code.I installed Atolic TrueStudio (version 9.3.0) and downloaded a sample project called "STM32100E-EVAL_USART_IrDA_Transmit". The project builds successfully, but I get the following error when I connect the nucleo device(s) and click on "debug":ST-Link enumeration failed Error in initializing ST-Link device. Reason: (2) ST-Link DLL error.I tried the relevant suggestions in this thread, but to no avail.Meanwhile I installed the STM32CubeProgrammer (version 2.2.1) and the STM32CubeIDE (version 1.1.0), but I got the same error message when I clicked on "debug" with an example pro