Product forums

Hello,When I right-click - create a new .c source file in a new STM32CubeIDE TouchGFX project, the file gets created in the STM32CubeIDE/Appli/Application/User/Core directory.  However, all the project source files are under Appli/Core/Src and headers in Appli/Core/Inc.  Is this normal and ok?  Why have the separate source file locations?Thank you 

Summary: With the STM32Cube VS Code extension (3.9.0, bundle-based), launching a default stlinkgdbtarget debug configuration fails with a GDB timeout and no visible server error. Root cause found: the extension does not pass the CubeProgrammer path when spawning the bundled ST-LINK_gdbserver, which then dies parsing its factory config.txt (the -cp line still contains the literal placeholder). Two workarounds verified below. Question: is the automatic path resolution expected to work for classic CubeMX CMake projects, or is this a bug? [Part Number] STM32H753ZITx (NUCLEO-H753ZI, on-board STLINK-V3)[Environment]STM32CubeIDE for VS Code extension 3.9.0 (bundle-manager based), Windows Project: classic STM32CubeMX 6.16 generated CMake project (not CubeMX2) Bundles under %LOCALAPPDATA%\stm32cube\bundles: stlink-gdbserver 7.12.0+st.2 and 7.13.0+st.3; programmer 2.21.0 and 2.22.0+st.1[Details — symptoms]F5 on the default configuration fails with:bound doStepConnectToTarget Failed: Remote repli

TouchGFX version: 4.26.0Visual Studio version: 18.6.3When TouchGFX generates or updates the “TouchGFX/simulator/msvs/Application.vcxproj” file it creates lines with<ClCompile Include="path/to/some/file.cpp"/>but Visual Studio updates the lines to <ClCompile Include="path/to/some/file.cpp" />. Notice the extra space. This means that in version control sometimes commits will be added without the space and sometimes with the space. This overcomplicates merges and causes merge requests. Please update the XML library or fix the output to be consistent with Visual Studio.

Why after last update the pins PD7 , PD6 are only with USB_OTG_HS functions: 

