Solved

So I want to order a STM32F407VG. But I would love to know where they are being shipped from. Because I don't see any VAT being added to my order. I could not find the information anywhere.I live in europe so I just wanted to know where they ship their products from.Thank you.

Hello,last week I purchased an  X-NUCLEO-67W61M1 eval board from ST eStore  (the cost is about 38$ = 32 Euro) taking advantage of the free-shipping. Yesterday, Fedex told me that I have to pay 28 Euro as custom duties (+ VAT for Italy). I'm very disappointed about that because I was not aware about that amount before paying.I would ask to add a feature in the ST eSTORE website in order to estimate the custom duties (shipping from USA) and VAT for Europe so the customer can check if it's more convenient to purchase the item on another website in Europe.Thanks 

Hello everyone,I’m working with the NUCLEO-WB55 (MB1355D-01) board, and looking at its LSE crystal, the NX2012SA 32.768 kHz with ESR ~120 kΩ and load capacitance 6 pF (Datasheet attached).Calculating the crystal’s minimum transconductance (Gₘ) using:Gm=4×ESR×(2πf)^2×(C0+CL)^2 ≈ 1.1μA/VFrom the STM32WB55 datasheet, the maximum critical crystal gm (Gmcritmax) values depending on the LSEDRV drive setting are:00 (Low): 0.50 µA/V01 (Medium low): 0.75 µA/V10 (Medium high): 1.70 µA/V11 (High): 2.70 µA/VMy software engineer mentioned ST uses the lowest drive setting (00) for the LSE oscillator by default, but based on the crystal’s Gₘ, this seems insufficient for reliable oscillation on the NUCLEO board.Given the crystal Gₘ is around 1.1 µA/V (above the lowest and medium low drive thresholds), how does the LSE oscillator function properly on the NUCLEO-WB55/EVM board? Even at the highest drive level, the margin seems small.Is ST actually using a higher drive level on the EVM/Nucleo boards

I am implementing a dual-bank-like firmware architecture on the STM32WLE5CCU6 microcontroller, which does not natively support true dual-bank flash. In this setup, I need to write data to a region of the internal Flash memory that is part of the same memory space from which the code is currently executing. I would like to understand how Flash write operations can be safely performed in such a scenario—specifically, how to write to a different section of the same Flash memory while code execution continues from another region within that same Flash.

Hello, all,I'm using STM32CubeIDE to design my first STM32 micro-controller circuit. I've used the tool to assign functions to about 20 pins on the micro-controller so far. Now, I'm at the stage where I'm creating the schematic and connecting external circuitry to the micro-controller pins.Is there an easy way to get a list of the pins I've assigned so far, along with User Labels, so I can go right down the list and wire up the circuits? What I'm doing so far is to keep the STM32CubeIDE open on one monitor and view the pin-out view, and work my way around the chip, wiring pins as I go. Is this the most efficient way to work? Is this how most others do it? I wondered if I was overlooking some built-in function of STM32CubeIDE to perform this task.Thanks for your advice and suggestions.-Kevin 

Hi.I like to make a little spreadsheet/graphic for MCUs that shows all of the available pins and the functions available on them. You can sort of view it in CubeMX, but not in a table. Makes selecting pins and layouts easier.I do them by hand but it's a chore, especially on MCUs with a lot of peripherals. Is the data available in some form that I can process automatically? There is a table in the reference manual of each part, but it's not easy to convert to something like CSV.Thanks.

HiI'm testing a FMC connection between the mcu on a STM32H753I-EVAL2 board, and a FPGA acting as a SRAM device.Write operations looks OK, but when I try to perform a read operation, it looks like that even thought the nxe and noe behave as expected, the mcu is driving the data bus with random data, not allowing the FPGA to drive desired data.I tried various timing settings, and also changed to PSRAM, in regular and muxed mode, but nothing changed.I also turned on the MPU, with a allow all transactions setting. Can you please point me to what I'm missing here?

I'm working with a NUCLEO-WB15CC board (MB1641C-01) and am trying to use three independent serial ports for my project.I have found that the D8 and D2 pins on the board are not working for serial communication. I believe this is due to a pin conflict with the on-board ST-LINK debugger, as a table in the board's documentation shows PA9 and PA10 are routed through jumpers to the ST-LINK (JP5 pins 13-14 and 15-16).My question to the community is whether D8 and D2 pins are indeed unavailable for user applications due to the ST-LINK routing.Thank you for your help.

