Solved

Hello, I am planning on implementing a ST25R3916 circuit starting from X-NUCLEO-NFC08A1 schematic, but LXRW0YV600-054 is marked EOL for 2026. Is there any recommendation for change of the implementation?  Thank you! Best regards, Dragos

Hello!I'm completely lost in my search for a solution.Question description: The 25R3916 in 14443A emulation mode. When sending data to the reader with a length of up to 255 bytes, everything works perfectly. However, if I need to send data longer than that (e.g., a response to an APDU read record request 00B2041400), which is 3 bytes longer (including the successful APDU response [x90_x00]), things start to get complicated.What should the EMD suppression configuration register be set to, and what is the algorithm for sending the data?

I would like to use SWV for debugging on the Nucleo-N657X0-Q board.I first enabled SWV debugging and also change the CPU clock to 400 MHz.   Then, I added some code to main.c (as reference here ).At the same time, I also set the core clock to 50 MHz in the TRACE configuration of Keil.But i can't see any string in Debug Viewer.Does anyone know what else I should check? Thank's 

I have imported several example projects into CubeIDE which don't show the header files. The header files do actually exist in the windows file explorer, and the project does properly build and run. So why don't these show up on the CubeIDE (Eclipse) project view? Is there some Eclipse setting that I am missing?

Hi everyone, Is that not connecting BOOT0 to GND a problem? I forgot to connect it. İs it fine to be floating? Thank you in advance. 

Hi,Using ST Workbench debugger my 16-bit timer TIM2 (china bought) overflows each 16 seconds as the prescaler is set to 10. With an 16MHz internal clock divided by 2^10 (1024) the timer should overflow theoretically each 4.1 seconds. Prescaler 9 takes 8 seconds an prescaler 8 takes 4 seconds. So it is consistent but not according documentation. Where do I go wrong? Or is the internal clock 4MHz???

Hi allI'm struggling for a while getting a µSD Card to run via SDMMC on FileX. I'm using a Nucleo U575 Board with an external SDMMC/SDIO-breakout board. I tried to follow the "Fx_uSD_File_Edit" example for the U575I-EV board.Long story short, I set up a FileX application thread on ThreadX and I'm trying to just open the media.In main.c there's the automatically generated MX_SDMMC1_SD_Init() initializing the the SDMMC1 interface just after GPIOs and ICACHE were initialized. In main.c everything runs through without any error.However, when entering the FileX application, the very first function getting called is MX_SDMMC1_SD_Init() again - as I configured FileX to initialize the SD IP (just as seen in the Fx_uSD_File_Edit-example). This time it ends in a HardFault in the Init. The one thing that I really don't understand is that it happens just on the call of  sdmmc_clk = HAL_RCCEx_GetPeriphCLKFreq(RCC_PERIPHCLK_SDMMC);in stm32u5xx_hal_sd.cI enabled a breakpoint on the very first li

Hi.I'm working with the EVAL STM32WB5MM-DK for a while now, already programmed the stack and the FUS many times, and it's the first time I got this error.After successfully open STM32CubeProgrammer (v2.19) and connected to the programmer, Selecting the latest FAS file (1.22.1)And pressing "Firmware Upgrade", the upgrade fails and stop on warning "FAS_STATE_IMG_NOT_FOUND".Same for my 2 laptops, 2 Evals, and 1 board connected to the ST-LINK programmer.Happen also for stack programming, and after full chip erase.Please advice.  Pressing Read FUS Info show information even after full chip erase. 

