Solved

Hello ST Support Team,I am reporting a regression issue with the latest STM32F0xx Device Family Pack (DFP) version 3.1.1 when used with Keil MDK 5.43a.Problem Description:Installation Issue: The DFP 3.1.1 often fails to install via the Pack Installer, showing validation errors or failing to resolve dependencies.Missing Registers: Even when successfully installed, the System Viewer in Debug mode is empty. Peripheral registers (GPIO, RCC, etc.) do not appear for the STM32F030 series.Environment:IDE: Keil uVision v5.43a.0Device: STM32F030xx (all variants)Pack: Keil::STM32F0xx_DFP.3.1.1OS: Windows 11Observations:The issue seems to be related to the new SVD (System View Description) file structure or pathing in the 3.x.x branch.Manually pointing to an older SVD file (from DFP v2.2.3) restores the register visibility.The "System Viewer" list in the "Peripherals" menu remains blank when using the default settings of the 3.1.1 pack.Request:Please verify the compatibility of the SVD files in th

I have a question about writing to the STM32F410's FLASH.I'm creating a program to write data received via USART to FLASH, but it's not working correctly.The writing to FLASH itself is happening, but the written data differs from what I expect.This different written data contains a large number of “0xAA” values that are not present in the original data.Do you know what might be causing this phenomenon?void FLASH_UNLOCK(){ while ((FLASH->SR & FLASH_SR_BSY) != 0){ } if ((FLASH->CR & FLASH_CR_LOCK) != 0) { FLASH->KEYR = 0x45670123; FLASH->KEYR = 0xCDEF89AB; } } void FLASH_DELETE(uint32_t address){ while ((FLASH->SR & FLASH_SR_BSY) != 0){ } FLASH->CR |= FLASH_CR_SER; FLASH->CR |= (FLASH_CR_SNB & 0x8); FLASH->CR |= FLASH_CR_STRT; while ((FLASH->SR & FLASH_SR_BSY) != 0){ } if ((FLASH->SR & FLASH_SR_EOP) != 0) { FLASH->SR |= FLASH_SR_EOP; } else { } FLASH->CR &= ~FLASH_CR_SER; } void FLASH_Write

I’m a beginner with TouchGFX, and I’m wondering whether it’s possible to make touch input behave the same way it does on mobile smartphones. Specifically, before a drag event is detected, the finger must move a certain number of pixels.What I’d like is this: when a press event is first detected, you check whether the user has moved their finger at least 10 pixels, and only then do you start moving the screen. However, once that threshold is reached, the screen should move starting from 1 pixel. When the user releases their finger, a release event occurs and everything is reset, so that after the next press event, the finger must again move 10 pixels before a drag event can occur.Is it possible to implement this behavior? I tried using setDragThreshold, but then the entire screen scrolls by the number of pixels specified as the threshold. Is it possible to change setDragThreshold dynamically in the view?

Hi,I am using the X-NUCLEO-NFC09A1 with the demo project “ST25R200_v3.0.0_Linux_demo_v1.0”.The code is running on a Raspberry Pi 3B and communicates with the reader via SPI.When I run the demo and place an NFC tag near the reader, the application reports “READ Fail”.Could someone please explain what this error means and what might cause it?Thank you.

Hi, I have been working on a project that is based on the ST25R3911b Discovery Board including building prototype firmware from the discovery kit's firmware. I have made sure not to edit any of the RFAL or HAL library files.Recently I had brought this prototype to be pre-scanned for radiated immunity. During this testing, I discovered a bug that I have not seen before.The process gets stuck in an infinite loop in the rfalTransceiveRunBlockingTx() function (found in rfal_st25r3911b.c).Specifically on line 1267, while( (rfalIsTransceiveInTx() && (ret == ERR_BUSY)) );In the rfalTransceiveTx() function, the process enters the RFAL_TXRX_STATE_TX_WAIT_TXE case and checks for interrupts. However, there will not be any interrupts to process, and so the process breaks without updating the gRFAL.TxRx.state.This appears to me like the interrupt from the NFC chip was either not sent or was not received correctly, so when that Do while loop checks "(ret == ERR_BUSY)", it will always be

