Recently active topics

Hello,I am working with an STM32N657 on the NUCLEO-N657X0-Q and I am trying to use the Ethernet PTP PPS signal as a hardware start trigger for TIM3.TIM3 is configured as follows: HAL_TIMEx_TISelection(&htim3, TIM_TIM3_TI1_ETH1_PPS, TIM_CHANNEL_1);sSlaveConfig.SlaveMode = TIM_SLAVEMODE_TRIGGER;sSlaveConfig.InputTrigger = TIM_TS_TI1FP1;sSlaveConfig.TriggerPolarity = TIM_TRIGGERPOLARITY_RISING;sSlaveConfig.TriggerPrescaler = TIM_TRIGGERPRESCALER_DIV1;sSlaveConfig.TriggerFilter = 0;HAL_TIM_SlaveConfigSynchro(&htim3, &sSlaveConfig);TIM3 itself uses an external clock on ETR2 and should only be enabled by the rising edge of ETH1_PPS.The internal connection works correctly when I use the normal/fixed PPS mode.For example: ETH1->MACPPSCR = 1U;In this case the PPS rising edge reaches TIM3, TIM3->CR1.CEN becomes set, TIM3 starts counting and the rest of my application starts correctly.However, I cannot get the same internal connection to

Hello,on a shared SPI bus (one master, several slaves, one NSS line per slave, the "Standard multislave communication" topology of RM0456 §68.4.5), an STM32U5 SPI slave with hardware NSS sometimes ends a transaction early. EOT is raised 112 or 126 bytes (frames) before TSIZE, with no UDR, OVR, MODF or FRE flag. The slave then stops driving MISO, so the master receives the last ~110 bytes as 0x00, while on the slave the HAL reports a normal "transfer complete". The data corruption is silent.When it happensEach slave prepares its next transfer on its own, with HAL_SPI_TransmitReceive_DMA, which sets SPE as its last step, and then raises a "ready" GPIO for the master. So the call sometimes falls while the master is clocking another slave: this slave's NSS is high and SCK is toggling. That is the only case in which the failure appears.With only one slave active (no foreign traffic on SCK) it never happens. It is the instant SPE is set that matters, not the DMA setup. Our workaround: prepar

When using I2C peripherals with an STM32, occasional NACKs or communication timeouts can be difficult to diagnose.How do you usually approach debugging these issues? Do you start by checking the bus signals with a logic analyser, reviewing the timing configuration, or inspecting the firmware error handling?I'd be interested in hearing which debugging techniques have been most useful in practice.

  I am integrating the STSAFE-A110 as a secure element with the STM32H523 as the host MCU. I am using the latest version of the X-CUBE-STSE01 middleware and want to establish and use a secure channel between the secure element and the host. Using the Host Key Provisioning example provided in X-CUBE-STSE01, I provisioned the Host MAC and Host Cipher keys into the secure element. I want to store 12 bytes of data in data partition index 2 during provisioning and read the data back during runtime in the host environment. Currently, I can successfully store and read the data using the following APIs with STSE_NO_PROT:             stse_data_storage_update_data_zone()            stse_data_storage_read_data_zone() However, I want to perform these operations using STSE_HOST_C_MAC_R_MAC, as this is the Host Session protection mode supported by X-CUBE-STSE01. On one board, I receive the STSE_INVALID_C_MAC error. I provisioned the keys on another board, but on that board, I receive the STS

Hello ST team,I am using MCSDK 6.4.1 with a custom STM32G431CBUx inverter board. My external ESC PWM signal is physically connected to PB10.As shown in the two attached images:1. Motor Control Workbench shows PWM_ESC_INPUT on PB10 / TIM2_CH3.2. After code generation, STM32CubeMX shows M1_PWM_INPUT on PA15, while PB10 is unconfigured.Why does the generated configuration differ from the Workbench setting? Is this a known limitation or a configuration issue?How can I use PB10 / TIM2_CH3 with the native MCSDK ESC functionality?Thank you.  

Hi there!I’m having an issue when flashing / debugging with the STLINK-V3SET + ISO (V3J17M11B6S1). From VSCode I get the error Error: Unable to connect to the target device, Access port is not valid. This issue does not appear when using STLINK-V3MINI (V3J17M10).I updated STM32CubeProgrammer vscode bundle to 2.23.0 and then code upload / debug worked once and now I’m getting the Access port is not valid error again. I tried setting the “serverApID” in the launch.json to force the correct Access port however I can’t get this to work.Is this a known issue? I made a log for both debuggers:STLINK-V3MINI V3J17M10:STMicroelectronics ST-LINK GDB server. Version 7.13.0Copyright (c) 2026, 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

Can the VNL5050N3-E operate reliably with a 3.3V Input logic signal while switching a load of maximum 2A?

