Solved

Hello,I’ve noticed a difference in behavior between STM32CubeMX configurations for STM32H7 and STM32N6 series.On STM32H7, when configuring CAN bit timing, the parameters such as Nominal Time Quantum, Nominal Time for one bit, and Nominal Baud Rate update dynamically based on the settings.On STM32N6 (using STM32CubeMX v6.16.0), these values remain constant. For example, even when using the official STM32 example with a nominal bit rate of 1 Mbit/s, CubeMX still shows a fixed value of 1000 bit/s and does not adjust the timing parameters.My question is:Is this a bug in STM32CubeMX v6.16.0 for STM32N6 series?Or is this a new feature specific to STM32N6 where the tool no longer recalculates these values?I’d appreciate clarification from ST or anyone who has encountered the same behavior.Thanks in advance!

Hi,   I'm a beginner programming a NUCLEO-N657X0-Q. The LD5 is blinking and I can't get a connection to the board. Even with the demonstration code/project, it wouldn't work. In STM32CubeIDE I get the attached error message. As of yet, I never got to launch any program at all.   Thank you for your help! Len

Hi,I want to know what software versions and licenses are part of the STM IDE v1.18.0. For Version v2.1.0 I have found these release Notes which list everything nicelyhttps://www.st.com/resource/en/release_note/rn0114-stm32cubeide-release-v200-stmicroelectronics.pdfOn the STMCubeIDE Download Page / Documentation / Release Notes only lists the most recent Release Note:https://www.st.com/en/development-tools/stm32cubeide.html?ecmp=tt9470_gl_link_feb2019&rt=rn&id=RN0114# How can I find this information for v1.18.0? 