──────────────────────────────────────────────SUMMARY──────────────────────────────────────────────While porting an existing STM32L4 project to an STM32L562CE target, source-levelbreakpoints are never hit and adding watch expressions fails with "No symbol incurrent context". The target runs normally (no fault), and manual pause resolvesto a plausible source line, but no symbolic debug capability works. Behaviour isidentical across both the ST-Link GDB server and the SEGGER J-Link GDB server,indicating a target/build-side cause rather than a debug-probe cause. ──────────────────────────────────────────────ENVIRONMENT──────────────────────────────────────────────- Target MCU    : STM32L562CE (Cortex-M33, ARMv8-M), Device ID 0x472, Rev Z, 512 KB- Target board   : External custom/eval STM32L5 board (self-powered, 3.3 V)- Debug probe    : On-board ST-Link of a NUCLEO-L476RG, used to program the           external L5 target via CN4 SWD (CN2 jumpers removed)- ST-Link firmware : V2J47M34 (ST-L

I have replicated the MB1936 Schematic for a dash-cam system based on the MP257FAIx series by choosing the relevant circuits from the reference to design my custom PCB. I would love to seek help from the community for the following requirement. If anything pops up my mind, I shall update on this thread - Can I use the 5-pin MOLEX/JST GH Signal Connectors to interface the Waveshare IMX335 USB Camera Module? I have used the USB Host Port Architecture to implement my logic, and it has worked well. Kindly find the Schematics PDF for your reference. Thank You!

Hi experts:    I’m working on NUCLEO-G031K8 trying to use its I2C2(I2C1 is OK),I set PA11/PA12 as SCL/SDA, pull-up, OD, when I tried to read data, I found SCL is always high, but SDA has datas, I can’t figure out what’s missing, can you help me with that?Bill 

I’m trying to have my own TCP Client with NetXDuo that I can configure with CubeMX in VSCode for the Nucleo-N6.There is an NetXDuo Echo Client example project in N6 FW1.3.0 and 1.2.0 releases. The 1.2.0 version of the sample has no IOC but works in VSCode, the 1.3.0 version has the IOC file but doesn’t work in VSCode.I’ve additionally started from CubeMX and generated a fresh project with the matching configuration from the sample project and attempted both a static IP and DHCP (this works with the sample code) but can’t get either functionality to work.Is there an IOC version of a TCP client with NextXDuo somewhere that is based on CMake that I can integrate into VSCode that has proven to work with either a static IP and DHCP? I have searched countless times and I can’t find any.

 I’m working with my stm32f769-DISCOvery board.I’m trying to work through a few things that are unfinished/missing with the various buildroot configs on github and the stock one in buildroot.On boot, it crashes like this:[    1.705669] Unhandled exception: IPSR = 00000006 LR = fffffffd I’m apparently hitting an error with binutils newer than 2.28.1.It’s looking like this report, except I have also managed to get fffffff1 instead of fffffffdhttps://github.com/fdu/STM32F769I-disco_Buildroot/issues/1#issue-340504566This emcraft patch seems to be intended to mitigate the crash:https://github.com/EmcraftSystems/linux-upstream/commit/2882de1d86bd536c855feee582d44722434c2ac9In theory, the fix should be upstream as as well, and the 5.15 kernel i’m playing with should be new enough. (I’ll need to validate that I guess)https://github.com/torvalds/linux/commit/afc9f65e01cd114cb2cedf544d22239116ce0cc6 Looking at this:https://github.com/fdu/STM32F769I-disco_Buildroot/issues/1It seems it is caused b

We are considering using the L6387ED with an STM32G431 powered at 3.3 V.The L6387ED datasheet appears to specify a minimum input high-level threshold, VIHV_{IH}VIH​, of 3.6 V under some conditions, which would not guarantee recognition of a 3.3 V STM32 GPIO high level over process, voltage and temperature.However, the ST B-G431B-ESC1 reference board appears to connect STM32G431 3.3 V PWM outputs directly to L6387ED inputs.Could you please confirm the following:Is direct connection of a 3.3 V STM32G431 GPIO to the L6387ED input officially guaranteed across the full operating temperature range and production tolerances? If yes, which datasheet specification or characterization data guarantees this compatibility? What is the guaranteed maximum VIHV_{IH}VIH​ for the L6387ED at VCC=12–15 VV_{CC}=12\text{–}15\ \mathrm VVCC​=12–15 V, over the full recommended temperature range? Does the B-G431B-ESC1 rely on typical rather than guaranteed input thresholds? If direct 3.3 V drive is not guarante

On the H743 using V1.12.1 library, CubeIDE,  the USB_CoreReset() procedure occasionally fails to reset the Host USB core in debug mode.  I have added a reset call which seems to fix the issue in debug, reproduced below.I would like to know if this is a known issue in CubeIDE debug mode?See fix below in USB_CoreReset() // mod - added extra reset as in debug the USB host core fails to reset correctly at timesstatic void USB_Hard_Reset(USB_OTG_GlobalTypeDef *USBx){/* Example from USBH_LL_Init() in usbh_conf.c USB_HOST/Target/__HAL_RCC_USB_OTG_HS_FORCE_RESET();HAL_Delay(50);__HAL_RCC_USB_OTG_HS_RELEASE_RESET();HAL_Delay(50);/* --- FS BACK-POWER FIX START ---HAL_PWREx_EnableUSBVoltageDetector();uint32_t to = 100000;while (__HAL_PWR_GET_FLAG(PWR_FLAG_USB33RDY) == 0U && to--) ;assert(to > 0);*/uint32_t timeout;/* 1. Mask all interrupts and stop AHB transactions */USBx->GINTMSK = 0U;USBx->GAHBCFG &= ~USB_OTG_GAHBCFG_GINT; // disable global int/* 2. Wait for AHB idle */time

Hello,I am making a device which will play encoded audio files from a (Q)SPI flash and I wanted to use the STM32C55 (with its internal DAC). Alas, I haven’t been able to find flash/RAM/CPU frequency requirements for the codecs except for MP3 Helix (https://github.com/liuduanfei/helix), but I would rather use Opus because it has a better bitrate-to-quality ratio.Does anyone have experience with decoding audio on the STM32C55 (or any similar MCU for that matter)? How much flash and RAM was needed for the decoder?Thanks.

I am into configuring a STM32H750VBT6 and I want to configure ETMv4 inside the code of the program and my objective is to detect and capture data on 5 trace pins.I configured all trace pipeline including, CSTF,ETF,ETM,DWT and TPIU. also I considered opening Locks, enabling TRCENA in CoreDebug_:DEMCR and enabling required clock domains in DBGMCU_CR.After all I am just sighting clock signal on TRACECLK pin. I also checked TPIU unit if it successfully outputs test patterns like AA55 and FF00. Test patterns worked properly but when disabling test pattern only clock comes out through the trace pins.I am looking for someone who configured that before to help me prevail it.here are my functions:#include "ETMv4.h"#include "core_cm7.h"uint32_t startAddr = 0;uint32_t stopAddr = 0;void Parallel_Trace_configure(){ TraceGPIO_Configure(); Disable_ETM(); TPIU_Configure(); ETF_Configure(); CSTF_Configure(); ETM_Configure(); SetupStartStopAddr(); DWT_Configure(); Enable_ETM();}void TPIU_Config

Hi everyone,I designed a board around the STM32G474 and I'm trying to use an external 24 MHz HSE crystal, but the crystal won't run under any configuration — the generated SystemClock_Config() call to HAL_RCC_OscConfig() returns HAL_ERROR and I land straight in Error_Handler() (infinite while(1) loop).Crystal I'm using:Manufacturer: Diodes Incorporated Part Number: FL2400159 Frequency: 24.0000 MHz Package: 3.2 x 2.5 mm, 4-pad ceramic SMD (Saronix-eCera FL series) Load Capacitance (CL): 18 pF ESR (Equivalent Series Resistance): 30 Ω Frequency Tolerance: ±10 ppm Frequency Stability: ±15 ppm Operating temperature: -40°C ~ +85°CLoad capacitor values I've tried (0603 package, X7R):22 pF 12 pF 28 pFSame result with all three: error. Based on the load capacitance formula (Cext = 2×(CL − Cstray), assuming Cstray ≈ 3-5pF), 28pF should be the closest to ideal, but even that didn't work.What I've checked/done so far:CubeIDE → RCC → High Speed Clock (HSE) is set to "Crystal/Ceramic Resonator" (not

Hello,How can I configure CubeIDE V2.1.1 to automatically swtch back to C/C++ perspective when GDB connection is lost?Best regardsMich

I am experiencing a critical issue with the hardware video encoder (VENC) on the STM32N6 when processing low-light frames.Setup: Sensor: IMX335 connected to STM32N6 Capture Pipeline: DCMIPP configured in 1080p@15FPS capturing and writing to RAM in RGB565 format. Encoder Input: The same RGB565 buffers are passed to the VENC. Storage: The encoded H.264 stream is saved directly to an SD card. The Problem:When the camera enters a dark environment (very low-light conditions) and I manually reduce the Gain/Exposure to very low values (where the image should be almost completely black), the video recorded on the SD card starts to progressively brighten up until it becomes completely white (a "flashbang" effect).When playing back the file on a PC, the transition from black to fully white takes about 1-2 seconds (accumulating over several frames).Key Observations & What I've Already Tested: DCMIPP Output is OK: I have a live preview on an LCD screen displaying the input buffers direct

When the connection fails “unexpectedly”, CubeIDE keeps re-trying for a long time: Although “unexpected” to the IDE, the reason may be obvious to the user - so it would be useful to be able to cancel these retries, exit the Debug Session, and return to the C/C++ perspective. See also: 

Hi,I want to use multiple VL53L8CX in my robot. I don’t like to connect a gpio to each of them nor use an gpio extender. In some other topic it is stated that MISO is connected with 47k to GND because the pin may configured as other than push/pull and the GPIO stated in datasheet are not really GP any more. So I got the idea to use MISO in I2C as a chained input to the next sensors LPn. There is nothing stated in datasheet other than don’t connect in I2C mode. So the questions are:is the state of MISO is defined at startup in I2C mode? Is it correlated to NCS pin even in I2C mode?after pushing the firmware and changing the I2C address is it possible to set MISO to high level independent to NCS or is it somekind hardwired?Ragards Chris

Hi all,I'm designing the control electronics for an automatic egg-candling machine (150 positions). An STM32F411 drives everything over a single shared SPI bus:A 74HC595 daisy-chain (shift registers → ULN2803A → solenoid valves) MCP3208 ADCs (reading LDR light sensors) on the same SPI bus, CS-selectedThe process is strictly sequential (read all sensors first, then actuate valves — never at the same time), so valve-switching noise never coincides with an ADC read, and SPI speed is not time-critical. That's why I want to keep the clock slow.Physical signal path (my concern):~100 cm total PCB trace 2 board-to-board connectors (PCB-to-PCB) then a 20 cm cable that enters the target IC (74HC595 / MCP3208) Planned SPI clock: 100 kHz, SPI mode 0, 3.3 V logicMitigations planned: series termination on SCLK/MOSI/LATCH at the source, ground interleaving in the cable, star grounding (valve PGND separated from SPI/logic GND), local 3.3 V regulation at the far end.My own bench test: I ran an SPI loop

Dear STM Support Team,We are currently developing a rear-view camera application on the STM32N6570 platform. Our existing implementation was developed using the Sony IMX335 image sensor, and we are now planning to migrate the design to a custom board using the OmniVision OV2312 sensor.We would like to clarify the following: Does the existing STM32N6570 camera driver framework support the OV2312 sensor directly? If not, is there an official OV2312 sensor driver available from ST? Can the existing IMX335 driver be adapted for OV2312, or is a separate sensor-specific driver required? If an OV2312 driver is already available, could you please provide the driver package, reference code, or the relevant documentation for integration with the STM32N6570 imaging pipeline? Your clarification will help us proceed with the custom hardware integration and software development.Thank you for your support, and we look forward to your response.

Hello Friends, I have selected STM32F401XE series for my new project. The device is expected to face road vibrations and shocks, so to make system more reliable I am thinking to use MEMS oscillator rather than standard Quartz Crystal. I tried to search any reference schematic of STM32 MCU having MEMS osciilator but couldn’t find. Please share if any information available on how to use MEMS Oscillator.  I understand  OSC-IN should be connected to OUT of MEMS Oscillator and OSC-OUT should be set to high -Z.   What about VDD of MEMS Oscillator?  Should it be set to same VDD as set in STM32F401XE MCU, which is 3.3V Thanks

Hi Team, I was going through the schematics of STEVAL-CTM010V1 solution for dual Motor controller application for Airconditioner.  Can anyone help me regarding the design equations of this application? If possible, we are ready for a meeting.Kindly reply. Thanks and Regards,Ajay P

Hello I’m developing long project.Tomorrow I open the project and try to save it without any modification,but appears this window  Can someone please help me, thankyou in advance.

Hello ST team,I am designing a circuit using the STM32N657 and want to minimise the total power consumption in this application. therefore, I am considering using the ultra-low-power U031 MCU to switch the STM32N6 on and off via this MCU. My question is: can I use a power switch instead of an LDO?I have attached my power tree I’d appreciate it if you could have a look.Regards  

Hello, I have tested, the VL53L8CX tof sensor in interior (fixation at 3m10), and the visualization of the matrices works very well, in an empty scene or with a person pass under the sensor. When my sensor is fixed at the same height, but light up with daylight, next to the window, my matrices are noised, and when a person pass under it, there are some noise with the passage of the person. For example, the sensor create lots of pixels with this situation rather than the other. How to reduce this noise and this sensibility to the daylight ?