Hello,I am designing a wall-mounted touchscreen panel using a VL53L1CB for wake-up and person/presence detection at approximately 2–3 metres. High absolute distance accuracy is not required, but detection must be reliable without frequent false triggers.The sensor will be mounted behind a single 0.70 mm cover glass. I have read AN5231 Rev. 2 and UM2133.The proposed optical construction is:Single-layer 0.70 mm cover glass Sensor mounted parallel to the glass Air gap kept at or below approximately 0.30 mm, if mechanically possible Full-height black gasket/light barrier between the Tx and Rx sides Separate clear apertures for Tx and Rx in the black printing/coating Target transmission above 87% at 940 nm and haze below 1% at 940 nm Crosstalk and offset calibration performed after final assemblyThe first production batch will consist of 15 mechanically identical units.I would appreciate clarification on the following points:AN5231 recommends a cover-glass thickness below 0.6 mm, an air gap

Hardware and software MCU: STM32F411CEU6 Board: WeAct Black Pill V3.0 IDE: STM32CubeIDE 2.2.0 Programming tool: STM32CubeProgrammer 2.21.0 Host OS: Windows 11 Application: Existing application built as an ELF and BIN file (approximately 69.11 KB) Current programming method: JTAG/SWD, which works correctly Board reference: https://stm32-base.org/boards/STM32F401CEU6-WeAct-Black-Pill-V3.0.html#Reset-buttonThe reference page describes the F401 version of the board; my board uses the STM32F411CEU6.ObjectiveI want to program a fixed application binary (.bin) directly using STM32CubeProgrammer over USB DFU or UART, using the STM32's factory-programmed system-memory bootloader.I am not developing a custom bootloader or implementing field firmware updates. The same application currently programs and runs correctly through JTAG/SWD.1. USB DFU behaviourI enter system-memory boot mode by holding BOOT0, pressing and releasing NRST, and then releasing BOOT0.Windows detects the device th

ProblemSTM32_Programmer_CLI.exe -c port=SWD sn=<sn> and -l stlink-only each take ~30 seconds (sometimes much more) under v2.23.0 when launched programmatically by another application (CreateProcess, stdio redirected to pipes, no console window) — the pattern any automated test/programming tool uses. CPU stays near-idle during the delay.Expected behaviorSame as v2.22.0 and same as running the CLI interactively on v2.23.0: under two seconds. Reinstalling v2.22.0, with no other change to our application, fixes it immediately.What doesn't explain itRuled out through direct testing: console presence, output redirection style, handle inheritance, antivirus, elevation, 32/64-bit calling process, working directory, concurrent vs. sequential calls, a full reboot, network reachability (disabled proxy auto-detect, firewall-blocked the exe, disabled WiFi entirely — none changed the timing), and the local Analytics\TrackedData.json cache (already empty).A Process Monitor trace of a slow call

Hello,I am evaluating cryptographic performance for a secure boot using a NUCLEO-H533RE board and the OEMiRoT example from STM32CubeH5.I compared two AES-128-CTR implementations:Software: mbedtls_aes_crypt_ctr(). Hardware-backed: bootutil_aes_ctr_encrypt() using SAES.The mean encryption times are:Input size Software SAES-backed implementation 32 bytes 10.55 µs 29.46 µs 256 bytes 76.70 µs 222.88 µs 1024 bytes 303.50 µs 886.02 µs  For an academic comparison, is it accurate to describe this result as “software AES-CTR versus SAES ECB with software CTR and driver protection overhead”? Thank you!

Hi!I'm trying to developing a Qt6 QML application with Vulkan support. But I having some issues. Can ST Dev Team give me an example of an Qt6 QML application that use Vulkan? It must work on STM32MP257. It will be a reference. I think I having wrong code settings on my Qt6 QML application. For OpenGL, it works. But not for Vulkan.Thank you!

Hello,Any idea how to get the price history for the part “STM32L053C8T6” ? (specifically on Sept06 th)I have a quotation conflict with my supplierThanksMiki

Hello,I am working on a requirement involving XIP (Execute-In-Place) from external QSPI flash on the STM32U5G9 and am encountering an issue executing the application from external flash.I have developed a working external flash loader for my QSPI memory and successfully programmed a simple GPIO toggle application into external flash.In the bootloader, I initialize the QSPI interface, configure the flash in memory-mapped mode, and then jump to the application located at 0xA0000000.Using the debugger, I can confirm that execution reaches the application's Reset_Handler at 0xA00002B4. However, when executing the very first assembly instruction, the processor enters HardFault_Handler at 0xA0000458.The fault status registers indicate: CFSR = 0x00000001 (Instruction Access Violation) HFSR = 0x40000000 (Forced HardFault) MPU is disabled VTOR = 0xA0000000 I have also verified that the application vector table contains valid stack-pointer and reset-handler addresses, and that the external

I am reading through AN5464 and UM1052 looking through the PID tuning sections.https://www.st.com/resource/en/application_note/an5464-position-control-of-a-threephase-permanent-magnet-motor-using-xcubemcsdk-or-xcubemcsdkful-stmicroelectronics.pdfhttps://www.st.com/resource/en/user_manual/um1052-stm32f-pmsm-singledual-foc-sdk-v43-stmicroelectronics.pdfTypically one would tune the inner loop PI for Torque and Flux then go onto tune the outer loop position PID. The calculated position control PID parameters for the project by default are completely unstable. I am looking for any documentation around the recommended method of tuning the inner loops as in both the Flux and Torque PI parameters. Is there anything along these lines available?

