Product forums

Greetings!   There's an errata for the STM32F6/STM32F5 chips that goes like this:   2.4.1 Extra data written in the FIFO at the end of a read transferDescriptionWhen all the conditions listed below are gathered:• QUADSPI is used in indirect mode.• QUADSPI clock is AHB/2 (PRESCALER = 0x01 in the QUADSPI_CR).• QUADSPI is in quad mode (DMODE = 0b11 in the QUADSPI_CCR).• QUADSPI is in DDR mode (DDRM = 0b1 in the QUADSPI_CCR).• A data is read in the instant when the FIFO buffer gets full at the end of a read transfer, an extra data is unduly written in the FIFO buffer.WorkaroundsApply one of the following measures:• Read out the extra data until the BUSY flag goes low, then discard the extra data.• After reading out all the expected received data, set the ABORT bit of the QUADSPI_CR register to flush FIFO and keep the BUSY flag low. The last register configuration is kept.   I believe this is also present on the STM32F769NI chip. I have done extensive research on this.  

Hello,I just downloaded STMCubeIDE 2.1.1 to generate a simple project for a Nucleo-C562RE board.I am not using CubeMX2 (for various reason, that is not the point).The default empty project generated for STM32C562RE by the IDE has only 1 SRAM element with a size of 64K, instead of 2 SRAM elements of 64K each.FLASH size is correct though.Out of curiosity, if ST were to push a fix for this kind of bug, would it be a new IDE release ? or could it be a STM32C5 pack update only ?

Hello everyone,I want to share some issues and their fixes when migrating the .ioc file that was created for the Riverdi 10" STM32 display with template 4.1.0 to the newer version of CubeMX ver 1.16.0, STM32Cube FW_H7 V1.13.0.My environment is:Target: Riverdi STM32 10" Display RVT101HVSNWC00-B TouchGFX 4.26.0, CubeMX ver 1.16.0 STM32Cube FW_H7 V1.13.0, CubeIDE ver. 1.19.01. The build in CubeIDE fails with multiple errors searching for the "cmsis_os2.h" file.     Fix: Include paths are missing. Manually add the following include paths in both the Include Paths section of MCU GCC Compiler and MCU G++ Compiler (In CubeIDE)     (Riverdi_101STM32H7_1_6_CM7-->Properties-->C/C++ Build--> Settings-->MCU GCC Compiler-->Include Paths)            The paths to be included are:     " ../../../Drivers/CMSIS/RTOS2/Include" and  "../../../Drivers/CM

 After porting the application "STM32Cube_FW_U5_V1.8.0\Projects\B-U585I-IOT02A\Applications\SBSFU" to our own board we have everything operational apart from the ability to invoke the local loader in production mode (RDP2).I have reverted to the original B-U585I-IOT02A board and project and have a similar issue so I am wondering if this is broken or we have misunderstood something. The loader can be invoked in TFM_DEV_MODE with RDP0 but not in production mode with RDP2. The SBSFU application runs fine.Changes from the default STM SBSFU project settings we used to test this on B-U585I-IOT02A1) In SBSFU_Boot project remove the TFM_DEV_MODE pre-processor symbol definition2) In boot_hal_cfg.h >> #define TFM_TAMPER_ENABLE NO_TAMPER3) In boot_hal_cfg.h >> #define #define TFM_OB_BOOT_LOCK 04) In flash_layout.h >> //#define MCUBOOT_PRIMARY_ONLY (definition commented out)5) In flash_layout.h >> #define MCUBOOT_APP_IMAGE_NUMBER 26) In hardening.sh

I am using the STM32H753VGT6 microcontroller and need to generate two PWM signals with the same frequency and duty cycle, with a 90-degree phase shift between them, using a single timer. Is this possible? If yes, how can it be achieved?

I am using the VL53L7CX to measure a black object. When the object is placed at a distance beyond 200 mm, the readings become very unstable and a large number of erroneous points appear. Additionally, when a highly reflective object enters the sensor’s field of view, the points that were previously showing valid data for the black object also start returning errors. Once I remove the highly reflective object, those points recover and start reporting correctly again. In the error state, the affected points return no data at all — it seems as if the sensor does not detect any object. However, the black object is still present in the scene. The only change is the removal of the white object, which causes the sensor data to change significantly. Has anyone encountered a similar issue? Could this be related to crosstalk, or are there specific configuration settings recommended for black targets at longer distances? Any advice would be greatly appreciated.

Split from How to open files on Host PC with fopen on STM32L5hi @KnarfB I tried semi-hosting with the instructions you provided... after debugging, I returned the error as follows: what does it mean?

Hello, I purchased an STLINK-V3PWR from Mouser. When I tried to use it, STM32CubeIDE 2.1.1 suggested updating the firmware. This failed, and the STLINK-V3PWR appears to be unusable (bricked). What can I do? Return the device for a refund/replacement? Or is there a way to re-flash the firmware using an STLINK-V3SET? If it is possible to restore the firmware by re-flashing it, where can I find the correct firmware? Kind regards, Jack.

