Product forums

Hi all,I am wondering if CubeMX2 + STM32C562RE are able to support cpp main applications? Thanks in advance

I am Having a 2.2 Kwatt PMSM motor i have created a custom power Board, I am using STM32F303Re nucleo board .I am using 2hall sensors for current feed back . my motor starts but does not reach the final full rpm. my power board schematic is attached herewith the powerboard is working correctly, why does the motor not attain the maximum speed. my motor parameters are correct, also i am not able to vary the speed of the motor while running application .from the oscilloscope waveforms it looks like the when the speed tries to increase the feedback drops and motor goes out of sync momentarily. the oscilloscope waveform frequency drops and the FOC again tries to catch the rotor , this keeps on happening and then after some time the motor goes into speed feedback. i am not using Motorpilot, i am running openloop in MCSDK and calling the start motor function from my code after speed ramp function .   

Please suggest abot EDGE AI 

When I open a VS Code workspace containing a project generated by STM32CubeMX, Windows Defender consistently detects Trojan:Win64/jscramSteal.DA!MTB.Environment: VS Code: 1.127.0 ST extension: 3.9.0 STM32CubeMX: 6.18.0 Windows: 25H2 (defender updated today) Steps to reproduce: Generate a project using STM32CubeMX. Open the generated project as a workspace in VS Code with the ST extension installed. Windows Defender immediately reports Trojan:Win64/jscramSteal.DA!MTB. Could you confirm whether this is a known false positive? If so, is there a recommended workaround, or is there an update available that resolves the issue?

We are trying to build BL2 for STM32MP13 with `TRUSTED_BOARD_BOOT=1` and mbedTLS 3.6.6, using a standard `arm-*-gnueabihf` toolchain. The build fails while compiling the first mbedTLS source file:...In file included from /src/mbedtls-3.6.6/library/aes.c:14:/src/mbedtls-3.6.6/library/common.h:23:10: fatal error: arm_neon.h: No such file or directory   23 | #include <arm_neon.h>      |...The failure occurs as follows. The STM32MP1 platform enables:ARM_WITH_NEON := yes This adds `-mcpu=cortex-a7 -mfpu=neon` to the compiler flags. When using a hard-float toolchain such as `arm-linux-gnueabihf`, GCC consequently defines `__ARM_NEON`.Since library/common.h is included by every mbedTLS source file, mbedTLS then tries to include:#if defined(__ARM_NEON)#include <arm_neon.h>However, TF-A builds with -`nostdinc` and uses its own libc headers. As a result, arm_neon.h cannot be found and the build fails.The same configuration builds fine with a soft-float toolchain, where `__ARM_NEON` i

The FDCAN_RxHeaderTypeDef typedef (for the STM32G4) includes:uint32_t IsFilterMatchingFrame; /*!< Specifies whether the accepted frame did not match any Rx filter. Acceptance of non-matching frames may be enabled via HAL_FDCAN_ConfigGlobalFilter(). This parameter takes 0 if the frame matched an Rx filter or 1 if it did not match any Rx filter */From the code, this member is loaded with the ANMF bit of an RX FIFO element. The documentation for this shows that ANMF is an abbreviation for “Accepted non-matching frame” - so the comment is correct (‘1’ → did not match a filter). Which means the member name should be something like ‘IsNotFilterMatchingFrame’.Code completion within CubeIDE does not show the comment:which means it is easy to get the state wrong if the name is interpreted semantically!Probably not a lot that can be d

Hi everyone,I am relatively new to the ST ecosystem, coming primarily from a web development and programmatic software background.I recently built a browser-based daily logic game tailored for my local market called hang 5. The core mechanics rely on a responsive visual letter grid, basic string matching for user inputs, and a specific vowel-penalty state machine.As a hobby project, I want to build a physical, standalone desktop version of this puzzle using an STM32 board and a small capacitive touch TFT display. I've been researching TouchGFX to handle the UI, as it seems more than capable of replicating the clean CSS grid layout I am currently using on the web version.Before I purchase my first board, I have two quick questions: Which STM32 Discovery kit would you recommend for a beginner wanting to utilize TouchGFX for a snappy, interactive 2D touch grid? The game requires a daily dictionary array of about 2,500 words. Is storing this plain text array directly in the internal flas

Dear all,I am writing to request assistance with activating an Ethernet connection between my PC and an STM32N657-DK development kit using NetX Duo.While my TouchGFX design is currently functioning correctly on the board, I am encountering issues when attempting to enable communication. Specifically, after flashing the Ethernet configuration, I am unable to successfully ping between the devices. I have attempted several troubleshooting steps but have not yet been able to resolve the connectivity issue.Please provide guidance or instructions on the proper configuration steps to establish this connection. Thank you so much. 

Hello, I am searching for a way to configure the VL53L9CX under linux using I2C.For previous sensors, a platform-independant driver library was available, but I am failing to find such a library here. How could I get a library that runs under linux, or even just a library without HAL so I can implement it myself using ioctl? Cheers,Daniel

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

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.

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

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