Solved

Just upgraded to the latest version of STM32Cube for VS Code extension (3.6.4) and now the extension stopped to work. I've tried reinstalling the extension pack several times. Every time after the bundle was installed an error show up saying "An error occurred while synchronizing metadata. Please try run "STM32Cube: Install prerequisite bundle" and "STM32Cube: Synchronize pack list". Or work offline."Running "STM32Cube: Install prerequisite bundle" from the VS Code command palette will result in a message saying "No STM32Cube bundle to install", subsequently running "STM32Cube: Synchronize pack list" will return the original metadata synchronization error.I checked my HOME/Library/"Application Support"/stmcube/ directory, the bundle/ folder seems to contain what I expected, things like cmake, gnu-gdb-for-stm32 or the stink-gdbserver, etc. However, the packs/ folder is empty, not sure if that's the problem. I checked the output log of STM32Cube Core and found the fol

I am trying to configure BMS63CHAIN component on AEK-MCU-C4MINI1 board connected to an AEK_POW_BMSNOTX but the allocated pin mapping created by the tool does not match the C4MINI1 board connectors.I tried following the AutoDevKit chapter in um3185 Getting started with AutoDevKit battery management system (BMS) evaluation boards:1. Open AutoDevKit Studio 2.6.12. Create New SPC5 Application using SPC58ECxx Platform Component RLA3. Add SPC58ECxx Init Package Component RLA4. Add SPC58ECxx Low Level Drivers Component RLA5. Add AutoDevKit 4 Mini Init Package ComponentNote: Getting Started guide mentions adding AutoDevKit Init Package, but I can not select this together with 4 Mini Init. Seems to be mutually exclusive.6. Add AEK-POW-BMS63CHAIN component7. Open AEK-POW-BMS63CHAIN -> AEK_POW_BMSCHAIN[0]8. Select Node type: AEK_POW_BMSNOTX9. Seletct dspi: dspi0, cs0Go back to the AEK-POW-BMS63CHAIN component and press Allocate button.Go to SPC58EC 4M Mini board view. This looks stra

Hi, Is there a LL Library project example or at least a code snippet of how to transmit uart data using the GPDMA?

I use STM32Cube FW_N6 V1.2.0 to create an FW to run a web server on the DK board. I figured out that I can not talk to the PHY chip to read the PHY ID. I compared the code with another example that ST released and figured out that these codes are missing on HAL_ETH_MspInit   __HAL_RCC_ETH1MAC_CLK_ENABLE(); __HAL_RCC_ETH1RX_CLK_ENABLE(); __HAL_RCC_ETH1TX_CLK_ENABLE();   after adding this to my MSPInit function problem was solved!   I wonder if this is a bug in this package or if I need to set it in the CubeMX settings?

Hi Champs, one of my customers develop on STM32WBA54KGU6. This SoC does not come with SMPS. Although he selects the righ reference (STM32WBA54KGU6) for code generation, SMPS seems to be used by default - he has to comment the line out form generated code to build properly. he uses the latest dev tool versions : IDE : STM32CubeIDE V1.19.0 Firmware  STM32CubeWBA : V1.7.0 is it a known issue? please note that it is not a blocking point but it still requires a post code generation control from his side to comment out the generated SMPS statement in the generated code. Warm regards, Agnès

Trying to get the STM32CubeIDE for VSCode working on MacOS. I am on the latest version I think it is 3.6.4.I installed the extension according to instructions and I made a project for my NUCLEO-446RE with CubeMx.When I open the folder in VSCode it throws a Bad CMake Executable Error when I open the Setup STM32Cube project(s) section. In the search box in this section it also seems the NUCLEO-446RE is missing as well.I am not sure what is going on I tried uninstalling everything and reinstalling. I do have it in its own profile the only extensions in there are copilot and the STM32 Bundle in its entirety.Another note: I do not have a local cmake installed so there should be no conflict there.Any help would be appreciated.

Documentation: RM0390Revision: Rev 7, June 2025Section 26.3.2 Page number 830:Under Simplex communications, it says the RXONLY bit is in the SPI_CR2 register but the register map confirms RXONLY bit is in the SPI_CR1 register.