I am using NUCLEO-H7A3ZI-Q (32 bits) . While Debugging the LED4 starts blinking solid red and never exits debugging,it shows a breaking point at MCU config();.I was running a program to obtain a sawtooth wave through the DAC pin PA5./* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 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 --

Hi,We are working on a custom carrier board based on STM32MP157DAC. We have built a custom yocto image.Yocto Version: MickledoreMachine: stm32mp15-discoSoM: STM32MP157DACDistro: openstlinux-westonLinux Kernel: 6.1.82-stm32mp-r2-r0WIFI-Bt: LBEE5PL2DL-921I have attached the dmesg log and device tree configuration.Is the driver support for this wifi-bt module directly available or do I need to configure something?bluetooth is configured as serial3 but I don't see any /dev/ttySTM2 device node.[ 14.597018] Bluetooth: Core ver 2.22[ 14.606728] Bluetooth: HCI device and connection manager initialized[ 14.614038] Bluetooth: HCI socket layer initialized[ 14.629270] Bluetooth: L2CAP socket layer initialized[ 14.637891] Bluetooth: SCO socket layer initialized[ 14.658379] Bluetooth: HCI UART driver ver 2.3[ 14.669248] Bluetooth: HCI UART protocol H4 registered[ 14.675392] Bluetooth: HCI UART protocol Broadcom registered[ 14.986555] Bluetooth: hci0: Frame reassembly failed (-84)[ 15.485933] Bluetoo

 Hi STM-Team, We have the custom board based on the STM32MP157DAC board.In that, we are not able to access the eMMC from u-boot command prompt. Currently, we are booting from SD card.We are able to see the 1 mmc device which is SD-card but not able to see any eMMC on device. Please see below logs: but emmc is being detected after kernel boot as seen from the dmesg logs and i was able to read and write to the emmc device  u-boot log:- STM32MP> mmc listSTM32 SD/MMC: 0 (SD)STM32MP>  dmesg log emmc being detected:- mmc1: new DDR MMC card at address 0001[    2.864763] mmcblk1: mmc1:0001 MT3204 3.56 GiB [    2.876500] mmcblk1boot0: mmc1:0001 MT3204 2.00 MiB [    2.884632] mmcblk1boot1: mmc1:0001 MT3204 2.00 MiB [    2.890880] mmcblk1rpmb: mmc1:0001 MT3204 512 KiB, chardev (244:0) below is my device tree configuration for sdmmc2 in kernel-source/arch/arm/boot/dts/stm32mp15x

Hi STM-Team,We have the custom board based on the STM32MP157DAC board with KLD35176BVIB LCD display.KLD35176BVIB is actually BOE3.49(VGA) + HX8394f  display.We are using yocto build to configure the display panel changes.I have attached my device tree configuration1) I need to configure below pins.Pin NamePin NumberFunctionImplementationRemarksPA14T2TP_INTTouch Panel interruptReference design has only DSI_LCD_INT, combined for Display + TPPD13AA19DSI_TEPin re-mapped FUNCTION MOVED FROM PC6 TO PD13PD15J2DSI_LCD_BL_CTRLPin re-mapped Function moved from PA15PH6Y11TP_RESET  I was not able to find how and where to map these pins for my display panel As I am not much familiar with ST pin-mapping I was not able to figure out these mappings.2) I was also looking for the DSI defaul data and clk pins pinmapping in device tree but not able to find it for below pins.DSI_D0PDSI_D0NDSI_D1PDSI_D1NDSI_CK_PDSI_CK_NDSI_RESETDSI_LCD_INT3) Additionally is there a display driv

Hi,We are using STM32mp157DAC som with a custom carrier board. We have built a custom yocto image. Yocto Version: Mickledore Machine: stm32mp15-disco SoM: STM32MP157DAC Distro: openstlinux-weston Linux Kernel: 6.1.82-stm32mp-r2-r0   below is my device tree configuration. aliases { serial4 = &usart1 }; &usart1 { pinctrl-names = "default", "sleep", "idle"; pinctrl-0 = <&usart1_pins_a>; pinctrl-1 = <&usart1_sleep_pins_a>; pinctrl-2 = <&usart1_idle_pins_a>; /delete-property/dmas; /delete-property/dma-names; status = "okay"; }; usart1_pins_a: usart1-0 { pins1 { pinmux = <STM32_PINMUX('Z', 6, AF7)>; /* USART1_Rx */ drive-push-pull; bias-disable; }; pins2 { pinmux = <STM32_PINMUX('Z', 7, AF7)>; /* USART1_TX */ drive-open-drain; bias-disable; }; }; usart1_idle_pins_a: usart1-idle-0 { pins { pinmux = <STM32_PINMUX('Z', 7, ANALOG)>, /* USART1_TX */ <STM32_PINMUX('Z', 6, ANALOG)>; /* USART1_RX */ }; }; usart1_sle

