Solved

Hello,I am facing an issue with the STM32C5 HAL SPI driver related to CRC error detection.In my setup, CRC is enabled for SPI. When a CRC error occurs, I can observe that the CRCERR flag is set before the transfer is closed. However, the CRC error is never reported via the HAL error callback.Looking into the HAL implementation, I noticed the following behavior:SPI_CloseTransfer() calls LL_SPI_Disable()After disabling SPI, SPI_CloseTransfer() checks LL_SPI_IsActiveFlag_CRCERR()When this check is performed after LL_SPI_Disable(), the CRC error is no longer detectedIf I move the LL_SPI_IsActiveFlag_CRCERR() check before LL_SPI_Disable(), the CRC error is detected correctlyAdditionally, in my case SPI_CloseTransfer() is called from HAL_SPI_IRQHandler(), but:the return value of SPI_CloseTransfer() is not evaluatedonly the Tx/Rx complete callback is invokedmy error callback is never called, even though a CRC error has occurredFrom my understanding:LL_SPI_Disable() itself does not clear the C

In CubeMX2 when configuring the I2S peripheral on an STM32C542 running from a clock of 144MHz and selecting an audio clock rate of 96000Hz, CubeMX2 computes a nearest reachable frequency of 97826Hz (I2SDIV = 23, ODD = 0). When code is generated and run on actual hardware, the HAL2 I2S driver computes a different value of 95744Hz (I2SDIV = 23, ODD = 1). The HAL2 hardware value has less error from the desired 96000Hz than the value reported by CubeMX2, but the CubeMX2 value may be used in designing other aspects of the firmware and result in unexpected performance.    

I know that Motor control workbench is only available on Windows but I hoped that it would be possible to open the generated .ioc file from Linux. I tried it and I got this error. Can this be fixed or I cannot even open the STM32CubeMx project from linux?  

Hello,I am using a STM32G474 and the RTC is counting >24.I have setup the RTC with the STM32CubeMX. regards Mark,

Hello ST Community,I am working on a custom PCB using the STM32H743ZIT.My project uses the LTDC to generate a VGA signal.I also need at least 1 DAC output and USB_FS. The issue is, in this specific MCU, the only 2 DAC’s are on:PA4 (conflicts with LTDC_VSYNC)PA5 (possibly conflicts with LTDC_R4) Now, I can move LTDC_R4 to PA11 but now it conflicts with USB_FS pins.Importantly, LTDC_R4 is not physically connected on our PCB. We only use 8 simple colors so I can use any LTDC pin to connect it to VGA signal. I’m completely fine losing LTDC_R4 altogether because we don’t use it at all. Question: If I do the following, will it cause any conflict issues due to the way the MCU works internally?1- Assign LTDC_R4 to PA5 in CubeMX to satisfy the configurator2- Immediately after HAL_LTDC_MspInit() completes, override PA5 to analog mode using HAL_GPIO_Init() for DAC use3- Configure DAC1 channel 2 manually in code and importantly, I call it AFTER HAL_LTDC_MspInit() Note: We are not reinitializing LT

Hi,I’m using a NUCLEO-C031C6 64 board.I successfully setup the tool chain and ran several test from STM32CubeMX templates, directly compile and programming through STM32CubeIDE.Until this morning, everything was working fine.But I have lost the connection to the MCU later on. From STM32CudeIDE:Target unknown error 19Error in initializing ST-LINK device.Reason: Unknown. Please check power and cabling to target. Using of STM32CubeProgrammer:Recognized as mass storage On board ST-LINK/V2 is recognized, updated to version V2J47M34 successfully Full chip erase and board recognition works fine on the NUCLEO-G031K8 boardBut I have repetitively following messages while I try to connect (): I have tried unsuccessfully:under reset mode  external SWD ST-LINK  How can I debug futher?Did I miss something?Thanks!   