Hi, does VL53L4ED support a programmable FoV? I am looking for a ToF sensor with extended temperature range, but require a narrower FoV and range up to ~2000mm.Thanks!-BH

I have a project which could use both OCTOSPI RAM and Flash but I also need an OCTO or Quad SPI port for a high speed ADC.It is unclear whether OCTOSPIM_Px_NCS1,2 can be configured to allow the memory to share one OCTOSPI portand, if so, how to do it.  It is entirely possible that I am missing something but I would appreciate input on the topic.Thanks. 

Hi all, I have designed a target board that operates at 2.5 to 3V. Is the STLINK-V2 SWDIO and SWCLK 3V3?Will it damage my board?Is the STLINK VAPP pin an input or an output i.e. does it sense my target supply voltage and level-shift accordingly?If so, will it be fairly high impedance i.e. not draw too much current from my target?The wording in the STLINK doc is unclear: 

New question split from this post.HiThank you for your response. Unfortunately, our PCB is already in the prototype phase and we need to find a solution to power up the board for at least some basic testing.Then, on STM32H725REV6, are both Direct SMPS and Bypass (external VCORE on VCAP, VDDSMPS tied to VSS, PWR_EXTERNAL_SOURCE_SUPPLY) officially supported supply configurations?BRGilberto

I am trying to configure IEEE 802.15.4 packet sniffing on a NUCLEO-WB55 using STM32CubeMonitor-RF and Wireshark.I flashed the following firmware: Wireless coprocessor (M0+): stm32wb5x_Mac_802_15_4_fw.bin from STM32Cube_FW_WB_V1.24.0 Application (M4): Mac_802_15_4_Sniffer_Nucleo.bin from STM32CubeMonitor-RF IssueThe sniffer is detected successfully as a USB Virtual COM Port, and Wireshark recognizes it as an STM32CubeMonitor-RF 802.15.4 sniffer.However, no packets are captured, even when transmitting IEEE 802.15.4 frames from another STM32WB board.Troubleshooting Performed Tested both USB and ST-LINK/SWD connections. Verified USB device and serial port detection. Verified Python, PySerial, and Wireshark compatibility. Confirmed Wireshark recognizes the sniffer interface through extcap. Tested direct capture using stm32cubeMonRf_sniffer.py. Tested capturing through Wireshark and STM32CubeMonitor-RF. Configured matching IEEE 802.15.4 channels. Verified that the transmitter

I believe I’ve encountered an Issue with the current version of the STM32 HAL2 and wanted to raise an issue, but I’m not sure where best to raise the issue.The one of the new features in the new HAL2 hash is that HAL_HASH_Update can handle input sizes that don’t perfectly line up with the block size, using HASH_SaveRemainingBytes to save any excess bytes at the end of a call and then calling HASH_AppendLastIncompleteWord at the next call to write those excess bytes to peripheral along with using some bytes from the new buffer to bulk it up to 4. This means that I can write something like: (where the buffer is 163 bytes long)HAL_HASH_Update(&hhash, &u8InputBuffer[0], 10,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[10], 10,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[20], 1,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[21], 62,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[83], 7,0xFFFF);HAL_HASH_Update(&hhash, &u8InputBuffer[90], 73,0

The MCU STM32G031K8T6 has the BOOT pin is in the same pin as the SYS_SWDIO. Should I just disregard the BOOT pin and allocate the function to SYS_SWDIO? I am not sure what is the function from the BOOT pin... the internet says:“Flash Memory Boot (Normal Operation): When the BOOT pin is pulled low (to ground), the microcontroller boots from its internal main flash memory, running the primary user application. [1, 2] System Memory Boot (Firmware Updates / ISP): When the BOOT pin is pulled high (to VCC), the chip bypasses user flash and boots into a factory-installed, read-only bootloader in system memory. This allows you to program or update the chip's firmware via serial interfaces like UART, USB, SPI, or I2C without needing an external hardware programmer. [1, 2]” The Nucleo (Nucleo NUCLEO-G031K8 Eval Kit) schematic for the G03 MCU does uses SYS_SDIO (the T_JTCK),and depopulates the pull down resistor from BOOT.Will my board NOT run my code automatically UNLESS I pull that resistor dow

Can I attach a hand-wound enamelled copper wire coil (about 0.05 to 0.1 mm wire) directly to the AC0 and AC1 pads of the UFDFPN5 package, with the chip mounted pads-up and the wire joined using solder or conductive epoxy, and no PCB? Is there any ST guidance or reliability concern with this?

Hi,  we use on a design a ISM6HG256X. We want to detect a shock end event using the interrupt INT2.We use this configuration :    * INT2_HG_WU = 0    * INT1_HG_WU = 0    * INT2_HG_SHOCK_CHANGE = 1     * INT1_HG_SHOCK_CHANGE = 0Logically, we should have an interrupt INT2 only when the shock event end is detected. In fact, we have an interrupt at wake_up event and at the shock end and sometimes we have interrupt on INT1. We use a STEVAL - MKI248KA to evaluate the ISM6.Do you have some tips to solve this problem?