Solved

We are currently using the AEKS MCU-SPC5 LNKU Kit to debug our custom board. However, we are encountering a "launching error" when attempting to connect to the board via SPC5 Studio. For your reference, we have attached the error image below.We would like to understand whether any specific debug configuration is required within SPC5 Studio for successful debugging.Upon investigating the issue, we came across information suggesting that a PLS UDE software license may be required. If this is the case, we kindly request guidance on how to obtain the license and activate it.Additionally, we would appreciate detailed steps on how to set up and use the LNKU Kit for debugging our custom board.Your support in resolving this issue will be greatly helpful for the progress of our project 

I'm currently testing the BLE_LLD examples provided by st. I have two Nucleo Boards one running BLE_LLD_Lowpower and one running the BLE_LLD_Pressbutton example. That example works fine and I can change whatever is transmitted.If I use the same BLE_LLD_Lowpower example on one of my own PCBs with a STM32WB5MMG6  module I can only make the example work if I provide 3.3V. If I change the supply voltage to anything else than 3.3V it only transmits one package. But as soon as it enters the LL_PWR_MODE_STOP2 low power mode and wakes up from it, it seems to be stuck at some point. If I debug said example at 1.8V it keeps on running. (I think it won't go into sleep mode).If I run both examples unchanged and run the Lowpower example at 1.8V I get the same results.Is there an explanation for said behaviour? Any help appreciated

Hello, Is it possible to add the download links for the old versions of all your software's and resources, like it's the case on the web page of STM32CubeIDE ? In my case, I search to download the versions v1.4.1 and v.1.4.2 of MEMS-Studio for documenting my project. I asked to your support for this in the case 00239175 "How do I get an old version of MEMS-Studio ?", but your employee didn't find this. I think it is important to be able to get the older version of your resources for work on old projects and documenting the bugs and errors encountered. In my case, it's MEMS-Studio, but, in my feedback, I ask this for other of your resources which hasn't the same same system of the web page of STM32CubeIDE. Thanks for your time in the reading of my post. Best regards, lxaiia

I am learning to use the PWM Input mode to measure input frequency. I am using examples from the internet to help me along.In my .ioc file SYSCLK is set to 8MHz and with a prescaler set to /8 my HCLK and APB1 are set 1MhzIn the examples I studied in the callback routine Frequency is calculated either:1:   1000000 / capture_valuewhile another uses this method2:  SystemCoreClock / capture_valueMethod 1: works but in case you eventually need to change the prescaler you also need to change the constant.Method 2: sounds more robust but when I hover over "SystemCoreClock" in main.c a window comes up stating that SystemCoreClock is set to 8000000 anyway. What variable do I need to use to ensure that the value used in the calculation is in fact HCLK or APB1?

I have compared my platforms using PDM microphones related to PDM to PCM and filtering:Platform 1:STM32H747 (Portenta H7), with SW PDM2PCM filter (and optional to add post-processing)Platform 2:STM32U5A5 with ADF filter (in MCU) or external PCMD3180 chip.My favorites:STM32U5A5 with ADF: but unfortunately just mono MICPCMD3180: still room for improvements, e.g. using "channel summing" for +6dB SNR or tweaking the filtercoefficientsIn general: all filters are pretty similar. The major differences are on:the DC offset they have left (STM32U5A ADF needs for sure a HP filter)the harmonics created (distortion): just with a post-filter (e.g. on PDM2PCM) I could improvethe noise in high frequency spectrum (above 10KHz): STM32U5A5 ADF is the winner hereHere the result comparison (should be an animated GIF to see the differences):So, my conclusion: if I need a PDM MIC - use the STM32U5A5 ADF (if just one MIC needed), otherwise use external chip (PCMD3180).

