Solved

The new version of CubeIDE is truly terrible.With a new project, there's no way to tell if it was created via the IDE or MX.On top of that, they don't synchronize with each other—an issue that never occurred with the unified versions up to 1.19.

There seems to be a documentation error between DS14053 Rev 4 and RM0492 Rev 3.  In the data sheet, section 3.17, table 3, "ADC Features" we see a different set of features compared to the reference manual, section 19.3, table 107.  The data sheet claims oversampling up to x1024, a data register of 32 bits and gain compensation is supported.  The reference manual claims oversampling up to x256, a data register of 16 bits and no gain compensation.The register set description only has oversampling fields with values up to 256.  It would be helpful if ST could correct whichever document is wrong, and if the reference manual is wrong and oversampling up to x1024 is supported, then please also correct the register definitions.Thanks,TG

I have two STM32G474 on a custom PCB, in which I want to use a SOM to program the microcontrollers via UART (USART1 or USART2).While most PCBs work fine (toggle BOOT0 + NRST and program via UART), some PCBs have intermittent access on the UART. It is not always the same microcontroller that fails on the boards.Tests I have done:Programming via USB DFU always works, even when toggling BOOT0 and NRST with the SOM, so it seems it is going into bootloader mode correctly. In the SOM I am using stm32flash. I have checked that no other signals are triggering the bootloader on another interface (e.g. I2C, other USART). I have checked that the 0x7F command is being sent correctly (timing, clean edges, amplitude) There is no reply at all from the micro I have tested with pull-ups and/or series resistors on RX line and better decoupling on power supply, nothing made a difference The same UART lines work fine during runtime, they only fail when in bootloader mode The good PCBs are always good and

I am trying the NUCLEO545RE-Q. I created a project, imported it to STM32CubeIDE 2.2.0. The build button is grayed out. I found several videos for version 2.0.0 where is easy and straight forward. With this version is not and I couldn’t find any help. What am I doing wrong? 

Hi everyone,I'm planning to develop a VoIP/IP intercom application using FreeRTOS, LwIP, SIP, RTP, UDP/TCP, and an audio codec (SAI/I2S). I'm trying to decide between the STM32F7 and STM32H7 series (e.g., STM32F769I-DISCO vs STM32H750B-DK).From real-world experience, what are the main differences between the F7 and H7 beyond the datasheet specifications? Is the H7 worth choosing for a new networking/audio project, or is the F7 sufficient? Are there any practical drawbacks of the H7, such as cache or DMA complexity?I'd appreciate any recommendations or experiences from developers who have worked with both series.

