Solved

Hello, We appear to be experiencing a severe code generation bug with CubeMX. After naming and sizing application regions in the memory management tool, what used to generate a correct linker script now generates bad output.Upon generation the linker script STM32U575XX_FLASH.ld now shows:/* Specify the memory areas */ MEMORY { RAM (rwx) : ORIGIN = 0x20000000, LENGTH = 768K FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K /*start of MX regions Auto-generated By STM32CubeMX*/ RAMBK (rw) : ORIGIN = 0x20000000, LENGTH = 768K RAM4 (rwx) : ORIGIN = 0x20000000, LENGTH = 768K SPIFLASH (rwx) : ORIGIN = 0x08000000, LENGTH = 2048K /*end of MX regions*/ }Given that we cannot downgrade the IOC and have performed more work this is an awkward situation and we will manually manage regions in the meantime. This was not an issue before. Please advise what may be going on. Host: OS X 26.2CubeMX: 6.16.1Target: STM32U575xx  

I am using STM32U575ZIT6QU Microcontroller to measure voltages on 4 analog channels. The 4 channels are configured as Injected Channels. In the RM0456 reference manual, for STM32U5 series, I am unable to find information about using GPDMA with ADC Injected conversions. Is it possible to use ADC Injected Conversion with DMA?

Oh boy, I'm frustrated...Just when I thought I found the right MCU with the N6 (multi-channel audio over gigabit ethernet), I find in CubeMX and the datasheet that SAI2_SD_A and ETH1_CLK use the same pin. And I need both SAIs completely.Very frustrating.Using some I2S might be a solution, but these cannot be synced internally, aside from some other helpful features the SAIs have.So, any other ideas, or will there be other packages where this pin-sharing problem might be solved? 

I am using cubemx to generate a CMAKE project for a NUCLEO_144 based board (NUCLEO_H563).Project generation creates a cmake/stm32cubemx/CmakeLists.txt file that generates a macro define "USE_NUCLEO_144".it also auto creates a stm32h5xx_nucleo_conf.h file that also creates the same define: /** @defgroup STM32H5XX_NUCLEO_CONFIG_Exported_Constants Exported Constants  * @{  *//* Nucleo pin and part number defines */#define USE_NUCLEO_144/* #define USE_NUCLEO_64 */ This creates a duplicate redefinition warning upon build in many places as this header is included throughout my project in many places.This is extremely annoying.I can suppress the warning by adding: #if !defined (USE_NUCLEO_144)#define USE_NUCLEO_144#endif /* USE_NUCLEO_144 */ to the stm32h5xx_nucleo_conf.h filebut of course, this change gets wiped out upon next cubemx code regeneration. It would be so helpful if this guard was included if whatever mechanism you use to generate the _conf.

Dear STMicroelectronics,This is a bug report on the UI for STM32CubeMX 6.16.0 running on Windows 11 Pro 25H2.Please report this internally so that it may be fixed in some future version. Steps to reproduceStart STM32CubeMXFile / New ProjectSelect MCU STM32H563RIT6Click button Start ProjectSelect with TrustZone activated and click OKUnder Categories, expand Middleware and Software PacksFor ThreadX, click the greyed out radio button in column M33NSClick it againExpectedThe popup is readable.ActualAfter the second click, the popup is shown partially obscured by the table and is not readable.If you select the row for ThreadX and click the radio button you can get the popup very much obscured - see attached screenshot.Further infoThe screen resolution doesn't seem to affect the behaviour.I have also reproduced this problem when running the Linux variant of 6.15.0 on Debian bookworm.     Best regards, Jesper 

Split from this thread. Yes, but No!CubeMX V6.16 now allows only exactly 32 TX Buffers ((TX Buffer Nbr + TX Fifo Queue Elmts Nbr) == 32).But less then 32 TX Buffer is allows by the Hardware, and some times, required if You want to maximize the RX Buffers.

There's a bug in latest STM32CubeMX v6.16.1. When enabling RAMCFG for Appli on STM32N6 MCU, the IOC file becomes unloadable.I attached the demonstration IOC file. I created new project for STM32N6570-DK board, enabled RAMCFG peripheral for Appli, checked the AXISRAM3-6 areas, defined single continuous area for those SRAMs in MMT and saved the project. After this CubeMX fails to load this IOC file. I get popup:In textual form the error is: Cannot invoke "com.st.microxplorer.mcu.memorymap.MemoryMapService.getInRangeAppRegions(long, long, com.st.microexplorer.mcu.Context)" because "this.mMemoryService" is null.The workaround is to not enable RAMCFG in CubeMX, rather control the peripheral manually.