Recently I'm trying to setup CLion and STM32CubeMX as I want to switch to a new IDE (By the way, the fact that STM32CubeIDE still doesn't have features like auto-triggered content asist, and that its poor, buggy GUI has bad compatibility with high DPI screen are just annoying). However, when I successfully generate the project in CubeMX and open it in CLion, CLion refuses to compile the project no matter what. I tried the bundled MinGW, CubeCLT1.18 and the older 1.16, and also CLion 2025.1, 2025.1.2, 2025.1.3. All didn't work. Up till this point I've been using CubeMX 6.15, and so I tried to install and use the older version (6.14.0). Everything suddenly works then. The project compiles without problem. Therefore, I suspect that there are some problems in the newest release of CubeMX (6.15) that are generating faulty CMake files.Here are some screenshots of what happened. I used the same version of CLion and CubeCLT in the same configuration on two projects generated by CubeMX6.15 and

I bought few STM32C071G8U6N from Mouser few month ago.As I know, the SRAM size in spec is 24K, but I will get error message as below when ZI-data over 8KB"Error: L6406E: No space in execution regions with .ANY selector matching xxx.o(.bss)."Program Size: Code=33736 RO-data=360 RW-data=132 ZI-data=6724 And the data in iirDataQueue will change into 8192 or around 65535 unexpected.. Following is my code(work fine on other platform), (iirData is no error).  memmove((uint16_t*)&dspMem.iirDataQueue[0], uint16_t*)&dspMem.iirDataQueue[1], (ADC_DATA_QUEUE_LEN - 1) * sizeof(dspMem.iirDataQueue[0])); dspMem.iirDataQueue[ADC_DATA_QUEUE_LEN - 1] = dspMem.iirData; We have also been using other series of products for a long time, such as STM32L4, but none of them is as frustrating as STM32C071. Could you please provide me with some direction to debug? Thanks.Environment:CubeMx 6.15.0 + STM32C0 1.4.0Keil MDK-ARM 5.29.0.0STM32C0xx_DFP 2.2.0 

why v2 stlink (stm32h7 series original Nucleo Board  ) + cupeProgrammer not connecting with w25q128 flash(external loader) .  external loader not working since from cube ide v18.0.0 has been released and recent version V19.0.0 having cubeMx qspi enable itself .I was fine  with qspi +cube ide v17.0.0  and qspi+cube programmer + CLIVEONE stldr.Even i have downgraded the cube ide again to v 17.0.0 and below version  the same work i carried out for cube programmer as well but nothing worked out .this is problem of v2 stlink driver or something else ? .  

Hello,I'm slowly losing my sanity so I figure I'd make a post here. I set up SAI4 to interface with BDMA, hoping to retrieve data from the onboard MEMS microphone and store it in a buffer in RAM_D3. Ideally I'd like for that data to be processed by the CPU, but I can't even get the buffer to fill up.The following code produces the output below:audio_buffer[0] = 5; audio_buffer[1] = 6; audio_buffer[2] = 7; audio_buffer[3] = 8; // ... // Inside main loop: printf("SAI State: %d \r\n", HAL_SAI_GetState(&hsai_BlockA4)); printf("SAI Error: %lu \r\n", HAL_SAI_GetError(&hsai_BlockA4)); printf("SAI Buffer Address: 0x%08lx\r\n", SAI4_Block_A->DR); printf("DMA State: %d \r\n", HAL_DMA_GetState(&hdma_sai4_a)); printf("DMA Error: %lu \r\n", HAL_DMA_GetError(&hdma_sai4_a)); printf("Pointer location: %p \r\n", audio_buffer); printf("Audio Buffer Data:\r\n"); for (int i = 0; i < 10; i++) { printf("[%d]: %d\r\n", i, audio_buffer[i]); } As you can see, SAI4 is in HAL_SAI_ST

