STM32 MCUs Wireless

Hello,We are having trouble reading FUS version using STMprogrammer application.0x20030030 always returns 0.The interesting bit, is that SHCI_GetWirelessFwInfo() API does return 1.1.0 as FUS version as expected.FW version is 1.5.0.Its either issue with the documentation (address changed?), or with programmer application.Any ideas?./STM32_Programmer_CLI -c port=SWD mode=UR -r32 0x20030030 1 ------------------------------------------------------------------- STM32CubeProgrammer v2.2.1 -------------------------------------------------------------------   ST-LINK SN : 31FF6B065248393731200143 ST-LINK FW : V2J36S7 Voltage : 1.82V SWD freq : 4000 KHz Connect mode: Under Reset Reset mode : Hardware reset Device ID : 0x495 Device name : STM32WBxx Flash size : 1 MBytes Device type : MCU Device CPU : Cortex-M0+/M4     Reading 32-bit memory content Size : 4 Bytes Address: : 0x20030030   0x20030030 : 00000000

Hello everyone, I am trying to code a program that uses DMA to transfer samples from an external codec through the SAI.The CPU is in Low Power sleep for most of the time between the DMA interruptsAfter each DMA interrupt whether its half-complete or complete, the CPU exists low power sleeps and executes a function on the samples from that the DMA fetched, then it goes to sleep. Unfortunately, the CPU exists low power sleep too fast, and apparently it's not the DMA that wakes it up. in fact, I cant even see anything in the interrupt log that might solve this "phantom interrupt" mystery. These are the main parts of the codeMain while loop: /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { HAL_SuspendTick(); SystemClock_Decrease(); HAL_GPIO_WritePin(GPIOC, GPIO_PIN_10, 1); HAL_PWR_EnterSLEEPMode(PWR_LOWPOWERREGULATOR_ON, PWR_SLEEPENTRY_WFI);   HAL_GPIO_WritePin(GPIOC, GPIO_PIN_10, 0);   HAL_PWREx_DisableLowPowerRunMode(); SystemClock_Config(); HAL_Resu

