STM32 MCUs

Hello,We programmed our STM32L011 microcontroller with firmware that enters STOP mode and waits for an interrupt.However, we accidentally disabled the interrupt on the PA4 line. As a result, the device now immediately enters STOP mode, and we are unable to reprogram it.Could you please advise how we can recover the device in this situation?Thank you in advance.

 Hello!We are using an STM32L0 microcontroller as a power switch.The device works correctly when the firmware is started from STM32CubeIDE using the Run command.However, if we switch the power supply off and then back on, the STM32L0 does not boot.We suspect there may be an issue related to the reset circuit.Please see the attached schematic. The relevant device is U6.Could you please advise?Thank you in advance.

Hello world!I want to move a motor with serial commands. I use the stm32g051 PWM and a DC motor. And for the sake of lower consumption of energy and cpu I use a dma in circular mode. And of course I want to change the pwm from time to time. But somehow, there is always a delay of more than 10 seconds between the calling of the function and the change in the motor behaviour. mid_error_t tim_forward_buffers(void) { for (uint16_t i=0; i<PWM_BUF_LEN; i++){ pwm_ch1[i] = (uint32_t)(param.speed * (htim2.Init.Period-2))/ MAX_SPEED; //pwm_ch1[i] = 0; // htim2.Init.Period; pwm_ch2[i] = 0; } __HAL_TIM_SET_COMPARE(&htim2, TIM_CHANNEL_1, pwm_ch1[0]); __HAL_TIM_SET_COMPARE(&htim2, TIM_CHANNEL_2, pwm_ch2[0]); return MID_ERROR_OK; }You may guess that the PWM_BUF_LEN is too big... There is just one element in pwm_ch1 and pwm_ch2. What may cause this problem? I use the __HAL_TIM_SET_COMPARE to change the pwm faster and the pwm_ch1 pwm_ch2 just contain one elem

Hello, i found a bug in the code generated by the Motor Control Workbench usign the 6-step algorithm. Even with Open Loop mode enabled, the code is still using the PID for the initial duty cycle computation (state CHARGE_BOOT_CAP in the TSK_MediumFrequencyTaskM1()). If the PID isn't set up right and starts with a low duty cycle, the motor won't turn. This means the Hall sensors don't trigger, the duty cycle never updating, and the motor just sits there even if you set a high duty cycle value. The Open Loop mode shall bypass the PID controller, otherwise it is useless.  I fixed it by changing row 174 of mc_tasks_sixstep.c as follows: from:  MCI_ExecBufferedCommands(&Mci[M1]); /* Exec the speed ramp after changing of the speed sensor */ to: if (SDC_GetOpenLoopFlag(pOLS[M1])) { SDC_SetControlMode(pSDC[M1], MCM_DUTY_MODE); } else { MCI_ExecBufferedCommands(&Mci[M1]); /* Exec the speed ramp after changing of the speed sensor */ } Leo Edited to apply source code formatti

Hi i am getting this error while opening motor pilot for gui in motor control,pls go throgh below attached file.        

Hello Team,We want to have Standalone Programmer based on ST`s Existing Flash Module Like St-Link V2, V3 Or Mini PCB tools.I should be able to Use External ST MCU to Command this SWD module for Flashing n all task , like CubeProgrammer.Basic Interface like Pushbutton to Start the Flash and Some LED to showcase any Error.   We would not prefer expensive available off-the-Shelf Programmer like Segger..... Not want to use Rpi as well.  This basically for FAE.Regards,

I recently built a motion-control setup using an STM32 MCU to drive a NEMA 23 stepper via a DM542 driver. STM32 timers reliably generate step pulses while DMA reduces CPU load, enabling smooth microstepping and precise speed control. Key tips: match driver current to motor specs, use a 24–48V stiff supply, keep motor and logic wiring separate, and provide cooling for the driver. Implement trapezoidal acceleration to avoid missed steps and add homing/limit switches for safety. For multi-axis systems, synchronize timers or use an RTOS for higher-level planning. Happy to share sample timer code or a parts list on request.

Hi,I am testing PD11 on an STM32H563ZI with a NUCLEO-H563ZI board.The pin is configured as plain GPIO input using STM32 HAL:GPIO_InitStruct.Pin = GPIO_PIN_11; GPIO_InitStruct.Mode = GPIO_MODE_INPUT; GPIO_InitStruct.Pull = GPIO_PULLUP; // or GPIO_PULLDOWN / GPIO_NOPULL HAL_GPIO_Init(GPIOD, &GPIO_InitStruct);I rebuild and reflash the firmware for each case, then read the pin with HAL_GPIO_ReadPin(GPIOD, GPIO_PIN_11).What I observe is:GPIO_MODE_INPUT + GPIO_PULLUP -> LOWGPIO_MODE_INPUT + GPIO_PULLDOWN -> HIGHGPIO_MODE_INPUT + GPIO_NOPULL -> LOWI also checked the pin with a multimeter, and the measured pin level matches what the MCU reads.I have rebuilt and reflashed multiple times and I keep getting the same pattern.My expectation was that a floating input with internal pull-up should read HIGH, and with internal pull-down should read LOW.Is there anything special about PD11 on NUCLEO-H563ZI / STM

Hello,I'm designing a 2 layer PCB using STM32WL for LoRa operations at 433MHz and need a review of my RF layout. The board is JLCPCB 2 layer standard FR4, 1.6mm thick 1.46mm core, 1oz copper, 50Ω microstrip at ~2.8mm width, about 38mm long. I have placeholder caps/inductor to be populated after board fabrication. I am seeking expert opinion for:Trace width & impedance - does 2.8mm yield 50ohm given FR4, 1oz copper, and 1.46mm dielectric height?Critical length - Are there implications for 38mm length on transmission-line behavior?Taper - Taper starts 5mm in. Are there optimal lengths for tapers? Should I taper for shunt pads?Stitching vias - Recommendations for via spacing for this trace width? Every 5-8mm?Test points - Recommendations for RF test points without effecting impedance?Any other best practices or tips would be helpful. I thank you for any guidance.Best, John

Using STM32CQubeCLT 1.20's libnano:I am trying to print an uint64_t using inttypes.h via an vsnprintf(line, sizeof(line), fmt, ap) wrapper and the sending the line via UART to a Terminal.However, using print_wrapped("%" PRIu64"\n", (uint64_t)1) gives only an output of "lu\n".I know that for floating point support I need to add -u _printf_float to the linker options. Is there something similar for 64bit integers? Or do I have to compile my own version of libnano? 

Hi ST Community,I create LBPAM application which continuously convert ADC4 data channel 22 (PC4) of STM32U575 VGTX.I add HAL_DBGMCU_EnableDBGStopMode(); so I can debug in stop mode. I run LPTIM1 and ADC4 before going to STOP mode. I also move VoltageData buffer to SRAM4 uint16_t VoltageData[32] __attribute__((section(".sram4")));LPBAM configuration contains one queue in Circular mode and only one node for ADC4 conversion.After enter stop mode 2, no adc4 trigger, and VoltageData always is 0.I attach my configuration so you guy can check it.Thank you. 

Background: I am designing a high-speed imaging system for an industrial press. I am using an STM32 to synchronize a camera (TIM3) and two flashes (TIM4) based on an external hardware trigger.The Setup:Both timers are in One-Pulse Mode (OPM) and Combined Reset + Trigger Mode (SMS = 1000).Both are triggered by the exact same physical edge using HAL_TIMEx_RemapConfig(&htim4, TIM_TIM4_ETR_TIM3_ETR)The digital filter is set to 16 µs for both (ClockDivision = DIV4, TriggerFilter = 0xf).The Goal: When a valid trigger arrives, both timers start automatically. TIM3 fires its pulse almost immediately. TIM4 counts down a configurable delay (via CCR) before firing the flashes.To prevent mechanical double-triggers from the sensor, I need a firmware "blind window." Once the initial valid trigger is received, I want to completely ignore the ETRF pin for a few milliseconds.The Catch: I want to disable the ETR input from inside TIM3's HAL_TIM_PWM_PulseFinishedCallback (which fires right after the

Hello!I was working on a project of mine and put it on pause for a few weeks and now when I tried to connect the stlink to my PC its no longer detected. Its not showing up in the device manager and the stlink has dim red and green lights lit.Does this mean that it's somehow bricked? What could have caused it?I tried it on two of my computers and with 3 different cables. I am assuming it's a different problem from this one https://community.st.com/t5/stm32-mcus/how-to-solve-connection-errors-when-connecting-and-programming/tac-p/786977 .Thanks in advance!

Hi everyone, I’ve been working on an STM32 project using STM32CubeIDE on Windows 10 (i7-9700K, 16GB RAM), and I’m running into a frustrating issue. Every time I start a debug session on my Nucleo-F446RE board, the IDE sometimes freezes or crashes after hitting a breakpoint. I’ve tried updating CubeIDE to the latest version and reinstalling the ST-Link drivers, but it’s still happening intermittently.One thing I did notice is that my system isn’t always completely clean in the background. I sometimes run lightweight games during breaks, like Stick War Legacy, and recently I tried a mod APK version from stickwarmods. I’m not sure if something from that could be affecting system stability or leaving background processes running, but I thought it might be worth mentioning in case it’s related.Has anyone faced similar issues, or is there a recommended way to debug without the IDE crashing? Any tips would be really appreciated!

Hello, Long time lurker here. First of all, thank you for the extensions, really appreciated the possibility to work directly in vscode.I have a couple of situation, however, that are really annoying and that I would like to solve. While developing in vscode with the extension enabled. It is sufficient to update the CMake presets in order to have the tools installed by the ST extension to make the git repository dirty.If before committing the files to the repo a pre-commit that formats the files in a proper way then it is amplificated.The files: c_cpp_properties.json in the .vscode folder is always updated with the compileCommands updated if dynamic folders for Debug and Release are used .clangd configuration file is updated in the CompilationDatabase field.In my opinion there are two different types of settings: settings that needs to be persinstent, and maybe reusable on different computers by different userssettings related only to the current runThere

Hi ST community,We are currently evaluating STM32WB05 vs STM32WB09 for an application involving continuous BLE data streaming from multiple sensors, and would appreciate guidance from experts who have worked with STM32WB0 series.The reason we choosing the STMWB05 over STM32WB09 MCU, STM32WB05 MCU comes at a lower cost.In brief our application sensor are2x IMU LSM6DSO sensors (high-frequency sampling)1x magnetometer1x analog force sensorA single BLE connection (no mesh or multi-node), with frequent sync occurring approximately every three minutes.Key Questions1. WB05 vs WB09 for continuous BLE streamingBoth MCUs seem to have similar BLE capabilities (Bluetooth 5.4, 2 Mbps PHY), but:Does WB09 (larger RAM/Flash) provide significant advantage for:Continuous streamingBufferingReducing packet drops?Has anyone faced RAM bottlenecks or BLE throughput instability on WB05, WB09 in such use cases?2. Single-core architecture suitabilityBoth WB05 and WB09 are single-core Cortex-M0+ with radio

Having issues compiling the source code found in the audio kit for the designer application.C:\x-cube-audio-kit-v1-4-1\package\Projects\STM32H573I-DK\Applications\Livetune\STM32CubeIDE\DesignerAfter importing the project into STM32 Cube IDE when I attempt to build the source without changing anything I get the following error.... make -j22 all arm-none-eabi-gcc -o "firmware.elf" @"objects.list" ../../../../../../../Middlewares/ST/STM32_Audio/Addons/PDM/Lib/libPDMFilter_CM33_GCC_wc32.a ../../../../../../../Middlewares/ST/Audio-Kit/lib/libAudioChainAlgos_CM33_GCC.a ../../../../../../../Middlewares/ST/Audio-Kit/lib/libAudioChain_CM33_GCC.a ../../../../../../../Drivers/CMSIS/DSP/Lib/libCMSISDSP_CM33_GCC.a -mcpu=cortex-m33 -T"../Project.ld" --specs=nosys.specs -Wl,-Map="firmware.map" -Wl,--gc-sections -static -L../../../../../../Drivers/CMSIS/DSP/Lib/GCC -L../../../../../../Middlewares/ST/STM32_Audio/Addons/PDM/Lib -Xlinker -no-wchar-size-warning -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mt

Hi all,I'm planning to get STM32H573I-DK to evaluate X-CUBE-AUDIO-KIT Livetune because there are project examples for specific boards and this is one of them. I'll be using an STM32U5A9 MCU eventually and both have an M33 core. This should make it easier to port from one to the other. I see that there are two versions of STM32H573I-DK: MB1677-H573I-D01 Board schematic has a WM8904 audio codec and MB1677-H573I-C02 Board schematic has a CS42L51 audio codec. This last one is marked as "Discontinued Product" by the manufacturer.Do the examples for STM32H573I-DK work for either version of the board without any modification or does it require a specific version/codec?Thanks.

Hi, I consistently hit HardFault when using PICOLIBC. I am using a STM32H735G-DK board.Setup:1. Start from a black CubeMX project, selecting the board and default pins. The FreeRTOS must be enabled, and the TouchGFX (with the MPU configured). We will target CMake and SR Arm Clang. Generate code.2. Open TouchGFX and load the project with the file ApplicationTemplate.touchgfx.part. No need to add anything, just generate code.3. Open the entire project with VSCode. The project by default uses the PICOLIBC in the file starm-clang.cmake. The project as is compiles successfully. flash onto the board and click Continue. The code will instantly go in HardFault_Handler().Here is a printscreen: Can anyone try to reproduce this, just to make sure it is not something only on my side? Thank you!If I change for STARM_NEWLIB in starm-clang.cmake instead of STARM_PICOLIBC, everything works as expected, no hardfault, and the screen initializes successfully.I have added a demo project.

Disclaimer:Probably not quite the right place for this bug report. However, since the issue appeared with the update to CubeIDE VSCode v3.8.0 and STM32CubeMX v6.17.0, and the project in the attached ZIP was created with these versions to reproduce the behavior, I am placing it here.IntroductionLink to Project on GitHub: init_array_issue (or use the attached ZIP file)The code in file init_array_issue.cpp demonstrates a misbehavior where, under certain conditions, the initialization of objects is silently skipped without any warning or error message when picolibc is used together with the linker description file STM32H753XX_FLASH.ld generated by STM32CubeMX and the default optimization -Og.picolibc / STARM_PICOLIBCThe use of picolibc has been the default since the STM32CubeMX update to 6.17.0, configured via the option STARM_PICOLIBC in the file .\cmake\starm-clang.cmake.Previously, STARM_HYBRID was set here by default.# STARM_TOOLCHAIN_CONFIG

I'm looking at Rev 9 of the STM32L412xxx Datasheet, as linked on Digikey, and I'm having a hard time understanding the current consumption figures specified for the Low-power Run & Low-power Sleep modes on the MCU.  Per the table on pg.24 (shown below), the current draw is 83uA/MHz in LPRun mode, which is higher even than the normal Run mode up to 26MHz (range2), which doesn't make sense to me.  Further, the current draw in LPSleep mode is also 83uA/MHz, which suggests there's no power savings putting the MCU to sleep in Low-power mode?  Can somebody tell me what I'm missing here, or is this a typo and one or both of those figures are wrong?

Could I erase rtc backup registers with STM32CubeProgrammer ?

hello,I encountered a problem while developing for stm32u585.I change the iwdg reload value by HAL_IWDG_Init(), and then HAL_PWR_EnterSTANDBYMode(), but the new reload value does not take effect: hiwdg.Instance = IWDG; hiwdg.Init.Prescaler = IWDG_PRESCALER_64; hiwdg.Init.Window = 4095; hiwdg.Init.Reload = 3600; hiwdg.Init.EWI = 0; HAL_IWDG_Init(&hiwdg); HAL_IWDG_Refresh(&hiwdg); HAL_Delay(300); //more than one downcount HAL_PWR_EnterSTANDBYMode();if delay before refresh, it seems work hiwdg.Instance = IWDG; hiwdg.Init.Prescaler = IWDG_PRESCALER_64; hiwdg.Init.Window = 4095; hiwdg.Init.Reload = 3600; hiwdg.Init.EWI = 0; HAL_IWDG_Init(&hiwdg); HAL_Delay(300); //more than one downcount HAL_IWDG_Refresh(&hiwdg); HAL_PWR_EnterSTANDBYMode();Is this the correct process ? If I want to ensure the modification is successful, what should I pay attention to

Hello,I am currently developing a LoRaWAN Class A device using the NUCLEO-WL55JC1 development board and the "LoRaWAN_End_Node_LBM" example from STM32CubeWL (version 1.5.0).I am facing an issue with context restoration after a reset. I am using the provided StoreContext() and RestoreContext() functions exactly as implemented in the example. However, after each reboot, the device always restarts the join procedure instead of resuming the previous session. As a result, the DevNonce is incremented on every reset.This behavior is problematic because repeated resets will continuously increment the nonce value. According to the LoRaWAN specification, this value is limited (16-bit), and once the limit is reached, the device will no longer be able to join the network.My understanding is that, when the context is correctly restored, the device should resume its previous session without triggering a new join procedure.Could you please clarify:* What is the correct sequence to restore the LoRaWAN

Label: MC Workbench[PN]: STM32G474RBT6 (Custom Board)[VERSION]: MCSDK 6.3.2[TOOL]: MC Workbench[DETAILS]: I am trying to create a new FOC project for a custom board driving a BLDC motor with Three Isolated Current Sensors (3-ICS). I am constantly getting the following UI error preventing me from creating the project: "It is not possible to create a motor control project with the FOC algorithm using the selected hardware. No proper path for motor control signals was found for the following mandatory features: - Current Sensing"However, when I check the .st_workbench/connectAlgo.log, the solver successfully finds a valid TripleADC route for my pins without any conflicts: DEBUG - CSConnect: ThreeICSCurrents TripleADCs processing start DEBUG - CSConnect: ThreeICSCurrents TripleADCs route: CURRENT_ICS_U PA0 ADC1_IN1 DEBUG - CSConnect: ThreeICSCurrents TripleADCs route: CURRENT_ICS_W PB12 ADC4_IN3 DEBUG - CSConnect: ThreeICSCurrents TripleADCs route: CURRENT_ICS_V PC4 ADC2_IN5 DEBUG - CSConn