I cannot get USB DFU serial boot to work correctly with STM32CubeProgrammer.I keep getting the error "Please specify Binaries path" but there is no area to specify the binary path.Does anyone have any experience with USB serial boot on the STM32N6.

Hello. I need to find this component. Thank you 

Hi, I'm Dheeraj Sudan from the UK. I'm a software developer and also run a business with my wife Meenu Hinduja. I’m trying to create a new project in STM32CubeIDE, but I want to make sure I’m following the best approach. RegardsDheeraj Sudan and Meenu Hinduja 

Dear Team ST,We are using the STM32 MCU (Part No. STM32F407VET6) on our custom board, and we are currently facing an issue related to the reset function.During board power-on or after program loading, the MCU appears to enter a hold or non-responsive state. This issue occurs every time the board is powered OFF and then powered ON. However, when the hardware reset button is pressed, the MCU starts functioning as expected.We kindly request your support in identifying the root cause of this issue. Please advise if any modifications are required on the firmware or hardware side to resolve this behaviour.We look forward to your guidance.Regards,Kaushik@Shubham Prakashpant BOHARAPI

When i try to add breakpoint, there is a cross sign on breakpoint symbol. So even if the code works, breakpoint never works.I try to add __asm("BKPT 0"); but it also did not work. I am not sure what is the problem.My CubeID version is: Version: 2.1.1Build: 28236_20260312_0043 (UTC)

Hello,I am currently working on a drone project based on the STEVAL-FCU001V2 board. My hardware setup consists of:Motors: 4x 8520 Coreless DC motors (3.7V).Battery: 1S LiPo 600mAh (30C).Frame: Custom micro-drone frame (~60g AUW).I am looking for a reliable and fully functional firmware (source code or .bin) that is compatible with the latest mobile application for flight control of STM.I’ve noticed that the original ST Drone (or ST BLE Drone) application sometimes has connectivity or stability issues with recent Android/iOS versions.My questions are:Is there a specific version of the STSW-FCU001 firmware that you recommend for best stability in 2026?Is the "ST Drone" app still the official way to fly this board via BLE, or is there a community fork or a newer ST app recommended for this specific FCU?Are there any known patches for the PID values or PWM frequency (specifically for 8520 motors) to improve the hover stability?Any advice, GitHub links, or updated STSW packages would be gre