Hi everyone,I am attempting to set up the new CubeMX version (6.16.0) inside a Docker container, but I am running into issues.Setup:Base Image: Ubuntu 24.04Target Software: STM32CubeMX 6.16.0Goal: Headless installation (auto-install), since CubeMX is no longer bundled with CubeIDE 2.0.0.The Issue: The headless installation fails. According to the User Manual "UM1718", this mode should still be supported. However, the installation process differs from the manual and aborts with an error. Note: The current manual still uses version 6.11.0 in its examples.What I have tried so far:Verified with v6.11.0: I tested the headless installation with the older version 6.11.0. This works perfectly and follows the manual exactly.Quiet Mode: I tried installing v6.16.0 using the -q operator, but this triggers an error as well.Error Log: I receive the following output/error trace:user:/# ./SetupSTM32CubeMX-6.16.0Check exe path on linuxFullExe path1 is: /SetupSTM32CubeMX-6.16.0Exe path is: /Search java

..

Hello there! I'm new here. I’ve just started working on my master thesis, which involves the STM32N6 and an image sensor.From what I've heard from colleagues, working with a camera that lacks a proper datasheet or driver can be frustrating. To avoid falling into the same trap, I’ve been searching for cameras/modules compatible with the STM32N6 that I can get up and running.Here's what I'm looking for:I need to capture images (video is not a priority) in daylight (IR filtered).Once sunlight fades, I will activate my IR illumination and take IR-only images. RGB should ideally be blocked to avoid mixed images. My two approaches so far:1. RGB Camera with Motorized Filter (e.g. RaspberryPi IR-Cut, motorized): It uses a clear filter and an IR-cut filter. The clear glass could potentially be replaced with an RGB-blocking filter.2. Dedicated RGB-IR Sensor: I came across Omnivision sensors and, later, ST’s own options. Here’s where things get tricky:The Omnivision sensors don’t s

Hello,Our project is based on the STM32WBA65MI, and we have an external flash chip on the board that we use STM32CubeProgrammer w/a custom external loader to program. This worked well with STM32CubeProgrammer v2.20, but when I updated to STM32CubeProgrammer v2.21, suddenly I was unable to connect to the board using the external loader.This happens as soon as I select the external loader andIf I select verbosity level 3, this is what I see:08:50:10:520 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX25R6435_STM32WBA65-LEGATO.stldr 08:50:10:520 : Error: Flash loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX25R6435_STM32WBA65-LEGATO.stldr cannot be loaded.Here's the StorageInfo:struct StorageInfo __attribute__((section(".Dev_Info"))) const StorageInfo = { "MX25R6435F_Legato", // Device Name + version number SPI_FLASH, // Device Type 0x00000000, // Device Start Address 0x800000, // D

Title edited - originally said, "sharing data between two boards" Good day y'all, I'm trying for the first time to have the two cores on a H7 board share data between one another on shared memory, in particular cm7 writing data and cm4 read it. From what I understand I need to use a semaphore to signal back and forth to alert the cm4 when there is new data in every iteration, the theory I get, but I'm not sure of the shared memory allocation and the semaphore correct availability. Is there any example code I can see to understand how it's supposed to go? I tried looking at the ide examples, but anytime I try to open the example folder the ide application just dies :\  Thx all for the advices,  P.S. I'm also using FREERTOS but it's not supposed to cause any problem but you never know 

I want to set the BOR_LEV of H523 to 1. If you have any good ideas, please let me know.

Hi everybody, I'm using a custom PCB which is build upon a STM32L431CBT6 MCU. When connecting to the CUBE Programmer i had this error:Error: Database: There's no active configuration for this device. All the 1 configurations are disabled!Then, i confirmed the issue arose from the DeviceID 0x435 .xml file not having the 128K flash memory settings. What i did is code it myself like this:<!-- JTAG_SWD Interface --> <Interface name="JTAG_SWD"> <Configuration number="0x0"> <!-- 256KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0100"/> </FlashSize> </Configuration> <Configuration number="0x1"> <!-- 128KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0080"/> </FlashSize> </Configuration> </Interface> <!-- Bootloader Interface --> <Interface name="Bootloader">

Hi, I'm designing a driver using 3x STSPIN9P12 to drive a Permanent Magnet Synchronous motor (PMSM).  I have a ADC connected to the SNSO outputs to measure current and I am controlling the current in the MCU's control loop.  I am not using the COUT and VREF pins.Can / should VREF be tied to GND?I think the TOFF pin does not exist on this version.  Do I leave TOFF floating?  or should TOFF be tied to GND?Jon

Hello, I've been following closely with the github while I work on the recording portion myself, and I saw that x-cube-azrtos-h7 was updated today.  I immediately looked for the recording project, and couldn't find it. Even this page shows up Error 404: https://github.com/STMicroelectronics/x-cube-azrtos-h7/tree/main/Projects/STM32H743I-EVAL/Applications/USBX/Ux_Device_Audio20_Recording Do I not have access to it?

