Solved

As reported in the following image the gauge reports a wrong value for FLASH free space

I currently have two boards equipped with different specific models of N6, namely STM32N647X0H3Q and STM32N657X0H3Q. I have an IDE project for testing the memory-mapped functions of each of these two chips.The problem lies in that this project can be implemented on the STM32N647X0H3Q in a manner similar to:  data = *(volatile uint8_t *)0x70100000;Such code reads the content from the external FLASH. However, on the STM32N657X0H3Q, it is impossible to read. The specific manifestation is that when I run this line of code in the debug mode, the program directly jumps tovoid SysTick_Handler(void)and the debugging connection is disconnected, as shown in the following figure. I have wondered whether it was an issue with the external FLASH soldering, or a problem with the PCB traces (my two circuit boards were not produced on the same PCB. The circuit board with STM32N647X0H3Q was purchased from the internet, while the one with STM32N657X0H3Q was designed based on the schematic diagram of the

Hi  ,   he system operates in timing mode with lower limit detection at 1.1-second intervals and a measurement duration of 33 ms; the status code is read to verify accuracy, though misjudgments may occur—for instance, when no object is present, measured values may fall below the lower limit, requiring correction. Parameters: long-distance reference Spad count = 7; aperture Spads = 1; HV settings = 32; Phase calibration = 1; Offset micrometer = 7000 (for 100 mm); myXTalk compensation rate (Mega CPS) = 66 (for 600 mm).Why is the refSpadCount value obtained by our school less than 10?Increasing the measurement time reduces the likelihood of misjudgment, as I use a battery-powered device and cannot extend the measurement duration.

Hi all,I'm reusing the STM32H7S78-DK's Octo-SPI flash (MX66UW1G45G) and Hexadeca-SPI PSRAM (APS256) sub-circuits on a custom board and want to match the DK's signal integrity. I can't find the fabrication stackup or impedance spec in the docs. Could ST share, for the DK (please confirm board rev):Full layer stackup — copper weights and each dielectric thickness/material. Target impedance (single-ended + any diff) and tolerance for the Octo-SPI / Hexa-SPI nets. Trace width/spacing for those buses, and their routing layer + reference plane. Any length-matching constraints on those groups.For reference, the published Altium reference-design project ships with an unconfigured stackup (single 1.5 mm dielectric, all layers typed Signal), so it doesn't reflect the real fabricated stack — which is why I'm asking for the actual values.Thanks!

Hello, I am using an STM32L431 and found an interesting behavior with TIM1 PWM output while debugging. Test conditions: - MCU: STM32L431- TIM1 CH2 PWM output- Debugger: ST-LINK- Debug halt enabled- DBGMCU TIM1 freeze enabled (DBG_TIM1_STOP) Observed behavior: TIM2:When the debugger halts the CPU (breakpoint or single-step),the PWM output keeps its current output state as expected. TIM1:When the debugger halts the CPU and TIM1 freeze is enabled,the PWM output no longer behaves like TIM2. Additional observations: 1. MOE remains set (MOE = 1). 2. With OSSI = 0:   the output appears to become high-impedance (or disconnected). 3. With OSSI = 1 and OIS2 = 0:   the output becomes Low. 4. With OSSI = 1 and OIS2 = 1:   the output becomes High. 5. If DBG_TIM1_STOP is disabled:   PWM continues running during debug halt. These results make it appear that TIM1 enters an Idle/Off-State condition during debugger halt and the output level is determined by OSSI/OIS settings. Questions: 1. Is this expec

In a larger design I’m using a LD39100PU33R for a 3.3V output. The input voltage is 5V and the device has decoupling capacitors as per the datasheet. The 3.3V circuit is consuming about 0.5A and the device is capable of delivering 1A. The circuitry connected is no inductive loads, but rather a steady consumption from sensors (air pressure & temperature).I am unable to find any information in the datasheet (Section 5. Typical performance characteristics) on what temperature the device will typically be at this load, but it’s running at a constant 75C. This seems to be very high, but how can I know if this is within spec when there is no graph in the datasheet showing current vs temperature?ref: datasheet https://www.st.com/content/ccc/resource/technical/document/datasheet/72/02/e5/ee/df/36/40/5e/CD00233788.pdf/files/CD00233788.pdf/jcr:content/translations/en.CD00233788.pdf

Hi,I am working on a new Project for the STM32C562MET6 with STM32CubeMX2 and VS Code.On the first run of toolchain generation, CubeMX generates all expected folders like arch, generated, stm32c5xx_dfp and stm32c5xx_drivers.But I dont want to version all files if they can be generated so i added the folders above to the .gitignore file.After running it a second time but with those folders missing, CubeMx2 doesnt generate it. I already tried to set the “conflict handling rules” to override. Any suggestions? 

Hi everyone,​I'm currently developing a MIDI controller/audio device for guitar VST plug-ins.​The project features a guitar audio input using the CS4272K IC connected to an STM32F446RET6. Additionally, the STM32 will operate in USB High Speed mode using Microchip's USB3300 PHY.​My main challenge at the moment is finding or designing the standalone minimum circuit (schematic) for these components to move forward with the project. Could anyone provide some guidance or share reference schematics for this setup?​Thanks in advance!

Can ST please fix this minor interconnection line missing in the RCC clock tree figure in RM0394.JW

Please support to update how LPS27HHW pressure sensor can detect the fall of a human being.

Heyho,working on a new project with a STM32G431, for now on a Nucleo-32 board.I have lots of things running (bare-metal, mostly no HAL), then I needed a timer with a higher resolution than the SysTick (running at 1 ms, looks valid).The only 32-bit timer is TIM2, so I set it up to simply count up, no interrupts, only with pre-scaler set to get 1 counter period of 10 us at a clock of 96 MHz. The code below is changed to a period of 1 ms, for simpler comparison to the 1 ms tick.Here’s the setup:/* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ *//* TIM2 * 32 bit timer * init function * 10 us timer -> NO interrupt */void TimComInit(void){ /* peripheral clock enable */ __IO uint32_t u32TmpReg; RCC->APB1ENR1 |= RCC_APB1ENR1_TIM2EN; u32TmpReg = ( RCC->APB1ENR1 & RCC_APB1ENR1_TIM2EN ); (void)u32TmpReg; TIM2->CR1 = 0; TIM2->CR2 = 0; TIM2->SMCR = 0; TIM2->CCER = 0; TIM2->CCMR1 = 0; TIM2->CCMR2 = 0; TIM2->CCMR3 = 0; TIM2->DIER =

 Hello ST Team,I am currently working on a project using the ST25R3916B NFC reader, and I would like to study and reference the PCB design shown in Figure 6, “Device used for single ended antenna with cable,” of application note AN5592.Could you please provide the editable PCB project files for this reference design, such as the Altium schematic and PCB layout files?I have checked the application note and the ST website, but I could not find the corresponding PCB source files.Application note reference:https://www.st.com/resource/en/application_note/an5592-st25r-single-ended-antenna-matching-stmicroelectronics.pdfThank you very much for your support!

Hello,I wish to report what I believe to be a bug in the new version of CubeMX (6.18.0).When configuring an STM32H743IIT6, I encounter an error in the Clock Configuration view (please refer to the attached screenshot). The same procedure carried out with CubeMX 6.17.0 works correctly.I have therefore reverted to CubeMX 6.17.0, which is not a critical issue for me, but I thought it important to bring this to your attention.Yours faithfully,Philippe 

Hi everyone,I'm having trouble bringing up an STM32MP257F-DK Discovery kit (board reference MB1605C). ST-LINK itself works correctly, but I cannot get any communication with the main STM32MP257 processor, and the board never boots. I'd appreciate any insight into what else to check before assuming a hardware fault.Board / setup:STM32MP257F-DK, main board MB1605, revision C-01 Powered via USB-C into CN21 (USB PWR/STLINK) Using the original microSD card that shipped with the kit (preloaded OpenSTLinux demo image) Boot switches set to: BOOT0 = ON, BOOT1 = OFF, BOOT2 = OFF, BOOT3 = OFF (microSD boot)What works:LD11 / power LEDs indicate the board is powered Windows enumerates two "STMicroelectronics STLink Virtual COM Port" devices (COM8, COM9) without issues STM32CubeProgrammer detects the ST-LINK probe: Serial number, FW version V3J15M6B5S1, Board correctly identified as "STM32MP257F-DK", Target voltage reads consistently 3.28-3.29VWhat doesn't work:Connecting via SWD always fails with "

0x0BF97000 (system bootloader base per AN2606): the jump appears to succeed (In Debug reaches the bootloader region), but execution then breaks at an address inside the bootloader ROM with no further progress and no USB enumeration. The hardware boot path works correctly. The problem is purely on the software-jump path.I created an empty project in sample you can download and test it. I also attached my option bytes (i think everything is default).MCU: STM32H573 (also tested h523)/** ****************************************************************************** * @file dfu_jump.c * @author Uğur Tümer * @brief See dfu_jump.h. Implements the magic-word + soft-reset path into * the STM32H523 system bootloader (USB DFU on PA11/PA12). ****************************************************************************** */ #include "dfu_jump.h" /** Magic word stored in TAMP_BKP0R between the request and the next boot. */ #define DFU_JUMP_MAGIC 0xDEADB007UL #define BOOT

Hi there,I am frustrated while searching the web for an normally easy task - 😒I am not able to detect, where Boot0 pin is on STLink-v3MODS module Rev.B.Does anyone know?I also asked ChatGPT and Google, but this only results in false answers - bricking the device.Please hlep - Thanks a lot.STLink-v3MODS Rev.B - front STLink-v3MODS Rev.B - backST32CubeProgrammer v.2.2.3.0 

Dear STM32 Community,I am using the STM32H745ZIT3 microcontroller with STM32CubeIDE for firmware development.I am facing an issue related to GPIO behavior during a watchdog reset.When a warm reset is triggered by either the Independent Watchdog (IWDG) or the Window Watchdog (WWDG), all GPIOs are reset to their default state. In my application, I need certain GPIO outputs (such as relay control signals) to retain their previous state during a watchdog reset, or at least avoid changing state until the application reinitializes them.Could you please clarify the following?Is it possible to prevent GPIOs from resetting during an IWDG or WWDG reset on the STM32H745ZIT3? Are there any software techniques to retain the GPIO output state across a watchdog reset? If GPIO retention is not supported, what is the recommended approach to prevent unwanted output glitches during a watchdog reset?Any guidance, application notes, or recommended design practices would be greatly appreciated.Thank you for

Hello everyone,I designed a board using the STM32MP157 and STPMIC1A. During the initial power-on tests, I noticed that there was no output from the VDD BUCK.The board was tested without any operating system or boot process. Is this normal? This is the first board I’ve designed with the STM32MP1, and if this is normal, I can proceed with porting the OS however, if it’s abnormal, I’ll need to investigate the source of the problem. The board was also successfully detected by the PC in USB boot mode. Regards

Hi,We designed a 24V to 5V DC-DC power supply using the LD1086DT50TR. However, we are experiencing an overheating issue. Our application load current is only 0.2–0.3 A, but the regulator temperature rises significantly. Could you please suggest a solution to resolve this overheating issue?

Hi all, Regarding EVKIOTST87M01-2. In the design guide is mentioned the High Speed Interface (HST), in the same guide specifies that this interface requires an external Hardware TPA device, named Dongle HST Logger to recover the data flow for ST Analysis. The questions are:Do you sale this Dongle HST Logger? Is the ST-Link compatible?or is the the data available through the STSW-ST87M GUI?Thanks in advance. Susana 

Hi, I am evaluating VL53L8CX and couldn’t find anything in the data sheet about a programmable FOV. I require a FOV of 2-3degrees. Does this sensor support a programmable FOV to that size?Thanks,BH

Hi,I am using the NBP8FD4ST1 pressure sensor with the S32K146 microcontroller. The CS_B/WAKE-UP pin of the sensor is connected to a GPIO pin on the microcontroller.The logic analyzer signal mapping is as follows:D0 → SCLK D1 → CS_B D3 → READY D5 → MISO D7 → MOSIDuring the communication sequence, when I pull the CS_B pin low to request SPI communication, the READY pin is asserted as expected. After READY goes high, I send the SPIOPS register read command (0x00E1). However, the sensor always returns 0x0000 on MISO. As a result, the firmware validation fails, and the CS_B pin is subsequently driven high to terminate the transaction.Could you please help me understand whether my SPI communication sequence is correct or if I am missing any required step, such as the wake-up sequence, dummy transfer, or SPIOPS handling described in the datasheet?I have also attached the logic analyzer screenshots for reference.Thank you in advance for your support.Best regards,Pratyusha.  

Hi everyone,I'm working on an STM32 (Nucleo-F446RE to be spesific) project using the STM32Cube extension for VS Code, not CubeIDE. I'm using CMake for building the project.I encountered a few issues:printf doesn't print anything to the serial monitor, so I switched to using HAL_UART_Transmit.When I try to print a float using sprintf(msg, "value: %f\n", var);, it doesn’t work. The output just skips the float value (e.g., "value: \n").After some research, I found out I need to add "-u _printf_float" to the linker flags to enable float formatting support with printf and sprintf.However, I'm new to CMake and I couldn’t figure out which CMake file I need to modify in the project folder to add this flag.I'd really appreciate it if someone could guide me:Where exactly should I add the "-u _printf_float" flag?Is there anything else I should do to make printf work properly over UART?Thanks in advance for your help.

Hello,I have programmed the OTP word 31 to 0xBBBBBBBB as follows, but when I want to write another value such as 0x12345678 or 0x00000000 to word 31, it reported the following errors， can you help to analyze this ? Thanks a lot!  

Hello!I have been trying to review and fix the configuration of my Ethernet LwIP+FreeRTOS STM32 project and I would like to ask more experienced people if I have correctly chosen memory locations, modified the linker script, configured MPU and a few other things. My project uses STM32F746VGT6 MCU that has 320KB of RAM and 1024KB of flash memory:MEMORY{ RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 320K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 1024K} Since this project uses Ethernet peripheral and LwIP library, a few memory sectors need to be defined: one for Tx Descriptor, one for Rx Descriptor, one for RX POOL and one for LwIP heap.I have set Tx and RX Descriptor addresses to 0x20048000 and 0x20048100 and checked in debugger that each one of them takes 160B of space, so 256B is more than enough to store a single Descriptor.I decided to store memp_memory_RX_POOL_base under 0x20040000 address in 32KB section. With ETH_RX_BUFFER_CNT defined to 16U, size of memp_memory_RX_P