I’m trying to configure an STM microcontroller, so I tried to download STMCubeIDE. When I load the download page the ‘Get Software’ section loads forever sometimes, other times I refresh and the button doesn’t appear, and sometimes when I refresh it actually shows me the download button. When I sign in, and hit the download button (when it shows) and then accept the terms of the agreement, it just does nothing. It just closes the agreement, no download. I tried with and without VPN, on multiple home and public networks and hotspots, on multiple browsers and even devices. For context, I am on windows 11. How do I resolve this? Edit: In fact, I’ve noticed many official install links seem to be broken, as STMCubeF4, STMCubeMX, and serveral others don’t install either. 

I’m using a custom board based 99% on the STM32H7S78-DK (except for the display, which is a 7”).I’m having a serious deadlock issue (the entire microcontroller freezes, and I can’t connect to the debugger).My firmware is composed:The bootloader that just checks if an SD card is attached (if so, it mounts, reads it, and, in case, updates the external flash with the firmware). If no SD card is detected, it loads the application.The bootloader uses I and D caches and sets up the external memory via XSPI (PSRAM and FLASH)The PSRAM is used for the TouchGFX framebuffer; the FLASH for the TouchGFX assets.The .icd defines (among other things)define symbol __ICFEDIT_intvec_start__ = 0x70000000;define region EXTRAM_region = mem:[from 0x90000000 to 0x91FFFFFF];define region ROM_region = mem:[from 0x70000000to 0x701FFFFF];define region EXTROM_region = mem:[from 0x70200000to 0x77FFFFFF];place in ROM_region { readonly };place in RAM_region { readwrite };place in EXTRAM_region { firs

Hi,On the stm32c5 nucleo board (NUCLEO-C5A3ZG) there is T1S OA PMD driver (not mounted?).  In the header file "stm32c593xx.h" exists a 10BASE-T1S control register "MAC10BT1SCR". But there is no documentation in the Reference Manual RM0522 Rev 1, and I can't find a way to enable T1S on MXcube2.Can anyone help me here? Is the T1S PDM really integrated in the C5 series?I would really like to experiment with 10Base T1S.RegardsPatrick

Hello,We are designing a custom board using the STM32MP157FAC1 device and need to provide provision for a Serial NOR Flash connected to the QUADSPI interface.We are planning to use Winbond's device W25Q256JVFIQ for this purpose. Kindly confirm whether this device is suitable for use with the STM32MP157FAC1 or if there is any recommended QSPI NOR Flash device that should be preferred with this microprocessor.Regards,Prashant

My design requires a microSD with the G474RE MCU.  The Eval board schematic shows the design and some code in the \driver\BSP.  However, I do not see the application example.  My requirements are to read and write multiple data files.  Where can I find an example with these features?  Any other eval examples I can port over?

Hello everyone!I am trying to get all services and characteristics from steval-stwinbx1 board running FP-SNS-Datalog2 function pack. Here's simple program I wrote:import asyncio from bleak import BleakClient MAC_ADDRESS = "DA:3E:83:DD:30:F8" async def discover_services(mac_addr): async with BleakClient(mac_addr) as client: for service in client.services: print(f"\n[Service] {service.uuid}") print(f"Description: {service.description}") for char in service.characteristics: print(f" |") print(f" +-- [Characteristic] {char.uuid}") print(f" Properties: {', '.join(char.properties)}") if __name__ == "__main__": asyncio.run(discover_services(MAC_ADDRESS)) I expected to get services listed by nRF Connect app.But the program output is empty. Why? PS: I have done some research and experiments. I have tried running same script on linux and it ran perfectly (I used 2 machines: same machine (dual boot) and raspberry pi). I have noticed that board crashes if you are trying to

I noticed that STM32CubeMX2 (DEBUG features page) offers only three debug modes: JTAG 4‑pin, JTAG 5‑pin, and Single Wire Trace Asynchronous.In many practical cases, developers use only the SWCLK and SWDIO lines to save pins, so the absence of a simple Serial Wire option (without Trace) seems to be a limitation of the current STM32CubeMX2 release.This option is still available in STM32CubeMX1 when working with similar MCUs, such as the STM32H5 series.Is this understanding correct?

Hello, I am preparing to develop a custom board based on the STM32MP15 series MPU and getting accustomed to the DDR testing procedures in the STM32Cube ecosystem with an STM32MP157F-DK2 evaluation board. However, I am running into issues with the SYSRAM loading option which seems to be the necessary method for DDR testing new, custom boards designed around the STM32MP157 MPU. Firstly, I am able to run the DDR Test Suite in STM32CubeIDE or STM32CubeMX after importing the STM32DDRFW-UTIL-main\DDR_Tool\STM32MP157C-DK2 project into STM32CubeIDE. I am able to run the test firmware on the evaluation board with the "Debug As" option (with boot switches set to Engineering Mode), and then I am able go to a new .ioc project file made for the STM32MP157F-DK2 (peripherals initialized in their default modes) and use the DDR Test Suite via the "DDR Interactive" mode with no issues. Similarly, I can open a serial connection in TeraTerm via the ST-LINK COM port and run the DDR tests the

when you enable SWD in CubeMX2 it automatically blocks the SWO pin as well (tested using C531FBP6), but I only need SWCLK / SWDIO to debug. please add a way to disable the use of SWO.

 The GUI for the programmer shows:  RM0440 Rev 8 shows:Are ‘BOOT0’ and ‘nBOOT0’ different? As it stands, the programmer requires a value of ‘0’ to boot from FLASH, but the table wants a value of ‘1’. Is the value referenced by nBOOT1 the inverse of the value set in nBOOT0?

Hello,    I have designed a custom PCB using STM32N657I0HxQ and W25Q32JWZPIQ NOR flash. I am following the STM32N6 FSBL Load & Run tutorial https://community.st.com/t5/stm32-mcus/how-to-create-an-stm32n6-fsbl-load-and-run/ta-p/768206 , but have trouble getting the application running. I am using below setup:STM32CubeIDE - v1.19.0STM32CubeProgrammer -v2.21.0STM32CubeMX - v6.15.0I have created a custom external memory loader for W25Q32JWZPIQ and able to connect device in Dev boot mode (BOOT1 -1, BOOT0-0) and flash FSBL-trusted.bin and Appli-trusted.bin at 0x70000000 and 0x70100000 respectively. Also, I am able to verify the contents.  When I connect to Flash boot mode (BOOT1-0, BOOT0-0), Led is not blinking. I tried to debug by setting device into Dev mode and run FSBL directly into internal RAM, I can see the FSBL is properly copying the application code to 0x34000000 but JumpToApp() ends up in fault.I have tried the belowFSBL-t

Hi, I’m working with FATFS + SDIO + USB mass storage class.But I can’t seem to get writing and as a consequence reading working.in my main.c I do: //fatfs test makeFileData("test12.txt", "TEST123"); char* data = readFileData("test12.txt"); printf("read data = %s\r\n", data); And in my console I get as a response:D-SH 0 /System Volume Information---- 209 /x1_DEFAULT.JSON---- 211 /x2_DEFAULT.JSON---- 211 /x3_DEFAULT.JSON---- 211 /Ik_heb_iets_verzonne.JSONTotal blocks: 1922016 (961 Mb)Free blocks : 1921888 (960 Mb)SD Card Block size = 512SD Card Block number = 1953792SD Card size = 1000341SD Card Version = 1Init WVR complete!f_write failed: 1read data = So It can open the card and perform a ls command, but for some reason I can’t write. I spotted that some people look at DMA but I’m not using DMA.My entire SD card Handler:/* * SD_Card_Handler.c * * Created on: June 24, 2026 * Author: william.vanraemdonck */#include "WVR/SD/SD_Card_Handler.h"#incl

We are using the STM32WBA5MMG in our design but because of space and the shape of the board we need to be very precise with our components. The issue i'm having is with the documentation of the clearance required for the STM32WBA5MMG.In document “DS14801 @6.4 schematics and layout for pcb” the clearance on the left side of the package is 1.93mm from the side of the packageBut in “AN6305 @figure 35 to 39” the clearance on the side of the package is 1.93mm from the left side of pin 72.We are going to use the STM32 with the +10dB for Bluetooth and need the best option but also need to fit a lot of components on the PCB. Q.What clearance do i need to follow for the best Bluetooth signal, clearance in AN6305 or DS14801?

My test conditionAs you can see the detection volume of FoV is going outside the reflective block (blue block) and I am not getting accurate reading. I want to know whether there is a way to make the FoV much narrower so that I can concentrate on the reflective block placed opposite to the TOF sensor.

After generating the BLE_Sensor project files for the B-WBA5M-WPAN board with STM32CubeMX Version 6.17.0, the STM32CubeIDE shown this error. I looked for the file in STM32Cube_FW_WBA_V1.9.0 and it is not there. Please advise.10:56:39 **** Incremental Build of configuration Debug for project BLE_Sensor ****make -j9 allmake: *** No rule to make target '/Users/user/STM32Cube/Example/BLE_Sensor/Drivers/STM32WBAxx_HAL_Driver/Src/stm32wbaxx_hal_pka.c', needed by 'Drivers/STM32WBAxx_HAL_Driver/stm32wbaxx_hal_pka.o'. Stop."make -j9 all" terminated with exit code 2. Build might be incomplete.

Hello, I am trying to create a very simple TZ-Enabled application on the STM32H573 in a CMake project. My application can build and flash to the IC and execute the main.c of the secure world but it hard faults, I believe when switching to the non-secure world. I am unsure of why it does this and would like help figuring that out. I’ve attached the project to this post and I will provide information below: Fault Analyzer OutputFault Analyzer OutputR0:      0x2009FC00 ← Non-Secure RAM (Non-Secure SP?)R1:      0x08110B68 ← Non-Secure FLASH (See Vector Table Non-Secure Memory (Non-Secure Main Entry?))R2:      0x08110B68 ← See AboveR3:      0x08110B68 ← See AboveR12:    0x08110B68 ← See AboveSP:      0x3004FF74 ← Secure RAMLR:      0xFFFFFFA9PC:      0x0C000FF6XPSR: 0x09000003 Vector Table Non-Secure MemoryThis is some data from memory address 0x0810 0000Address 0 4 8 C 0x0810 0000 200A 0000 0811 0B69 0811 0BC5 0811 0BC5 0x810 0010 0810 03BD 0811 0BC5 0810 03C3 081

Hello ST Team,The STM32N6 DK2 board includes the Sony IMX335 image sensor, but I have not been able to find the official sensor datasheet or a complete register reference document.For advanced development tasks such as HDR configuration, exposure control, gain tuning, and custom sensor initialization, access to the sensor register descriptions is essential.Could ST please clarify: Is the official IMX335 datasheet available to STM32N6 DK2 users? If the full datasheet cannot be shared due to Sony licensing restrictions, is there a register map, application note, or programming guide available that documents the sensor registers used by the STM32N6 DK2 BSP driver? What is the recommended process for obtaining the official IMX335 documentation required for sensor configuration and HDR development? Without access to the sensor register documentation, it is difficult to implement or evaluate advanced sensor features beyond those already exposed by the BSP driver.Thank you for your suppor

I recently tried to use -noreconnect via the cli on windows and it still attempted to reconnect.I was connected via UART and programming option bytes. Here was the command I used:& "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=COM14 br=115200 -noreconnect -ob ndbank=0x0I see that there was fix put in for linux. Im wondering if the same bug exists on Windows.Thanks,Daniel 

I have ordered the Nucleo-C542C board. I am waiting on the board to arrive so I thought I would setup a blinky project to test on the board. i used MX2 to setup the GPIO, clock, etc. I then imported the project int CubeIDE using the CMAKE option.Apparently there is no way to build a release file. This means I will not be able to program the board. The build hammer only shows the debug build option.Also, I do not see the .ioc file in the project tree. Apparently I don’t understand how MX2 and CubeIDE link together. If I am able to ever find the .ioc file, will it be updated if I make changes in MX2? The old version of CubeMX linked the.ioc files together. If changes were made by CubeMX, those changes were reflected in CubeIDE.As a side note, there is one aggravating minor issue with CUBEMX2. Why are all the screens so washed out and difficult to see?. Everything that should be solid black is a barely visible light colored grey. This is particularly annoying in the GPIO chip pinout view.