Hello, I am using a NUCLEO-H7A3ZI-Q to send and receive packets over serial. I have a varying payload size, so I am using: HAL_UARTEx_ReceiveToIdle_DMA(&huart3, rx_buffer, 4096); as this searches for an idle at the end of the frame to begin processing this data. To process this data and copy it into a look up table (LUT)  capable of being 0-4096 bytes long I have this following script; which comprises two uint8_t into one uint16_t to be represented by a 12-bit DAC, hence the clipping if they exceed 0FFF (4095).This receives and writes perfectly up to 512 bytes of memory (256 uint16_t within the LUT), however above this all remaining values in the LUT are left unpopulated. uint16_t length = 0; void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t size){ if (lut != NULL) { HAL_DAC_Stop_DMA(&hdac1, DAC_CHANNEL_1); free (lut); lut = NULL; } if(rx_buffer[0] == 0XAA) { length = rx_buffer[2] | (rx_buffer[1] <<8); frame_rate = rx_buffer[3

Hello, I am having a issue with HAL_UARTEx_ReceiveToIdle_DMA on a NUCLEO-H7A3ZI-Q, when using the following code:uint8_t rx_buffer [4096]; HAL_UARTEx_ReceiveToIdle_DMA(&huart3, rx_buffer, sizeof(rx_buffer)); void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t size){ /*code*/ } My rx_buffer is only populating the first 512 bytes, with the remaining data remaining as 0.__HAL_DMA_GET_COUNTER(huart3.hdmarx);Provides the incorrect amount of data being passed over serial.I have used serial plotter and CoolTerm to try and send packets but both hit this 512 byte limit.rx_buffer not populated past 512 byteslength correctly calculated as 640 bytes long

I am using STM32N6570-Dk board.   I want to perform edge-AI testing on this board. Trying to generate code with X-cube-AI. I am confused with FSBL and application mode, which one to choose? It is visible that FSBL is  default for X-Cube-AI in STM32N6.My question is:1. What to choose FSBL or application mode or both while generating the code for X-Cube AI ( I want to do some edge AI based testing )?2. Only X-Cube AI in STM32IDE (working in .ioc file) is sufficient for edge AI programs or I need something more than that for this purpose?I am unable to find documentation related to edge AI use for this MCU, If you have one, kindly provide. Thanks & RegardsChanchal                                                                         

Split from Benchmark Validation in App does not match Arduino Uno R4 WiFi as this is a new question.thanks for the response @Andrew Neil If i'm not overstepping my bounds, given the requirements of an audio classifier (also need wifi support and display support), which ST board would you suggest.  This is simply for prototyping purposes. Thank you in advance.Danny 

I have an ST32CubeMX project for a STM32H7 mcu generated with STCubeMX 6.4 and using STM32Cube FW_H7 V1.9.1 where the project files are generated via cmake. Now I want to use STM32Cube FW_H7 V1.12.1, but apparently, in order to be able to generate the new files, I have to migrate the project to STM32CubeMX 6.16.1:The problem is that, once I click in "Migrate", it removes two important lines from my code:So, I went to CubeMX to check, and apparently, at a first glance, the field to configure ADC3 Prescaler is gone ( I do not have any other ADC on):Also, the clock configuration tab was showing a problem. I went to check and apparently ADC clock is not allowed to be more than 100 MHz anymore:Unfortunately, I can not slow PLL2P down, since it is used for other peripherals (e.g. SPI), but I could maybe change the clock source to PER_CK and then derive it from HSI to have it as 25 MHz ( 150 MHz + Prescaler of 6 ), although I do not know which other implications it could have.I looked up some

Hello,I was playing around with different versions of MCU and I've notice STM32H7B3LIH has no Graphic Accelerator mentioned in Product Selector.But as soon as I'm selecting it in CubeMX I can enable DMA2D in Multimedia.And think there are more MCUs with Chrome-ART Graphic Accelerator which are not correctly shown in Product Selector.

I am using the STM32N6570-DK and I want to use the external PSRAM to declare a large variable buffer. Here is what I have done: 1. Initialized XSPI1 and the External Memory Manager. The PSRAM parameters I got from How to execute code from the external PSRAM using the STM32N6 . 2. Set the XSPI1 clock to 200MHz. Here is my system clock configuration:    Here is my main code from the FSBL. I also added a `gpio_toggle` to turn the user LED on before `MX_EXTMEM_MANAGER_Init()` as a debug indicator.After adding the header and programming, the FSBL boots correctly — the user LED turns on — but then it gets stuck at `MX_EXTMEM_MANAGER_Init()` and never jumps into the `while` loop.int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MPU Configuration--------------------------------------------------------*/ MPU_Config(); /* Enable the CPU Cache */ /* Enable I-Cache---------------------------------------------------------*/ SCB_EnableIC

Hello ST Community,I am working on a commercial vending machine controller and would like to get feedback from ST engineers and experienced STM32 designers regarding a system architecture change.Problem StatementOur current system uses a single MCU, but we are now hitting hard peripheral limits, mainly:Timer availability (stepper + DC motor control)GPIO interrupt countGPIO pin availabilityIncreasing real-time jitter when multiple loads are activeThis is not a software optimization issue anymore; it is a resource saturation issue.Because of this, we are planning to move from a single-MCU architecture to a multi-MCU system.Proposed ArchitectureMaster MCU: STM32H563ZIT6Handles:All sensors (ADC / digital)Control logic & state machineRecipe executionSafety checksUI communicationNo direct motor timing generationSlave MCUs (2x):Dedicated load-handling controllersOne for stepper motorsOne for DC motors / PWM-based loadsSlaves perform only deterministic actuationNo sensors, no business logi

Hi I'm new to the STM32 board but not to Arduino IDE. I want to use two STM32 boards (with DXV lr30 900) for LoRa communication. I'm starting with a minimal program (without LoRa), just to see how the communication works between the STM32 and the Arduino IDE's serial interface. I can compile and download this program without any problems, but I don't see anything on the serial interface, whether using the ttyUSB0, ttyUSB1, or ttyS0 ports at 9600 baud.   here is the test program   void setup() { Serial.begin(9600); delay(2000); Serial.print("hello"); } void loop() { Serial.print("."); delay(1000); }   Can anyone help me ? Thanks in advance

Dear ST Community, Since the STUSB4710 is now NRND and no longer readily available, could you please advise what its recommended replacement is?I am specifically looking for a USB-C Power Delivery source controller that requires no firmware or only minimal firmware.Thank you in advance.

Hello,Does anyone know how to setup the clock source for the N657 processor?  I want to use an oscillator for the HS clock input and setup HSE = Bypass clock source...using Bypass clock it should only use PH0 (clock in) and free up the PH1 pin (clock out).  But it seems the IDE / cubeMx always wants to use both pins regardless of the clock configuration.am I missing something or is this a bug?thanks, Matt  

I am developing a solution using a STWBC2-HP tx running from a 24VDC supply to drive a STWLC99 rx and need to use the STSC protocol to achieve 50~100W. This is for bespoke power transfer rather than a conventional charger. I am basing the design on the steval-wbc2tx50 datasheet with ratings upgraded for the extra power. Also referring to '100w-wireless-charging-solution-based-on-stwbc2-hp-and-stwlc99-rayna-wang.pdf' from ST's website.Does the STSC protocol require Qi1.3 (ie does it need STSAFE-A110) and how do I enable this?Do I just need to configure the current and voltage parameters via the UART for this power level?Thanks.

Hi, I'm trying to spec a fully integrated H-bridge for driving a small motor taking up to 6A nominal, with spikes up to 12A (looking at the VNHD7012AY, VNHD7070AY, and the VNH7100BAS). There are a lot of numbers for current limitation on the ST datasheets that I've come across and I haven't been able to find an explanation for. How should I interpret all of these, and how are each of these numbers obtained?Specifically, I'm looking at:- Continuous maximum output current I_max- High-side current limitation I_lim_h- Shutdown low-side current I_sd_ls- Output saturation current I_out_sat (under Current Sense)

Hi,I’m experiencing issues configuring a display using a custom PCB with the STM32H747BIT MCU and LVGL for the UI. Currently, the project runs a minimal setup with only one loop calling lv_timer_handler();. At this point, my main goal is to get the screen working correctly.I’m using LVGL in direct mode for the display buffers.The issue I’m facing is that the screen occasionally shows horizontal glitches. I’ve created a simple spinner using the following code: /* Create a spinner */ lv_obj_t * spinner = lv_spinner_create(lv_screen_active()); lv_obj_set_size(spinner, 64, 64); lv_obj_align(spinner, LV_ALIGN_BOTTOM_MID, 0, 0);You can see the glitch in the attached video.As you can see, the glitching is more noticeable in Video_1 than in Video_2. These are the display timing configurations used for each:Video_1:Video_2: Please note that the configuration in Video_1 follows the manufacturer’s recommended settings. In Video_2, I performed some tests and observed that increasing either

I'm encountering a persistent issue when setting up an STM32Cube project in VS Code. Even when reverting to a previously working commit or starting a fresh setup from scratch (using the "Setup as an STM32Cube project" button), the process fails.The following error message appears:"Cube project discovery CMake configure step failed. Setup might be incomplete. Please check output logs"I have tested this on two different machines running both Linux and Windows, but the result is the same. Here are the relevant logs: 2026-02-20 08:41:11.309 [Info] Adding cube-cmake path to environment: /home/user/.vscode/extensions/stmicroelectronics.stm32cube-ide-build-cmake-1.43.0/resources/cube-cmake/linux2026-02-20 08:41:19.016 [Info] Running STM32Cube commands 'cube pack sync + cube pack install STMicroelectronics.stm32f4xx_dfp.1.1.0'2026-02-20 08:41:19.665 [Error] /home/user/Downloads/project needs to be configured first2026-02-20 08:41:22.979 [Info] Activating STM32Cube configurations for the c

Generating code for the STM32WLE5CBU.In timer_if.c:extern RTC_HandleTypeDef h;but in rtc.c:RTC_HandleTypeDef hrtc; It happened in CubeMx 6.16.1 and STM32Cube_FW_WL_V1.4.0 and is still happening using CubeMX6.17.0 and STM32Cube_FW_WL_V1.5.0

I have a problem with disabling gfxmmu. I don't have a rounded display so that actually I do not need GFXMMU.I created a project by using Touchgfx Designer Templates (STM32H7S78 DK BPP). GFXMMU is activated in default. I would like to disable it. So, I disable it in cubemx then exclude instrumantation files. Then I updated TouchgfxHal.cpp and frame buffer adresses as 0x9000 0000 - 0x9020 0000.Then I could succesfully build the project. When I run it, it is working particularly but the frame/image is broken down. I am adding the image here!Could you explain me how to enable or disable gfxmmu properly from project?

Hello, I read somewhere that I can use the ST-LINK built into my H563ZI to program my custom cards with STM32F401.Could someone help me figure out how to do this?Thanks in advance.

Hi,I have setup three channels in Timer_2 on an 32F429 MCU and have come across a seemingly inconsistent behaviour with regards to the alternate functions mentioned on the datasheet.More specifically, I have setup pins PA0, PA1, PA2 for Output_Compare, Input_Capture and PWM against channels 1, 2 and 3 of Timer_2 respectively and although the behaviour I observe on pins PA0 and PA1 is the expected one (well nearly the expected one but will ask a new question a bit later as that's probably a separate issue), pin PA2 is entirely dead as I don't get any pulsation happening whatsoever.I checked my configuration again and again in order to make sure it's setup correctly and verified the alternate functions I've setup for the gpio pins match the datasheet but that all looked fine:I then scrolled a bit further down on the datasheet and noticed that there's an alternative alternate-function pin for Timer_2 channel 3, namely PB10:So, I tried configuring that for the PWM pin and voila, it al

I used to work with Nucleo board STM32G474 and programm them. Recently I can not open the file to programm my devices. I looks a window problem.I installed again all the ST Tools but the problem remain.I can not open files.

Hello everyone, I'm facing a very frustrating issue with USART2 on my Nucleo-L475VGT6 board using the built-in ST-LINK Virtual COM Port. What works: - ST-LINK is detected (COM3 appears, Windows sound plays on connect) - Code downloads successfully (no error in CubeIDE console) - LED blinks (proof that main() is reached and while(1) is running) - HAL_UART_Transmit is called  What does NOT work: - Nothing appears in any terminal: MobaXterm, PuTTY,  PowerShell serial reader - No garbage, no partial characters, just black screen - Same behavior in Run mode (no breakpoint) and after physical Reset button MY code: /* USER CODE BEGIN 0 */ uint8_t tx_buff[]={0,1,2,3,4,5,6,7,8,9}; /* USER CODE END 0 */ while (1) { /* USER CODE END WHILE */ /* USER CODE BEGIN 3 */ HAL_UART_Transmit(&huart2, tx_buff, 10, 1000); HAL_Delay(10000); } What am I missing? Is there a jumper / solder bridge I forgot on Nucleo-L475VGT6 for VCP? Or is there a known bug with USART2 VCP on L4 series? Tha

Hello,I want to generate four 50% duty cycle frequencies up to ~12kHz. It should be possible to enable/disable single outputs. Currently no special high requirements about accuracy, etc. Using a STM32U0 device (56MHz max).My first thought was to use an upcounting timer with four output compare channels where the timer itself is free running (ARR set to max. value). The compare channels are set to toggle on match and on each OC interrupt, the corresponding CCR register value is set to the next equivalent ARR value to toggle again. For example, if the timer is running at 1MHz and 1kHz frequency is needed, 1000 will be added to the CCR. To start/stop the output, I'd modify the corresponding OCxM value between toggle and frozen mode.However, I'm not sure if this is the most efficient way, especially regarding overhead and complexity. Another solution which came to my mind was to use a DDS approach with a (low power) timer, constantly firing interrupts at the needed resolution. On each