No best answer

Hello, There’s probably a solution, but I haven’t been able to fix it. Could you help me?In the circuits I’ve designed recently, the LSE crystal either doesn’t work at all or its operation is unstable. Generally, when debugging, it gets stuck at the SystemClock_Config(); section and won’t proceed.I’ve designed circuits using different MCUs and have encountered this problem across the board.  In my latest circuit design (4-layer FR-4), I used an STM32WBA54CGU6 MCU and, for the crystal, the ABS07-LR-32.768KHZ-6-1-T recommended in the AN2867 Application Note. I’m using an 8pF C0G 0402 package capacitor as the load capacitor. I also tried a 6.8pF capacitor, but it didn’t work at all. The 8pF capacitor is also unstable. I tried driving it in different modes (LOW, MEDIUM, MEDIUMHIGH, etc.), but it remains unstable. I didn’t adhere perfectly to the layout rules, but I haven’t experienced problems in previous circuits where I followed them even less strictly. I’m trying to keep as few signals

Hello ST team,I’m looking for information about ST tools/software for gang programming multiple STM32 devices simultaneously, particularly for production programming.We are planning to program minimum 8 STM32 devices in parallel using 8 ST-LINK programmers. Could anyone suggest the recommended ST tool or production programming solution for this setup? 

Hi all,I am bringing up the Ethernet switch (ETHSW) on an STM32MP257F-DK, bare-metal on the Cortex-A35 (no OS), following RM0457 Rev 5.Ping works with the switch bypassed (ETH1 directly to the PHY), and ping also works under Linux with the switch enabled on the same board. In bare-metal switch mode, ARP works but ICMP never arrives.SETUP- ETH1 -> Port0 (internal, no PHY), PHY (RTL8211F, RGMII) on Port2, negotiated 100 Mbps full duplex- SYSCFG_ETHSWCR = 0x6   SYSCFG_ETH1CR = 0x12 - Init order:ETHSW reset -> clocks -> SYSCFG_ETHSWCR -> release reset -> pulse ETHSW_FES_GEN_CTRLR INIT_REQ (bit 15) -> then ETH1 clocks/reset/DMA- PORT0 UNDER MANAGEMENT,MII,100 MBPS- PORT2 UNDER NORMAL, MII,100 MPBS WHAT WORKS- Broadcast/multicast from the PC reach ETH1 (ETH1 MMC broadcast counter increments)- The board's ARP reply (unicast) leaves ETH1, crosses Port0 -> Port2 (Port0 RX_UNICAST=1, Port2 TX_UNICAST=1) [confirm in Wireshark that the PC actually receives it]- Dynamic MAC tab

I had trouble setting the PLL3N field in PLL3DIVR in an STM32H533.  The documentation says the field CANNOT be set if PLL 3 is enabled.  I spent a whole day running iterations, trying to turn PLL 3 off, reordering writes, etc.  What I FINALLY found is that the field CANNOT be set if PLL1 is enabled, i.e. the WRONG PLL.The following code fails: RCC->PLL1CFGR = 0x00030007 | ( XTalMHertz << 8 ); // PLL 1 Input = 1 MHz; HSE in; RCC->PLL1DIVR = 0x00000000 | ( SystemMHertz - 1 ); // DivN = VCO Output in MHz RCC->CR |= RCC_CR_PLL1ON; // Enable PLL 1 while(( RCC->CR & RCC_CR_PLL1RDY ) == 0 ) { } // Wait till PLL 1 is ready RCC->PLL3CFGR = 0x00070007 | ( XTalMHertz << 8 ); // PLL 3 Input = 1 MHz; HSE in; RCC->PLL3DIVR = 0x030306BF; // DivN = 192 (n=191); R/4, Q/4; P/4 RCC->CR |= RCC_CR_PLL3ON; // Enable PLL 3 while(( RCC->CR & RCC_CR_PLL3RDY ) == 0 ) { } // Wa

I'm working on a battery-powered sensor node using an STM32L4 series MCU. I need to wake from STOP2 mode on either of two GPIO interrupts (button press or external sensor trigger) and want to identify which one triggered the wake before running my main loop.What's the recommended way to configure and distinguish the wake source cleanly — checking EXTI pending register flags right after wake, or is there a better pattern people use for this?

