Product forums

Hello, I use STM32WB05KZ. Could you give me an example about how to store configuration data to NVM by aci_hal_write_config_data() function? - When I tried to store to 0x00 (I used static randow MAC address), it returns 0 but the data is lost when the chip is rebooted; - When I save to any other address (such as, 0x40), it always returns to 0x12. Thanks a lot.  

I have questions regarding estimated_reflectance and range_sigma in VL53L5 and L8The reflectance: how is it calculated? Is it R=signal_rate_per_spads*depth^2/K? the number_of sapds_enabled seems a useless parameter for a user? Can we know this calibrated constant K?The ambient_light has nothing to do with the R calculation?For these multi zone TOF, if we place a flat target in front of TOF, it shall give the same R. ST’ already does the internal compensation for the depth and for the angle of incidence. Right??  I can not find this kind of info in ST’s doc. Can only guess. If it has, please point out the Docs sourceThe range_sigma: for L5, if the resolution is 4 x 4, the readout is zero. I can read out  this parameter if it is 8 x8What is the default sigma_threshold for distance in L5? Is it the same for resolution  8x8 and 4 x4? Also, when I change this threshold, it is unclear if this threshold, e.g.,100mm shall multiply with a scale factor 128. Please confirm thatThan

Hello,Before compilation:   I’m having an issue with IntelliSense (possibly clangd).When a macro is undefined, the code inside #ifdef is correctly shown as inactive (dimmed). However, after I build and flash the project, the same code becomes highlighted as if it were active, even though the macro mDEBUG is still not defined.The highlighting only returns to the correct state after I switch tabs or force a refresh.Is this expected behavior, or could this be a bug or bad config on my side? It brings confusion to my workflow.After compilation: 

I'm using the library here: https://github.com/stm32duino/VL53L1, and it seems to stop measuring around 3.2-3.5 meters. I may be wrong, but think that means that it is not using the histogram? I set it to long distance ranging mode.Here is my code:bool Sensor::ConfigureSensor(TOF &tofSensor) { Log.noticeln("Configuring [%s]", tofSensor.name); if (tofSensor.sensor_object == nullptr) { Log.fatal("No TOF sensor object initialized."); return false; } VL53L1_Error status; status = tofSensor.sensor_object->InitSensor(tofSensor.address); delay(10); if (status != VL53L1_ERROR_NONE) { Log.fatal("Failed to initialize %s. Status: %d. Halting.", tofSensor.name, status); while (1){;} return false; } Log.noticeln("%s address set to 0x%x", tofSensor.name, tofSensor.address); status = tofSensor.sensor_object->VL53L1_SetPresetMode(VL53L1_PRESETMODE_RANGING); delay(10); if (status != VL53L1_ERROR_NONE) { Log.errorln("Failed to set preset mode for %s", tofSen

Hello, I am using this sensor for a project where it is mounted on a cane to detect overhanging objects that could hit visually impaired people. This works fine indoors, but outdoors, when the ambient light is around or greater than 10k Lux—and keeping in mind the sensor is pointed upwards and hit directly by sunlight—it only catches obstacles when they are very close. I am currently using a 4x4 resolution with continuous ranging at 30Hz. My question is: is there a way to increase its efficiency? By efficiency, I mean increasing the detection distance through hardware, structural, or software solutions.

Hello, I have started evaluation of X-NUCLEO-ESE02A1 shield with NUCLEO-F401RE board, and used STM32CubeMX for project generation according to PDF inside X-CUBE-SAFEA1 package. However, I can't get any demo running, and both these generated demos, as well as my attempt, fail with error code 0x01 which maps to STSAFEA_COMMUNICATION_ERROR. I have tried putting jumpers for I2C lines pullup on the shield, jumpers P4 and P5, but it did not help. Then I read in the product User manual UM3579 about additional RST PIN so I tried also putting a jumper on P3 connector but still nothing. However then I traced it to PB5/D4 PIN which is actually not used and not advised to be initialized in the Getting started document. So my question is: Do I need to use this pin, and if so, how exactly should it be used, to enable communication with STSAFEA110? Everything other, related to I2C, USART, expansion package itself is enabled, project compiles and app shows logs after flashing to Nucleo,