I'm migrating from Windows to Linux (Ubuntu 22.04) as my main OS, and I'm setting up the STM32CubeIDE for development.  I noticed that the Linux install of STM32CubeIDE (v2.0.0 downloaded from this site) is missing almost all of the ST specific features that make using the IDE worth it for me.  Is there a reason for this?  Is there a way to install these after the fact?The ST specific features I'm speaking of are the integration of STM32CubeMX and ability to generate all the initialization code for the various peripherals that I'm looking to use.   Specifically: I'm looking for the Linux install to have an option of File > New > STM32 Project, which then gives me the option to select a board (Nucleo, etc.) or a bare MCU (STM32U575xxx, etc). It then generates a .ioc file and eventually generates the code.  

When I open STM32CubeProgrammer (v2.21.0) it displays an error modal "Old ST-LINK firmware version. Upgrade ST-LINK firmware. If I click the "Firmware Upgrade" button an STLinkUpgrade 3.16.8 shows up with Current firmware: (blank)Type: (blank)Version: UnknownUpdate to Firmware: Unknown.The upgrade button does nothing when clicked. How do I fix this?I downloaded the software here  https://www.st.com/en/development-tools/stsw-link007.htmlAfter running/usr/lib/jvm/java-17-openjdk-amd64/bin/java -jar stsw-link007-v3-17-10/stsw-link007/AllPlatforms/STLinkUpgrade.jarThere is another upgrade dialog with version 3.17.10 displaying the same firmware info as above, with the upgrade button greyed out.Other commands ive run$ ls -l /dev/bus/usb/001/019crw-rw----+ 1 root plugdev 189, 18 Feb 9 09:36 /dev/bus/usb/001/019$ lsusb | grep STBus 001 Device 019: ID 0483:374b STMicroelectronics ST-LINK/V2.1$ STM32_Programmer_CLI -l---------------------------------------------------------------

We have a design that has been working fine for some time now using STM32G071CBT6 in LQFP48 but a new batch is suddenly failing with ADC readings from VREFINT that are quite a way out of spec.Previous versions have always been slightly low - reading maybe ~3.15v on a ~3.25v supply voltage but that's always been "close enough", but now the latest batch of devices are dipping below 3.0v on the same ~2.35v supply and triggering our under-voltage detection.We are monitoring a few voltages using the ADC, including the supply voltage which is commoned with VDD/VDDA, VBAT and VREF pins - decoupling is per the power supply scheme shown in the datasheet DS12232.VREFBUF is disabled.Since we are not worried too much about absolute accuracy, we are not running the calibration routine on the ADC.System clock is 16MHz and ADC sampling is 79.5 cycles, ADC resolution is 12 bit.The ground pin is solidly grounded, supply voltage going into the pins is ~3.25v and I can't see any significant current being

Hi everyone,I’m building a coffee machine project using STM32C071 (C0) mainly because it has USB. I need USB Host MSC to:Mount a USB flash drive (FAT)Read/write files (params/logs)Firmware update from USB driveThe “official” ST stack seems to be ThreadX + USBX + FileX. Since there’s no USB Host MSC example for C0, I used an STM32L4R5 example (much larger RAM) as reference and adapted it.Issue: To pass ThreadX/USBX init, I kept increasing stacks/pools until I’m using ~20 kB of RAM. Then, when I plug the flash drive, enumeration fails with out-of-memory errors (e.g., UX_DEVICE_ENUMERATION_FAILURE / allocation failure).Questions:Is ~20 kB RAM just to init (and still fail at enumeration) expected for USBX Host MSC + FileX, or does it strongly suggest misconfiguration?Is there any official guideline/table (ST/Azure RTOS) for typical/minimum RAM for USBX Host + MSC + FileX (FAT)?Is there a practical RAM “floor” to enumerate + mount FAT + read/write files (single device, no HUB)? Like “below

