Solved

Hello. I have a custom board with original f103c8t6 (sampled from eStore). PWM for pin PB4 is not functional, but bit banging with gpio write works. If tim3 respective channel is configured as pwm output, the output is stuck at VCC.  I configured the board correctly in CubeMX, as every other pin works correctly (including pin PB5, same timer, different channel) and double checked it again and again. Unfortunately I can't attach a project that reproduces the bug at the moment as I moved forward by changing the operating mode of the board (it commands a MC33926PNB H bridge and instead of having the H bridges enabled and sending PWM over IN1 and IN2, i set them as high or low depending on the direction and pwm the enable input, which functions well), but in a few days I can reproduce it. I am curios about what can cause the strange behaviour. It's not a conflict between JTAG reset as I have SWD enabled and even disabled it for a test which led to the same results.Here

Extension 3.7.0st-arm-clang 19.1.6+st.10Hello,I am using CubeIDE für VSCode.I write programs for the STM32F756ZGTx. I have set ST Arm Clang as the compiler in CubeMX. Redirecting the output (printf()) via the serial debug interface is possible without any problems. When I try to output float or double values with printf(), I get some weird results.printf() with integer float/double yields correct results for integer float/double wrongprintf() with float/double integer always leads to incorrect resultsI repeated the experiment for double variables. The same problem occurs here as well.#include "main.h" #include <stdio.h> extern UART_HandleTypeDef huart3; double floatVar = 1.1f; void mainThread(void) { printf("\r\n\nHello from Nucleo F756 - float Test\r\n" "-----------------------------------\r\n"); for(;;){ printf("Float value: %f - Integer %u\r\n", floatVar, (unsigned int) floatVar); printf("Integer %8u - Float value: %f\r\n", (unsigned int) floatVar, floatVar); H

I am using a ST25R3916B with RFAL 4.0, connected to a STM32WB55 via SPI in a battery powered application, so naturally wakeup mode is used. Specifically inductive wakeup with auto averaging. For a short test on the table this works just finde, but when I let the setup run for multiple hours and thousands of wakeups, at some point it becomes unresponsive. If I measure the generated field via oscilloscope, I can still see the ~35µs pulses every 400ms, just as I have setup the mode, but there is no interrupt generated.I do not want to completely dismiss the possibility that the MCU is missing one interrupt somehow, but shouldn't a consecutive change trigger a new interrupt?What I have found in the AN is Values close to the edges can lead to a configuration that never wakes-up the system, so, if delta is the difference that triggers an interrupt, the reference value must always satisfy the following conditions: • reference - delta > 0 • reference + delta < 255Is there

Hi ST, How i can I use M33 co-processor of stm32mp257 series , and how can i connected debug with Cubeide,how can i use Ethernet port  through the Co-processor,Note: I am using Opnestlinux distribution package.

Hello everyone! In our system we have a set of subsystem that uses F4/F7 MCUs and one - with STM32H743 MCU. We want to use system CAN bootloader for all of them. Everything seems ok, except STM32H743 device. From AN2606 we know that it starts in bootloader with such FDCAN config: 'Connection bit rate 250 kbit/s', 'Data bit rate 1000 kbit/s', 'FrameFormat = FDCAN_FRAME_FD_BRS'. So, it waits for FD frames. The question is: can we use default CAN (not FD) with 250 kbit/s bitrate to update every subsystem there? Will STM32H7 recieve default frames and work in default  CAN formats?

Framebuffer is RGB565,Can I make a dynamic bitmap of ARGB8888? I made one by cacheable container and display the dynamic bitmap by a texturemapper but the image came out is not correct,something did appear on screen,but size and color not right. but if I change bitmap type to rgb565,the image show correctly,but with black background and  no alpha ,not what I wanted. There is enough  cache,I confirm the dynamic bitmap is created successfully on both type.I tried to display the dynamic bitmap by a Image widget,but the result is the same.In this forum,I can see a solution,to register a LCD32bpp class and set it as Auxiliary LCD in the hal.But I didn't found any thread on this subject.How to use off screen rendering of a textarea in a... - STMicroelectronics CommunityCan I get any help from any @st_it guys?

Background: I am using the STM32H747I-DISCO board and the BSP SDMMC example from the ST Repository as my starting point.  I can provide my code if necessary but wanted to keep post as short as possible.  I have looked at AN4838, AN4839 and AN5200 ST Micro Documents.  They are detailed but not getting me to my answer fast enough.   My Goal:I am trying to understand the detailed reason(s) why I need to enable the D-Cache when using FatFS calls with the SDMMC peripheral on the STM32H747I-DISCO board to avoid a timeout and also why I-Cache does not necessarily need to be enabled.     My Understanding to this point: The CLIFF NOTES of what I think I understand (between the ST documentation, AI hallucinations and true answers): Enabling the D-Cache reduces AXI bus contention since the IDMA in the SDMMC peripheral needs AXI bus to move data from the FIFO to SRAM on a very tight timeline, mandated by the SDMMC peripheral.  When you enable the D-Cach