Hi. I am using STM32H735VG for SPI communication with external ADCs.But I want to add external ADCs and I already used all 5 SPIs.So I will use OCTOSPI, can OCTOSPI play the same role as classic SPI?In menual, OCTOSPI in indirect operating mode works like a classical SPI interface.If they play the same role, how I set the pin?(I will use only one OCTOSPI.) Thank you.

Hello,I'm new to STM32Cube-IDE (and Eclipse). Normally I use the ARM-gcc toolchain and do assembly coding.I managed to create a New STM Project by using the Example Selector tab in the Target Selection window.In this case it was the BSP Example for the B-U585I-IOT02A Discovery Kit (with the STM32U585 chip). After modifying the code in accordance with how-to-use-semihosting-with-stm32cubeide  the code runs OK. Now I would like to COPY the Project and edit that. From the multiple "how to clone a project" threads it appears that this is not trivial. (?) One of the threads I read was from 2022 and IDE version 1.8. It seemed that multiple otherwise experienced developers found it odd that this wasn't a straightforward task. Manually copying and search/replace seems very odd and error-prone.Has there been any progress on automating this?  In my case there aren't even any .ioc or .project files. As expected, the following don't work:Simply copying the P

This is our first board design that uses the STP16CPC26. We have two chips daisy-chained together. The SDO output from the first chip never goes high. The SDO pin is definitely not shorted to ground or any other net, and is definitely connected to the SDI pin of the daisy-chained downstream chip. If the chip is properly powered, the SDI pin is held high, and clocks are applied to the CLK pin, is there any reason why the SDO pin would not go high?

My apologies if this is the wrong ST forum... it seemed like the closest one to the part I'm using.I have a new STM32F072 board design that has a STP16CPC26 LED driver connected to one of SPI busses. I just could not get the chip to do anything using the SPI bus, so I switched to a dirt-simple bit-banged (temporary, throw-away) driver so that I could easily change any aspect of the timing to make the chip work. Same problem... no matter what I do none of the outputs ever turn on and the SDO output stays low all the time. I've used a DMM to ensure it's properly connected to power and ground and that the supply voltage is okay (it's at 3.3V). I've had 3 other embedded developers look at the scope traces of the SDI, CLK, LE and OE- signals and they all agree that the timing and sequencing matches what the datasheet says you have to do to make the part work, but... it acts like it's dead. I've tried 5 different boards, and none of the outputs on any of them ever change state. I've also ver

I want help to understand this. The STM MOS FET STP6NK60ZFP has a MAX gate-source voltage (Vgs) at 30V. In order to protect it from ESD it has a built-in TVS diode. Over 30V it can fail. But the bulit-in TVS has breakdown voltage (Vbr) set at 30V. It's when it begins to conduct. The clamping voltage (Vcl) is a couple of volts more. It's when it conducts fully. But then it's over the limit 30V. More voltage than that can make the MOS FET fail. Shouldn't it be that the Vcl should be 30V so an ESD can't exceed 30V? Or is it really enough with Vbr at 30V and Vcl some volts more? Se table below.  

... ideally automatically as part of a normal Debug or Release build.

I fully appreciate that CubeMX is geared towards hobbyists and demo projects.But let's imagine for a second that someone is trying to use this software professionally.I have created a template to generate some custom code with CubeMX and it works as expected. However, in the IOC file my settings are stored as shown below:ProjectManager.TemplateDestinationPath=C\:\\path\\to\\my\\project\\cubemx\\my_project_name ProjectManager.TemplateSourcePath=C\:\\path\\to\\my\\project\\tools\\cubemx-templatesNow imagine someone else is working on this project. Maybe they have checked out the code to a different directory, or maybe they are using Linux. The IOC file is broken for them. If they fix it on their side and commit it, it will be broken for me.Please add support for setting these paths relative to the IOC file itself, so that multiple people can work on the project.By the way, I tried editing the file manually and setting a relative path, but then the file is no longer generated.I am using C