We are facing an intermittent EWGF (Error Warning Flag) issue during CAN communication at 1 Mbps on multiple STM32 MCUs. The same hardware and software setup works reliably at 500 kbps without any CAN warnings.MCUs UsedSTM32L443VCT6STM32L443CCT6STM32F437ZGT6All devices communicate together on the same CAN bus.Issue DetailsWhen CAN bit rate is configured to 1 Mbps, the EWGF bit in CAN_ESR register gets set intermittentlyCommunication does not stop immediately, but error counters increase over timeAt 500 kbps, the issue is not observedSame CAN transceivers, wiring, and termination are usedCAN ConfigurationCommon SettingsCAN peripheral clock: 24 MHzGPIO speed for CAN TX/RX pins: High speedSame clock source and configuration across all MCUsFor Bit Rate 500KHzCANx->BTR = CAN_TSEG1(12) | CAN_TSEG2(1) | CAN_BRP(2) |CAN_SJW(0); For Bit Rate 1MHz (Tried for different TQ , but still getting CAN warning)TQ per bit = 8 TQCANx->BTR = CAN_TSEG1(5) | CAN_TSEG2(0) | CAN_BRP(2) |CAN_SJW(0);&

 Hi, Can i use the NUCLEO-N657X0-Q board as custom ASIC over an Octal SPI style bus? Thanks Atchaiah

Hello, I need a circuit schematic for the NUCLEO-L010RB development board, specifically for lighting up the LEDs.

Greetings, I am looking for pointers to material describing recommended ways to interact with built-in flash memory for general data reading and writing.DS9716 indicates there are several memory-mapped regions that could suffice, but maybe block 6 (starting at 0xC000 0000) seems like a safe bet, since it is "Not used"?Since this is for data storage and retrieval only, not instruction storage and retrieval, is there any need to mark the region of memory in some way in the loader script?Also, I noticed the HAL functions have some flash-based functions (UM1725) - there is some good info in there but again I'm not sure what memory target would be best for these functions.Apologies if this has been written up somewhere already. I see several "lab" type resources on the web for demonstrating how to do this, but I haven't seen a recommended practice in the official documentation or the knowledge bases here.

