Solved

 URL is: https://community.st.com/moderation-archive-109/st-community-highlights-april-to-june-2026-166891?tid=166891 

In the stm32 cubeMX Board selector menu I cant find board MKI-109D.How can I develop the board firmware? 

Hello, we are testing using an STM32H7R7L8H6 paired with an IS42S32800L-6BL. There are no data failures at 100MHz, but data failures occur after prolonged execution at 150MHz. What is the maximum FMC execution speed of the STM32H7R7L8H6? This test was conducted with the MCU DVDD pin unconnected. Is this related to the DVDD pin connection?

Hello,I am debugging USB function on STM NUCLEO-H723ZG demo board. I set the USB_DEVICE Mode as CDC(Virtual Port) mode. USB_OTG_HS can as below.Now I can get the virtual port number on the computer. But the VBUS over current LED (LD7) is always on. It indicates the VBUS over current. But I have configured the EN pin of STMPS2141STR as high (Set PD10/USB_FS_PWR_EN) to disable this fault. Can anyone please help to check what’s the problem? Thanks, 

I spent a lot of time designing a prototype using the STM32H573MIY3Q, but now it’s out of stock (DigiKey/Mouser/JLC) and 78 week lead time (available Jan 1, 2028). I’m kicking myself for not asking earlier about STM’s commitment to this part.How do we get samples now? I guess I can go to the scalpers...But then is it even smart to design this into a product? What is STM’s planned production ramp?Initially I’ll sell a few hundred units but if it goes well I might need 10K+ per year.Am I delusional in hoping for the possibility?I apologize for my tone of frustration, but SEVENTY EIGHT WEEK lead time is hard to believe, and upsetting. Is this not a flagship microcontroller (STM32H5) and flagship package (WLCSP-80)?

Hi everyone,I'm working with the STM32F446RE and exploring the 6-step BLDC motor control example provided by the STM32 Motor Control SDK. In the CubeMX configuration of the firmware:3 GPIOs are configured as analog inputs:M1_BEMF_U → PC3 → ADC1_IN13M1_BEMF_V → PA7 → ADC1_IN7M1_BEMF_W → PB0 → ADC1_IN8However, in the ADC Injected Conversion Mode, only Channel 13 (PC3) is selected and used (1 injected conversion configured).See image below for reference:My question is:Why are all 3 BEMF pins configured in CubeMX if only Channel 13 is used in the ADC injected group?I expected that all 3 channels would be used in the injected sequence to sample U, V, and W BEMF voltages.Do they dynamically change the injected channel in code depending on the commutation step? Or is there another reason for this configuration?Thanks in advance for any clarification!