-->According to the datasheet and reference manual, I learned that the microcontroller has 64KB of memory, and I tested it and was able to read/write on pages 29, 30, 31. But why does the website say it has 32KB? #define FLASH_SAYFA_SAYISI 3 //#define FLASH_SAYFA_1 0x08006800 //#define FLASH_SAYFA 2 0x08007000 //#define FLASH_SAYFA_3 0x08007800 #define FLASH_SAYFA_1 0x0800E800 //29 #define FLASH_SAYFA_2 0x0800F000 //30 #define FLASH_SAYFA_3 0x0800F800 //31 void Flash_Kayit() { SensorKalibre_t *pFlashData; uint32_t yeni_sira = 0; uint32_t sayfa_adresi = 0; uint8_t sayfa_bul = 0; uint32_t sayfa_adresleri[FLASH_SAYFA_SAYISI] = { FLASH_SAYFA_1, FLASH_SAYFA_2, FLASH_SAYFA_3 }; for (int i = 0; i < FLASH_SAYFA_SAYISI; i++) { uint32_t* sayfa_baslat = (uint32_t*)sayfa_adresleri[i]; if (sayfa_baslat[0] == 0xFFFFFFFF) { sayfa_adresi = sayfa_adresleri[i]; sayfa_bul = 1; break; } } if (!sayfa_bul) { uint32_t eski_sira = 0xFFFFFFFF; for (int i = 0; i < FLASH_SAY

After updating Cube IDE to version 1.15.0 the memory details & memory regions map in the build analyzer are not showing any informations beside the linker script file name in all my projects start to be bold!!!