Not sure what is going on, im unable to toggle an IO and im not sure why...This is a very simply custom board, it uses I2C, CAN and USB. I've configured everything in CubeMX and double checked the pinout and gerber files several times but i can't find anything wrong. I've double checked the voltages on VDD and VDDIO2, both are 3.3V. I've tried configuring PD2 as Push-Pull and Open drain with and without pull-up but i get no change on the pin when measuring with my scope.PD2 is connected to the CAN STBY pin that has an internal pull-up, the pin remains high when the PHY is connected and low when the PHY is disconnected. This would indicate that there is no short on the board and that the electrical part is fine. I have physically probed the connections on the board and they are correct.What am i missing, do i need to configure something else? Below is the minimum CubeMX project. I2C and the EXTI work fine but PD2 does not.  int main(void) { /* USER CODE BEGIN

Hi all,I’m running into an issue with LPTIM1 when using LSE as the clock source. The exact same configuration works perfectly when I use LSI or PCLK, but with LSE the code gets stuck waiting for the ARROK flag after writing ARR.The code blocks forever at:while (!LL_LPTIM_IsActiveFlag_ARROK(LPTIM1)) {} So it looks like the ARR register update is never acknowledged when LSE is the clock.Important notesLSE is definitely running — it’s already used elsewhere in the system without issues.We are looking for low power applicationwe using STM32U073CBT6Clock configurationLL_RCC_SetLPTIMClockSource(LL_RCC_LPTIM1_CLKSOURCE_LSE); LL_APB1_GRP1_EnableClock(LL_APB1_GRP1_PERIPH_LPTIM1); LL_IOP_GRP1_EnableClock(LL_IOP_GRP1_PERIPH_GPIOC); NVIC_SetPriority(TIM6_DAC_LPTIM1_IRQn, NVIC_EncodePriority(NVIC_GetPriorityGrouping(), 3, 0)); NVIC_EnableIRQ(TIM6_DAC_LPTIM1_IRQn);LPTIM configuration/* Make sure timer is disabled before config */ LL_LPTIM_Disable(LPTIM1); /* Select clock & prescaler FIRST *

I referred to this article: “Bootloader jump to Application HardFault - STM32H563.”I am also using the STM32H563, and used the following function to jump to the application, but the jump does not succeed. My test program is very simple. After creating an STM32H563 project, I only configured the UART to print messages so I can identify which program is currently running./* Bootloader */ typedef void (*pFunction)(void); void relocate_exe(uint32_t app_addr) { uint32_t appStack; uint32_t appResetHandler; pFunction appEntry; appStack = *(volatile uint32_t *)app_addr; appResetHandler = *(volatile uint32_t *)(app_addr + 4); appEntry = (pFunction) appResetHandler; __disable_irq(); SysTick->CTRL = 0; SysTick->LOAD = 0; SysTick->VAL = 0; SCB->VTOR = (uint32_t) app_addr; __set_MSP(appStack); //__enable_irq(); appEntry(); } int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_USART3_UART_Init(); char msg[128]; sprintf(msg, "Bootloader!!!(%x)\

Title edited to flag that this relates to a Blue PillI'm trying to connect an STM32-STLink-V2 with three wires via SWD (GND, SCLK,SDIO). Was able to run a firmware upgrade, now V2J46S7.Clicking on Connect gives:15:35:11 : UR connection mode is defined with the HWrst reset mode 15:35:11 : ST-LINK SN : XXXXXXXXXXXXXXXXXXXXXXXXXX 15:35:11 : ST-LINK FW : V2J46S7 15:35:11 : Board : -- 15:35:11 : Voltage : 3.02V 15:35:11 : SWD freq : 4000 KHz 15:35:11 : Connect mode: Normal 15:35:11 : Reset mode : Hardware reset 15:35:11 : Device ID : 0x410 15:35:11 : Revision ID : Rev X 15:35:11 : Debug in Low Power mode is not supported for this device. 15:35:12 : UPLOADING OPTION BYTES DATA ... 15:35:12 : Bank : 0x00 15:35:12 : Address : 0x4002201c 15:35:12 : Size : 8 Bytes 15:35:12 : Bank : 0x01 15:35:12 : Address : 0x1ffff800 15:35:12 : Size : 16 Bytes 15:35:12 : UPLOADING ... 15:35:12 : Size : 1024 Bytes 15:35:12 : Address : 0x8000000 15:35:12 : Read progress: 15:35:13 : Error: Data read failed 15:37:1

In STEVAL-KITXCB for controlling SD/OD pin of L6491 using such method. PWM_en connected to MCU pin. I want use same principle in my design. Can anybody describe how program this.Is such hw connection support both function for enable PWM and for controll error state of driver? (I need both) 

According to a Blogpost regarding the the TeseoVI series from February 2025, ST has already released the TeseoVI family chipsets ("ST is launching today the TeseoVI [...]").Yet, as of January 2026, neither the chipsets, nor the modules or the Evaluation boards are available anywhere.What's the state on the actual release/availability on the TeseoVI modules/devboards?When will at least the evaluation boards be available?I'm specifically interested in the Teseo-ELE6A.

Can Nano edge AI be used to log data from STM32N6570-DK, which is connected to three sensors? If Yes, Is there any documentation available ? 

  Hello everyone, I am facing a confusing behavior with USB SOF events on two identical STM32 boards and I would appreciate any insight. Hardware 2 × NUCLEO-H743ZI2 Same MCU revision (checked device ID, revision ID – identical) Same USB connection to the same PC (USB OTG FS, device mode) Software Exactly the same firmware binary programmed on both boards STM32 HAL + CubeMX generated project USB CDC device (USB OTG FS) No conditional compilation, no board-specific code What I want to measure I wanted to check: Whether USB SOF events are really occurring every 1 ms Whether SOF can be considered a reliable timing source So I implemented a very simple counter in the SOF callback: #if (USE_HAL_PCD_REGISTER_CALLBACKS == 1U) static void PCD_SOFCallback(PCD_HandleTypeDef *hpcd) #else void HAL_PCD_SOFCallback(PCD_HandleTypeDef *hpcd) #endif { sof_eventc++; USBD_LL_SOF((USBD_HandleTypeDef*)hpcd->pData); } Additionally: TIM2 is configured as a 1 Hz timer In t

Hi team,I am working on the STM32U585I-IOT02A board and trying to implement USB dual-role functionality (Host + Device).My goal is:USB Host: MSC class (to read firmware from a USB flash drive)USB Device: CDC class (for communication with a PC)I have enabled both the USB Host stack and USB Device stack in CubeMX, but I am unable to get the dual-role setup working reliably.My main objective is to upgrade firmware using a USB flash drive (MSC Host) while still supporting CDC Device communication.I would like to know:Does STM32U5 support USB dual-role operation (Host + Device) simultaneously or via role switching?Is there any example project or reference implementation for USB dual-role on STM32U5?Are there recommended approaches for implementing firmware upgrade via USB MSC Host on this board?Any guidance or example projects would be very helpful.Thank you.

Hello STMicro Community,I am working with the LIS2DH12 accelerometer, STEVAL-MKI109V3 and MEMS Studio environment. My application is the measurement of vibration on rotating equipment.A vibration signal of 118Hz is being applied to the board and using ODR=400Hz, Scale +/-4g.I am noticing a significant difference in magnitude measurements when switching the filter bit on vs off (FDS). See attached image of the time series data yellow (Z-axis) where:- with FDS=0 I see -500 to -1500 for ~1000mg range- with FDS=1 I see -800 to +800 for ~1600mg rangeI DO expect to see gravity getting removed but NOT an increase in the magnitude. Is there an explanation for this?-Edwin 

Hi Community,I’m just finishing off development of a product containing VL53L4CD and need to start to think about approvals etc. ready for product launch. The product as a whole relies on human interaction, so users will be physically close to the product and therefore the beam.Judging by the datasheet for the part, there is no need to perform any testing for eye safety, relying instead on ST’s own certified testing, provided that we use the device in accordance with the datasheet (which of course we do) and there’s no attempt to focus the beam (which there isn’t). This will all be wrapped up in a detailed technical file, along with ST's certs.The artwork on the product carries the Class 1 laser radiation logo and in the instructions the customer is warned never to attempt to focus the beam, nor to stare into it.Is this sufficient due diligence, or have other developers done more and if so, what?TIA.

Hi,I want to fly the STM32F429I-DISC with the 8 MB SDRAM. I use CubeIDE and selected the right board. All units are set to default. I commented out everything that had to do with os.With help of ChatGPT I hacked together an initialization of the SDRAM and set up a SDRAM Test. That seems to work partly but with weird effects. In the following code: start/end 0x00/0xff or 0x100/0x1ff works fine, but start/end 0x00/0x101 reads out 0x100 at  address 0x0. Maybe it is an timing issue with precharged lines.THXCheersDetlef #define SDRAM_BASE_ADDR ((uint32_t)0xD0000000) void SDRAM_Test(void) { volatile uint16_t *p = (volatile uint16_t *)SDRAM_BASE_ADDR; uint32_t i ; uint32_t start = 0x100 ; uint32_t end = 0x302 ; for (i=start; i<end; i++) p[i] = i; sprintf(buf,"start \r\n",i); HAL_UART_Transmit(&huart1, (uint8_t *) buf, strlen(buf), HAL_MAX_DELAY); while(1){ for (i=start; i<end;i++) if (p[i] != i){ sprintf(buf,"no 0x%x 0x%x\r\n",i,p[i]); HAL_UART_Transmit(&