Even I am using the latest CubeProgrammer v2.21.0, it indicates an update available but when I check it, there is no update and the updater log does not update, it cannot update its last update date as well.I know not so important but quite annoying problem, i`d like to mention, 

Dear ST team,I need some tips!!!I am using STM32H745 for my project. In the project, the M7 core is dedicated to control and measure the power circuit values and M4 core is responsible for communications (few UARTs) and LCD. I configured the MCU with STM32CubeMX and use Keil uvision fore code composing. After generating code, I noticed that there are two separated codes were generated for each CPU.How can I bridge between two CPUs to share data? I want to send measured data by M7 via UARTs controlled by M4?I will appreciate if you give me some applicable suggestions.

Hi,We are designing a compact, battery-powered system that requires a regulated high-voltage DC output with the following specifications:• Input: 5V• Output: Adjustable 400V to 1000V• Load current: 1µA to 200µA• Very low ripple and noise• High efficiency and small form factorThe supply will be used as a bias source for sensitive detectors (e.g., APD/PMT-type devices), so output stability and low noise are critical. The output must remain stable across the specified load range.I am currently considering a closed-loop flyback topology with post-filtering, but I am open to alternative architectures.Could you please recommend:• Suitable controller ICs from your portfolio?• Relevant reference designs or evaluation boards?• Design techniques for minimizing ripple and noise at these voltage levels?Any guidance or application notes would be greatly appreciated.Thank you.  

I have build a Fully pin compatible STM32H750B-DK board with USB Device only setup along with Touchgfx and Freertos , Touchgfx is displaying everything correctly but the USB Isn't responding , I have setup the USB OTG FS in Device Mode as shown in the attached Images.PC is not detecting anything

Hello everyone,I’m working on a project with an STM32H750B-DK board using TouchGFX and LWIP (Ethernet). After configuring LWIP in CubeMX and generating the code, I encountered a compilation error that took me a while to understand. I’d like to share the problem to help anyone who might run into the same issue.The ErrorIn file included from ../Application/User/gui/NetworkTask.cpp:13: ../../TouchGFX/gui/include/gui/model/ModelListener.hpp:13:23: error: macro "bind" requires 3 arguments, but only 1 given 13 | void bind(Model* m) | ^ In file included from ../Application/User/gui/NetworkTask.cpp:11: ../../Middlewares/Third_Party/LwIP/src/include/lwip/sockets.h:616: note: macro "bind" defined here 616 | #define bind(s,name,namelen) lwip_bind(s,name,namelen) | Similar errors appeared for Model.hpp.                                                     

STM32CubeIDE for VS Code is there a memory window? like MDK Memory window   

Is STM32WB55xx (Multiprotocol wireless 32-bit MCU Arm®-based Cortex®-M4with FPU, Bluetooth® 5.3 and 802.15.4 radio solution) is Automotive grade(AEC-Q100 Grade)?

Custom MP157AAA3 board.  SD card formatted with ECO 5.0.0 using the SD tools using the files from the starter package. (including rootfs etc..) .  Build the TF-A, OP-TEE (in SYSRAM), U-boot and kernel from the ECO 5.0.0 sources.Kernel generates the messages as below and then feezes. The DT's were generated using CubeMX and customized for the board. It looks like drivers are all waiting on resources to become available, perhaps one single one they all need. Hence the deferred probe.Any hints/steps how to debug this ?[12.832984] Run /init as init process[ 13.390242] platform 50000000.rcc: deferred probe pending[ 13.395778] platform 5000d000.interrupt-controller: deferred probe pending[ 13.402749] platform 48002000.dma-router: deferred probe pending[ 13.408792] platform soc:pinctrl@50002000: deferred probe pending[ 13.414956] platform soc:pinctrl@54004000: deferred probe pending[ 13.421084] platform 48000000.dma-controller: deferred probe pending[ 13.427498] platform 58000000.dm

I am testing Ethernet on STM32H723ZGT6 by transmitting UDP packets (1024 bytes) every 1 ms. Setup / Implementation: No CubeMX / HAL used Fully bare-metal Ethernet driver (lwIP integrated manually) Ethernet interrupts enabled and serviced RX handled inside while(1) loop Non-blocking transmit path MPU enabled Memory configuration: RX pool located in AXI RAM lwIP heap: 32232 bytes in D2_SRAM Observed Behavior: System runs normally for many hours (sometimes >12 hours) Eventually UDP transmit stops working Ping continues to work without issues Debugging shows failure occurs at: pbuf_alloc(PBUF_TRANSPORT, len, PBUF_RAM); After failure: 1) pbuf_alloc() returns NULL (ERR_MEM) 2) ETH->DMACSR reads 0 while (1) { sys_check_timeouts(); if (eth_rx_rdy) { eth_rx_rdy = 0; ethernetif_poll(&gnetif); ETH->DMACIER |= ETH_DMACIER_RIE; } if (sys_now() - udp_tx_timer >= 1) // 1 ms transmit interval { ret = udp_server_send(udp_tx, sizeof(udp_tx)); if (ret