When I burn BLE_Ota_reference.hex and try to put my app seems that SysTick_Handler() is never called and after a while the PC goes to a strange location at 0x0800433e. This is outside 0x08007000.The application is ok when I link everything at the default address 0x08000000 but when I change to 0x08007000 an put the BLE_Ota_reference.hex it behaves as described in the above line.I attach my linker script. Any help would be appreciated.I tried with two different versions of GCC in Linux just to check if it's something weird with the compiler./* Entry Point */ ENTRY(Reset_Handler)   /* Highest address of the user mode stack */ _estack = 0x20030000; /* end of RAM */ /* Generate a link error if heap and stack don't fit into RAM */ _Min_Heap_Size = 0x400; /* required amount of heap */ _Min_Stack_Size = 0x1000; /* required amount of stack */   /* Specify the memory areas */ MEMORY { FLASH (rx) : ORIGIN = 0x08007000, LENGTH = 484k /*RAM1 (xrw) : ORIGIN = 0x20000004, LENGTH = 191k*/ R

..

Dear My friendsI would like to receive some advise and help. I am developing a medical device that controls with smartphone and I am using STM32WB55 and BLE for comminucation. Today, I found that the Cybersecurity Vulnerabilities in BLE system and SDK from STmicroelectronics was one of them. Please help me or indicate me to someone that can support me. Thanks and regardshttps://www.fda.gov/medical-devices/safety-communications/sweyntooth-cybersecurity-vulnerabilities-may-affect-certain-medical-devices-fda-safety-communication

Hi,I have some problems with the code generation in CubeMX. In the HAL_Init() are three defines checked for enabling or disabling the flash instruction cache, the flash data cache and the prefetch buffer. The default configuration says the following:/* Configure Flash prefetch, Instruction cache, Data cache */ /* Default configuration at reset is: */ /* - Prefetch disabled */ /* - Instruction cache enabled */ /* - Data cache enabled */ #if (INSTRUCTION_CACHE_ENABLE == 0U) __HAL_FLASH_INSTRUCTION_CACHE_DISABLE(); #endif /* INSTRUCTION_CACHE_ENABLE */   #if (DATA_CACHE_ENABLE == 0U) __HAL_FLASH_DATA_CACHE_DISABLE(); #endif /* DATA_CACHE_ENABLE */   #if (PREFETCH_ENABLE != 0U) __HAL_FLASH_PREFETCH_BUFFER_ENABLE(); #endif /* PREFETCH_ENABLE */I have checked this with the preconfiguration inside CubeMX. The default settings are correct. But after generation I can find an activated prefetch buffer in the HAL config file:#define PREFETCH_ENABLE 1U #define INSTRUCTION_CACHE_ENABLE

Hi,I'm missing a .ioc file when using the example applications of the USB dongle from the Nucleo set. Why this is not delivered with the firmware for the STM32WB55?Thanks a lot,Ben

Hello,I'm a student that is currently developing a firmware for a custom board with the STM32WB55CE-MC. I want to communicate with the MC over BT. I have tested my software on the Nucleo-Board where it works fine. When i try the firmware on my custom board, the microcontroller can not be seen in the BLE-Sensor app. While debugging the software, I realized, the MC never leaves the idle-State. I am using STM32CubeIDE for software developement.Has anybody experienced similar problems? Do I need to upload firmware to the RF-Core before I can use the BT-Feature? I have not done this up to now but I also have not done this with the Nucleo board. Thanks in advance for all your answers and kind regards,Florian P

..

I am trying to set a baseline for low power measurements in my own application. To do this, I imported the PWR_STANDBY_RTC example in the STM32Cube_FW_WB_V1.3.0 repository and installed it on the P-NUCLEO-WB55. I then powered the board via 5V_EXT and connected a Keithley DMM6500 across JP2.In this configuration, I measure about 10 mA when LED2 is flashing and about 499 uA when it turns off (should be in standby mode). The latter value is unexpectedly high, which makes me think I'm missing something.Are there additional steps required in order to measure standby current draw correctly with this example running on the P-NUCLEO-WB55?Michael

Hello there! I am debugging the TSC function of the STM32WB55CGU6. I cannot set the TSC function in MubeMX. However, in the official materials, I learned that the TSC function can be supported through the txt file. Refer to the STM32L476G_EVAL board example. Process, and transplanted it to my WB55 project, which uses PB4 (TSCx_TS1_IO_PIN) and PB5 (TSCx_TS1_SAMPLING_PIN), but it always fails to debug, my configuration is: ESD-Resistors: 10 kOhm, Group-Sampling: 22nF Because the pins on the board are limited and the Shield function is not used, but there is no waveform (low level) on both pins (PB4 and PB5) and it does not cause interrupts to trigger. I have adjusted it for a while, no Break a little bit, please give me some help! Thank you very much!

Hello,After playing around with the Nucleo board and wanting to try the simple BLE Beacon example, I believe I somehow got the bootloader stuck.I could enter DFU mode the first time and flash accordingly to the instruction given. However, trying to flash another binary gave the STCubeProgrammer a segfault, and now the device is not recognised anymore and can't seem to be flashed through USB.Is there any way to recover? Possible to rewrite bootloader / FUS through the STLink?Thanks a lot

Hi everyone,Up until now I've been doing FUS upgrades and BLE stack flashing on my WB55 Nucleo through the USB bootloader interface, but given that my final PCB won't have a USB port on it (space restrictions), I've had to start learning how to flash through the SWD instead. Following the instructions in the release notes for the wireless copro binaries, I can run -fwdelete just fine, and I can also successfully upload the BLE stack and run my application after that. My only concern is that when I try doing an FUS upgrade with:STM32_Programmer_CLI.exe -c port=swd mode=UR -ob nSWboot0=0 nboot1=1 nboot0=1 -fwupgrade stm32wb5x_FUS_fw_1_0_2.bin 0x080EC000 firstinstall=0I get the following output:------------------------------------------------------------------- STM32CubeProgrammer v2.4.0 -------------------------------------------------------------------   ST-LINK SN : 066AFF3837334D4E43125539 ST-LINK FW : V2J34M25 Voltage : 3.26V SWD freq : 4000 KHz Connect mode: Under Reset Reset

i am using STEVAL-IDB007V1M and BlueNRG-1 Navigator v3.1.0 but when i flash from Navigator examples it's not working , could you please help me?

Hey guys,now that the problem with the linker table is finally fixes with FW1.3.0 I have encountered another problem:If I create a new project in CubeIDE using the standard pin configuration for the WB55 Nucleo board and start debugging after the init sequence the mcu jumps to the Default_handler (startup_....s).Anybody knows how to fix this?Best regards,Philipp

I created a simple BLE peripheral project by CubeMX with the clock setting below.HSE=32 PLL M=2 N=16 R=8 SYSCLK=32M system clock mux=PLLCLKEverything looks right and even the BLE sniffer receives the advertisement broadcast. However, the cellphone cannot discover the BLE device.Accidentally, i changed the "system clock mux" to HSE from PLL. and the problem resolved. and the problem re-appears after changing back the clock setting. I'm wondering why the PLL clock cannot work eve it has same frequency as HSE. is there any restriction on ble clock?attached the clock initialization code. RCC_OscInitTypeDef RCC_OscInitStruct = {0}; RCC_ClkInitTypeDef RCC_ClkInitStruct = {0}; RCC_PeriphCLKInitTypeDef PeriphClkInitStruct = {0};   /** Configure LSE Drive Capability */ __HAL_RCC_LSEDRIVE_CONFIG(RCC_LSEDRIVE_LOW); /** Configure the main internal regulator output voltage */ __HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE1); /** Initializes the CPU, AHB and APB busses c

Hello everybody.I am using B-L072Z-LRWAN1 to create a LoraWAN node class C. I am using the software STM32CubeExpansion_LRWAN_V1.3.1 . The compiler is Eclipse with the plugin SW4STM32. the version of eclipse is 4.14.0the LoRaWAN region I am using is US915. the project I am testing is "End_Node"I am able to get and receive data from the board. The Since I know the channels I want to use (The channels configure in the Gateway), I want to limit the channels in the End_Node. In this case, allow the board to use only 6 through 23. In the file RegionsUS915.c, in the line 523, is the setting of the default mask. If I set these values:      NvmCtx.ChannelsDefaultMask[0] = 0x0000;        NvmCtx.ChannelsDefaultMask[1] = 0x00FF;       NvmCtx.ChannelsDefaultMask[2] = 0x0000;       NvmCtx.ChannelsDefaultMask[3] = 0x0000;       

I want to use MB1293c (STM32WB55CG) as BLE beacon to broadcast a ibeacon frame continuously at every second.

Hello Geeks!I have dive-in with the STM32WB. I'm designing one product for the health care application I have got the Heart-rate code working with the FreeRTOS. More-over my CubeMX Code is also working with the FreeRTOS (After some modifications at msp file as per the examples provided with FreeRTOS ) My intend is to integrate around 7-8 different healthcare senses with SOC to work with Advertising mode having FreeRTOS Middle waresI have Integrated Heath Thermostat code along with the Heart rate with FreeRTOS api (I have made the changes in hts_app.c as per the hrs_app.c to run task instead of the scheduler) Problem StatementNow the problem is that, when i run the code then HW_TS timer working for the both of the task (I'm just enabling the Hert-rate and Thermostate services form the app) but any time my only one task is able to run (hrs working well, which is stopping as soon as i start the hts services from the app)I have put the breakpoints at HTSAPP_UpdateIntermediateTemperature a