I am currently working with the VL53L1X Time-of-Flight (ToF) distance sensor and am experiencing inaccurate and inconsistent distance measurements.The sensor is able to detect objects and provide distance readings, but the measured distance does not consistently match the actual physical distance. I have observed variations/errors in the distance readings even when the target position remains unchanged.Could you please help me identify the possible cause of this issue and suggest the recommended configuration or calibration procedure?I would appreciate your guidance regarding the following points:* Recommended initialization and configuration settings for the VL53L1X.* Recommended timing budget and ranging frequency settings.* Calibration procedure for accurate distance measurement.* Recommended offset and crosstalk calibration procedure.* Effect of target reflectance, ambient light, and target size on measurement accuracy.* Recommended sensor mounting and target conditions for reliabl

Hello, I am using VL53L9CX with adapted drivers for ESP32 / Arduino environment. I am able to read values and play with the settings but I am a bit worried with the precision I get. I run the sensor in precision mode, 4ms exposure time. My bench is indoor. Sensor facing the ground ( 1 m ish, wood) or the roof (1.6m ish, white ceiling). Resolution is 8 x 6 (Binning 12). I have radial to perpendicular conversion enabled so I am expecting to see all distances being equal +/- precision across the cells of the frame (excluding corner cells maybe). According to table 34: Precision for “ambient mode 24x20” profile from the sensor datasheet: (results are better for 24*20 then they are for 54*42, so I assume it is the same or better for 8*6 compared to 24*20)I am expecting less than 0.8 mm difference between the values but instead I get 50 mm - 100 mm or more of difference. So I was wondering, is there some specific settings to enable to achieve such precision / accuracy ? PCB is of my own (not

Hi, STNow I followed the X-NUCLEO-53L7A1 User guide connection for the SATEL-VL53L7A TOF breakout boards LEFT and RIGHT Connection as Shown in the attached image and it worked well, even if there are 2.2K pull up resistors for each sensor which makes the equivalent pull up resistor = 2.2K / 3 but I worked well till I also added another 2 SATEL-VL53L7A TOF breakout boards in addition to 1 Barometer Sensor breakout board which has the part number STEVAL-MKI225A it started to make undefined behaviors such as (TOF sensors Initialization fault, Barometer Sensor Initialization fault, Barometer wrong readings).So, could this problem caused by another 2 SATEL-VL53L7A TOF breakout boards with there Pull-up resistors?and If yes, Should I remove the 0 Ohm resistors on solder bridges to disconnect the pull-up resistors from each sensor as shown in the second attached image?

Board: custom STM32N657Z0H3Q (not a Discovery/Nucleo)Flash: Macronix MX25U12835F, 16 MB, Quad (x4), 1.8 V, no DQSTools: STM32CubeProgrammer 2.22.0 and 2.23.0, LinuxWe need to program the external XSPI NOR flash (FSBL + application) using only USB serial boot / DFU, with no ST-LINK connection.This is a product requirement, not a bring-up convenience. On our board, entering development boot requires BOOT1 = 1, and BOOT1 (PA6) is wired as DCMIPP_PIXCLK and actively driven by an on-board FPGA. We cannot reliably force that pin without contending with the FPGA driver. USB serial boot needs only BOOT0 = 1 and BOOT1 = 0, which is the FPGA-idle state, so it is the only strap combination that is safe on this hardware. We attempted to relocate BOOT1 via OTP19 dev_boot_port/dev_boot_pin, and that attempt left the board permanently inaccessible. That is a separate open thread with no resolution so far: https://community.st.com/stm32-mcus-products-25/stm32n657-after-programming-otp19-dev-boot-port-

Hi,This is for STM32U5 and STM32H7 series MCUs.I was starting to use ThreadX because it looked like it was preferred over FreeRTOS. Now it looks like it is going the other way FreeRTOS is preferred over ThreadX ... or so I read/watched.I liked ThreadX with FileX because they seemed better integrated than FreeRTOS and say FATfs. But I don't have a lot of experience with RTOS in general. I've used a bit of FreeRTOS before but it looked like ThreadX was a better option for STM32U5 series MCU (in cubeMX).The video I watched and info on going back to FreeRTOS  with separate FileX (from STM) said that it was going to happen by the end of 2025. I prefer to stay with one RTOS, whichever is going to make my life easier but I also need a file system.We're at the end of 2025 so I wonder if this switch from ThreadX to FreeRTOS with separate FileX has already been implemented in the new STM32cubeIDE v 2.0? BTW I'm currently using STM32CubeIDE v1.19.0 with Windows 11.Comments/suggestions w

I designed a small PCB for LSM6DSV but I got no signal on SPI-MISO and got NACK on I2C-SDA.I have replaced several chips but all the chips have the same behaviour(no signal reply).I'm very sure the SPI and I2C pins are correctly connected to LSM6DSV.(1)Custom PCB designThis is the PCB design of my custom board. All the net label are connected to pads on board. Never mind "LSM6DSOTR" in the schematic. Actually I soldered LSM6DSV on board since LSM6DSV has the same chip package with LSM6DSO.VDDIO and VDD are 3.3V and this board shares the same ground with stm32.(2)SPI communication issueSPI_SCK and SPI_MOSI signal is correct but SPI_MISO has no signal.I configured STM32H743XIH6 SPI in STM32CubeMX like this. No NVIC, no DMA.I implemented the SPI polling read/write function for official ST LSM6DSV driver code. int32_t lsm6dsv_spi_read(void* handle, uint8_t reg, uint8_t *data, uint16_t len) { reg |= 0x80; LL_SPI_SetTransferSize(handle, len+1); LL_SPI_Enable(handle); LL_SPI_StartMas

In document PM0264, chapter 4, section 4.3.11, it is referring to System handler control and state register (SHCSR) of the System control block (SCB).However, Table 75 of that section is describing the fields of Configuration and control register (CCR). It seems the content of table 70 of CCR register and table 75 is somewhat similar, and the fields of SHCSR register is completely missing!Does anybody know if this is an issue with the document, or am I reading it wrong? I want to read more about SHCSR register but it’s nowhere to be found in this document.Table 70:Table 75: 

PROBLEM:When loading a program, with size filling an odd number of memory sectors, into flash memory the program only starts every other upload. I have a custom board with an STM32L4KBU. I am connecting to the stm32 with the STLINK-V3SET, over SWO. I am developing with the VSCode STM32CubeIDE extension pack, on linux mint.STM32CubeProgrammer version: 2.23.0Boot0 pin is pulled to GND through 10k, default boot option bytes When using the STM32_Programmer_CLI to upload code there is a bug where the FLASH_SR PEMPTY register is not cleared correctly. It appears that the flash loader resets the register by writing all 1s, but the PEMPTY bit is specifically write 1 to toggle. This actually seems to be an odd design choice as the rest of the bits are write 1 to clear, and the language in the RM0394 Reference Manual is quite inconsistent (section 3.7.5, bit 17). A correct reset is to set this register to itself.The FLASH_SR register seems to get this toggling for every sector written into flash

Hi, I'm having some issues with the STM32WB06 when trying to achieve low power consumption. I hope someone can help me solve these problems. Issue 1: After initializing the Bluetooth protocol stack and enabling automatic connection establishment, it causes the device to fail to enter the low power state (BLE wake-up has been disabled). Is this a normal phenomenon? If not, what are the solutions? Issue 2: Before entering the low power mode, disabling automatic connection establishment allows the device to enter the low power mode normally. However, after waking up, attempting to re-enable automatic connection establishment fails (aci_gap_start_procedure(GAP_AUTO_CONNECTION_ESTABLISHMENT_PROC, LE_1M_PHY_BIT, 0, 0)). What is the solution for this problem?   I look forward to your replies. Thank you very much!

I’ve got a working graphics system.  It does high level operations on a 32 bit virtual image of the display’s resolution.   The image is then translated to a 16 bit buffer image (RGB565 for an ILI9341 display).  That image is then transferred over SPI to the display.  The SPI drivers can be polled, interrupt driven, or DMA driven.  Software drivers are used for all of this, and work.Moving to a different processor (U575 from L562), ChromART is available.  It could be used for filling the virtual image, translating to the RGB565 image.  2D DMA can be used to transfer modified blocks to the display.Now the problem.The transfer works erratically in some cases.  Some data (and I’m using mostly saturated colors) doesn’t transfer well into RGB565 (say 100% blue), it may just end up with black.  Other times, the complete color palette is transferred properly.I’m investigating whether or not the repeated restart of the ChromART peripheral is a problem.  Mostly what happens is that the mode sho

Setup:MCU: STM32N657X0HXQ (Cortex-M55), STM32N6570-DK Boot architecture: FSBL (runs from internal RAM) → single secure Appli, no TrustZone split, executing XIP from external NOR (XSPI2, mapped at 0x70000000) PSRAM (XSPI1, APS256XXN-OBR-BG) also mapped via the same EXTMEM_Manager framework FW package: STM32Cube FW_N6 V1.4.1 Linker script places Appli's .isr_vector at 0x70100400 (0x400-byte header region reserved before it)What's confirmed working:FSBL boots, maps both PSRAM and NOR successfully via EXTMEM_MemoryMappedMode() NOR flash program/verify succeeds cleanly via ST-LINK GDB server I independently verified the vector table content with a raw GDB memory read (x/4xw 0x70100400), bypassing Eclipse's Memory view (which was misleadingly showing byte-reversed values — a display artifact, not real data): the actual words are correct — 0x34100000 (valid SP, matches linker's RAM origin) and 0x701066a5 (valid Reset_Handler address, correct Thumb bit set, inside the linked ROM range)The prob