I am looking for a software solution for this race condition:* The power button is connected to both the On/Off pin PD3 and the wakeup pin PB5. See the partial schematic.* The issue is that the STM32G0 enters shutdown mode, but immediately wakes up. Please see my function below.What is missing? Thank you!  void Enter_Shutdown_Mode(void) { sprintf(msgString, "Enter_Shutdown_Mode...\r\n"); Debug_Print( msgString ); HAL_Delay(50); /* Enable the Power Controller (PWR) APB clock */ __HAL_RCC_PWR_CLK_ENABLE(); /* Wait for the pin to be HIGH after the button release. If the power button is currently pressed (LOW), entering shutdown with "LOW" polarity will cause an instant restart. */ while (HAL_GPIO_ReadPin(WAKEUP_GPIO_Port, WAKEUP_Pin) == GPIO_PIN_RESET) { // Wait for user to release the button HAL_Delay(10); } // Debounce the button press HAL_Delay(50); /* Clear the Wakeup Flag. If a flag is set from a previous wakeup, the MCU will fail to enter Shutdown and

 Hi,  I've implemented the antenna selection circuit as per AN6121 but I'm getting some strange behaviour. Background- I have designed and manfactured a test pcb using the ST25R3916.   On it I have 2 ST25R3916 chips, one with a single antenna connected and the other with 6 antennae and a multiplexer circuit as described in AN6121- Each has a header where I can connect it to my MCU host board so I can use the same software on both to compare- I have the single antenna chip working - it can detect tags correctly.  The chip connected to the multiplexer is not doing so well. I have attached the circuit diagram which i'm pretty sure matches the diagram in AN6121, paying careful attention to which way round the FETs are.  Note I've used the same fets as in the AN.  I'm assuming SW must be low to select the antenna?What i see, which i'm not expecting, is a large voltage drop across R1 in my diagram,  12v incoming drops to 7.6 vo

Hello everyone! I'm new to the NUCLEO-H743ZI2 board. I need help with two questions: 1) I can't find a description of the STLK backup port -CN2 anywhere. Can you tell me if I can use it to program other STM32 devices on other boards, and how? 2) Can anyone share the schematic for the H743ZI2 board?  

I have an application where I run the VL53L1X in lite ranging mode and short distance mode with a timing budget of 10 ms (100 Hz) as described in AN5263.I recently noticed that on at least one unit (and probably more) the VL53L1X reports a spurious distance reading of 0 mm with no errors even though the sensor is pointing into an empty space and there are no objects within the 1.3 meter range of short distance mode.  This spurious reading happens about 10 times per minute, and the rest of the readings are regular expected errors.I am not using the API (STSW-007) directly, but have implemented code that does the equivalent thing.Here are some VL53L1X register values from these spurious readings:The lower 5 bits of the VL53L1X result__range_status register (0x89) is always 9.  That corresponds to VL53L1_DEVICEERROR_RANGECOMPLETE and that is the value that the API maps to 0.The result__stream_count register (0x8B) is between approximately 130 and 250.  The&nb

hello,I encountered a problem while developing for stm32u585. When the stm32 wakes up from standby mode, the HAL_RCC_OscConfig() function occasionally fails, "Wait till LSI is disabled" timeout in HAL_RCC_OscConfig() (this project uses IWDG)The specific process is as follows:1. start boot HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_ICACHE_Init(); MX_UART4_Init(); boot to other address(app) 2. app init HAL_Init(); SystemClock_Config(); RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI48|RCC_OSCILLATORTYPE_LSI |RCC_OSCILLATORTYPE_HSE|RCC_OSCILLATORTYPE_LSE; RCC_OscInitStruct.HSEState = RCC_HSE_ON; RCC_OscInitStruct.LSEState = RCC_LSE_ON_RTC_ONLY; RCC_OscInitStruct.HSI48State = RCC_HSI48_ON; RCC_OscInitStruct.LSIState = RCC_LSI_ON; RCC_OscInitStruct.LSIDiv = RCC_LSI_DIV128; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON; RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSE; RCC_OscInitStruct.PLL.PLLMBOOST = RCC_PLLMBOOST_DIV1; RCC_OscInitStruct.PLL.PLLM = 1

Hi,I would like to inquire whether the STM32C5 series supports ITTIA DB. Additionally, is it possible to use this library directly within CubeMX for development?

I would like to enable spread spectrum on the STM32H573RIT6.We are currently running on 250Mhz and at that frequency we have big peak which is 15dB above the limit, that's why I would be able to enable the spread spectrum. I looked into the STM32H7 example, so I am already aware and able to modify the PLL realtime. Now my question is how do I connect the DMA of the STM32H5 properly to a timer and a buffer to load the PLL. And also a question I have, what are good values for the PLL.  

Hello,I must implement a SSI (Synchronous Serial Interface) to output a measured value. As SSI in principle is just a bitstream which is clocked out with the serial clock, I wanted to use a SPI in slave mode, as the clock comes from the SSI master.This works in principle, but from time to time I get a bit shift and the received data is delayed by one bit, which results in a division by two.Checking the SSI data clock, I didn't find an expected unstable clock with additional edges but from time to time the SSI master makes a pause after the first falling edge before it starts clocking. Could it be that this pause disturbes the SPI interface? I would have expected, that the SPI in slave mode only checks the clock edges and that the time between the clock edges isn't that critical?

Hi friends, Again I have come with a problem. Please see my code. PWM works as usual. But it is made to stop by resetting PC3 bit, PWM does not stop rather, it behaves randomly. Sometimes the PWM channels are driven high, driven low or PWM pulse is there. Many modifications has turned futile. Hence I seek your support. Regards ankhola Main,c /* MAIN.C file * * Copyright (c) 2002-2005 STMicroelectronics */ #include "stm8s.h" #include "ccp.h" void inv_on(void); void inv_off(void); void sw_state(void); unsigned int pwm_duty1 = 40; unsigned int pwm_duty2 = 50; unsigned int i=0; unsigned int duty; unsigned char toggle=0; unsigned char off_state; unsigned char on_state; unsigned const int table []= {0, 16, 32, 48, 64, 80, 96, 112, 127, 143, 159, 174, 190, 205, 220, 235, 250, 264, 279, 293, 307, 321, 335, 349, 362, 375, 388, 400, 413, 425, 437, 448, 460, 471, 481, 492, 502, 511, 521, 530, 539, 547, 555, 563, 570, 577, 584, 590, 596, 602, 607, 612, 616, 620, 623, 627, 630, 632, 634

We are designing a lens cover to be used with VL53L9CX. Can you share any more data on the FoV of the time of flight sensor? The attached data sheet on the part page is for a different sensor "VL53L7CX" is there a data sheet for the "...9CX" version? In "Description of the fields of view of STMicroelectronics' Time-of-Flight sensors" Sections 3.2 & 3.3 reference exclusion cones which are given in a product data sheet. Could you please share this file? Also, 3.3 references keep-out cones which can be shared by contacting support. Any additional information would be helpful to ensure our lens does not interfere with the required FoV. Thank you! 

Hello. I'm using a combo of a wba board and a LSM6dsv IMU sensor. I collect sampoles from the imu and then send them to my pc to do some fft there and als odo fft on board using the cmsis dsp libraries. The thing is that my pyrhon spectrum appears to be correct. I'm using a vibrator to make sure about that it [produces the requested  frequency and monitor the results with the integrated vibrator's sensor. The python sprectrum appears to match the vibrator's sensor sprectrum whereas the cmsis results appear a lot more noisy and have an almost mirrored in the middle  huge harmonic. Lets say than my sensor'f sampling rate is 4 KHz, so im able to do fft on up to 2 KHz event freq. If my vibrator is at 300 Hz i will see a huge harmonic in lets say 1600-1700 hz which gets closer the more i go to 1000 Hz. At 900- 1200 Hz the spectrum appears to be a complete mess and at 1300 HZ and afterwards it is simply beautiful. Here is the mcu code. I do a hanning window and median removal