Product forums

Hi,I'm working on a custom STM32MP157C board with a Microchip LAN8742A PHY (RMII). Originally the board uses an external 50 MHz oscillator that feeds both the PHY and the SoC's PA1 (ETH1_RMII_REF_CLK) — the classic LAN8742A "REF_CLK In Mode" setup, same as ST's reference schematic. That works fine.I'm now trying to get rid of the external oscillator and have the SoC generate the 50 MHz REF_CLK itself instead, using RCC's CLK_ETH_PLL3Q — the setup ST documents in AN5031, Figure 45 ("RCC provides 50 MHz ETH_CLK"). For this test I desoldered the two series resistors that fed the oscillator signal in, isolated the oscillator, and bridged PA1 straight to the PHY's XTAL1/CLKIN through a wire + the same 22 Ω resistor as before. I also added st,eth-ref-clk-sel; to the ethernet node in both the kernel and U-Boot device trees, rebuilt and reflashed.Result: PHY never comes out of reset (phy_poll_reset failed: -110), and an oscilloscope on PA1 shows absolutely nothing — not even a weak or distorte

i recently install STM32cube IDE2.2.0 in my laptop and i m not able to generate .ioc file not pin configuration please give some solution.

I'm developing for the NUCLEO-WBA25CE1 using BLE_HeartRate. In the main function, I called MX_APPE_Init(NULL) followed by BSP_LED_Init() to initialize each LED, but they seem to be blinking rapidly throughout the operation. I want to disable this blinking, but I can't find where to do so. Could you tell me how to deal with this?  

Greetings.I'm a Linux user, I use Windows on a smaller notebook for tools like TouchGFX, but this is quite inconvenient.Is there any plan to release a Linux version of TouchGFX Designer?I saw in the documentation that there's a simulator and that it can even be used with Wine; I'll test it today, but it would be really good to have a native version.Link where I saw information about the simulator: https://support.touchgfx.com/docs/introduction/prerequisitesthanks

Hello,I am using an STM32L4R9ZIT6 in a new project. After replacing the MCU with a new one, the LSE oscillator stopped working. And the MCu doesn’t start until one activates the LSI.To troubleshoot the issue, we have:Replaced the crystal Tried different capacitor values Verified that the crystal works normally in another setupSince the only change was the MCU replacement, we are wondering what could be causing this problem. Do you have any suggestions on possible causes or additional checks we should perform?Thank you in advance for your help.Best regards,Roland

