Solved

Hi,We recently bought a STM32H757I-Eval board and played around with it. This did overwrite the demo program it came with so I downloaded the stm32h757i-eval_demo.zip package to restore the demo.I used STMCubeProgrammer for this, did a full chip erase and pointed it at the hex demo file. The programming failed with                       Error : failed to download Sector[0]I tried the other hex demo files in the with the same result and on two different laptops and the latest CubeProgrammer.The weird thing is that when I power the board the demo seems to work as when new so I don’t know if only part of it is working. It could even have arrived in this condition.Anyone else have this problem? and perhaps a fix?I did try to compile one of the examples from the x-cube-azrtos-h7-v3-5-0.zip package to see if the generated hex would program ok.After a few issues I loaded the program with CubeIDE in debug mode and found the code would enter an infinite loop:                        while ((PWR-

Hello.I have project for STM32U575 created in CubeIDE just before new release of separate CubeIDE and CubeMX.I imported it into the new version of CubeIDE (2.1.1, it asked whether to “renew” project, and I clicked "yes").Both then and now, the project has this warnings:I didn't pay attention to it earlier because the project was working, but now I see that there are more and more strange problems in it. Could it be because of that?What could cause such warnings? This part of code is not mine, but generated by CubeMX.I didn’t have this warnings on another project for STM32H7.HAL code looks very similar for H7 and U5:H7:U5:But only the one for U5 generating warnings.

I'm using STM32N6570-DK board and developing an image processing application.When I tried to use STM32CubeMX to generate the project, I was able to set DCMIPP Pipe1 just like the attached screen capture.I would like to downsize the source image data to 800x480, but I could not find the option field in the DCMIPP Configuration view in STM32CubeMX.Is there something that I missed?My STM32CubeMX is Version 6.16.1 for Windows 11.  

According to AN5054, to prepare SFI (secure internal firmware install) or SFIx (secure external firmware install) "STM32 Trusted Package Creator" is required. Were do I find it? Searching ST website I find no such software product. Was it maybe recently replaced or "absorbed" by STM32Cube Programmer?

Hello,I am using STM32CubeMX with an STM32WBA63 project in TrustZone enabled mode, and I have a question about interrupt security attribution.My use case:PA11 is configured as USART2_RX (non-secure application). In low power mode, I need wakeup on UART RX activity. This relies on EXTI11, so I need EXTI11_IRQn to be targeted to the Non-Secure world (ITNS0 bit 22 = 1).Issue:In CubeMX, I cannot find a way to set EXTI11_IRQn as Non-Secure while PA11 is kept as USART2_RX. EXTI11 appears configurable only if I change the pin function to GPIO EXTI, but then USART2 configuration becomes incomplete.Questions:Is it supported in STM32CubeMX to configure EXTI11_IRQn as Non-Secure when PA11 is assigned to USART2_RX? If yes, where is this setting in the CubeMX UI? If not currently supported, what is the recommended ST approach? Manual USER CODE override in partition configuration? Post-generation patch/script? Any other official best practice? Current workaround:I manually set EXTI11 to Non-Secure

Hi all, Is this possible with a DMA on an STM32N6 device, using the HPDMA/GPDMA? (or I assume the H7 is quite similar, I believe?)Source array: RGBRGBRGBRGB (24 bpp) Destination array: xRGBxRGBxRGBxRGB (32 bpp)Or vice verca:Source array: xRGBxRGBxRGBxRGB (32 bpp) Destination array: RGBRGBRGBRGB (24 bpp) This would solve my issue, where I need both the 24bpp (NPU input) and a jpeg-encodable format (display; which all seem to be either 16bpp or 32bpp). If the above is not possible, then … I’d be open to suggestions on what else to do… Best regards, rphii

Hi,I am evaluating the ST25R200 using the ST25R200 Eval GUI. In Reader Mode, there is a Field Measurement tab that displays a numerical value together with a circular indicator. However, the displayed value does not appear to have any unit.Could you please clarify:What exactly is being measured in this tab? Does the value correspond to a physical quantity (e.g., magnetic field strength, ADC count, RSSI, amplitude, etc.)? Is there a conversion from the displayed value to a standard unit (A/m, µT, V, etc.)? Which ST25R200 registers or measurement circuitry are used to obtain this value? Is this functionality available through the ST25R200 firmware/API so that it can be implemented in a custom application?Any explanation of the measurement principle and interpretation of the displayed value would be greatly appreciated.Thank you.

The new community seems to be very slow in terms of surfing it (3/6 second for each page load). It’s definetly not my internet as I’ve 1gbps and before it was super snappyEDIT above seems back to normalI’ve figured out that there’s no HTML view when edit the post________________________________________________________________________________________________ Another thing is that the answered questions have basically the same feeling of the unanswered ones. A green checkmark is not enought in my opinion. It should be highlighted more. 

Hello ST Community,I am working with the STEVAL-DPSLLCK1 LLC full-bridge evaluation kit, specifically the STEVAL-DPS334C1 STM32F334 control board. My goal is to access and monitor the LLC firmware variables using STM32CubeMonitor through ST-LINK.For STM32CubeMonitor variable access, I need a firmware executable with debug symbols, such as an IAR .out file or an ELF file. The .bin file is not sufficient because it does not contain variable names or debug information.I downloaded the available ST firmware package for the LLC kit and opened the IAR workspace in IAR Embedded Workbench for ARM 9.70.4. IAR asked to convert the old project to the newer format, and I accepted the conversion. After conversion, the project fails to build, so no .out file is generated.The main errors are:Error[Pe018]: expected a ")"These occur mainly in:Control_Layer.cFault_Processing.cLLC_PWMnCurrVoltFdbk.cStateMachine.cparser.y / y.tab.cThere are also many warnings like:Warning: The header file 'cmsis_iar.h' is

Hi, Could somebody please explain why CAN on the NUCLEO-C5A3ZG is not populated? 

Hi,good day,would like to seek help for this question.what is the difference between L9906TR VS L9906QTR?.tried looking for documents online but can't find for L9906QTR.thank you for understanding and help.

Dear Engineers, is there any way of routing the internal OPAMP output of the STM32C5 to an ADC directly, or can it only be wired to the COMP1 ?CubeMX2 doesnt let you pick OPAMP as an input to neither ADC nor COMP, but i did find some notes on beeing able to route the OPAMP output to COMP1 minus input in the LL code somewhere.If yes, is there a way to do this within MX2, or does it have to be written by hand in code?Also, the datasheet shows a pin output option for the OPAMPs output on PA6. I know you could route form PA6 to a neighboring ADC input capable pin, but not only would that occupy 2 pins, my PA6 is in use for UART, so not usable in my case. Thanks in advance.

Hi, i experimented the following configuration STEVAL-MKBOXPRO with BLEMLC code available within FP-SNS-STBOX1 package. For my specific application, i want to increase the BLE transmit power of the BlueNRG-LP chip of the MKBOXPRO. So i modified the code with the aci_hal_set_tx_power_level(1,31) +8dBm (since default value was  aci_hal_set_tx_power_level(1,4) -16dBm). Everything is fine with compilation with Cube IDE. But in practice with the app ST BLE Sensor v5.2.6, the real connection distance still remains about 25m, with a disconnect when RSSI is about -92dBm. These values are correct but what is not correct is that any tries to change aci_hal_set_tx_power_level with different "theoretical" power levels (from -54dBm to +8dBm) do not change anything in practice. It looks like aci_hal_set_tx_power_level has no effect on "real" transmitted poser. Any help will be welcomed to this topic. Thanks reading et thanks in advance or your help. Christian

Hi,I am working with the STM32MP135F-DK board and built an SD card image using Yocto Scarthgap (openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06).The image boots successfully. To prevent the Year 2038 (Y2038) problem, I confirmed that require conf/distro/include/time64.inc is already included and processed in the distro configuration.To test Y2038 compliance, I manually set the system time to the year 2040.The time was set successfully, and verifying it via the date command showed the correct time (2040).Checking the RTC using hwclock --show --verbose also returned the correct time in 2040.NTP is explicitly disabled via timedatectl set-ntp false, so network time synchronization is not causing any interference.The Problem:The issue occurs upon a reboot. After the system reboots, the time rolls back to the year 2024.My Analysis:Upon looking into the Linux kernel source (drivers/rtc/class.c), it appears that the kernel clamps or prevents system time overflow. This seems to be a fallback mech

Hello,Please review my schematic. I am using STM32F030RCT6TR. I have attached screenshots of the schematic and the peripherals interfaced with it. Recommend EMI/EMC related suggestions.NOTE: this STM will be controlled and is interfaced by ESP32 S3 for IO purpose by UART protocol. Following are the sections I have attached screen shots of:STM32 controller ICUARTRTCWATCHDOGDEBUG UARTDECAPAND GATE IC All suggestions/recommendations will be welcomedThank You!

Is the overcurrent protection set to 3A on the STSPIN840? If so, is there a way to change the trip value of the overcurrent protection to better align with its application? I want to change it so that the overcurrent trips at 1A. Thank you!

I have a STM32U585 (edit: ...VIT6, so not the one where this doesn't work due to errata) product with Trustzone enabled, Bootlock disabled and RDP level 0.I want to bring this into ST bootloader mode from software (for easy Firmware change via USB).To my understanding that would mean implementing the last entry of Pattern 12 from AN2606  Which means the following code, executed from secure side.RCC->APB3ENR |= RCC_APB3ENR_SYSCFGEN; //clock is disabled after startup, so enable __DSB();//make sure data is written SYSCFG->RSSCMDR = 0x1C0; //pattern from AN2606, RM says any value will do? __DSB();//make sure data is written __NVIC_SystemReset(); //SW reset But all I get is a restart to SECBOOTADD0. And RSSCMDR is zeroed out afterwards, even though the RM states that it is only affected by power on reset.What am I doing wrong?

After a long time, i started to look into using the BLE_Thread_dynamic stack image on WB55 again. First without success with my own code on my own board, which I do think to remember worked before.But afterwards with the BLE_Thread_dyn example on a WB55 Nucleo Board and that doesn't work as well. This is how the FUS Info looksAnd this is where it gets stuck Any Ideas what I might be doing wrong?I already tested with and without "Start Wireless Stack" from the programmer. Not using it, makes it stop even earlier, at hci_reset.Starting to look into older stack images now.Edit: I went back up to 1.18 (using the example code from 1.24, which seems to be untouched since way back) and nothing worked :thinking_face:.

We are developing a project using the STM32H743ZIT6 where RTC timekeeping is a critical requirement. During field testing we noticed significant RTC drift on our board. We tested the same hardware three times — each time flashing a different RCC_LSEDRIVE_* setting  to identify which drive level gives the best RTC accuracy. Sharing the full details below test results, firmware, and hardware in case others are facing the same issue.Quick Results We ran a 16-hour test measuring RTC drift on the same STM32H743ZIT6 board, flashed three times with a different RCC_LSEDRIVE_* setting each time."Drive setting Drift over ~16 hours PPM RCC_LSEDRIVE_LOW 69 seconds ~1161 RCC_LSEDRIVE_HIGH 30 seconds ~519 RCC_LSEDRIVE_MEDIUMHIGH 6 seconds ~101 RCC_LSEDRIVE_MEDIUMHIGH gave the best result by a large margin. RCC_LSEDRIVE_LOW — which is often recommended as the default — gave the worst result on our hardware.Hardware DetailsCrystalParameter Value MPN ECS-.327-6-12-TR Frequency

Hello everyone,I have encountered an issue with the STM32WB05KZ on a custom board which only allows me to flash the board under very specific conditions. The first time out of the box, everything works fine, I can flash using a ST-LINK V3-PWR straight from CUBEIDE V1.18.0. After this first time programming, the board becomes fully unresponsive to the debugger. My code does seem to run (verified by two LEDs connected to PB4 and PB5). When using STM32CubeProgrammer, the system reports that it's unable to read the Chip ID. After much trial and error, I've found that by disconnecting the reset pin from the debugger and pressing the Close Debug button in the Debug Authentication (which I haven't enabled anywhere) menu, I can connect to the board through the STMCubeProgrammer software. I was wondering if this behaviour is to be expected, because I can't find it in the Reference manual or Datasheet. And if this behaviour can be disabled. For context:- The board has a 32 MHz crystal and a

Hello,I'm sorry to bother again, but it seems there is another issue in the latest update of VSCode STM32IDE extension. While trying to Start Debugging with GDB Server (STM32Cube Debug STLink GDB Server v1.3.0), with launch.json as: "version": "0.2.0", "configurations": [ { "type": "stlinkgdbtarget", "request": "launch", "name": "STM32Cube: STM32 Launch ST-Link GDB Server", "origin": "snippet", "cwd": "${workspaceFolder}", "serverReset": "Connect under reset", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "runEntry": "main", "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ], "faultUnalignedAccess": false, "liveWatch": { "enabled": true, "samplesPerSecond": "4" }, "preRunCommands": [ "set output 16" ] } ] } The Debug starts and I get an error message as:PARSE ERROR: Argument: -cp (--stm32cubeprogrammer-path) Argument already set! Brief USAGE: C:/Users/.../AppData/Local/stm3

I've seen the other post, but my issue is different. I'm now getting:Rolling back doesn't seem to be fixing this issue, even though nothing about my setup has changed since 2 weeks ago.I can't even figure out if it's the update causing this issue thanks to this utterly useless update information:Spoiler (Highlight to read)Breaking ChangesComplete architecture redesign: The tool architecture has been split into three major building blocks with the purpose of creating a flexible, maintainable and updatable platform consisting of the following blocks: GUI, CLI tools and STM32 device support.Breaking ChangesComplete architecture redesign: The tool architecture has been split into three major building blocks with the purpose of creating a flexible, maintainable and updatable platform consisting of the following blocks: GUI, CLI tools and STM32 device support.What changed?!How am I supposed to update my 3.8 configs to 3.9?

We are designing an STM32-based SOM and want to know whether STM32H7 controllers support DDR memory, or if DDR support is available only in STM32MP series. Please suggest compatible STM32 controllers and reference designs for DDR interfacing.

Hello.I would like to use ST AIoT Craft with a SensorTile Box Pro and the MKI234AA DIL24 board to have an external LSM6DSV16BX IMU (different from the onboard LSM6DSV16X).Six months ago, in December 2025, the accelerometer and gyroscope data logging from the LSM6DSV16BX was visible in the ST AIoT Craft interface, and I was able to collect data successfully.Today, I can no longer select the LSM6DSV16BX device because it is no longer visible in the available sensor choices. As a result, I am no longer able to collect data from it.I find this situation rather surprising, and I understand that ST AIoT Craft has evolved since the version I was using in December 2025.However, when creating a new project, it is still possible to select the SensorTile Box Pro and then choose the external board STEVAL-MKI234KA. The issue is that during the data logging phase, the LSM6DSV16BX sensor never appears among the available sensors, making it impossible to collect accelerometer and gyroscope data from t

Hi,Thanks for your response.Where can I get schematic of STM32100E-EVAL or similar board?