Hi, During the development of a bare-metal driver for USB CDC (virtual com port) in device mode i noticed an unexpected behaviour when trying to configure the USB Core to do a transmission of a multi packet message. I've got the following code which prepares the transmission over usb for a data array "data" whose size is "dlen" over endpoint number "epNr". "epInBuffers" contain the pointers to the data buffers for each endpoint, "epInBytesTransferred" keep track of how many bytes have already been transmitted and "epInDataCntrs" the total amount of bytes to transmit. __RAMFUNC void prepareUSBTransfer(uint8_t epNr,const uint8_t*data,uint16_t dlen) { USB_OTG_INEndpointTypeDef * inEndpoint = ((USB_OTG_INEndpointTypeDef*)(USB2_OTG_FS_PERIPH_BASE + USB_OTG_IN_ENDPOINT_BASE + epNr*0x20)); uint32_t epCtrl = inEndpoint->DIEPCTL; uint16_t npackets; if(dlen==0) { npackets = 1; USB2_OTG_FS_DEVICE->DIEPEMPMSK &= ~(1UL << epNr); } else { npackets = ((dlen + epInMaxPacket

Hi, I have been developing IoT application for the  B-U585I-IOT02A (STM32U585AI) and encountered following problem:When attempting to set a socket to non-blocking mode  MX_SO_BLOCKMODE = 1 using the MX_WIFI_Socket_setsockopt() API the call fails immediately and returns -1.Steps to reproduce:1. Create a socket using MX_WIFI_Socket_create()2.Try to configure  MX_SO_BLOCKMODE = 1     MX_WIFI_Socket_setsockopt()3. Get instant -1 in the runtimeMinimal Reproducible Code#include "mx_wifi.h"#include "mx_wifi_bare_os.h" /* Using Bare OS mode */void test_nonblocking_socket_config(void){ int32_t sock = -1; int32_t optval = 1; /* 1 = Non-blocking mode */ int32_t ret = -1; /* 1. Create TCP Socket */ sock = MX_WIFI_Socket_create(MX_WIFI_AF_INET, MX_WIFI_SOCK_STREAM, MX_WIFI_IPPROTO_TCP); if (sock < 0) { /* Handle socket creation failure */ return; } /* 2. Configure Socket to Non-blocking Mode */ ret = MX_WIFI_Socket_setsockopt(sock,