Hi all,I'm struggling to get SPI working on my STM32U5G9J. I have an nordic master device outputting 6 bytes of data every 500 ms over SPI and plugged into the proper pins, double checked and confirmed on analyzer.stm32u5g9j_dk2.overlay/ { aliases { spi-slave = &spi1; }; }; &spi1 { status = "okay"; pinctrl-0 = <&spi1_sck_pa5 &spi1_miso_pa6 &spi1_mosi_pb5 &spi1_nss_pb0>; pinctrl-names = "default"; /delete-property/ cs-gpios; fifo-enable; };main.c#include <zephyr/kernel.h> #include <zephyr/logging/log.h> #include <zephyr/drivers/spi.h> #include <zephyr/drivers/gpio.h> #include <zephyr/sys/util.h> LOG_MODULE_REGISTER(main); #define SPIOP (SPI_OP_MODE_SLAVE | SPI_WORD_SET(8) | SPI_LINES_SINGLE | SPI_TRANSFER_MSB) static const struct device *spi_in_dev = DEVICE_DT_GET(DT_ALIAS(spi_slave)); static const struct spi_config spi_in_cfg = { .frequency = MHZ(1), .operation = SPIOP, .slave = 0, }; int main(void) { if (!dev

Hello, I'm starting a new project with the N657 device.  I can't get the debug SWO port to work. 1- I'm redirecting the putchar to the SWO port: int __io_putchar(int c) { ITM_SendChar(c); // HAL_UART_Transmit(&huart3, (uint8_t *)&ch, 1, 0xFFFF); return (c); } 2- The trace and debug clock is set to 8mhz 3- In the debugger setup, i enabled the port and set it to 8mhz 4- in the debugger, I enable trace 0, and enabled it.   Nothing ever seems to get sent to this window.  Note: I know the cable/usb dongle is good since it works with the h743.   Does anyone have any suggestions? thanks Matthew    

HI, I have a strange issue with our STM32H747 board using the IS42S16400J SDRAM chip.We have been reading the "How to set up the FMC peripheral to interface with... - STMicroelectronics Community" page and this all seems OK.The differences between the system described and our board is that we have 8 MB RAM instead of 32 MB and we do not use the byte lane select signals (LDQM and UDQM from the SDRAM chip are routed to ground). When writing to SDRAM, we see (random) writes to the other 32 bits word within the same 64 bits. This is true for both 16 and 32 bits write from the CM7 core. So writing 0x12345678 to address 0 in the SDRAM results in a random value being written to address 4. Same applies when writing to address 4 - there I see a random value appearing at address 0. If I first write 0x12345678 to address 0 and then 0xaa55aa55 to address 0x14, I see the value 0x12345678 being writting to address 0x10.This is almost as if the processor performs a 64 bits write with the lower o

Hello, I created a complex project for a STM32H573 based custom board. That project is ThreadX based and it shall use the USPBD package. I generated to project with STM32CubeMX version 6.16.1 using STM32Cube MCU Package for STM32H5 Series 1.5.1 (see attached IOC file for reference) I create the code for the latest STM32CubeIDE 2.0.0. The project is imported successfully, but does not compile and the following errors are logged: Description Resource Path Location Type 'USBPD_CORE_PDO_TYPE_APDO' undeclared (first use in this function); did you mean 'USBPD_CORE_PDO_TYPE_FIXED'? usbpd_dpm_user.c /test03/USBPD/Target line 1100 C/C++ Problem 'USBPD_CORE_PDO_TYPE_APDO' undeclared (first use in this function); did you mean 'USBPD_CORE_PDO_TYPE_FIXED'? usbpd_dpm_user.c /test03/USBPD/Target line 1577 C/C++ Problem 'USBPD_ParamsTypeDef' has no member named 'PE_UnchunkSupport' usbpd_dpm_user.c /test03/USBPD/Target line 1507 C/C++ Problem 'USBPD_ParamsTypeDef' has no member named 'PE_UnchunkSupport

Hello ST/TouchGFX team,Our team have been using scroller widgets to display data that is lazily loaded from a persistent database. It works well, but since these widgets use 16-bit indexes, it limits the amount of rows that can be displayed to 32k. Given the way these widgets work, it's only necessary to keep the visible items in memory and the index is kept only as the first visible item's offset, increasing the index size would have minimal if not negligible memory impact, and since TouchGFX only runs on 32-bit ST MCUs, any arithmetic operations are done in 32-bit anyway so there should be no performance impact.In fact, we've been able to hack a solution to this by modifying the provided framework headers and source files to these widgets. The only issue is that the TouchGFX generator is hardcoded to create the updateitem callbacks with int16 signature and there is no way to change this except for modifying the base classes -- which are overwritten every time the project is rege