The new tooling is nice and the UI is much cleaner to navigate with.Positive Feedback ​@MorkBeck:We love the VS Code direction YES, it would be helpful to get H5 on here as well as it would keep our code bases aligned. AI? No thank you, “focus to stay on reliability, documentation quality, and API maturity”. As anyone savvy knows, AI scrapes those docs anyways. Good docs and samples help a lot.A few of issues we’re running into that are major speed bumps. I don’t know where your bug list is at to report or to see if it’s tracked:Code Generation overwrites our `main.c` EVERY TIME. Yes it’s documented above, yet this is painful. The `*.c.base@x.y.z” files are just absolute clutter!  “YAGNI” - You Ain’t Gonna Need It And i can’t disable it either, that option is always grayed out. Upgrading from CubeMX2 v1.01 to 1.1.1 Broke the EXTI configuration screen, and the page NEVER renders. Causes other lack of functionality issues Feel free to reach out to me. Inability to pull Packs dynamica

Using a new ST-LINK/V2，it always Error: Problem occured  while trying to connectI use the wire I bought before to connect it, it will be OKI want to know why this is 

Section 2.5 of UM3656 says "For a complete description of the library capabilities, refer to the vl53l9-transform-c documentation." The X-CUBE-53L9A1 v1.0.0 package ships Documentation/ media-object/transform-c.chm and media-c.chm, but those document the generic transform framework they do not contain any mention of VL53L9, binning or resolution.In vl53l9-transform-c, _retrieve_output_size() accepts only raw frame sizes 14842 (54x42) and 3844 (24x20); the stream capability tables likewise list only those two resolutions. Calling the pipeline at other binnings is rejected, so 18x14, 12x10, 8x6 and 4x4 produce raw data with no calibrated depth.The underlying algorithms appear resolution-generic — vl53l9_algo_extract() takes frame width/height, crop offsets and binning as parameters, the calibration offset map is bicubic-resized to arbitrary width/height, and the radial-to-perpendicular map is computed per width/height/binning.Questions:Is support for the other binnings planned, or delibe

Dear ST Community Team,I am working on an STM32H747 project with a custom bootloader and OTA update mechanism. The OTA download completes successfully, metadata is written, and CRC verification passes. However, after the OTA apply step, the device does not reboot into the new firmware. The system continues running the old application, and I never see the expected reboot message from the bootloader.Details: Device: STM32H7 series Bootloader checks metadata at 0x081E0000 Staging slot at 0x08100000, App slot at 0x08020000 OTA side writes metadata fields (magic, version, staging base, app base, slot size, image size, CRC) Logs show: "Download OK" and "Applying..." but no reboot occurs

Hello ST team,I noticed what appears to be a documentation typo in the STM32MPU Wiki page “How to configure TSN switch”, section 3.1 – Run the PTP stack.The documentation states:“dePTP stack is started by default. To start it using via systemctl:”but the command shown immediately after that sentence is:systemctl stop deptpI believe the intended command is:systemctl start deptpThis is also consistent with the later “How to trace the PTP stack” section of the same page, where the documentation correctly uses:systemctl stop deptpto stop the service, and:systemctl start deptpto start it again.The Qbv section also states that gPTP synchronization should be started beforehand and thatdeptpis started by default.Could you please confirm and correct the command in section 3.1 if this is indeed a documentation typo?Thank you.

Hello,Is it possible to pull Vref- lower then Vss? For reverse voltage protrection I use a diode and a resistor to create GND1. GND1 is then connected to VSS of the µC.Scematic. All caps omittedCan I connect Vref- to GND? See Image.Datasheet stm32c542ccThe datasheet does not specify.If I connect Vref- to GND1 all values i measure with the ADC must be against GND1 otherwise the result is off by the offset of GND1 to GND.

Hello, I’m having some issues connecting my sensor tile box pro to my pc via a USB cable and with an ST-Link V2. I’ve followed the documentation regarding DFU mode, and the board doesn’t respond to it in STM32 Programmer ( I’ve double checked  if its a data cable, and this was confirmed). With the ST-Link, my Device Manager recognizes the debugger, but it has issues communicating/connecting with the board. However, I am able to flash it via Bluetooth. Is there some initialization I missed?

Hello Team, I am using STM32N6,I am using about 50 GPIOs, all for SPI and I2C communications, and the VDD port supplies 200mA, Will the usage of all these pins consume less than 200mA, or do I have to widen the range of VDD? Also, what is the total max current consumed by the STM32N6 during its maximum processing, Please let me know.Thank you.

MCU / setupSTM32F746IGK, VDD = 3.3 V HSE 16 MHz, PLL: M=8, N=200, P=/2 → SYSCLK = 200 MHz (AHB=200, APB1=/4, APB2=/2) Scale 1 + Over-drive, FLASH_LATENCY_6 Already below the 216 MHz maximum Application executes from the ITCM Flash alias (0x002xxxxx; AXI alias 0x080xxxxx) Cortex I-Cache and D-Cache disabled at startup ART accelerator / prefetch enabled in HAL (ART_ACCELERATOR_ENABLE, PREFETCH_ENABLE) Bare metal, 1 ms cyclic scheduler, no RTOS X-CUBE-STL Flash TM every 1 ms: 1 KB window, HW CRC-32 (poly 0x04C11DB7, init 0xFFFFFFFF, word reverse in / reverse out). Expected CRC is a table built offline from the same image (zlib.crc32 / IEEE 802.3).What we see After several hours in RUN (typically ~11–19 h, not at POST), Flash TM returns STL_FAILED (0xD32D) on a 1 KB window. A software CRC of the same window also mismatches, so this is not only the CRC peripheral.On fail we dumped the 1 KB window from the CPU. The dump CRC always equals the TM computed CRC and differs from the programmed im

I have a custom board using an STM32G431RB (LQFP64) that was previously programmable/debuggable without issue. After switching to a new ST-LINK debugger, I started consistently getting:Error: ST-LINK error (DEV_TARGET_HELD_UNDER_RESET)Root cause identified: the board was being powered entirely from the debugger's VDD/VTref pin rather than an independent supply. Powering the board from an external bench supply (debugger providing only SWDIO/SWCLK/GND, not VDD) resolves the connection issue. My working theory is that the ST-LINK's VDD/VTref pin is intended as a voltage sense input, not a real power source, and different probe units/firmware versions apparently have inconsistent (often very limited) current-sourcing capability there — my original debugger happened to supply enough current for this board to stay stable; every replacement unit since (including confirmed-genuine ST-LINK/V2 and V3 probes) could not, leading to what looks like repeated brown-out resets rather than an actual st

Having problem getting STM32C091FCP6 that is new (not otherwise programmed) to respond to STLINK device at power on.Details-Preparing to move a project from STM32C011J6M6 to STM32C091FCP6 to obtain larger pin count and larger memory capacity. On first attempt to attach STLINK V2 device to the target containing a new STM32C091FCP6 (SWDIO, SWCLK and GND to a device on 3.3V power), STLINK not starting as expected (power is being applied before STM32CubeProgrammer is commanded to “Connect.”To rule out PCB layout error on the (new) STM32CX091FCP6-based version of project, I attached another (also new from supplier) MCU to STLINK V2 device attaching only SWDIO, SWCLK and GND to STLINK, applied 3.3V power (all other pins open), and again STLINK not handling “Connect” command as expected. STM32CubeProgrammer is reporting “unable to get core ID” and/or “DFU_TARGET_CMD_ERR.The development environment (STM32CubeProgrammer) and STLINK device firmware are up-to-date.The STM32C091FCP6 devices are fr

In the STM32H5 series security document, STM32H5F4 is missing from the OEMiRoT + OEMuROT support controller list. Is STM32H5F4 a derivative of STM32H5F5, and does STM32H5F4 have the same security support as STM32H5F5?  

Hello everyone,I am working on a custom locker controller board based on the STM8S208CBT6 in the LQFP48 package. I am using the Cosmic C Compiler inside the STVD environment and flashing the MCU via STVP with a standard ST-Link V2 clone.I am experiencing an issue where two specific pins, PD0 (Pin 41) and PC7 (Pin 34), are stuck at a constant logic high level ('1') when configured as standard digital inputs with internal pull-ups (GPIO_MODE_IN_PU_NO_IT), completely ignoring external buttons / shorts to GND. At the same time, six other GPIO pins configured exactly the same way work perfectly fine and detect shorts to GND without any issues.Here is the hardware configuration and what I have observed so far:1. PD0 (Pin 41) is multiplexed with TIM3_CH2, TIM1_BKIN, and CLK_CCO. On this 48-pin package, it is also right next to the SWIM pin (Pin 40). 2. PC7 (Pin 34) is multiplexed with SPI_MISO.3. The board relies on standard UART1 (TX on PA5, RX on PA4) for RS-485 communication, which must re

Hello,I am working on an STM32 USB CDC (Virtual COM Port) device using the STM32 USB Device Library (CubeMX-generated project).My goal is to have the device appear on Windows as a custom COM port name such as:MO3 Device (COMx)However, I want to achieve this without using a custom INF file, since distributing and installing drivers on every PC is not practical for my use case.From my current understanding:The Product String (iProduct) in usbd_desc.c can be modifiedThe Interface String (iInterface) in the CDC descriptor may also influence the displayed nameWindows typically uses usbser.sys and assigns "USB Serial Device (COMx)" by defaultFriendly Name seems to be controlled primarily via INF, not firmwareI have a few specific questions:Is there any reliable way to influence or override the COM port Friendly Name purely from STM32 firmware (USB descriptors), without an INF file?Does modifying iInterface (or using IAD / composite device descriptors) improve the likelihood of Windows using

I am trying to use touchgfx and gfxmmu on H7R7 with a round lcd panel,but failed. So ,Is there a demo of this kind?

I am currently working with the VL53L1X Time-of-Flight (ToF) distance sensor and am experiencing inaccurate and inconsistent distance measurements.The sensor is able to detect objects and provide distance readings, but the measured distance does not consistently match the actual physical distance. I have observed variations/errors in the distance readings even when the target position remains unchanged.Could you please help me identify the possible cause of this issue and suggest the recommended configuration or calibration procedure?I would appreciate your guidance regarding the following points:* Recommended initialization and configuration settings for the VL53L1X.* Recommended timing budget and ranging frequency settings.* Calibration procedure for accurate distance measurement.* Recommended offset and crosstalk calibration procedure.* Effect of target reflectance, ambient light, and target size on measurement accuracy.* Recommended sensor mounting and target conditions for reliabl

Hi, STNow I followed the X-NUCLEO-53L7A1 User guide connection for the SATEL-VL53L7A TOF breakout boards LEFT and RIGHT Connection as Shown in the attached image and it worked well, even if there are 2.2K pull up resistors for each sensor which makes the equivalent pull up resistor = 2.2K / 3 but I worked well till I also added another 2 SATEL-VL53L7A TOF breakout boards in addition to 1 Barometer Sensor breakout board which has the part number STEVAL-MKI225A it started to make undefined behaviors such as (TOF sensors Initialization fault, Barometer Sensor Initialization fault, Barometer wrong readings).So, could this problem caused by another 2 SATEL-VL53L7A TOF breakout boards with there Pull-up resistors?and If yes, Should I remove the 0 Ohm resistors on solder bridges to disconnect the pull-up resistors from each sensor as shown in the second attached image?

 I have been reading the discussion here: Understanding the bootloader GO command on the STM32H5 seriesI am trying to understand one point in particular. The discussion describes the problems associated with using the bootloader GO command on STM32H5, and refers to the state of the device and peripherals when the bootloader transfers control to the application. Does the H5 system bootloader GO command actually support transferring execution to an application loaded into SRAM? I ask because the wording left me uncertain about whether the issue being discussed applies to SRAM applications, Flash applications, or both. Perhaps ​@STea or someone else from ST, could clarify please?

I am currently working with an STM32 MCU and facing an issue while trying to connect the board to my PC using an ST-LINK debugger. The board powers on normally and there does not appear to be any obvious hardware issue, but STM32CubeProgrammer is unable to detect the target device. The connection attempt either fails or reports that no target is found, so I am currently unable to program or debug the MCU.So far, I have checked the basic connections and setup:USB cable and ST-LINK connection Board power supply and voltage SWDIO and SWCLK connections STM32CubeProgrammer installation ST-LINK firmware and connection settingsI am not sure if the problem could be caused by the MCU configuration, SWD interface, boot mode, or some setting that may have been changed in the firmware. I would also like to know if there are any recommended STM32CubeProgrammer options or recovery procedures that should be tried when the target MCU is not detected.Has anyone experienced a similar issue with an STM32

I am trying to build a STM32L0 based low powered project , i am hitting target hold under reset randomly and when i left it power off for few hours its back to working . idk why its happening randomly