tldr; if you're using a task to service the touchscreen (do the I2C reads/writes), how do you ensure it plays well with TouchGFX? I am finding that it would have to consistently run faster than TouchGFX (and perhaps be a higher priority) to be able to get it a new (x, y) coordinate every tick, so that TouchGFX doesn't consider the touch to be over and release the click.Long version:I am using a touchscreen with a GT911 controller on a custom ST board. We initially architected it such that a touch generates an interrupt, and in that interrupt we do two I2C reads and one write. Bad practice to do anything long in an interrupt, I know, but we were following guidance that we found elsewhere. This is what our ISR did:// Function to read out touch coordinates when a rising edge is detected on CTP_INT. // This is called from the CTP_INT GPIO ISR. bool Touch_Callback(void) { uint8_t number_of_coordinates; uint8_t point_info; // Read the touchpoint information register bool success =

When I assign pinouts for LED1 and LED3 on the NUCLEO-H753ZI in STM32CubeMX with the BSP selected, they are no longer assigned when the project is reloaded.

Hi All, Using STM32CubeProgrammer with the ST-LINK in SWD mode.If the RDP flag is set to 0xBB (level 1) and programmed the programmer can no longer connect to the device.How can I reconnect to the device to set it back to 0xAA? _Carl_

Hello,Working on STM32F767BITx and using Free RTOSEnable USART2, here is the init codestatic void MX_USART2_UART_Init(void) { huart2.Instance = USART2; huart2.Init.BaudRate = 115200; huart2.Init.WordLength = UART_WORDLENGTH_8B; huart2.Init.StopBits = UART_STOPBITS_1; huart2.Init.Parity = UART_PARITY_NONE; huart2.Init.Mode = UART_MODE_TX_RX; huart2.Init.HwFlowCtl = UART_HWCONTROL_NONE; huart2.Init.OverSampling = UART_OVERSAMPLING_16; huart2.Init.OneBitSampling = UART_ONE_BIT_SAMPLE_DISABLE; huart2.AdvancedInit.AdvFeatureInit = UART_ADVFEATURE_NO_INIT; if (HAL_RS485Ex_Init(&huart2, UART_DE_POLARITY_HIGH, 0, 0) != HAL_OK) { Error_Handler(); } }So I can see even just after init or even after some times, the gstate == 0x20 always, and thats why unable to transmit any message over uart as it is not ready.Please guide me what is missing here.Thanks,Nitin 

Hello everyone,I'm observing inconsistent FLASH ACR EMPTY flag behavior on two STM32G070RB chips (DEV_ID 0x6460) after a full chip erase by using STM32CubeProgrammer]Observed behavior:STM32G070RB (REV_ID 0x2000): After full erase, FLASH_ACR EMPTY flag correctly sets to '1' (chip boots into system memory). This is the expected behavior.STM32G070RB (REV_ID 0x2001): After full erase, FLASH_ACR EMPTY flag remains '0'. The chip attempts to boot from main Flash (0x08000000) despite being empty, leading to unexpected behavior.Questions: Is there a documented difference in the Flash empty check mechanism or FLASH_ACR EMPTY flag behavior between STM32G070RB REV_ID 0x2000 and REV_ID 0x2001?Are specific option byte settings or erase sequences required for REV_ID 0x2001 to correctly assert the EMPTY flag after a full erase? (I have tried power cycling.)Thanks,Tomislav

Hi, I am working with STM32MP157A-DK1 board with Yocto build system.I am trying to build synchronised system, that means I want to synchronise both CortexA7 and CortexM4. Basically I want to have the same time at both of them. I want to use STGEN for that, read it's counter on both A7 and M4 and share the values to calculate difference.And here is my question, how can I enable STGEN in my own linux image (I am not using OpenSt distribution right now). My image is basing on core image minimal.When I try to read STGENR registers provided in RM0436 with that piece of code (it is executed by M4):#include "stgen_read.h" #include "openamp.h" #define STGENR_BASE_ADDR 0x5A005000UL #define STGENR_CNTCVL_OFFSET 0x000 #define STGENR_CNTCVU_OFFSET 0x004 #define STGENR_CNTCVL_REG (*(volatile uint32_t *) (STGENR_BASE_ADDR + STGENR_CNTCVL_OFFSET)) #define STGENR_CNTCVU_REG (*(volatile uint32_t *) (STGENR_BASE_ADDR + STGENR_CNTCVU_OFFSET)) #Debug purpose extern struct rpmsg_endpoint ept; uint64_t

