Solved

Hi,I've flashed an application in the STM32N6570-DK board using a FSBL and Appli projects. The application boots fine.But when the application is running, I can't attach to it using the debugger and ST-Link.I've tried to open the debug port of the STM32N6 by writing 0xB4 to the BSEC_AP_UNLOCK register, but it still fails.The error I get is:STMicroelectronics ST-LINK GDB server. Version 7.11.0 Copyright (c) 2025, STMicroelectronics. All rights reserved. Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled Target unknown error 32 Error in initializing ST-LINK device. Reason: Unknown. Please check power and cabling to target.Using STM32CubeProgrammer, I get this error on Access Port 1 with Hot Plug mode:But I've not configured anything: I've not blown any OTP fuse, nor changed any Option bytes. And I'm not using a secure bootloa

Hello.. can anyone advise the SWD pin for F767? and how these are connected to F767? PA13 PB3? Any schematic will be great !! I'm using it for debugging. Can anyone advise? 

Newly installed Ubuntu 25.04Newly installed VSCode with STM32Cube for Visual Studio Code(preview)The project generated by STM32CubeMX can be compiled, but cannot be debugged.    

Hi,I'm planning to use STM32H562ZI as I3C controller with an I3C v1.0 compatible Target endpoint. Since STM32 I3C IP supports I3C v1.1.1, will there be any potential issues on RSTDAA, ENTDAA, I3C Private Write, I3C Private Read or other electrical parameters with v1.0 ? Though I do not see any limitation based on v1.0 & v1.1.1 specifications (Apart from IBI mandatory byte and new CCCs), I'd like to hear from the community. Appreciate the help.Thanks,Srinath

Ive been trying to get active passthrough between my adc and dac from pa1 and pa0 respectively. Ive confirmed all my functions are being called but i just cant seem to get any value loaded into my DAC. if i give it a value manually, i get the correct value at the pin. I am putting a 2.6 VDC source at my adc pin but have failed to get anything out. I have included my main.c file. I am using the nucleo-l476rg board

Hello there, I ran into an issue with my STM32WBA55CGU6 chip. I designed my board with schmematics from Mouser: 511-STM32WBA55CGU6 with the UFQFPN48 pinout. When setting up my chip in CubeIDE I also chose the STM32WBA55CGU6 version. But when comparing the pinout of the chip the SMPS version of the UFQFPN48 footprint is displayed.Is this an issue I can solve by selecting the correct footprint in CubeIDE or is it, that CubeIDE is wrong at that point? The UFQFPN48 version should have PB12 on Pin1 and not VSSSMPS as shown in the image. Thanks in advance,Tim 

I am using the  Nucleo-L433RC-P board and have configured pin PC13 as SYS WKUP (for the blue top button).How can I read the state of this pin when the processor wakes up, because HAL_GPIO_ReadPin will not work.I am sure I used a function or macro to read the state of this pin before, but can't remember how I did it.I need to distinguish between an RTC wake or a pin wake from shutdown.I use wake markers stored in an RTC backup register to detetc an RTC wake.  I write to the backup register just before calling shutdown in the function SCH_mcuSleep....void SCH_mcuSleep (void){ /* The Following Wakeup sequence is highly recommended prior to each Standby mode entry mainly when using more than one wakeup source this is to not miss any wakeup event. - Disable all used wakeup sources, - Clear all related wakeup flags, - Re-enable all used wakeup sources, - Enter the shutdown mode. */ // write value to RTC backup register to indicate mcu was in sleep HAL_RTCEx

Hello, I need to do FFT transforms of long signal traces, so  using CMSIS DSP doesn't look possible because of the 4096 points limit. I tried to use fftw3 library (3.3.10). I built it using OpenSTLinux SDK from the Github source without problem. Here is configuration I used: configure --host=arm-ostl-linux-gnueabi --enable-neon --enable-single --with-slow-timerLibrary libfftw3f.a  was built successfully and test app was also successfully linked with it. Here is relevant part of the test app code:int fft_points = 131072;fftwf_plan pr2c, pc2r;fftwf_complex* fft_cbuf = 0;float* fft_buf = 0;fft_cbuf = (fftwf_complex *)fftwf_malloc(sizeof(fftwf_complex)*(fft_pts/2 + 1));memset(fft_cbuf, 0, sizeof(fftwf_complex)*(fft_pts/2 + 1));fft_buf = (float *)fftwf_malloc((fft_pts + 2) * sizeof(float)); memset(fft_buf, 0, (fft_pts + 2) * sizeof(float));printf("allocated buffers: %p, %p\n", fft_cbuf, fft_buf);pr2c = fftwf_plan_dft_r2c_1d(fft_pts, fft_buf, fft_cbuf, FFTW_ESTIMATE);&nbs