Hi,I am testing the new X-NUCLEO-67W61M1 with the NUCLEO-H7S3L8 for the purpose of sending data over WiFi and BLE. For reference, I am using the STM32CubeIDE.However, I have followed the guide in the software package for the X-NUCLEO-67W61M1 in Github (link https://github.com/STMicroelectronics/x-cube-st67w61/tree/main/Projects/NUCLEO-H7S3L8/Applications/ST67W6X/ST67W6X_CLI ) and when I try to send commands with Tera Term with the recommended settings, I see no output in the terminal.I can see that the X-NUCLEO-67W61M1 is working and correctly identified when flashing the NUCLEO-H7S3L8 with the NCP_update_mission_profile.bat file (which for some reason I could only find in the software package provided directly on the official ST site https://www.st.com/en/embedded-software/x-cube-st67w61.html). I have also tried flashing the NCP_update_mission_profile_t01 and NCP_update_mission_profile_t02 from the Github software package but I still see nothing

Hi,In STM32H56xx, if both EDATA1_EN and EDATA2_EN are set to 0, can I place application code in the high-cycle data flash memory?I am confused by these two descriptions in the reference manual:“A threshold per bank (EDATA(1/2)_STRT) is programmable in user option bytes to determine the beginning of the data flash area. By default, all flash memory is used for code.”“Attempt to fetch instructions from flash memory high-cycle data area.”

I'm trying to talk to a string of WS2812C LEDs with an STM32C011J4M6. The timing requirements are:Here's the schematic. I populated R3 and removed R1:I'm hoping for the simplest hardware implementation, so I'm using the HSI 48MHz clock. This means that each clock cycle is 20.8ns, which means that, for a 0, the pin can only be high for at most 18 clock cycles. With that in mind, I tried to write the most efficient driver that also takes the same time for each bit.My problem is that, when I try to output a string of 1s, the timings vary despite the code being the same for each bit:I get 4 short pulses (840ns, good) followed by 4 longer pulses (1670ns, too long). Somehow, ~45 extra clock cycles are embedded in the long pulses, which doesn't make any sense since the code is the same for each bit.Is the microcontroller doing background tasks or something? Why is the timing different in such a predictable way?Here's my main.c:#include "main.h" #define NUM_COLOURS 3 #define LED_COU

Hello,I'm migrating from a H743 to the N657 device.  Are there any tutorial / documentation / video that shows what the meaning of FSBL / Application / ExtMemory does and how to configure?and how to use this?thanksMatthew 

Hello to the support community,  i'm currently working on some custom coils used with the ST25R3916. I've studied the ISO/IEC 14443-2 for quite a while and recently had a look into the AppNote AN6065 from you guys.  There is quite some confusion on the topic stated in the AN around Figure 15.First of: the minimum timing values stated in Table 3 are somewhat different from the ones in the actual ISO norm. That is not really the point of my question, but i just wanted you to know.  The real question arises from the following fact:In the AN the Q factor of the coil is calcaulated to be Q<= 13.56 MHz * 3µs = 41. (The very bottom line on Page 18).The 3µs represents the time that the unloaded coil would need to rise/ fall to the min/max amplitiude. So far so good.  Looking at this timing diagram: I would expect that those 3µs would represent t3 or t1-t2 as those are the rise and fall times of the symbol. Looking in the table:* t3 = 16/fc =

Dear ST Technical Support, I am looking for reliability data for the STM32L151 series microcontrollers, including:- FIT rates (failure rates)- MTBF/MTTF calculations - Lifetime expectations- Qualification test results Could you please provide the relevant documentation or direct me to the appropriate resources? Thank you.

Hello  I tried to upgrade the STWIN.box Wi-Fi Module with the instructions provided in the  STM32CubeFunctionPack_DATALOG2_V3.1.0.  i tried dragging the HEX file to tera term with the following settings attached in the images below. i was not able to successfully upgrade the wifi module.i am using the stlink-v3minie with the boardi really appreciate the help of community memberskind regards Jose John

We are currently evaluating components for a new product design and are considering the following ST part:Part Numbers:EMIF06-MSD02N16Before proceeding, we would like to confirm the lifecycle status of these components. Specifically, we would appreciate it if you could confirm whether these parts are:Active and recommended for new designsNot recommended for new designs (NRND)Scheduled for End-of-Life (EOL) or already discontinuedAlso confirm the End of Life status (no. of Years) for these parts.If the part is not recommended or is approaching EOL, we would also appreciate any recommended alternatives or cross-reference partWe look forward to your response to help us make an informed decision.Thanks in advance..!!

STM32F411CEU6 Minimum System Board Microcomputer STM32 ARM Core BoardI'm unable to flash my board using USB DFU mode. When I enter DFU mode, Windows fails to recognize the device and shows a USB error. However, UART flashing works correctly using PA9 (TX) and PA10 (RX)- Hold the BOOT0 button- Pressed and released RESET button- Then released BOOT0- Windows shows a popup:_USB device not recognized. The last USB device you connected to this computer malfunctioned- Device Manager says "USB Device Descriptor Failed"- STM32CubeProgrammer and dfu-util do not detect the deviceAnd also I installed STM32CubeProgrammer, Drivers and more but still cant enter dfu mode On the other hand Im unable to flash board with UART which I dosent like Note- Im new to STM boardsI'd appreciate help in diagnosing and fixing the USB DFU issue on my STM32F411CEU6 Black Pill board. 

Hi AllHope everyone is well,Im working on a large and expensive project that requires dual core processing, therefore prior to committing to the cost of my project I created a custom dev board  to ensure I can achieve what is required for my project.My dev board I am soldering components using stencil and reflow plate. The Chip connects to Cube PRG and runs code I uploadWhen powering my board via USB (5v VBUS) the STM32 is getting extremely hot (Burn your finger hot), I have checked the following. 1. VCAP and VCAPDSI tied to GND via 2.2UF CAPS2. Don't appear to have any bridges across pins / pads , iv checked under microscope.3. Board is drawing current of 1.2amps when using USB.4. I am getting continuity between 3.3v and VCAP pins, which suggest I have a short, I can only think maybe a bridge on the rear of the pins that I cannot see.5. When powered on Im reading 1V on the VCAP pins, suggesting the VCAP are being pulled done by over current.6.  D+/D- pins when powered ,

Hi ST,I am using the STW3N170 in a linear application (constant current source) where the voltage can be 1500V and current as high as 16mA - total 24W.Can you please share the DC Curve of the SOA, please include in the graph the Thermal Instability due to secondary breakdown of the MOSFET. Best Regards.

I have been working recently on a board that i have made for a flight computer. But unfortunately, I have encountered some problems while programing the board.The conection to the board works great, and I´m able to upload de code and read it. The Issue comes when I try to make the code run that the board does not do anything. I have the doubt of it being a hardware or software problem as I did the design of the board.Here I adjunt some of the evidences that I have been looking in case someone needs them to provide and answer:debugger console log:warning: ARM M in lockup state, stack unwinding terminated. set *(unsigned int *)0xe00430a0&=~0x1 Note: automatically using hardware breakpoints for read-only addresses. set *(int *)0xE000EDFC=*(int *)0xE000EDFC|0x7F0 set *(unsigned int *)0x5c001004|=0x3f warning: ARM M in lockup state, stack unwinding terminated. set *(unsigned int *)0xe00430a0&=~0x1 Note: automatically using hardware breakpoints for read-only addresses. set *(int

#include <stdint.h> #include <stdio.h> #include "stm32f4xx.h" volatile uint8_t rxdata = 0; int main(void) { SystemInit(); SystemCoreClockUpdate(); // clock configutation RCC_AHB1PeriphClockCmd(RCC_AHB1Periph_GPIOB, ENABLE); // TX: PB6 RX: PB7 RCC_AHB1PeriphClockCmd(RCC_AHB1Periph_GPIOD, ENABLE); // LED LED4: PD12 LED3: PD13 RCC_APB2PeriphClockCmd(RCC_APB2Periph_USART1, ENABLE); RCC_APB2PeriphClockCmd(RCC_APB2Periph_SYSCFG, ENABLE); NVIC_PriorityGroupConfig(NVIC_PriorityGroup_4); // gpio initialization GPIO_InitTypeDef GPIO_InitStruct; GPIO_StructInit(&GPIO_InitStruct); GPIO_InitStruct.GPIO_Mode = GPIO_Mode_AF; GPIO_InitStruct.GPIO_OType = GPIO_OType_PP; GPIO_InitStruct.GPIO_Pin = GPIO_Pin_6 | GPIO_Pin_7; GPIO_InitStruct.GPIO_PuPd = GPIO_PuPd_UP; GPIO_InitStruct.GPIO_Speed = GPIO_Speed_50MHz; GPIO_Init(GPIOB, &GPIO_InitStruct); GPIO_PinAFConfig(GPIOB, GPIO_PinSource6, GPIO_AF_USART1); GPIO_PinAFConfig(GPIOB, GPIO_PinSource7, GPIO_AF_USART1); // usart initiali

I have made an adapter that sits between the STLink V3 and the device that needs to be programmed, so that I can give T_VCC on the STLink side 3.3V from an external supply.So far I have used 3.3V as VCC on the target as well, but I am considering lowering VCC on target to 3.0V instead.As far as I can tell from datasheets, there shouldn't be an issue with keeping T_VCC on the STLink side at 3.3V while VCC on target is 3.0V, but I wanted to check here if anyone has something different to say about this mismatch. If it's a bad idea, I will need to have adapters around with T_VCC 3.0V and others with T_VCC 3.3V depending on which target device I work with, which in this case is a bit of a hassle.

HiJust hours ago, I updated the IDE from 1.14.0 to the latest version 1.19.0, a build on the project I have been working on fails by RAM and Flash overflow. This issue has been resolved before the IDE update. Check the 2 map files, I found the (NOLOAD) in the linker script has no effect in the new IDE.The error message from the linker:  The F767 board is customized with 32MB external SDRAM, memory map and sections are defined as below: MEMORY { MEM3BASE (xrw) : ORIGIN = 0X20000000, LENGTH = 60K MEM3MAP (xrw) : ORIGIN = 0x2000F000, LENGTH = 4K MEM1BASE (xrw) : ORIGIN = 0x20010000, LENGTH = 160K MEM1MAP (xrw) : ORIGIN = 0x20038000, LENGTH = 10K RAM (xrw) : ORIGIN = 0x2003A800, LENGTH = 512K-234K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 1024K LCD_BUF (xrw) : ORIGIN = 0XC0000000, LENGTH = 2000K MEM2BASE (xrw) : ORIGIN = 0XC01F4000, LENGTH = 28912K MEM2MAP (xrw) : ORIGIN = 0XC1E30000, LENGTH = 1807K MEM4BASE (xrw) : ORIGIN = 0xC1FF3C00, LENGTH = 49K } /* Afte

I just discover that the TouchGFX tool run only on Windows ...:(I do not use Windows and I have no plan to use it one day.Do you know if it run on Linux with Wine ?Thanks