Hello,  please help on the title topic, thanks.

Hello,I am using an STM32F207VC custom board with Ethernet and LwIP. I am facing an issue related to Ethernet cable connection during power-up.I performed the following tests:Test A: Ethernet cable connected before power ONConnect the Ethernet cable.Power ON the STM32 board.Result:Ping: WorkingTCP server connection: WorkingTest B: Ethernet cable disconnected during power ONDisconnect the Ethernet cable.Power ON the STM32 board.Wait until all STM32, Ethernet, and LwIP initialization is completed.Connect the Ethernet cable.Result:PHY Link Up: DetectedPing: WorkingTCP server connection: Not workingTest C: Cable disconnect and reconnect after normal startupStart the board with the Ethernet cable connected.TCP server works normally.Disconnect the Ethernet cable.Reconnect the Ethernet cable.Result:Ping: WorkingTCP server connection: WorkingThe issue occurs only when the STM32 board is powered ON while the Ethernet cable is disconnected and the cable is connected later.Since ping works and th

Hello ST Team,I want to use USB interface to update firmware of STM32F405RGT6 MCU.We have verified it with USB DP and DM from external USB but now want to put in our board.Our board is also generating 5V and USB will also have 5V. What should I do so that it will not conflict or cause any issue? How to connect CC1 or CC2 pins of USB to our MCU so that we got to know connection is available from USB? If we want to do firmware update using USB then how our MCU will go in boot mode?Please find screenshot of our schematic which we are working now: 