Hey there at @Pavel A. I've implemented USBCDC as a device In stand alone mode successfully I intend on implementing CDC host stand alone that is to say without X-thread RTOS.The generated files from cube MX don't have Read_run and Write_run functions for stand-alone when implementing the host side which makes me wonder if it is achievable you to have USBx as a host in stand alone.

Hi everyone,I am working on a custom board based on the STM32F429I MCU (RMII mode) and I am trying to integrate LwIP with a DP83848 PHY.At the moment, I am unable to get Ethernet working. The issue appears during PHY initialization — the code blocks while trying to communicate with the PHY over MDIO.Project ContextMCU: STM32F429IPHY: DP83848 (RMII mode)Middleware: LwIPDevelopment tool: STM32CubeIDE (project originally generated with CubeMX, but I cannot re-generate it now due to version mismatch)ETH driver: HALI have tried:Using the LwIP stack with the HAL ETH driverAttempting raw Ethernet (without LwIP)In both cases, the system gets stuck during PHY initialization.Observed BehaviorThe code freezes when accessing PHY registers (MDIO communication).When debugging, execution appears to stop when checking or configuring the ETH clock.The PHY does not respond to register reads.Suspected CauseI suspect either:The RMII clock (50 MHz reference clock) is not correctly generated or routed.The P

 # External Loader Issue: STM32U5G9ZJT6Q + MX25L12833FZNI-10G (Quad-SPI)## 1. Problem SummaryHello, I'm a novice developer who recently started working with embedded systems. I've been struggling significantly with implementing an external loader for several weeks now...I'm developing an external loader for **MX25L12833F** (16MB Quad-SPI NOR Flash) connected to **STM32U5G9ZJT6Q** via OCTOSPI1, but it continuously fails in STM32CubeProgrammer. The loader compiles successfully and generates a `.stldr` file, but programming operations fail.---## 2. Hardware Configuration### 2.1 MCU: STM32U5G9ZJT6Q (LQFP144)- Cortex-M33, up to 160 MHz- 2.5MB SRAM- OCTOSPI peripheral### 2.2 External Flash: MX25L12833FZNI-10G (Macronix)| Parameter | Value ||-----------|-------|| Capacity | 16MB (128Mbit) || Max Clock | 133 MHz || Page Size | 256 bytes || Sector Size | 4KB || Block Size | 64KB || Operating Voltage | 2.7V - 3.6V |### 2.3 Pin Mapping (OCTOSPI1 Port 1)| Function | STM32 Pin | Flash Pin ||--

(STM32L476RG+X-NUCLEO-NFC07A) I use Android ST25 (ST25AndroidApp-V3.12.2) to communicate with NFC7(STM32L476RG) by FTM.Click FTM demos of  Menu ST25DV Demostrations on Android ST25 APP, and click Send data to tag, 1000 bytes by default, the Transmission/Reception success with showd 1000/1000 bytes as showed in image below:but the show exception "Command failed"  from mDataReceived = mFtmCommands.sendCmdAndWaitForCompletion(...)of source_ST25AndroidApp-V3.12.2\app\src\main\java\com\st\st25nfc\type5\st25dv\ST25DVFtmDemoActivity.javathe frimware is built bySTMicroelectronics\ST25NFC_Embedded_Lib_ST25R3911B_1.8.0\Projects\STM32L476RG-Nucleo\Applications\X-NUCLEO-NFC07A1\FTM\STM32CubeIDEand the uart console shows successAfter build and run (with ST25FTM_ENABLE_LOG enabled), the uart log as below---------------------------------------- *****Welcome to x-cube-nfc7 example***** ---------------------------------------- 10988: RxState = ST25FTM_RX_INIT_RECEPTION 10992: F

Hello, I just started in stm32 system, I want to ask for stm32N6 series can use other camera module? such as camera product from Arducam where the product is made for raspberrypi systemwhich uses CSI-2 interface, here product link : https://www.arducam.com/product/64mp-quad-camera-kit/Thankyou

