Solved

 Hello,Years ago, I integrated the DFUSe DLLs (STDFU.dll, STDFUFiles.dll, STDFUPRT.dll, STTubeDevice30.dll) into my 32-bit .NET application to update firmware on my devices. Everything has been working perfectly and is still running smoothly.Now, I need to run my application as 64-bit, but unfortunately, the DFU DLLs are only available in 32-bit.I was able to obtain the DFUSe C++ project and successfully recompile it in 32-bit. However, when attempting a 64-bit build, I encountered multiple errors. Since I’m not very experienced with C++ (I mainly work with C# in Visual Studio and C with STM32CubeIDE), I couldn’t resolve the issues on my own.I’m looking for a way to obtain these DLLs compiled for 64-bit:STDFU.dllSTDFUFiles.dllSTDFUPRT.dllSTTubeDevice30.dllI understand DFUSe is considered obsolete, but this update method fits perfectly with my systems, which are fully based on it. I would prefer not to change anything in the infrastructure—just to have the DLLs compiled for 64-bit.

Hello, I am designing a device that will have an STM32L4 or maybe an STM32U and will communicate with an ESP32 for internet connectivity. However, at some point, I would like to update the firmware remotely, and have the ESP32 stop executing its conventional software and act as a programmer for the STM32. Is this possible? And if so, where can I find detailed information on how to do it? I hope you can help me, thank you.

Hi all,I followed this STM32CubeIDE tutorial to debug an STM32H7S3L8 project running from external flash (OSPI NOR). After flashing and starting the debug session, I get the following error:Break at address "0x8000B2C" with no debug information available, or outside of program code.Here is the log from STM32CubeProgrammer:STMicroelectronics ST-LINK GDB server. Version 7.11.0 Copyright (c) 2025, STMicroelectronics. All rights reserved. Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled Waiting for debugger connection... Debugger connected Waiting for debugger connection... Debugger connected Waiting for debugger connection... ------------------------------------------------------------------- STM32CubeProgrammer v2.20.0 ------------------------------------------------------------------- Log output file: C:\Users\Admin\AppData\Loca

Hi, I am running firmware for USBX MSC device. The example project  "Ux_Device_MSC" on demo board STM32U575I-EV.  MSC device is enumerated on computer and FATS file system is used. It can transfer file from computer to storage on STM32U575I-EV.  I am trying to figure out the following parameters. 1. how many times the following function in source file "ux_device_msc.c" is called when transfer a large file UINT USBD_STORAGE_Write(VOID *storage_instance, ULONG lun, UCHAR *data_pointer, ULONG number_blocks, ULONG lba, ULONG *media_status) { UINT status = UX_SUCCESS; /* USER CODE BEGIN USBD_STORAGE_Write */ UX_PARAMETER_NOT_USED(storage_instance); UX_PARAMETER_NOT_USED(lun); UX_PARAMETER_NOT_USED(media_status); ULONG WriteFlags = 0U; /* Check if the SD card is present */ if (HAL_GPIO_ReadPin(GPIOI, GPIO_PIN_0) == GPIO_PIN_SET) { /* Check id SD card is ready */ if(check_sd_status() != HAL_OK) { Error_Handler(); } /* Start the Dma write */ status = HAL_SD_WriteB

 Hey there,I’m trying to enable SPI on the NUCLEO-H7S3L8 using the Template_XIP project from STM32CubeH7RS, but I’m running into issues.First, I tried enabling SPI1 through CubeMX on the Template_XIP project, but it didn’t generate the necessary driver code. When I build, I get this error:/Users/++++++/STM32Cube/Repository/STM32Cube_FW_H7RS_V1.2.0/Projects/NUCLEO-H7S3L8/Templates/Template_XIP/Appli/Src/main.c:167:(.text.MX_SPI1_Init+0x96): undefined reference to `HAL_SPI_Init'collect2: error: ld returned 1 exit statusmake: *** [makefile:66: Template_XIP_Appli.elf] Error 1 So I made a new project from scratch for the same board, copied the relevant config from Template_XIP, and now CubeMX does generate the SPI code. But when I run it, I get a HardFault right away.I tried digging into it with the usual debug steps according to this blog "How to debug a HardFault on an Arm® Cortex®-M STM32" (SP was 0x2000FFDC, next addresses 0x20020000, 0x20010024…), but honestly none of it

Hello, I am quite new to this. I am generating a PWM signal(100Hz with 40% duty cycle) using Tim1 on my stm32f103c8t6(Bluepill). I want to take ADC readings(both ADC1 and ADC2 in simultaneous mode) during the high part of the PWM signal at a frequency of 1KHz. I want to understand how many timers would be required for this. Currently I am trying to use Tim2 set at 1KHz and trying to trigger it using the TRGO of Tim1. Then I am using TRGO of Tim2 as external trigger conversion source for the ADCs. However as far as I know for Tim1 PWM signal I can only get an interrupt for either when the signal start(Update Event) or when it goes from high to low(Output Compare). How can I get both interrupts so that I can start and stop Tim2.Any help would be appreciated.TIA

I have developed code (on the NUCLEO-L433RC-P) that uses shutdown and wake.The code works when I debug or run, but it stops working after a cold restart (power removed then reconnected).After a cold restart, the software runs correctly until the first shutdown is called.  Once shutdown is called, it seems to crash and I have to perform a reset.From power up, the MCU should run as follows...Run for 10 secondsShutdown for 5 secondsRun for 10 secondsShutdown for 5 secondsAnd so on.....This cycle should continue until 60 seconds is reached, when it should shutdown and stay shutdown.It should not wake again until the WKUP pin is pressedWhy does it seem to crash after the first shutdown (step 2 above) ?I am aware that RTC backup registers are lost when power is removed, but I cannot see this causing the problem.I have attached a flowchart diagram (wake_shutdown.png) to show how my code works.The relevant code is also belowmainMX_RTC_InitwakeConfigResetwakeConfigUpdatemcuSleepm

Hi,I've been using ST Edge AI Dev Cloud to benchmark my human activity recognition models on some ST platforms and I would like to do the same for the STM32N6570-DK but it only accepts quantized models and the quantization option throws and error:Executing with: {'model': '/tmp/quantization-service/0f29903b-6961-4c97-bde9-83219e06f56f/gmp_wl_24_human_activity_recognition_WISDM.h5', 'data': None, 'input_type': tf.float32, 'output_type': tf.int8, 'optimization': <Optimize.DEFAULT: 'DEFAULT'>, 'output': '/tmp/quantization-service/0f29903b-6961-4c97-bde9-83219e06f56f', 'disable_per_channel': False}Invalid value for argument `reduction`. Expected one of {'mean', None, 'sum', 'none', 'sum_over_batch_size', 'mean_with_sample_weight'}. Received: reduction=auto2025-07-31 09:19:58.238638: I tensorflow/core/util/port.cc:153] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them

Hello all,I'm evaluating the STM32H743VIT6 on a third-party development board. I tested it with the system clock configured at 480 MHz (double checked everything, and all looks absolutely fine in terms of configuration). I did enable the "overdrive" setting as is done in the LL example (PWR_VOS0_480MHZ).Thing is, it gets very hot while running at 480 MHz (haven't measure exact temperature, but one can't leave a finger on it for more than a couple seconds, so I'd say close to 70°C).Maybe that's fully normal and this chip in this package (LQFP-100) can't be run at 480 MHz. I'm not sure. I configured the clock for 400 MHz instead (and no overdrive), and the temperature drops a lot. It's a bit warm, but that's it. So fully normal.Any tips to run it at 480 MHz, or is it a lost cause? Going for a larger package (LQFP-208?) for my application is not an option. Would a small heatsink be an option? Or is running this at 480 MHz just not recommended at all? Is the overdrive mode needed

Hello, im trying to convert a .tflite model (encoder-decoder model, with only supported layers by stedgeai) to C-code to use it in my STM32CubeIde project.When using the command:/opt/ST/STEdgeAI/2.1/Utilities/linux/stedgeai generate --model model.tflite --target stm32n6 --st-neural-art I'm getting the following error output, im not really getting my head around:ST Edge AI Core v2.1.0-20194 329b0e98d WARNING: gemm_0 is not quantized WARNING: nl_0_nl is not quantized WARNING: gemm_1 is not quantized WARNING: nl_1_nl is not quantized WARNING: gemm_2 is not quantized WARNING: nl_2_nl is not quantized WARNING: reshape_3 is not quantized WARNING: gemm_4 is not quantized WARNING: nl_5 is not quantized WARNING: reshape_6 is not quantized >>>> EXECUTING NEURAL ART COMPILER /opt/ST/STEdgeAI/2.1/Utilities/linux/atonn -i "/local/projekte/Uni/Masterarbeit/EmbeddedModelsSt/gcode_prediction_dataset/gcode_prediction_model/STM_friendly_LSTM_model/st_ai_output/gcode_mo

Hi all! I'm using the Nucleo-H755ZI-Q board and trying to write a simple program where the LED should turn on (and stay on) only when I press the USER button (the blue one on the board). I’ve shared a screenshot of my code below. The code builds and debugs without any errors, but when I run it, the LED just starts blinking on its own... even when I haven’t pressed the button. What’s more interesting is that when I stop the program in the IDE, the LED keeps blinking, and it only stops if I enter debug mode again. I expected the LED to stay off by default and turn on steadily only when the button is pressed. Also, after flashing and starting debug, I only see a "Resume" button instead of "Run"... Not sure if that means something’s wrong or if it’s normal. Any help figuring this out would be great!my program

Currently the extention only builds an ELF file.How can I tell cmake to not only build an ELF file but also a HEX or BIN file?

Dear community,I am selecting an accelerometer to use in a project and I am looking for some advice.Essentially I am looking for the highest performance accelerometer (regarding noise) in the STM portfolio.The sensor requirements are: ~±2g scale support, I2C support (preferred), FIFO buffer, at least 1 (absolute) threshold interrupt. I am currently using the LSM303AGR in my design, which I am comparing to the LIS2DW12 and LSM6DSV16X as a potential replacement. For the comparison (see table), the most important factors are noise and active current consumption in high-performance mode. Note that the LSM303 and LSM6 are not pure accelerometers, since they offer additional functionalities (i.e., magnetometer & gyro). I am only interested in the performance of the accelerometer part.  SensorNoiseActive current consumptionCosts component(eu.mouser.com)Costs breakout board (eu.mouser.com)LSM303AGR3mg (RMS)40µA@200Hz€4.15€11.88LIS2DW1290μg/√Hz120µA€1.24€3.71LS

Hi,I am using STM32Cube_FW_H5_V1.5.0. I initialize a MPU region with the following code, using only LL-calls:LL_MPU_ConfigRegion(LL_MPU_REGION_NUMBER6, LL_MPU_REGION_PRIV_RW|LL_MPU_INSTRUCTION_ACCESS_DISABLE|LL_MPU_ACCESS_NOT_SHAREABLE, LL_MPU_ATTRIBUTES_NUMBER2, 0x90000000U, 0x9FFFFFFFU);The corresponding MPU register MPU_RLAR_Ax gets set to 0x9FFFFFE3, wich is obviously wrong because I wanted to select attribute#2 and instead the attribute field gets set to 0x1.For verification I did the same initialization using HAL-calls:MPU_Region_InitTypeDef region; region.Enable = MPU_REGION_ENABLE; region.Number = MPU_REGION_NUMBER6; region.AttributesIndex = MPU_ATTRIBUTES_NUMBER2; region.BaseAddress = 0x90000000U; region.LimitAddress = 0x9FFFFFFFU; region.AccessPermission = MPU_REGION_PRIV_RW; region.DisableExec = MPU_INSTRUCTION_ACCESS_DISABLE; region.IsShareable = MPU_ACCESS_NOT_SHAREABLE; HAL_MPU_ConfigRegion(&region);Now the MPU register MPU_RLAR_Ax gets set to the correct va

Hi everyone,I’m currently working with the ST25R3916B NFC reader and controlling up to 6 external antennas via a multiplexer. The antennas are activated sequentially, i.e., I switch between them one after another in a polling loop.However, I’m experiencing an issue where not all antennas work reliably in every cycle. Sometimes an antenna seems unresponsive or is not detected by a test card, even though it worked in earlier cycles.I suspect that the problem might be related to RFAL_worker() not being called frequently enough.Could that be the root cause?My current architecture is based on FreeRTOS, and I’m considering the following approach:Run RFAL_worker() continuously in a dedicated FreeRTOS task, perhaps at a high frequency or short interval.Run the other NFC logic (polling, tag handling, antenna switching, etc.) in the main task or another thread.My questions:1. Is it safe and recommended to call RFAL_worker() in a separate FreeRTOS task while performing the rest of the NFC logic i

Hi,I’m currently working with the ST25PcDemoApp. The project works well on its own—it can detect ST readers, read tags, and write NDEF messages successfully.Now, I’m trying to add FEIG reader (MR102) support. To do this, I copied the FEIG resource files provided in the SDK (readers\feig\resources\windows\x64) into the ST resource folder, as I had already set up the path to that folder in the project. I also included the FEIG library files from readers\feig\lib.In the application, I added the FEIG reader detection code (copied from ST25PC_NFC) into the scanForReaders() method in MainApp.java.When I first ran the project, I encountered the following error:java.lang.Exception: Old native Library Version of OBIDISC4J.DLL detected. Version 05.06.03 requested, but Version 05.05.02 detected To resolve this, I replaced the OBIDISC4J.dll with the updated one used in the ST25PC_NFC project, which successfully detects the FEIG reader.However, after updating the DLL and running the project ag

Hello,I am using the ST25R3920B NFC reader in wake-up. My goal was the interrupt pin only came to 1 when it detected the presence of a smartphone (or other strong RF fields), however currently the interrupt pin comes to 1 periodically without any RF sources close enough. This is my current configuration:if (rfalNfcGetState() != RFAL_NFC_STATE_IDLE) rfalNfcDeactivate(RFAL_NFC_DEACTIVATE_IDLE); /* Retrieve default discovery parameters */ rfalNfcDefaultDiscParams(&m_discParam); //m_discParam.notifyCb = m_fncPollNotification; m_discParam.p2pNfcaPrio = true; m_discParam.totalDuration = 1000; m_discParam.techs2Find = flags; m_discParam.wakeupEnabled = true; m_discParam.wakeupConfigDefault = false; /* Wake up mode configurations */ m_discParam.wakeupConfig.period = RFAL_WUM_PERIOD_50MS; // Check every 800 ms m_discParam.wakeupConfig.swTagDetect = false; m_discParam.wakeupConfig.irqTout = false; /* ST25R3920B does not support capacitive sensing */ m_discParam.wakeupConf

Hi!I am currently using the X-NUCLEO-NFC08A1 and NUCLEO-F411RE boards to develop NFC-V related applications. I am encountering an issue when trying to set the power level of the NFC08A1.I use the following function to adjust the power level:void set_power_level(uint8_t level) { if (level > 15) { level = 15; // Cap the level to a maximum of 15 } uint16_t powerID = RFAL_ANALOG_CONFIG_CHIP_POWER_LVL_00 + level; ReturnCode ret = rfalSetAnalogConfig(powerID); if (ret != RFAL_ERR_NONE) { platformLog("Error setting power level: %d\n", ret); } else { platformLog("Power level set to %d\n", level); } }However, this function does not seem to work as expected. I tested the tag reading range after calling set_power_level(0) and set_power_level(15), but there was no noticeable difference.I am wondering if this is the correct way to set the power level.Thank you.

In developing a bootloader and application for an STM32H5 project using STM32CubeIDE v1.19.0, and STM32H5xx HAL Driver v1.5.0.RC1; when I place the ISR at 0x08008200, I can start the debug process but the application appears to be stuck in void SVC_Handler(void) once an interrupt occurs. What's interesting is that if I adjust the ISR location to 0x08008000, or 0x08008400, and define VECT_TAB_OFFSET in system_stm32h5xx.c [along with changing definition of .isr_vector to 0x08008000/0x08008400 in LinkerScript.ld] everything behaves as expected; it's only when setting to 0x08008200 that things break. I previously had a build environment with STM32CubeIDE  v1.15.1 using v1.4.0 STM32Cube MCU package and everything worked fine then. Any guidance on where to look to zero-in on what might be the culprit?

Dear ST Developer Support,I want to enable LVDS panel on STM32MP257F-EV1 based on Android OS.I tried to modify device tree stm32mp257f-ev1.dts and stm32mp257f-ev1-overlay.dts to enable LVDS panel.But I could not enable it. When I revert the device fdt file, I saw that the LVDS related device tree nodes lvdsltdcpanel-lvdspanel-lvds-backlightdisplay-controllerstatus were "disabled".In stm32mp257f-ev1.dts and stm32mp257f-ev1-overlay.dts file, the LVDS related device note are status="okay".So, I confuse on this problem. Maybe somewhere dts overlay this device node, but I cannot find it.Would you help me solve this problem?Thanks.

Hello, I have recently started getting familiarized with the P-NUCLEO-WB55 kit, and I have run to my first big mess up. I was attempting to perform a wireless stack FUS routine over the STLink interface, and I might have set a wrong start address for the FUS_fw.bin file (which I have updated to v 2.00). Hence, it seems that I can no longer do a firmware update over the stlink.  The other main issue that I am also facing is that I cannot seem to get the board to boot up to DFU mode. I have tried the dongle, and it boots to DFU mode normally after toggling the switch. However, and correct me if I am wrong, If I follow the procedure outlined here: https://visualgdb.com/tools/STM32WBUpdater/connecting/ , I should be able to boot into DFU mode in the development board. Yet, it does not work. If this is salvageable, I would greatly appreciate any help/support you can provide. Thanks  

Hello and good day.When using my custom board, I am facing "The following has evaluated to null or missing" errors during code generation. I have tried a few variation of custom boards but I can't seem to solve the issue. FYI, this doesn't happen when generating code using ST evaluation boards.Is this an issue from my side?I am using the latest MCSDK v6.41 and STM32CubeMX 6.15.I have attached my project file for reference.Edit: I am using STMC Board Designer Version: 1.2.1 and I just uploaded the board design. 

Hi everyone,I'm starting a project using the STEVAL-MKI109D motherboard with the following sensor adapter boards:STEVAL-MKI247A STEVAL-MKI240KA My main goal is to collect sensor data wirelessly for analysis, rather than being tethered to a PC with a USB cable. I'm trying to figure out the best approach and would appreciate some advice on the options I've considered.

Greetings. I am a beginner and an electronic student and I am currently getting my hands on STM32H523. I have created a mcu board in Altium Designer just to control LEDs by GPIO, hopefully to understand more about STM32. I have the PCB fabricated, and the connection for ST Link v2 is SWDIO---SWDIO, SWCLK---SWCLK, GND---GND. I have also connected a wire at the VCC and GND to the 3.3v power supply to power up the MCU. For Boot0, I set it to HIGH since I see people saying that to program the MCU, I need to set it to HIGH. I have soldered everything and connect the board to st link, and I cannot debug. I was hoping if anyone can give me some guide, and here I will attach my schematic so you may spot out any design errors... Thank you very much, understanding the STM32 means a lot to me as I intend to use them in my future advanced projects.    

STLINK V3 stopped working after upgrade. Red light is flashing. Device manager - Unknown USB Device. NUCLO and DISCOVERY with ST-Link2 are still working! Installing dpinst_amd64.exe not help.