Split from: Nucleo-H7S3L8 Board in Arduino IDE - this is a new question.Hi @Andrew Neil Trying to send text via USART3 (which is linked to the virtual com ST LINK USB, correct?)  and show it with Putty. But as I see the USART3  in the MX is disabled (grayed out) that I cannot configure it. Any help with that?  

Hi, I am using an STM32H523 MCU where I transmit some data via SPI (master tx only) in blocking mode.In debug build the SPI behaves as it should be and everything is fine.In release build the SPI CLK line remains high for too long, after the last bit of a transmission has been sent.This results in the (software) CS line going high before the CLK returned to 0 (the DAC7562 slave does not like that)How it looks like in Release:How it looks like in Debug (correct):My code for the transmits: HAL_GPIO_WritePin(GPIOA, CS_Pin, GPIO_PIN_RESET); hal_status = HAL_SPI_Transmit(spi_handle_, data, sizeof(data), HAL_MAX_DELAY); HAL_GPIO_WritePin(GPIOA, CS_Pin, GPIO_PIN_SET); CubeMX config code:void MX_SPI1_Init(void) { hspi1.Instance = SPI1; hspi1.Init.Mode = SPI_MODE_MASTER; hspi1.Init.Direction = SPI_DIRECTION_2LINES_TXONLY; hspi1.Init.DataSize = SPI_DATASIZE_8BIT; hspi1.Init.CLKPolarity = SPI_POLARITY_LOW; hspi1.Init.CLKPhase = SPI_PHASE_1EDGE; hspi1.Init.NSS = SPI_NSS_SOFT; h

Hi!I'm working with the STM32F042K6T6TR (LQFP-32 package), and the documentation on mouser.com says that it is moisture sensitive. So what is the maximum temperature I can put this chip into the oven at (for ~24 hours) to dehydrate it. The working temp is max 85C, but I'm guessing it can take 100C when not powered, just dehydrating, right?Link to mouserLink to datasheetThanks!

Hi everyone,I'm currently trying to flash firmware to a custom board with STM32WLE5CCU6 MCU using the onboard debugger of a NUCLEO-WL55JC1 development board. I'm running into multiple issues and would appreciate any help.Setup:Target MCU: STM32WLE5CCU6 (custom board)Debugger: Integrated ST-LINK on STM32WL55JC1 (used as programmer)Tools: STM32CubeIDE(Ver 1.15.1) and STM32CubeProgrammerIssue Summary:CubeProgrammer only connects at very low frequency (200 kHz SWD clock). Higher frequencies fail to detect the target. Even when connected, flashing consistently fails with different errors on both IDE and Cube programmer depending on the attempt.(in all modes). Errors observed in STM32CubeIDE:Spoiler (Highlight to read)Failed to execute MI command:load ...\LoRaWAN_End_Node.elfError message from debugger back end:Error finishing flash operationFailed to execute MI command:load ...\LoRaWAN_End_Node.elfError message from debugger back end:Error finishing flash operation4. Errors observed in

Edited console output - see here for future referenceHello,I encounter a problem with my LCD from Winstar model WF50DTYA3MNG10.I have a custom board based on STM32MP157 with a display connected to Mipi 2 lanes.On previous Openstlinux(kirkstone) without optee, the driver and display working well.After switching to the latest Openstlinux I discover a problem with "ltdc fifo underrun" root@telemach-somunknown:~# [ 96.350190] weston[1406]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set[ 111.422211] [drm] ltdc fifo underrun: please verify display mode[ 130.546427] [drm] ltdc fifo underrun: please verify display mode[ 190.539247] [drm] ltdc fifo underrun: please verify display mode[ 250.549608] [drm] ltdc fifo underrun: please verify display mode[ 310.542950] [drm] ltdc fifo underrun: please verify display mode[ 370.537518] [drm] ltdc fifo underrun: please verify display mode[ 430.556994] [drm] ltdc fifo underrun: please verify display modeInitialization seems t

I read the AN5510 at section 5.1 RMA Pasword(s). I am working on STM32MP257F so the RMA pasword is 128-bit as describe in the table 5.The AN5510 also mentions that "The RMA password(s) are chosen by OEM". I understand that I need to generate a 128 bit binary file as RMA Password. So I use the following Command to generate RMA Password.STM32_KeyGen_CLI -rand 16 stm32mp_rma_password.binIs this the correct way to generate RMA Password? 

Hello ST Community,I am working with an STM32MP2-based board and would like to load an initramfs image into DDR RAM using dfu-util and then boot it without having to manually enter U-Boot commands. I have tried to follow the documentation, specifically:How to load U-Boot with dfu-utilHow to execute a U-Boot script via DFUHere are my observations:When using a flashlayout, after transferring the images, U-Boot does not boot the kernel automatically — it stops at the U-Boot prompt and waits for manual commands.When using a U-Boot script (as described in the documentation), I am able to transfer artifacts for ramfs in DFU mode, but when I attempt to load the kernel (alt=0), the process hangs: and after about 30 seconds to 1 minute the board resets itself (as if by a hard reset).I have tried both compressed (Image.gz) and uncompressed (Image) kernel images, with the same result. My questions:Is it possible to load and boot a Linux kernel with initramfs in RAM using dfu-util, so th

Hello,Based on the NVM example, after: ZbPersistNotifyRegister(zigbee_app_info.zb,APP_ZIGBEE_persist_notify_cb,NULL).What actions cause the device to enter the callback? Where can this information be found?Thanks,

Hello,I am looking how to shorten the timeout and/or failure entering of the callback.I am using ZbZclClusterCommandReq(cluster, &req, callback, arg). I currently have my own ACK timeout implementation, however, the callback still is entered with either ZCL_STATUS_TIMEOUT or ZCL_STATUS_FAILURE. I noticed this may cause flooding-like effects and overload the network.Is there a way to shorten this timeout (to around 300ms instead of its default ~6s) so I can remove my ACK timeout implementation and just work with this? Is that recommended to do?Thanks,

Hi support, I’m currently working with a Nucleo-WB55RG board, and my goal is to perform a firmware update using an ESP32 as the host. The ESP32 is connected to the STM32 via USART1 (PA9 and PA10).The sequence followed is : 1. Connect to the bootloader2. Test the link with Get command3. Erase memory (mass erase)4. Write binary + read for checking data5. Go I’m encountering an issue when sending the Extended Erase command to the bootloader (3. Erase memory). I followed the documentation closely for both the hardware and protocol, as described in AN2606 (pattern 16) and AN3155. Here is my manipulations :=====================First step : activation and synchronization with the bootloader :0x7F sent0x79 received Then, Get command to check supported commands on the chip. Those are following : 0x00, 0x01, 0x02, 0x11, 0x21, 0x31, 0x44, 0x63, 0x73, 0x82, 0x92.-> So, this confirm that the uart interface and hardware setup are working correctly . When I send

I was able to get CDC_Standalone in STM32CubeH7RS running on Nucleo-H7S3L8.Next, I am trying to get USB FS CDC running based on the Templates_board project.First, I need to modify the .ioc file to display the COM port in the Windows Device Manager. However, the USB regulator ready flag (PWR_CSR2_USB33RDY) is not set within HAL_PWREx_EnableUSBVoltageDetector(), causing a timeout.I have attached the current .ioc file.Any advice would be greatly appreciated.

Hello,I need to modify an old application which has initially been created with Atollic TrueStudio and was then adapted to an early version of CubeIDE. It's a project from a colleague who has retired.From what I can see so far is that the projects .ioc file was made with a version 6.5 or older (CubeIDE throws an error about it if I try to open it). However, thanks to the project PDF report I was able to recreate the .ioc file with the original device settings. I copied the application sources without modifications and created the project.Unfortunately, the application does not work, so I'm trying to figure out what's going wrong. From what I can see so far is that the interrupts seem to be correctly enabled and the handlers are called (currently I could verify this only for SysTick, for the other interrupts I need to create a dedicated test setup).But the original generated code makes calls to the corresponding peripheral handlers from the interrupt handlers which are either missing in

Hi everyone, for several days I've been trying to replicate the Nx_TCP_Echo_Server application example by creating a project with the .IOC file, but I can't establish Ethernet communication. If I compile and run the example, everything works, but my application doesn't. I'll send you my project if anyone can help. Alternatively, can someone point me to a simple TCP stack without using an RTOS? Thanks so much for your help. I'm using a NUCLEO-N657X0-Q board, STM32CubeIde 1.19

tried to set up a USB device serial emulation (CDC) for STM32H563. Started a Free RTOS based project project in STM32CubeMX. But there I only can activate USB as "device_only in the "connectivity" segment but do not find any other USB related settings. I did that previously with the stm32F series and there it was in STmCube, no prob.The generated code also seems not to have the USBD_DESC_Private_Defines or similar things needed. Is it somewhere hidden under another name in STM32Cube? Or does STM32Cube does not support it? Or is this  CPU issue? Or do I need to somehow get me drivers from other places and when yes, from where?  

I am using the BLE_p2p_Server_ext example on a stm32wba55cg and i want to use ADC_Channel_2 as a way of voltage measurements.My current setup:I use a new adc handle:ADCCTRL_Handle_t adc_channel2_handle = { .Uid = 2, .State = ADCCTRL_HANDLE_NOT_REG, .InitConf = { .ClockPrescaler = ADC_CLOCK_ASYNC_DIV1, .Resolution = ADC_RESOLUTION_12B, .DataAlign = ADC_DATAALIGN_RIGHT, .ScanConvMode = ADC_SCAN_DISABLE, .EOCSelection = ADC_EOC_SINGLE_CONV, .LowPowerAutoPowerOff = DISABLE, .LowPowerAutonomousDPD = ADC_LP_AUTONOMOUS_DPD_DISABLE, .LowPowerAutoWait = DISABLE, .ContinuousConvMode = DISABLE, .NbrOfConversion = 1, .ExternalTrigConv = ADC_SOFTWARE_START, .ExternalTrigConvEdge = ADC_EXTERNALTRIGCONVEDGE_NONE, .DMAContinuousRequests = DISABLE, .TriggerFrequencyMode = ADC_TRIGGER_FREQ_LOW, .Overrun = ADC_OVR_DATA_OVERWRITTEN, .SamplingTimeCommon1 = ADC_SAMPLETIME_814CYCLES_5, .SamplingTimeCommon2 = ADC_SAMPLETIME_1CYCLE_5, .OversamplingMode = DISABLE, }, .ChannelConf =

Hello ST team,  I have logged raw data by using hsdatalog_GUI.py in STM32CubeFunctionPack_DATALOG2_V2.1.1 from STEVAL-STWINKT1b board to PC and seen the FFT diagram in GUI. The acquired raw data was saved locally in an automatically generated folder. After that I tried to plot FFT figure by activing the command hsdatalog_plot.py -ft. However, figures it plot are all in time domain. Figures are attached below. What I expected is the power density spectrum over a frequency band.   

We develop firmware on STM32H7R3L8HxH.STM32CubeIDE version is 1.19.0MxCube version is 6.15.0The problem is that code generator creates additional wrong include file for "regular" H7 MCUs:#include "stm32h7rsxx_hal.h" #include "stm32h7xx_hal.h"As this second file does not exist, compiler gives error:fatal error: stm32h7xx_hal.h: No such file or directoryIn application project it appears in main.hIn bootloader project the issue does not appear, but there is a blank line instead.In extmemloader project it appears in extmemloader_init.h Had same problem already STM32CubeIDE v1.18 and we have been manually fixing it (by removing bad include) so far, but it appears that it won't get fixed by itself so I report the issue now.