Hello,At present I trt o interface an SPI based SSD1309 Display and I2C based DS3231 RTC with STM32F103RBT6 using Nucleo board MB1136 F103RB C. For your reference I have attached screenshot of port assignment for those devices.  void Init_GPIOs(void) {/* --- 1. Peripheral Clock Enable --- */// Enable clocks for all GPIO ports and AFIO (Alternate Function I/O)RCC->APB2ENR |= (RCC_APB2ENR_IOPAEN | RCC_APB2ENR_IOPBEN |RCC_APB2ENR_IOPCEN | RCC_APB2ENR_IOPDEN |RCC_APB2ENR_AFIOEN); /* --- 2. Pin Remapping & JTAG Management --- */// Disable JTAG/SWD remap to reclaim PB3, PB4, and PA15 for GPIO/Alternate Function usageAFIO->MAPR &= ~AFIO_MAPR_SWJ_CFG;AFIO->MAPR |= AFIO_MAPR_SWJ_CFG_JTAGDISABLE;// Remap SPI1 to PB3/PB4/PB5 as per hardware designAFIO->MAPR |= AFIO_MAPR_SPI1_REMAP; /* --- 3. Initialize Display Control Pins (Soft-Step) --- */// Configuring critical control pins first ensures the display state is stable// before the high-speed SPI clock begins toggling.GPIOB-&gt

I have created a project and none of the options on my screen seem to do anything. All im trying to do is compile a simple code on STM32CubeIDE and flash a board using the STM32CubePRG software. 

Create a new project on macOS using STM32CubeIDE for VSCode.In the CMakeLists.txt file, add:add_link_options(-flto=auto -ffat-lto-objects)Build the project.You should get a linker error like this, because GNU Tools for STM32 is located in the “Application Support” folder which contains a space, so lto-wrapper can’t manage to access its dependencies:[build] Linking C executable core_mcu_firmware.elf[build] make[3]: /Users/romain/Library/Application: Permission denied[build] make[3]: /Users/romain/Library/Application: Permission denied[build] make[3]: *** [/var/folders/hb/49ldjdz961l9dtpyqq8dqhcr0000gn/T//ccLALceE.ltrans1.ltrans.o] Error 1[build] make[3]: *** Waiting for unfinished jobs....[build] make[3]: *** [/var/folders/hb/49ldjdz961l9dtpyqq8dqhcr0000gn/T//ccLALceE.ltrans0.ltrans.o] Error 1[build] lto-wrapper: fatal error: make returned 2 exit status[build] compilation terminated.[build] /Users/romain/Library/Application Support/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/bin/.

HardwareBoard: NUCLEO‑U5A5ZJ‑QMCU: STM32U5A5ST‑LINKSoftware / ToolsST Edge AI (via STM32CubeAI Studio)Target: STM32U5Model source: STM32 AI Model ZooModel used:miniresnetv2_s1_64x50_tl_int8.tflite(Audio Event Classification → ESC‑10)Steps FollowedImported the miniresnetv2_s1_64x50_tl_int8.tflite model into STM32CubeAI StudioSelected NUCLEO‑U5A5ZJ‑Q as the target boardKept default settings in all stepsRun on Target Generated code, built, flashed, and attempted (Step 4 – Validate) failed Observed IssueDuring Run on Target, validation fails with the following error:Run failed: Error: validate error: E200 (ValidationError): TARGET: Unable to bind the ST.AI runtime with "network" c-model E801 (HwIOError): Invalid firmware - COM8:115200I have attached the complete validation failure log for reference.Additional ObservationDuring Step 1 (Code Generation), I consistently receive the following warning from STM32CubeMX:Warning: Code GenerationMain Config: These peripherals still have some n

I’ve noticced recently that in CubeIDE 2.x, the MXCube program was separated from CubeIDE and is now a standalone app. I’ve also noticed that the extensions download a more recent C standard for STM32 compiler and MCUFinder is now web-only. This to me signifies a pivot in where STM is going with development environment and my guess is that everything will focus on VSCode extensions. Having said that, I’m inclined to port my whole project in VSCode but I want some reassurance that the platform and its MCUs will get future enhanced support for VSCode extensions and better integration.So far, CMake scrips in VSConde aren’t fully fledged, specifically missing out-of-the-box commands and buttons for:- Switching active configuration (Debug or Release)- Flashing the target MCU.- Debugging via line-by-line walkthroughs.- Set debug levels and optimisations.- Set hardware or software floating points.- Output .bin firmwareMy question is. Is this the case and is better for me to port everything to

Here: I guess it indicates a “sticky” post, but please add a pop-up - as for the ‘Solved’ tick: 

Hi,I'm developing a composite USB device on STM32N6 with:- 2x CDC ACM interfaces (Dual Virtual COM Port)- 1x UVC (USB Video Class) interface for camera streamingThe CDC ports work correctly. The UVC class enumerates successfully and the camera application opens without errors. However, the video stream shows a black screen - no actual frame datais being transmitted. What Works1. USB Composite device enumeration succeeds2. Both CDC ACM ports work (LOG port sends heartbeat, DATA port echoes)3. UVC class registers correctly with USBX4. Host can open camera application (VLC, Cheese, etc.)5. UVC GET_DEF(PROBE) requests are handled correctly6. SET_CUR(PROBE/COMMIT) requests are handled correctly7. StreamChange callback fires when host starts streaming (alt=1)8. Packets are queued via ux_device_class_video_write_payload_get() (returns success)9. ux_device_class_video_transmission_start() returns UX_SUCCESSWhat Doesn't Work→ PayloadDone callback is never triggered→ No video data reaches the ho

Hi everyone,I am working with the STM32C071 and experiencing problems with USB enumeration after my bootloader execution.I wrote a custom bootloader that performs checks (like CRC, metadata, etc.) and can also trigger the embedded STM32 DFU bootloader in System Memory using this method:void boot_jump_to_bootloader(void){ uint32_t i = 0; void (*SysMemBootJump)(void); uint32_t BootAddrC0 = 0x1FFF0000; __disable_irq(); SysTick->CTRL = 0; HAL_RCC_DeInit(); for (i = 0; i < 8; i++) { if (i < (sizeof(NVIC->ICER) / sizeof(NVIC->ICER[0]))) { NVIC->ICER[i] = 0xFFFFFFFF; NVIC->ICPR[i] = 0xFFFFFFFF; } } __enable_irq(); SysMemBootJump = (void (*)(void)) (*((uint32_t*) ((BootAddrC0 + 4)))); __set_MSP(*(uint32_t*) BootAddrC0); SysMemBootJump(); while (1) { /* Code should never reach this loop */ }}After performing my bootloader-specific instructions, I jump to the main firmware application using this f

Hi,after Update to v6.18.0 we get the following warning: Our configuration: Mouse hover: Obviously, you don't have a single source. Otherwise, it wouldn't be possible for the “240 MHz” label below the text field and for the “225 MHz” label to appear when hover over that same text field.Please, ST, conduct more integration tests! Attached our .ioc file.

Hi there, I found several issues in the STM32CubeMP2 CMSIS headers as follows:1. Missing opening parenthesis in bitmask macrosIn stm32mp21*xx.h, _Msk macro definitions were missing the opening parenthesis, leaving a dangling closing parenthesis with no matching open:// Before #define USB_OTG_GCCFG_FSVMINUS_Msk 0x1UL << USB_OTG_GCCFG_FSVMINUS_Pos) // After #define USB_OTG_GCCFG_FSVMINUS_Msk (0x1UL << USB_OTG_GCCFG_FSVMINUS_Pos)While the C preprocessor performs simple text substitution and the shift operation may still evaluate correctly at the call site depending on context, the unbalanced parentheses break static analyzers, automated code-generation tools, and linters that parse these headers. Adding the opening parenthesis also makes operator precedence explicit and unambiguous.2. Malformed comment delimitersAll of header files involves inline comments used *!< instead of the correct /*!< Doxygen-style comment opener, missing the l

Hello,We are experiencing an intermittent CAN-FD issue in our system and would appreciate any advice from the community. We have developed seven new I/O modules based on the STM32G491VETx with an external 20 MHz crystal.All have the same CAN configuration using ISO1042BDWVR. The CANopenNode stack with the CANopenNodeSTM32 driver is implemented on all electronic units.See https://github.com/CANopenNode/CanOpenSTM32  The CAN bus operates at 250 and 500 kbit. All electronic units occasionally experience the problem that the NodeGuarding or heartbeat (set to 3s!!!) stops responding after 24 hours to 5 days. SDOs do not respond either, whilst TPDOs continue to operate. We have set up over 10 networks, each with 4 different nodes (all G491), and all exhibit the same behaviour sporadically. We can rule out hardware faults.The electronic runs for about 48 hours with no Problem on 500k an low bus load (about 2%, Nodeguarding and some TPDO/RPDO).Suddenly FIXFDCAN RF0 FIFO FULL and RX NEW MESSAGE

I have copied this link from the post “STM32CubeIDE 2.2.0 released”:https://community.st.com/stm32cubeide%2Dmcus%2D28/stm32cubeide%2D2%2D2%2D0%2Dreleased%2D166532 But that link actually goes to:Text of the URL (with the https prefix removed, to stop the forum linkifying it):community.st.com/stm32-mcus-embedded-software-32/how-to-send-int-values-efficiently-through-cdc-usb-39682?postid=166532#post166532Which does, in fact have the same ?postid=166532#post166532 as the other link!

Hi,STM32H533 datasheet (DS14539 Rev 2) in table 88 says that RDY input setup and hold time are both 0.5ns. From my naive point of view it looks like superb value (RDY have to be stable only +-0.5ns around CLK edge). Isn't that a typo ? (STM32H7 PSSIs hold time is about 5.5ns)Thanks,Michal Dudka

Dear Team,I hope this email finds you well. I am writing to seek your expert clarification on a critical hardware design decision we are currently evaluating for our STM32MP257-based custom board.   --- Current Memory Configuration --- • SoC         : STM32MP257• Memory Part : Micron MT53E1G32D2FW-046 WT:C• Type        : LPDDR4• Density     : 32 Gbit (4 GB)• Organization: 1 x32 (Dual Channel — Channel A + Channel B) --- Our Understanding from ST Documentation --- Based on our research of the following official ST documents: 1. AN5723 (Rev 3, Aug 2024) :   "Interface width is 32-bit when full-populated, or 16-bit when half-populated." 2. AN5724 — DDR Routing Guide:   "For the 16-bit LPDDR4 interface, one 16-bit LPDDR4 is used in point-to-point connection. With this configuration it can drive up to 2 Gbyte memory." 3. AN5489 (Rev 6, Sep 2025) :   STM32MP257 supports both 16-bit (half-populated) and 32-bit (full-populated) LPDDR4 configurations. Our understanding is:• If using a native x1

 I have activated spread spectrum on two of the three PLLs I’m using in an STM32H7S7 via codeLL_PLL_SpreadSpectrumTypeDef sspr2;LL_PLL_SpreadSpectrumTypeDef sspr3;// in SystemClock_Config LL_RCC_PLL2_EnableSpreadSpectrum(); LL_RCC_PLL3_EnableSpreadSpectrum(); sspr2.DitheringRPDFN = 1; sspr2.DitheringTPDFN = 0; sspr2.IncrementStep = 1200; sspr2.ModulationPeriod = 10; sspr2.SpreadMode = LL_RCC_PLL_SPREAD_CENTER; LL_RCC_PLL2_ConfigSpreadSpectrum(&sspr2); sspr3.DitheringRPDFN = 0; sspr3.DitheringTPDFN = 0; sspr3.IncrementStep = 214; sspr3.ModulationPeriod = 60; sspr3.SpreadMode = LL_RCC_PLL_SPREAD_CENTER; LL_RCC_PLL3_ConfigSpreadSpectrum(&sspr3);Is there a way in CubeMX to activate it to make the settings generated automatically, as everything else I’m using?I’ve checked the RCC section in System Core as well as the Clock Configuration tab, but I can’t see anything regarding spread spectrum

Hello,I am designing an NFC reader based on the ST25R300, using the STEVAL-D25R300A schematic as a reference for the antenna matching network. My board uses the same component values on each side of the differential output:L1/L2 = 120 nH (EMC filter series)C11/C8 = 390 pF (EMC filter shunt)C1/C12 = 82 pF each, in parallel (series matching)C14 = 120 pF (shunt)C67 = 39 pF (shunt)C59 = 10 pF, C16 = 150 pF (RFI divider)R3/R4 = 2.2 ohmI could not find the antenna coil parameters in the user manual or the design files. Could you please provide the following for the antenna used on STEVAL-D25R300A?1. Coil inductance at 13.56 MHz2. Coil AC resistance (or Q) at 13.56 MHz3. Whether the antenna is a PCB trace coil or a discrete component, and if it is a PCB trace, the outer dimensions and number of turns4. The target differential impedance the matching network above was designed for Thank you.

Dear ST Support Team,We are currently developing a board based on the ST25DV04K and would appreciate your guidance regarding the antenna interface.In our schematic, we have placed a π coupling filter (series inductors and shunt capacitors) between the AC0/AC1 pins and the antenna matching circuit, upstream of the latter, for coupling at 13.56 MHz, as shown in the attached schematic.Could you please clarify whether the use of this π coupling filter, positioned before the matching circuit, is recommended by ST, or whether it is not necessary in this configuration?Thank you in advance for your support — we look forward to your recommendations.Best regards, 

I’ve designed a flyback w/ Viper27HD.  Turn on voltage is 120Vdc.  Max design input volutage is 500Vdc.  Output voltage is 12V.  I designed the VCC tertiary winding for 16V, but due to spike rectification the actual votlage is 20.2V for Viper VCC.  The prime supply is a MagnaPower SLx-1.5-500-3-xxxxx power supply with voltage, current, power, control and + and - slew rate control. The Viper “wakes up” when the input voltage is at ~110V.  I have an internal POR circuit that holds off my controls until 250 ms later.  When the POR ends, the 12V housekeeping power is used to energize the gate drive of a FET from the input power rail to a large capacitor bank through a 40 Ohm “Soft Start” resistor.  When the gate drive initiates, the Viper chip shuts down for 22 ms which temporarily glitches the housekeeping power.  I’m using a FOD2711 isolation regultor for FB control. I observe: VCC of Viper is STABLE through the shutdown. VBR never approaches the brown out threshold FB switches hard to G

Hi all, I merged the VENC_JPEG_Encoding example with a DCMIPP app. Both parts work on their own, but the JPEG encoding breaks (error -9 = JPEGENC_HW_BUS_ERROR) as soon as I turn on the DCMIPP capture. The JPEG input/output buffer is completely unrelated to the DCMIPP buffer. It’s just that as soon as I start the DCMIPP in CONTINUOUS mode, the JPEG encoder breaks… Very strange.Did anyone else experience this problem? What could cause this? How would I fix this? Best regards, rphii