When adding the VectU2F function to a processing list, it defaults to creating three buffers: pDst (float32_t), pSrc (float32_t), and pSrcuint32_t (uint32_t), instead of just pDst and pSrcuint32_t.There seems to be no way to select a different uint32_t input in the GUI. There is a field pSrcuint32_t, but this only allows me to select a float32_t buffer. I believe the type checking in the GUI for this buffer is incorrectly set to float32_t instead of uint32_t, and as a result it both creates the extra unused float32_t buffer (pSrc), and won’t let me change the actual pSrcuint32_t buffer it uses. This is supported by the VectItoF function which correctly checks that pSrcInt32_t is an Int32_t, and creates only two buffers. This results in extra memory used in the BRAM section, and means I can only ever have one buffer that converts uint32_t into float32_t. I suspect I will be forced to bypass the GUI to create this processing list as a result. (As an aside, the function naming in the Vect

Hello,I would like to evaluate  IIS2MDC mounted on MKI185V1 evaluation board using MEMS Studio. in the “Save to File” section I can choose Timestamp, Magnetometer, Magnetometer [LSB}, and Interrupt 1, but not Temperature, although the device has an internal temperature sensor. my setup:STEVAL-MKI185V1 on STEVAL-MKI109V3, FW: 3.79.1. MEMS Studio ver. 2.4.0 on Windows 11.Please advise,Shmulik

Hello, we are planning to use LSM6DSO in Mode 1, but PCB is fixed and pins 10 and 11 are connected to GND. This conflicts with LSM6DSO datasheet but I was wondering if it is still OK to connect them to GND. Can you clarify on this?

We are experiencing issues on STM32MP13 when using TF-A with OP-TEE due to an "Undefined instruction" exception during low-power entry.When TF-A is built with a standard arm-*-gnueabihf toolchain, the compiler is allowed to generate NEON instructions because the STM32MP1 platform enables:ARM_WITH_NEON := yesIn our case, GCC generates NEON instructions when compiling lib/compiler-rt/builtins/udivmoddi4.c, which is reached from udelay() during the low-power sequence. At that point, however, the VFP/NEON unit is disabled, so execution aborts with an "Undefined instruction" exception.Relevant TF-A build settings:ARM_CORTEX_A7 := yes  (from STM32MP1 platform settings) ARM_WITH_NEON := yes  (from STM32MP1 platform settings) AARCH32_SP := optee CTX_INCLUDE_FPREGS=0Relevant compiler options:-mcpu=cortex-a7  (generated by TF-A from ARM_CORTEX_A7 := yes) -mfpu=neon  (generated by TF-A from ARM_WITH_NEON := yes) -ffreestanding -fno-builtin -OsWe have verified that replacing udelay() with a simple

Even when running stm32cubemx2-1.0.1-X64-Windows-installer.exe as Admin: Failed to add cube-wrapper to PATH: Could not create / read registry 'HKEY_LOCAL_MACHINE\Environment': The parameter is incorrect. (0x80070057) On Windows 11 Pro Installing to C:\Program Files\STMicroelectronics\STM32Cube\MX2\1.0.1

Helloi’m using USBX 6.4.0 with CUBEMX to make a custom id device on a stm32H5  everything work fine BUT my report descriptor have four report ID i wanto to use :hid_event.ux_device_class_hid_event_report_id = 3;// some data in the bufferux_device_class_hid_event_set(hid_custom, &hid_event); and in order to do that i have to change custom_hid_parameter.ux_device_class_hid_parameter_report_id = UX_FALSE;to custom_hid_parameter.ux_device_class_hid_parameter_report_id = UX_TRUE;in the function: UINT MX_USBX_Device_Stack_Init(void) i can’t find in cube MX the property to change.. where is it?? thank you in advancebest reguards  

I am using SPI6 on an STM32H562 to write data to a WS2812 LED strip. The following code is called once per second to  write the data: LOGIF ("bytes left=%d", GPDMA1_Channel2->CBR1); LOGIF ("TXC %d", (WS2812_SPI.Instance->SR & SPI_SR_TXC) != 0); LOGIF ("ready=%d", HAL_SPI_GetState(&WS2812_SPI)== HAL_SPI_STATE_READY); if (HAL_SPI_GetState(&WS2812_SPI) != HAL_SPI_STATE_READY) { LOGIF ("error=%d", HAL_SPI_GetError(&WS2812_SPI)); HAL_SPI_Abort (&WS2812_SPI); } HAL_SPI_Transmit_DMA (&WS2812_SPI, spi_bytes, RESET_BYTES + nvalues * BYTES_PER_FRAME); Here is the log output for the first two calls:[101] ws2812 75: bytes left=0[101] ws2812 76: TXC 1[101] ws2812 77: ready=1[201] ws2812 75: bytes left=0[201] ws2812 76: TXC 1[201] ws2812 77: ready=0[201] ws2812 79: error=0The first time, GetState reports READY, but the second time it does not, even though bytes_left is zero and TXC is 1, so an Abort is required before the next transmit. Unfortunat

https://github.com/STMicroelectronics/meta-st-stm32mp/blob/scarthgap/recipes-bsp/trusted-firmware-m/tf-m-stm32mp.inc#L263 and the following cp commands preserve the ownership of the file which is a problem for yocto.When I build the sdk, I am getting the following error:Exception: Exception: KeyError: 'getpwuid(): uid not found: <my-uid-here>'Path <path-to-build-folder>/tmp/work/x86_64-nativesdk-<distro-sdk-name>-linux/nativesdk-tf-m-stm32mp-scripts/v2.1.4-stm32mp-r2.1/sstate-build-package/package/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-<distro-sdk-name>-linux/usr/share/tf-m/scripts/wrapper/imgtool/__init__.py is owned by uid <my-uid-here>, gid <my-gid-here>, which doesn't match any user/group on target. This may be due to host contamination.The fix is quite easy, any instance of “cp -a” needs to be replaced by “cp -a --no-preserve=ownership”. So you copy every other attribute but the ownership.I fixed it in a .bbappend but that would be

I tried to use the Build analyzer in VSCode, but there are some important allocations missing:VSCode:STM32CubeIDE (using *.elf file produced by VSCode):This is probably because the VSCode plugin is using the *.map file while the STM32CubeIDE uses the *.elf file.Is there any chance to have the same Analyzer in VSCode?

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 =