Hi Admins,I've posted valid question earlier today...https://community.st.com/t5/stm32-mpus-software-development/stm32mp157-ev-debugging-and-running-code-on-m4-from-stm32cubeide/m-p/825683#M2044Tried to follow the link to my message and noticed that it is now marked as SPAM ?!?!! so it is not visible to anyone but myself or I guess Admins. What was the reason to flag my post as SPAM ?Question in a post was of strictly technical nature.Here is what I am seeing when I look into it. I can follow link to post but there is no record of this post on my profile.What is the reason for all that ?

Hi everyone,I'm developing a bare-metal application with an STM32H725RG MCU using STM32CubeIDE (including HAL and code generation).I want to use the IWDG1 for reliability purposes, but for some reason, it seems to not work for me at all - upon startup, the MCU enters the Error_Handler loop, due to the HAL_IWDG_Init call returning HAL_TIMEOUT.In particular, I enabled the IWDG1 in the .ioc file editor, so it gets initialized and enabled by the generated HAL code. This enables the LSI as expected (RCC_CSR = 0x3), and I can confirm that the LSI itself works by outputting it to the RCC_MCO_2 pin.However, the initialization of the IWDG doesn't seem to complete. As far as I can tell from debugging, all the initial writes to IWDG_KR work as expected, and IWDG_PR and IWDG_RLR receive their correct values. This results in IWDG_SR = 0x3 as expected, which should go back to 0x0 within a few LSI cycles as the changes are applied - but this never happens. Instead, IWDG_SR remains at 0x3 permanently,

Hello ST Community,I’m working with an STM32WB55RG NUCLEO board and following the P2P Client tutorial. I’ve encountered an issue where my smartphone(ST BLE Sensor app) is not able to discover the board1. Hardware & Project• Board: NUCLEO‑WB55RG• Example: P2P Server (found in P-NUCLEO-WB55.Nucleo folder)2. FUS / BLE Stack Upgrade• Files used:stm32wb5x_FUS_fw.binstm32wb5x_BLE_Stack_full_fw.bin• Uploaded via STM32CubeProgrammer with “Start address automatic determination” - When I manually enter the address refer to Release Note, there was an error message "no mage found",  but Firmware successfully updated when using automatic determination mode.3. Observed BehaviorAfter the upgrade and code upload, the board powers on, but my smartphone does not see any BLE device advertising.No new entries appear in the phone’s Bluetooth list.+ All the programs are up-to-date  Any guidance on how to get my STM32WB55RG NUCLEO advertising would be greatly appreciated. Thank you in adva

Hi ST Team, I am new to NFC and have designed the schematic for NFC reader and antenna based on ST25R3916B. I am connecting these 2 PCBs with UFL connector antenna cable. When i started to test, some how it did not work, meaning tag is not detected. Can you pls review my design and suggest what changes should i do changes  in BOM to  have matching circuit and tune the antenna so that i can get the signals when tag is detected.Below is are the schematic and PCB images attached here for review. I would appreciate if i get any reply at the earliest.Since I am using antenna on a different PCBA, so I have used  reader in a single ended mode and used RFO1 and RFI1 for transmission and reception.  