Hello Community,I would like to report another significant logic bug in the generated firmware libraries for the Vienna Rectifier project (specifically located in the Digital Power Control stack file BSP/DPC_FW_PACK/src/DPC_Loopctrl.c).The Issue:Inside the function DPC_LCT_FeedForwardCtrl(..), the firmware is supposed to evaluate whether the AC Voltage Feed-Forward task is enabled before adding the d-axis and q-axis AC feed-forward grid terms (fVd_feed_sub and fVq_feed_sub) to the current loop outputs.However, the original ST framework code erroneously checks the DC voltage feed-forward enable flag instead of the AC one.The Code Snippet:cvoid DPC_LCT_FeedForwardCtrl(DPC_LCT_CDC_t *pCDC_sub, float *pVd_ctrl_FF_sub, float *pVq_ctrl_FF_sub){ float fVd_feed_sub = pCDC_sub->fVdFeed; float fVq_feed_sub = pCDC_sub->fVqFeed; float fVd_ctrl_sub = pCDC_sub->fVdCurrentCtrl; float fVq_ctrl_sub = pCDC_sub->fVqCurrentCtrl; /* AC feedforward task */ // BUG: Checks bVDC_FF_Enable

Hello Community,I am writing to report a highly critical issue regarding the Vienna Rectifier reference project generated and downloaded via eDesignStudio / Digital Power Workbench (targeting the STM32G474 MCU).The Issue & Context:Upon downloading the automatically generated project package from the eDesignStudio platform and opening the .ioc configuration file locally, STM32CubeMX flags that the template is outdated and prompts the user to either maintain legacy libraries or migrate.The downloaded template from eDesignStudio was built with legacy STM32CubeMX V6.14.0 and STM32Cube FW_G4 V1.6.1. Modern local environments prompt for a migration to STM32Cube FW_G4 V1.6.3. The Critical Hardware/Firmware Bug:If a developer chooses the "Migrate" path to align the project with modern libraries, the automatic code generation introduces a catastrophic control bug:After completing the migration, generating the code, and flashing the MCU, HTRIM2/Timer A output generates incorrect PWM switchin

Hi ,I am using STM32H573VIT3Q MCU, I need USB so i am using internal PHY. I configured all in cubeMx all other things are working well only problem is with USB. I have tried both Host and Device modes but nothing works. Then i created a test project only for USB in device mode, I have connected the logic analyser on USB pins to see the data , but no single pulse is there if i plug/ unplug the usb cable to PC. I have attached this full project as well for your reference. I have tried GPIO toggle to confirm all connection are ok and well soldered. Here is my circuit diagram of MCU.I have also attached my IOC files. Please help me to solve this error. Thanks

Hello all, Im Currently working with my own Hardware with the L072CZTx on it.I want to use a Terminal over the 2 USB Pins.(USB_DP and USB_DM)I activated the Clocks with 48MHzActivated USBActivated USB_ Device as a Communication Device Class(Virtual Port COM) I got told i should see it in the Device Manager as a Com Port or a unidentified Device.Sadly i can only see my V3set im using to Programm the Controller with (SWD). If very new to Programming with STM32 and if you have any ideas that could fix it i would really appreciate it. Thank you in Advance