Move from MCU forums: STM32MP25 are MPUs - not MCUsHello Experts, I am using  STM32MP257F-DK board and trying to bring up the board with starter package. I followed the steps as mentioned in this link - https://wiki.st.com/stm32mpu/wiki/STM32MP25_Discovery_kits_-_Starter_PackageThe starter package that I have downloaded and flashed - en.FLASH-stm32mp2-openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06.tar.gzI was able to flash the SD card successfully as mentioned in section 6.(Note that I have taken care of boot switches accordingly)However, when I restart the board for booting, seems there are issues and does not stop at login prompt. Instead stops or boots in loop. Attaching 2 logs with 2 instances of reset. Kindly help to review and suggest work around if  have missed any steps.~R 

I'm having an issue with a breakout board housing a VL53L1X sensor where, between the breakout board and MCU, the only connections are power, gnd, sda and scl through a PCA9617ADPJ I2C buffer. I've set it up for continuous ranging at about 200ms timing budget and is usually accurate for my purpose of just detecting if something is within about 1-2 meters. I have my codes set up so if the sensor status returns 255 VL53L1_RANGESTATUS_NONE, the code will attempt to reinitialize the sensor for re-connection.  However, sometimes it will randomly enter this state when plugged in normally. While I'm still yet to figure out WHY it enters this state, my big issue is that once it reports VL53L1_RANGESTATUS_NONE and reinitializes, the ranging accuracy is hopelessly screwed up, where hovering a target about 4cm in front of the sensor reports a maxed out distance value of 8043mm, and linearly scales from there as an object gets closer. The absolute worst part about this is that a physical rese

Hi everyone,So I'm trying to get the VL53L8CX ToF lidar working in ZephyrRTOS running on a NRF9151 chip. I'm using the VL53L8CX ULD driver version 2.0.1. The VL53L8CX is connected to the NRF9151 using i2c with the address 0x52, however when I call the vl53l8cx_is_alive() function from the driver i only see the messages being sent over i2c and getting a NAK. The i2c setup itself is confirmed to be working given that other devices use the same bus and are working as intended (we have tested with just the VL53L8CX connected as well with no difference in behaviour). We are using a custom pcb and the lpn pin is connected to 1.8v IOVDD with a 47k resistor and the system is powered with 3v AVDD. The VL53L8CX relevant circuitry for our custom pcb looks like this:With pull-up resistors for the i2c lines.The vl53l8cx_is_alive() function is called right at the beginning of main, but we have tried to add a delay before calling to give the system time to get fully powered up without effect.As

I discovered a strange phenomenon:After I powered on the VL53L4CD, I called the interfaces:The interfaces such as VL53L4CD_SensorInit, VL53L4CD_SetRangeTiming, VL53L4CD_SetDetectionThresholds, and VL53L4CD_SetSignalThreshold complete the initialization operation.Then call the VL53L4CD_ClearInterrupt and VL53L4CD_StartRanging interfaces to start the measurement. At this time, interrupts can be received normally, and the interrupt pin can rise and fall normally.At this point, I call the VL53L4CD_StopRanging interface to stop the measurement. At this time, tthe interrupt pin is at a high level.At this point, I put the device aside without operating it for about two or three days.I recalled VL53L4CD_ClearInterrupt and VL53L4CD_StartRanging, and immediately received an interrupt. At this time, I called the VL53L4CD_GetResult and VL53L4CD_ClearInterrupt  interface to read the result and found that the value of range_status was 2.Subsequently, the interrupt pin remained at a low level. I

Hi,I've installed TouchGFX following the instruction at https://support.touchgfx.com/docs/introduction/installation on a completely new installation of windows 10. When I try to create a project, TouchGFX crashes at 88% and simply closes. When I checked the TouchGFXDesigner.log file the error is System.IO.FileLoadException: Failed to load native freetype library!Any idea how I can fix this?Please see attached log file.Thank for your help. Looking forward to get the designer working.Richard