i have successfully make some basic module in stm32l552 nucleo in register level and in asm , successfully programGPIO, TIMER, UART RX,TX,. But stuck in interrupt section for few days. i am tring to toggle onboard led(PA9) using user button PC13. my hal code running successfully using call backvoid HAL_GPIO_EXTI_Falling_Callback(uint16_t GPIO_Pin)  &void HAL_GPIO_EXTI_Rising_Callback(uint16_t GPIO_Pin)But failed to get into ISR without using HAL. Athough EXTI->EXTICR[3] , IMR1, RTSR1 value is same as my HAL auto generated code.please help. here is my simple code......................  //user button PC13(NUCLEO BOARD MANUAL PAGE NO.33 ) input STM32L5 Series//pa9 onboard led//board : NUCLEO L552ZET6Q#include "stm32l5xx.h"volatile int userbuttoncounter; //for monitoring //void EXTI13_IRQHandler(void)void EXTI13_IRQHandler(){//if (EXTI->RPR1 & EXTI_RPR1_RPIF13) orif ((EXTI->RPR1 & (1U<<13)) != 0 ) {//clear PR flagEXTI->RPR1 |= (1U

Hello ST Community, I have designed a custom PCB using the STM32H750XBH6 microcontroller. After soldering the chip to the PCB, I attempted to connect it via ST-LINK using the standard SWD interface, but the device is not being detected. I have verified the following points: VDD, VDDA, and VDD_LDO are supplied with 3.3V VSS and VSSA are connected to GND PDR_ON is tied to VDD (as recommended) VCAP1 and VCAP2 are connected to 2.2µF capacitors to GND BOOT0 is pulled down to GND SWDIO, SWCLK, and NRST are correctly connected to the ST-LINK Voltages and connections are checked with a multimeter — all seem fine Despite this, ST-LINK shows "Target voltage: 0.0 V" and fails to detect the core ID. Additionally, I noticed that in the official STM32H750 Nucleo board schematic, some NC (Not Connected) pins are routed either to 3.3V or GND, even though the datasheet specifies these pins as NC. This seems contradictory, and I’d like clarification on whether NC pins must be left unconn

I want to check and ensure the option bytes are correct from with my executing program. But writing the option bytes is very flaky if the IWDG is active. For some reason, there is a stall at "FLASH_CR_OBL_LAUNCH". Or maybe it makes it past but not soon after the watch dog resets the MCU and the option bytes are not written. This is an ongoing cycle forever.If I disable the IWDG then things work normally. Any idea why? void CodeProtect() { bool needsUpdate = false; // Unlock FLASH if (READ_BIT(FLASH->CR, FLASH_CR_LOCK) != 0x00U) { /* Authorize the FLASH Registers access */ WRITE_REG(FLASH->KEYR, FLASH_KEY1); WRITE_REG(FLASH->KEYR, FLASH_KEY2); } // Unlock Option Bytes if (READ_BIT(FLASH->CR, FLASH_CR_OPTLOCK) != 0x00U) { /* Authorizes the Option Byte register programming */ WRITE_REG(FLASH->OPTKEYR, FLASH_OPTKEY1); WRITE_REG(FLASH->OPTKEYR, FLASH_OPTKEY2); } // --- Check and update RDP level --- uint32_t optr = FLASH->OPTR; const uint32_t c

Hello there!I am on my first foray away from HAL and into bare-metal programming, and am trying to configure LPTIM1 and LPTIM2 on my stm32u031 to periodically trigger interrupts. I am experiencing bizarre behavior that I'm struggling to understand how to troubleshoot. I have two config functions for these timers, one of them looks like:  static void configure_lptimer2() { RCC->APBENR1 |= RCC_APBENR1_LPTIM2EN; if ((RCC->CSR & RCC_CSR_LSION) == 0) { RCC->CSR |= RCC_CSR_LSION; while ((RCC->CSR & RCC_CSR_LSIRDY) == 0); } RCC->CCIPR &= ~(RCC_CCIPR_LPTIM2SEL); RCC->CCIPR |= RCC_CCIPR_LPTIM2SEL_0; LPTIM2->CR &= ~LPTIM_CR_ENABLE; LPTIM2->CFGR &= ~LPTIM_CFGR_PRESC_Msk; LPTIM2->CFGR |= (0x0 << LPTIM_CFGR_PRESC_Pos); LPTIM2->ICR = 0xFFFFFFFF; LPTIM2->DIER |= LPTIM_DIER_ARRMIE; NVIC_EnableIRQ(TIM7_LPTIM2_IRQn); NVIC_SetPriority(TIM7_LPTIM2_IRQn, 0); LPTIM2->CR |= LPTIM_CR_ENABLE; LPTIM2->ARR = 1333

Hello everyone, I've designed a custom board with STM32H723ZG, previously based on STM32F767ZG. When I connect board with ST Link V2 prog through SWDIO, SWDCLK and GND, I get response that no target has been detected. I'm currently using ST-Link Utility software. If I desolder H723ZG and replace it with F767ZG, board works completely fine, without any issues. What could possibly be issue, should I order ST-Link V3 prog for the H723 MCU?Please check attached schematic of the board, MCU related stuff is on second page.Thanks everyone in advance! :)