Hi everyone,I'm currently working on the PCIe part of the STM32MP25 and would like to ask if there's anything wrong with my configuration. I’ve followed the official documentation provided by ST.Here are the documents I’ve referenced:PCIe device tree configuration - stm32mpuCOMBOPHY device tree configuration - stm32mpuBelow is my device tree configuration:/ { clocks{ /* USER CODE BEGIN clocks */ pad_clk: pad-clk { #clock-cells = <0>; compatible = "fixed-clock"; clock-frequency = <100000000>; }; /* USER CODE END clocks */ }; }; /*root*/ &pcie_rc { pinctrl-names = "default", "init"; pinctrl-0 = <&pcie_pins_mx>; pinctrl-1 = <&pcie_init_pins_mx>; status = "okay"; /* USER CODE BEGIN pcie_rc */ reset-gpios = <&gpioa 2 GPIO_ACTIVE_LOW>; wakeup-source; wake-gpios = <&gpiog 8 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>; /* USER CODE END pcie_rc */ }; &combophy { status = "okay"; /* USER CODE BEGIN combophy */ // st,ssc-on

Hello Friends,Most STM32 based Evolution / Development Board has Crystal 32.768 Khz and Boot switch connected. In my Custom design board , I do not need RTC Function and Bootloader to load.8 Mhz Crystal is used for Master Clock. Can I remove 32.768 khz Crystal and Bootloader Switch from Boot0 pin ?What should be default level maintain on these pins after removing both ? 

I'm trying to deploy my own simple AI model (Handwritten digit recognition) on my STM32N6570-DK board. I have already finished this project on STMF407 discovery board using Keil MDK. However, linker garbage problem popped up and I don't know how to solve it.First I created the project following the example below using STM32CubeIDE:https://community.st.com/t5/stm32-mcus/how-to-create-an-stm32n6-fsbl-load-and-run/ta-p/768206 and the led worked properly. Then I imported the pre-trained onnx model to X-CUEB-AI and generated the code. Here two problem occurred:1. The folder X-CUBE-AI appeared under the FSBL project, which doesn't have enough flash and RAM to support the model. I think it should belong to the Application project.2. When I tried to build the project (and I didn't change any of the generated code), linker garbage problem occurred as shown below. For project of STM32F407 in Keil MDK, I solved the problem by changing the C language compilation mode. Also, the

From what I can read on this diode it is from ST for sure, and it says VU beside the logo, the next line is M R, and the last line is GP922.   Any help would be appreciated.

Hello everyone,I have designed a custom PCB using STM32F103RBT6 and I’m facing a serious issue:The MCU is not getting detected by the programmer.Symptom:When connecting via SWDIO, SWCLK, 3.3 V, and GND, both STM32CubeProgrammer and ST‑Link Utility fail to detect the target.Power rails are verified: 3.3 V present at VDD pins, proper decoupling capacitors placed close to supply pins.No shorts observed on the board.Important hardware details:Boot0 pin (on my design) is directly tied to GND by mistake – I’m wondering if this could block programming or reset behavior.NRST pin has a 10 kΩ pull‑up to 3.3 V as recommended.BOOT0 is pulled low (GND) on the board without Resistor, any problem? Any advice would be greatly appreciated!schematic snippet attached. Thank you in advance for your help.

I'm trying to set up CAN communication between two STM32F4 boards using CJMCU-230 transceivers, but I'm not receiving any messages. Here's a full breakdown of the setup and what I've tried:Hardware Setup:MCU: STM32F4 Discovery (hcan1)Transceiver: CJMCU-230Second Node: Another STM32F4 with same configurationBitrate: 125 kbit/s on both endsTermination: 120Ω termination resistor is likely present on the transceiver (CJMCU-230) board, but not manually added externally. I haven't removed or measured it directly, but many CJMCU-230 modules include onboard termination resistors by default.STM32 Configuration:txHeader.DLC = 1;txHeader.IDE = CAN_ID_STD;txHeader.RTR = CAN_RTR_DATA;txHeader.StdId = 0x245;sFilterConfig.FilterMode = CAN_FILTERMODE_IDMASK;sFilterConfig.FilterFIFOAssignment = CAN_FILTER_FIFO0;sFilterConfig.FilterIdHigh = 0x0000;sFilterConfig.FilterIdLow = 0x0000;sFilterConfig.FilterMaskIdHigh = 0x0000;sFilterConfig.FilterMaskIdLow = 0x0000;sFilterConfig.FilterScale = CAN_FILTERSCALE_