Hello everyone,I'm working with an STM32L562E-DK board and testing the "TrustZoneEnabled" template included in the "STM32Cube_FW_L5_V1.6.0" package. The goal is to run the basic example that transitions from the secure to the unsecured zone, but I'm finding that, after following all the instructions in "README.txt" and compiling the project, the code gets stuck in the next function:static void NonSecure_Init(void) { funcptr_NS NonSecure_ResetHandler; SCB_NS->VTOR = VTOR_TABLE_NS_START_ADDR; /* Set non-secure main stack (MSP_NS) */ __TZ_set_MSP_NS((*(uint32_t *)VTOR_TABLE_NS_START_ADDR)); /* Get non-secure reset handler */ NonSecure_ResetHandler = (funcptr_NS)(*((uint32_t *)((VTOR_TABLE_NS_START_ADDR) + 4U))); /* Start non-secure state software application */ NonSecure_ResetHandler(); } Specifically on the "NonSecure_ResetHandler()"; or it doesn't even execute the no-secure part.Current option bytes configuration (verified with STM32CubeProgrammer):DBANK => Checke

Hi,I just installed STM32CubeProgrammer v2.17.0 on Linux.When I connect to the board (tried with several different ones), I get the following error;flash loader cannot be loaded. FlashLoaderPath = /home/[yadayada]/bin/FlashLoader/0xI can read the flash, I can do everything, with the exception of flashing. This fails.I first thought it might be a truncated log message. But when I just copied any of the loader files and gave it the file name "0x", I didn't get the error message. So it really looks for a file named "0x". It looks like in the code, the assembly of the file name (all the files match the pattern 0x*.stldr) I tried to do an software update, but this also fails: "The updater package on server is corrupted"  

Hello,just updated to STM32Cube FW_H7 V 1.13.0 but it seems it still contains CMSIS RTOS2 V2.1.3.I'm develop with Keil and STM32 IDE but Keil is using V2.3.1 while Cube comes with V2.1.3.In STM32 IDE I got a compile error when I imported source code developed on Keil.E.g. the thread attribute osThreadUnprivileged, introduced in V2.2.0, is missing in V2.1.3.https://arm-software.github.io/CMSIS_6/main/RTOS2/rtos_revisionHistory.html Any progress here? If no, why?Thanks,Jochen    

I want to add a EXTI0 line to act as a wakeup. I took the BLE_Heartrate example as a base. Out tyhe box, it compiles & runs ok. When I use CubeMX 6.16 to edit the BLE_Heartrate ioc to add PE0 as the EXTI0, next time I compile, I get an error that I'm missing stm32wbaxx_ll_utils.c. If I "cure" this by copying the file from elsewhere, I get other file-not-found errors on stm32wbaxx_ResetHandler_GCC.s and app_bsp.c. What gives? Surely the example provided by ST should be able to handle a minor change in the ioc file? The BLE_Heartrate and other BLE_ examples are inpenetrable and difficult to understand at the best of times. ST is not helping anybody by not explaining how the BLE_Heartrate example may be modified to get e.g. true low power stop2, how to set an RTC alarm to wake up from this.

 Hello,I am encountering an issue with the ST example projects "BLE_p2pServer" and "BLE_DataThroughput_Server" for the NUCLEO-WBA65RI board.After generating the code using STM32CubeMX (version 6.17), the project does not include all the required source files. As a result, the compilation fails immediately, even before making any modifications to the code.I enabled the option:"Generate peripheral initialization as a pair of '.c/.h' files per peripheral".The main issue is that the following file is missing:"stm32wbaxx_ll_utils.c" .It seems that some HAL/LL driver files are not being generated or included properly in the project.Could you please advise on:Whether this is a known issue with STM32CubeMX 6.17?If there is an additional step required to include all necessary driver files?Or if a specific configuration is needed for these BLE examples?Thank you in advance for your help.Best regards,Pierre A

Hi,During the design with the STM32H743IIK6 MCU few questions arise:(1)  While designing a PCB with the STM32H743IIK6 (UFBGA176+25 package) with VDD=3.3V or 2.8V, I am unable to locate the VCCLDO pin, which is expected to be connected to external capacitor. Am i missing something in the pinout, or does the internal LDO in this specific package rely solely on the capacitors on the VCAP pins?(2) There are two sets of QUADSPI I/O sets: BK1 and BK2 (i intend to use the BK2). However, I do not see any separate clock pins for each. Do both channels share the same QUADSPI_CLK signal for both banks?(3) Regarding the USB interface: I see a VDD33USB pin, but there is no VDD5USB pin. Does this require an external 3.3V DC input, or is it an internal signal output that only requires a decoupling capacitor?Additionally, I am unable to locate the USB_DP and USB_DM pins on the UFBGA176 package. Is there specific hardware documentation / example schema that clarifies the physical lo