I try to create code, which flashes LED2 ( few flashes , not one toggle ) in response of one press of Blue button.What could be wrong in my code ? Selected two pins PA5 ( input for LED2 ) and PC13 (EXTI for Blue button with External interrupt Mode with Rising edge trigger detection   + no pull up no pull down )   NVIC EXTI line  checkbox - marked.And Cube IDE generated code with EXTI callback function etc.In my main.c file, I added this code only:/* USER CODE BEGIN 4 */ void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin) { /* Prevent unused argument(s) compilation warning */ UNUSED(GPIO_Pin); if (GPIO_Pin == GPIO_PIN_13) // If The INT Source Is EXTI Line9 (A9 Pin) { HAL_NVIC_DisableIRQ(EXTI15_10_IRQn); // Disable EXTI interrupt Flash_LED2(); HAL_NVIC_EnableIRQ(EXTI15_10_IRQn); // Re-enable EXTI interrupt } } void Flash_LED2(void) { //HAL_NVIC_DisableIRQ(EXTI15_10_IRQn); // Disable EXTI interrupt for (int i = 0; i < 7; i++) { HAL_GPIO_WritePin(

Hi everyone,I am currently working with the NUCLEO-H7S3L8 board and using STM32CubeMX version 6.14.1 to generate code. I've kept everything at default settings and only added pins to toggle LEDs for testing. However, when I try to debug the code, I run into an issue where the boot subproject gets stuck at the SCB_EnableDCache(); function for a while, before eventually jumping to Error_Handler(void).I haven’t modified anything else in the generated code, so I'm wondering if there’s a configuration setting I may have missed or something I need to tweak in order to resolve this issue.Has anyone encountered this behavior or know what steps I should take to fix it?Thanks in advance for your help!

I cannot enable DCMI for STM32H753ZIT in STM32CubeMX version 6.15.0. I'd assume DCMI can be indeed used and that this is just a bug on CubeMX's part, but I'd like to verify before I do any orders. Related:- https://community.st.com/t5/stm32-mcus-products/minimum-clock-speed-and-enabling-pssi-problem/td-p/709772- https://community.st.com/t5/stm32cubeide-mcus/dcmi-cannot-be-used-on-the-latest-revision-cubeide-1-15-1-with/td-p/691876

Dear community,In STM32G0 or maybe in STM32 family in general, is there a possibility to disable the debug module permanently, the idea is that when the code is loaded and tested, then the next step is to disable SWD/JTAG port so that debug or loading another firmware is not possible anymore.Thank you in advance for your support.Best regardsB.T

I am using the USB CDC driver code provided by ST in stm32cubeide, and am trying to figure out a proper minimum heap size. I have found various slightly conflicting answers, but the consensus seems to be that 512 bytes is not enough.In the same application, I also use FATFS, but I'm not 100% sure if that is supposed to use the heap.Now I wanted to test just how much of the heap is in fact overwritten. To do this, I brutally stored the byte sequence AA BB CC DD over and over in the first 1 KB of the heap. I did that with this piece of code inserted in main.c, immediately after the entry point:uint32_t *heapPtr; uint32_t *heapOrigin; (...) /** * @brief The application entry point. * @retval int */ int main(void) { /* USER CODE BEGIN 1 */ uint16_t i; heapOrigin = malloc(4); free(heapOrigin); heapPtr = heapOrigin; slDebug6 = (uint32_t)heapOrigin; for (i = 0; i < (1024 / sizeof(*heapOrigin)); i++) { *heapPtr = 0xDDCCBBAA; heapPtr++; } /* USER CODE END 1 */The malloc(4

 Folks,I suddenly have this weird thing where when I set a breakpoint in the Cube IDE it doesn't work, I don't get the usual blue symbol and I do get the one above. I can't even make out what it's supposed to be to Google it. Anyone seen this and know what's going on please?Thanks!

How does this work with a ClickListener?I have a view with 10 custom containers. How can I tell the view when a custom container has been pressed and which one? Do you have a simple example?ThanksRegards, Roger

 Hello,Years ago, I integrated the DFUSe DLLs (STDFU.dll, STDFUFiles.dll, STDFUPRT.dll, STTubeDevice30.dll) into my 32-bit .NET application to update firmware on my devices. Everything has been working perfectly and is still running smoothly.Now, I need to run my application as 64-bit, but unfortunately, the DFU DLLs are only available in 32-bit.I was able to obtain the DFUSe C++ project and successfully recompile it in 32-bit. However, when attempting a 64-bit build, I encountered multiple errors. Since I’m not very experienced with C++ (I mainly work with C# in Visual Studio and C with STM32CubeIDE), I couldn’t resolve the issues on my own.I’m looking for a way to obtain these DLLs compiled for 64-bit:STDFU.dllSTDFUFiles.dllSTDFUPRT.dllSTTubeDevice30.dllI understand DFUSe is considered obsolete, but this update method fits perfectly with my systems, which are fully based on it. I would prefer not to change anything in the infrastructure—just to have the DLLs compiled for 64-bit.

Hello, I am designing a device that will have an STM32L4 or maybe an STM32U and will communicate with an ESP32 for internet connectivity. However, at some point, I would like to update the firmware remotely, and have the ESP32 stop executing its conventional software and act as a programmer for the STM32. Is this possible? And if so, where can I find detailed information on how to do it? I hope you can help me, thank you.

Hi all,I followed this STM32CubeIDE tutorial to debug an STM32H7S3L8 project running from external flash (OSPI NOR). After flashing and starting the debug session, I get the following error:Break at address "0x8000B2C" with no debug information available, or outside of program code.Here is the log from STM32CubeProgrammer:STMicroelectronics ST-LINK GDB server. Version 7.11.0 Copyright (c) 2025, STMicroelectronics. All rights reserved. Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled Waiting for debugger connection... Debugger connected Waiting for debugger connection... Debugger connected Waiting for debugger connection... ------------------------------------------------------------------- STM32CubeProgrammer v2.20.0 ------------------------------------------------------------------- Log output file: C:\Users\Admin\AppData\Loca

Hi, I am running firmware for USBX MSC device. The example project  "Ux_Device_MSC" on demo board STM32U575I-EV.  MSC device is enumerated on computer and FATS file system is used. It can transfer file from computer to storage on STM32U575I-EV.  I am trying to figure out the following parameters. 1. how many times the following function in source file "ux_device_msc.c" is called when transfer a large file UINT USBD_STORAGE_Write(VOID *storage_instance, ULONG lun, UCHAR *data_pointer, ULONG number_blocks, ULONG lba, ULONG *media_status) { UINT status = UX_SUCCESS; /* USER CODE BEGIN USBD_STORAGE_Write */ UX_PARAMETER_NOT_USED(storage_instance); UX_PARAMETER_NOT_USED(lun); UX_PARAMETER_NOT_USED(media_status); ULONG WriteFlags = 0U; /* Check if the SD card is present */ if (HAL_GPIO_ReadPin(GPIOI, GPIO_PIN_0) == GPIO_PIN_SET) { /* Check id SD card is ready */ if(check_sd_status() != HAL_OK) { Error_Handler(); } /* Start the Dma write */ status = HAL_SD_WriteB

 Hey there,I’m trying to enable SPI on the NUCLEO-H7S3L8 using the Template_XIP project from STM32CubeH7RS, but I’m running into issues.First, I tried enabling SPI1 through CubeMX on the Template_XIP project, but it didn’t generate the necessary driver code. When I build, I get this error:/Users/++++++/STM32Cube/Repository/STM32Cube_FW_H7RS_V1.2.0/Projects/NUCLEO-H7S3L8/Templates/Template_XIP/Appli/Src/main.c:167:(.text.MX_SPI1_Init+0x96): undefined reference to `HAL_SPI_Init'collect2: error: ld returned 1 exit statusmake: *** [makefile:66: Template_XIP_Appli.elf] Error 1 So I made a new project from scratch for the same board, copied the relevant config from Template_XIP, and now CubeMX does generate the SPI code. But when I run it, I get a HardFault right away.I tried digging into it with the usual debug steps according to this blog "How to debug a HardFault on an Arm® Cortex®-M STM32" (SP was 0x2000FFDC, next addresses 0x20020000, 0x20010024…), but honestly none of it