I have made a custom PCB with the Murata CMWX1ZZABZ-091 module. When I try running the LoRa End Node or PingPong example (for LoRa Discovery kit B-L072Z-LRWAN1) , I get "Tx Timeout" on UART. The GPIOs and UART are working fine. How do I solve this?

I am using TrueStudio as my IDE, so had to port the files from the example into a TrueStudio project. After a lot of work i gotten the project to build and run on the p-nucleo wb55. But when i connect to the HRSTM thorugh the ST BLE Sensor app on my phone, the heart rate never updates.. And i have a hunch that the Bluetooth connection disconnects af a short while (~30 s). As if it never registered that it actually had established a connection.I think i have narrowved the problem down to the fact that the HCI thread takes full control of the CPU, as if it was in some sort of deadlock.. But i can't figure out why or if thats even the case.Would be really nice if the example projects were ported to more IDE's such as the stm32CubeIDE. Any ideas, for what is going on in my project?

I just received STM32WB55 Nucleo pack. I'm going through the instructions in Projects/STM32WB_Copro_Wireless_Binaries/Release_Notes.html.All going fine until I get to step 4:0x20030030 : 00050300 : FUSv0.5.3 => Must be updated using STEP 5.Next I run STM32_Programmer_CLI.exe" -c port=usb1 -fwupgrade stm32wb5x_FUS_fw.bin 0x080EC000 firstinstall=0FUS update tries twice and ends with FUS status is FUS_IMAGE_NOT_AUTHENTICError: Firmware not authentic!Googling shows me MANY other people have had this problem, with apparently no resolution from ST. Oh, well I press on and check the FUS:0x20030030 : 01000200 - looking OK.STM32_Programmer_CLI.exe -c port=usb1 -fwupgrade stm32wb5x_BLE_Stack_fw.bin 0x080CB000 firstinstall=1and it ends with Firmware Upgrade SuccessI have the full log I could attach - what is with the "FUS status is FUS_IMAGE_NOT_AUTHENTIC" error ?

Goodday, would you mind advice me pls if this module GPS Development Tools STEVAL-STRKT01 LoRa IoT tracker can work standlone powered with a battery.. i need to track an hobbyists drone and my per car. which program on smartphone or pc can be use?

Hi thereI am currently developing a product and i would like to use either stmb32wb55ce or stm32wb55rgI have done most of the softwaredevlopment on the nucleo board with stm32wb55rg.I am a bit stuck with the analog world on this MCU.I would like to use a 2.5V reference and use ADC.I would like to use the internal 2.5V reference since if I go into standby using RTC to save power and only wake up every 15 minutes or so.I am uncertain as to how VSSA and VREF+ and the VREFBUF should be connected even after going through datasheets.Queations1) I wanted to use STM32wb55ce but according to datasheet VREFBUF is unavailable thus my understanding is i cant use internal 2.5V reference for my adc?2) If i rather use stm32wb55rg I can use vrefbuf and set to 2.5V. IF i do this do i connect Vref+ to VDDA? and ad external 1uF and 100nf cap? Or are they internally connected and i just add 100nF and 1uF to each pin?3) for stm32wb55RG there is no VSSA pin , how is VSSA connected to GND pins? I normally us

how to plugin STM32WB software to stm32CubeMX?