I have this Riverdi 7-inch display which has a STM32H757XIH6 micro controller.  And I am trying to use freertos to run a uart task when a button is tapped on the display.  I am running into an issue though with the button response.  So I created a virtual function and that works when I tap the button.  I created another freertos kernal and have a callback function names UART_Task.  I am trying to send a message via a queue to start a process when a button is tapped.  When the program runs the GUI displays, but when I tap the button it is unresponsive and does not seem to send the message.  I messed around with setting different times on the osDelay within the callback to give the GUI and other tasks time to initialize.  I also messed around with the priority of the task as well. No luck though.  Here is the Freertos code that is initialized from the main.c. The MX_FREERTOS_Init() is called in the main.c/* USER CODE BEGIN Heade

Hi,I am using STM32G0 with STM32 Motor Control SDK. ADC1 is used for motor current sensing (triggered by TIM1 for FOC control).Since STM32G0 has only one ADC and does not support injected channels, I needed to read an additional NTC sensor (ADC channel 8) for motor stator temperature.I implemented this using Regular Conversion Manager (RCM):Registered ADC channel using RCM_RegisterRegConv()Requested conversion periodically (~300 ms)Read the value after conversion completionThe motor is running stable, and I am able to get temperature readings without visible disturbance.My question:Is this a correct and recommended approach for reading an additional analog signal in STM32G0 + MCSDK?Are there any potential risks (timing issues, FOC accuracy impact) when using RCM alongside motor control?Or is there a better recommended method for this use case (e.g., external ADC, different MCU, or MCSDK-specific approach)?Thank you.

Heyho, wanted to check if C5 might be good for next project and have a first look at MX2. Installed it, started project with C562 / Nucleo - and nothing happens, except for a short error message in the bottom right corner of the window: "error when downloading packs" ( + some file name). Further info: - Windows 11 - started MX2 first as normal user, then as admin, same behaviour - all other STM32 tools running fine (MX1, IDE, Prog)

hello ST Community,Is it possible to generate a binary file that is a *.elf file from a project developed by STM32CubeIDE?Using the correct settings for generating *.bin files.The *.bin file would be used to create a bootloader via UART for one of the STM32 microcontrollers.Thanks for your valuable support.  

We have a custom board with an STM32MP151A and STPMIC1. The PMIC is connected to I2C4 over pins PD12 and PD13.In the process of migrating our software from OpenSTLinux 6.0 to 6.2, I initially got stuck into an optee panic (attached optee-panic.log with optee log level set to 3); after some investigation I *think* I figured out that the problem was coming from I2C4 being assigned to the secure context, but pins D12/D13 not being secure.I managed to go around that by making the I2C4 controller non-secure and removing all reference to it from the optee dts, but then the kernel was hanging forever (attached optee-pass-kernel-fail.log) until I also marked the RCC as non-secure for optee and changed the clock definitions in the kernel to not use SCMI (to do so I had to patch stm32mp15-scmi.dtsi to be empty).I now have a booting configuration by essentially avoiding SCMI for clocks and regulators (I have attached the kernel and optee dts), but I am wondering whether this is necessary bec

Yesterday I was able to generate a cmake project which included main.c/h files. I opened the project in VS Code but had errors trying to build. I had VS code fix the errors so now I am able to build the project. Today, I generated another project but the main.c/h files are missing as seen in the screen shot. I've timed the project generation and it takes 3 minutes to generate a project. Why so long? Why are the IOC files created outside of the project folder?      

I am using two Nucleo-STM32WL33 board, one as a transmitter and one as a receiver. The transmitter sends two messages in ASK modulation and the receiver records the messages in IQ sampling mode.Below is a visualization of the IQ samples time series.The logical 1s are quite clear and all have a similar amplitude, however for some reason there seems to be a sinus-like subsignal whenver the transmitter sends a logical 0. I would have expected an amplitude close to zero, like seen during the time frame between the two messages or after the end of the second message. There is a distinct 1/4 period phase shift between I and Q component, so its clear to me this has something to do with the IQ modulation itself. But what is causing this sinus subsignal? Is it caused by the receiver or transmitter? How can I remove it?

Hello, I am currently working on a ble project on the stm32wb09ke nucleo board that uses the stm32 sequencer. My application is working as intended but I want to make it low power for optimal battery life. If i understand correctly the sequencer itself handles when to enter the Idle state if there is no current running task. From the HeartRate example I've copied the logic for the "UTIL_SEQ_Idle" function. The problem I'm having is that the "UTIL_SEQ_Idle" function is not included in "UTIL_SEQ_Run" as it is in the HeartRate example and is therefore never called. Why is this part not included/generated? Should I just copy whats in the example?   My UTIL_SEQ_Run: if ((local_evtset & EvtWaited)== 0U) { UTIL_SEQ_PreIdle( ); UTIL_SEQ_ENTER_CRITICAL_SECTION_IDLE( ); local_taskset = TaskSet; local_evtset = EvtSet; local_taskmask = TaskMask; UTIL_SEQ_EXIT_CRITICAL_SECTION_IDLE( ); UTIL_SEQ_PostIdle( ); } HeartRate example: if ((local_evtset & EvtWaited)== 0U) { UTIL_SEQ_PreId

The problem is that the transceiver will set the RX pin high at boot , this will put the G431 in boot mode and never start . The question is how to set and reset the nSWBOOT0 bit in the program . I mean , if I am right ::2) at setup (yes , Arduino) , the nSWBOOT0 bit is set in order to disable BOOT0 pin , thus allow normal (CAN bus) operation after boot  on PB8 .1) but this will reset the STM32 , so before doing 2) , one need to read the level of nSWBOOT0 , and only set it if it is 0 . (one time action)3) but this will brick the DFU uploading . To reset this , for exemple by a customer In order to update the firmware , one have to reset the nSWBOOT0 by the program . This could be done by a button , or by a code received trough USB .Hope this is clear enough (and correct of course) . But doing this is not that simple for me , so I wonder if there is a working code available for this (sure , some people have done the trick successfully ) ?Thank you !Edit : c

Hello,I am currently experiencing some difficulties using the NUCLEO-N657X0-Q board.I am using STLinkUpgrade v3.17.10, and the device ID is correctly recognized as 003500244142501120353451, as shown in the attached image.However, when I click "Open in update mode," the PWR_STATUS LED on the Nucleo board turns off and the connection is dropped.I am not sure if this specific update is critical for operation, but I would greatly appreciate any guidance or help to resolve this issue.

I'm having an issue with STM32CubeProgrammer v2.22.0. I'm making an external loader for the stm32U031R8 (on the nucleo board). My spi flash code works fine in the my actual application program. If I strip my code down (removing Read,Verify, instrumentation, etc) and get it under the 8K of SRAM1, the programmer works. Once my object is into SRAM2 (0x20002000-0x20002FFF) the programmer behaves incorrectly.First off, to make sure I understand whats going on, in the good case:every operation begins withw ap 0 reg 15 PC (0x20000000)w ap 0 reg 17 MSP (0x20000500)w ap 0 reg 16 xPSR (0x01000000)w ap 0 @0x20001CA0 : 0x00000200 bytes, Data 0x00000000...w ap 0 @0x20000000 : 0x00000004 bytes, Data 0x0000BE00...w ap 0 @0x20000004 : 0x0000186C bytes, Data 0xDEC0ADDE...Not sure why 0x20000500 is chosen as the SP, or what those 0x200 bytes written at 0x20001CA0 are, but I see that a bkpt instruction is written at the base of SRAM1 and then my object is written after that, which makes sense.Then I see

NUCLEO F767ZI, CubeIDE 2.1.1, CubeMX 6.17.0I'm trying to set up UART with printf()#include <stdio.h> UART_HandleTypeDef huart3; static void MX_USART3_UART_Init(void); int __io_putchar(int ch) { HAL_UART_Transmit(&huart3, (uint8_t *)ch, 1, 10); return ch; } .... // in main // in while prinf("UART test\r\n"); // MX generated USART3 init static void MX_USART3_UART_Init(void) { /* USER CODE BEGIN USART3_Init 0 */ /* USER CODE END USART3_Init 0 */ /* USER CODE BEGIN USART3_Init 1 */ /* USER CODE END USART3_Init 1 */ huart3.Instance = USART3; huart3.Init.BaudRate = 115200; huart3.Init.WordLength = UART_WORDLENGTH_8B; huart3.Init.StopBits = UART_STOPBITS_1; huart3.Init.Parity = UART_PARITY_NONE; huart3.Init.Mode = UART_MODE_TX_RX; huart3.Init.HwFlowCtl = UART_HWCONTROL_NONE; huart3.Init.OverSampling = UART_OVERSAMPLING_16; huart3.Init.OneBitSampling = UART_ONE_BIT_SAMPLE_DISABLE; huart3.AdvancedInit.AdvFeatureInit = UART_ADVFEATURE_NO_INIT; if (HAL_UART

when you enable SWD in CubeMX2 it automatically blocks the SWO pin as well (tested using C531FBP6), but I only need SWCLK / SWDIO to debug. please add a way to disable the use of SWO.