Hi All,   I have been using SPI1 over DMA2 on Zephyr RTOS recently to read my external flash. I had done similar thing on Bare metal / FreeRTOS based program. Both of them work fine. However, there is a problem in Zephyr based implementation of its driver compared with what i developed on Bare Metal. I configure the SPI1 to use its full possible clock 42MHz on both platforms. On my bare metal platform it runs at full 42Mbps but on Zephyr it starts giving read errors. However, if i reduce the clock to < 42MHz (to which zephyr driver forcelly rounds it down to 21MHz) it works fine.Here is my dts node of spi1 for my development board: &spi1 { pinctrl-0 = <&spi1_sck_pb3 &spi1_miso_pb4 &spi1_mosi_pb5>; pinctrl-names = "default"; clock-frequency = <42000000>; // 42MHz dmas = <&dma2 2 3 (STM32_DMA_PERIPH_TO_MEMORY | STM32_DMA_MEM_INC | STM32_DMA_PRIORITY_HIGH) STM32_DMA_FIFO_1_4>, <&dma2 3 3 (STM32_DMA_MEMORY_TO_PERIPH | STM32_DMA_M

The main website states:"STM32CubeIDE integrates STM32 configuration and project creation functionalities from STM32CubeMX to offer all-in-one tool experience and save installation and development time. "https://www.st.com/en/development-tools/stm32cubeide.html However, @Aimen1 writes here:"STM32CubeIDE is now independent from STM32CubeMX."https://community.st.com/t5/stm32cubeide-mcus/stm32cubeide-2-0-0-released/td-p/857110 This caused us some useless troubleshooting trying to see why the installation didn't contain everything that was expected.Perhaps the main website can be updated, and/or a notice can be added in the CubeIDE that it will no longer generate the .ioc files for projects.

Hey, I am running into issues with a custom PCB based on STM32H743IIT6.Using IS42S32400J-6TLI as SDRAM,  with an LCD screen. Using TouchGFX and DMA2D deactivated.A hard fault is encountered after entering Model:Tick()Hard Fault Error Detected at: Debug stack view: LTDC:SDRAM - only 16 data bits used:TouchGFX: MCU:  Any suggestions what could be causing this Hard Fault error? 

I am using below component toolsMCU: STM32H750IBT6IDE: STM32CubeIDE Version: 1.20.0GUI: TouchGFX Version: 4.26.0SDRAM: IS42S32400J-6TLIFLASH: MT25QL512ABB8ESF-0SIT (QUADSPI) I have made my own external loader that proves works for the QUADSPI IC using this video: https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/external_QSPI_loader.html Thank you in advance!

Hey,I am using STM32H750IBT6 with MT25QL512ABB8ESF-0SIT QSPI flash IC for external memory and IS42S32400J-6TLI as SDRAM, on a custom PCB with an LCD screen. Using TouchGFX.QSPI pinout is as follows:I've edited the FLASH_Id script - added as a .c file as an attachment.I would prefer to not use a bootloader, but if that is the only way or quickest way to get this working then please let me know. I have looked at using external loaders but as the pin out of my QSPI is slight different, external loaders will not be compatible. My code compiles but it does not flash: Under 'ASSETS_FLASH', ExtFlashSection does appear as expected after loading images onto TouchGFX. If you have any suggestions why I can not flash the external QSPI flash IC, please let me know. Additionally, within STM32CubeProgrammer I can connect to the MCU. I can successfully mass erase the flash too. Thank you for any assistance in advance!  

I am running into issues with a custom PCB based on STM32H743IIT6.Using MT25QL512ABB8ESF-0SIT QSPI flash IC for external memory and IS42S32400J-6TLI as SDRAM,  with an LCD screen. Using TouchGFX. I am getting this error. Any ideas what could be causing it? Thank you in advance!

Hi, I followed the guide at the following link:https://community.st.com/t5/stm32-mcus/how-to-build-an-ai-application-from-scratch-on-the-nucleo-n657x0/ta-p/828502and I've run an example gently posted here that is similar (the link was posted on the comments of the guide):https://github.com/YousefDessouki/STM32_N6_NuceloBoardwithNPU.gitWhen I run the model posted on github on my Nucleo it's all fine and it will print output results on PuTTY console.However, when I try to change the neural network with one of those used for speech enhancement posted at the following link:https://github.com/STMicroelectronics/stm32ai-modelzoo/blob/main/speech_enhancement/stft_tcnn/ST_pretrainedmodel_public_dataset/valentini/stft_tcnn_medium_sigmoid_257xsl_float.onnx https://github.com/STMicroelectronics/stm32ai-modelzoo/blob/main/speech_enhancement/stft_tcnn/ST_pretrainedmodel_public_dataset/valentini/stft_tcnn_medium_sigmoid_257xsl_qdq_int8.onnx(I need to run a speech enhancement model for a project

I'm trying to establish communication with FDCAN and view the signal via PCan View, but nothing appears on the screen. There are no errors in the connections. These are the codes: /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2026 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS. * ****************************************************************************** */ /* USER CODE END Header */ /* Includes ------------------------------------------------------------------*/ #include "main.h" /* Private includes ---------------------------------------------------------