Product forums

Hello,We have a custom board based mainly on stm32mp257-dk design. The sdcard supply voltage doesn't activate on STPMIC for some reason. Is the stpmic preprogrammed on the DK board or should the Rom code of the MPU activate it via I2C? Best RegardsRaimo

Hi,We are using the STM32WLE5JCI6.In our design, the TCXO (HSE) is powered directly by the 3.3 V on-board power supply, and the VDD_TCXO pin is left unconnected. Is this acceptable?Should we avoid using the Set_TcxoMode command in this case?Thanks for any help

Hi.I'm in progress of making an iOS app that needs to send custom commands to a ST25DV tag. I've been going through the same error all week (Feature not supported, from CoreNFC), so I started using the ST25SDKiOS but I still don't get how to use it. I was wondering if there is any instruction to use it to send custom commands to the tag.Thanks.

EDIT: After doing some more research and testing, I've discovered that doing a software reset of the STM32 actually pulls the nRST pin itself low briefly. I did not realize this.  I assumed a software reset was purely internal.In my previous testing, I noticed that the LAN8742A PHY was recovering after resetting only the STM32, so I thought it was something in the startup initialization sequence that was pulling the PHY out.  However, I now realize that the PHY is also being hard reset.  (more details about this in latest reply below).ORIGINAL MESSAGE:Hello.  We have a controller using an STM32F429 with a LAN8742A ethernet phy.  That part of the design is roughly based on the STM32F429 discovery board.  Long story short - what is the correct process/procedure for reinitializing everything related to ethernet and LWIP?  We are experience ethernet lockups associated with electrical noise.  Resetting the STM32 without resett

l6566b model spice file is required can u please provide us for our project

Hello,I had generated an External QSPI loader for W25Q128JV and STM32H743 some 2 years ago.I originally used it with STlink Utility Programmer and then switched to STM32CubeProgrammer.  All good and working as expected with CubeProgrammer v2.17.I stopped updating the CubeProgrammer as every version after that including the latest v2.20 no longer functional with my custom .stldr file refusing to mass erase the device. Does anyone know what changed in CubeProgrammer support for External Loaders starting with v2.18 ?Thank you,Yuri

HelloSTM32H7R3L8I have trouble using the circular mode of GPDMA when trying to transmit data over SPI4. When I set the GPDMA channel 12 to be in circular mode, it generates the GPDMA channel init in the msp init file instead of the main file as if it is a linked list. When I try to start the SPI DMA transmit with function HAL_SPI_Transmit_DMA, then I get an error in the following section of the function’s code/* Packing mode management is enabled by the DMA settings */ if (((hspi->Init.DataSize > SPI_DATASIZE_16BIT) && (hspi->hdmatx->Init.SrcDataWidth != DMA_SRC_DATAWIDTH_WORD) && \ (IS_SPI_FULL_INSTANCE(hspi->Instance))) || \ ((hspi->Init.DataSize > SPI_DATASIZE_8BIT) && (hspi->hdmatx->Init.SrcDataWidth == DMA_SRC_DATAWIDTH_BYTE))) { /* Restriction the DMA data received is not allowed in this mode */ __HAL_UNLOCK(hspi); return HAL_ERROR; } However the transmission works fine if the GPDMA was in standard, non circular and n

Hello All,We have made a custom board design with STM32WB55CGU6.But we are struggling to detect the device with STM32CubeProgrammer. I am using P-NUCLEO-WB55's ST-LINK connection to detect and flash the M0 Firmware with STM32CubeProgrammer.SWDIO, SWCLK, RESET, GROUND and Power connections are fine.Could some experts suggest how to go ahead?Thanks and regards,Paul

The examples/code snippets found in the ST Edge AI Core Technology Documentation (ST Edge AI Core Technology 2.2.0) show a variety of functions/macros used that don't seem to get generated via STM32CubeMX on my end.For reference, I generated the code for CMake, with version 10.2.0 of X-Cube-AI and 6.13.0 of STM32CubeMX.A couple examples from the legacy client -> new edge ai embedded client migration guide:#include "network_inputs.h" - No such file <model_name>_inputs.h seems to get generated via CubeMX.STAI_NETWORK_CONTEXT_DECLARE - this macro is undeclared in the generated code.stai_network_init() - I get an implicit declaration of function warning for this one (cannot find this declared/defined anywhere in the generated code).STAI_NETWORK_ACTIVATIONS_NUM - also undeclared in generated code. Is this specific to the code generated for CMake? Are there perhaps other header files I should be looking to include aside form the ones noted in the examples? EDIT: Confirmed

Hello STM32 Community,I am working on an STM32 project using NanoEdge AI Studio, where I’ve trained models on sensor data and deployed them to my STWINBX1 for anomaly detection. The model is successfully integrated, and now I need to send real-time notifications wirelessly whenever an anomaly is detected.Requirements:Bluetooth (Preferred): I would like to transmit "normal" or "abnormal" status using Bluetooth Low Energy (BLE) and receive real-time notifications on the Android ST BLE Sensor app. How can I achieve this? Are there any examples or libraries available for BLE communication on STWINBX1?Wi-Fi Alternative: If BLE is not the best approach, how can I send this anomaly detection data over Wi-Fi? Are there example implementations for sending real-time alerts via MQTT, HTTP, or another protocol?Since STWINBX1 includes BlueNRG-M2 (BLE 5.0) and EMW3080 (Wi-Fi), I believe there should be an efficient way to integrate wireless communication with my anomaly detection system. Could someo

Hey,Looking at the image classification application example, I couldn't find any part of the code that handles the normalization of pixel value from [0,255] to [-1,1] or [0,1] that I would expect from a CV model of that kind. Do you mind explaining how this implementation that is based on the mobilenet_v2_0 skips the need for normalization?Thanks. 

Hi,I’m working on a project with an STM32G491 board and need to document our firmware-upgrade process.Current setup:Initial flashing is done with ST-Link/CubeProgrammer.Later updates come from an embedded Linux device that runs a custom binary to flash the MCU over UART/I²C.We already have a basic document that covers the application side, but we’d like to add a brief section explaining the MCU-side flashing flow.Does anyone have a flowchart or reference diagram showing the STM32 flashing process—either using CubeProgrammer (ST-Link) or via UART/I²C bootloader—that we could include or adapt?Thanks! 

I have a custom board with a 1024x600 display. It works fine.Some demo examples only work in lower resolution. I want to get those to work on my display.I was able to trick TouchGFX Designer to think lower resolutions are supported by changing AvailableResolutions in ApplicationTemplate.touchgfx.part. This sort of works, but you see some objects out of the window. It's wasted rendering time too.By changing pLayerCfg.ImageHeight of the LTDC I was able to get lower vertical resolution work. For instance 1024x300. This way the bottom half is black. Which is good.However, when I change pLayerCfg.ImageWidth to 800 I get garbage. I I set it to 1022 the image is skewed. I also played with pLayerCfg.WindowX0 and pLayerCfg.WindowX1, but it doesn't seem to do anything. #include "ltdc.h" /* USER CODE BEGIN 0 */ #include <gui_generated/common/SimConstants.hpp> /* USER CODE END 0 */ LTDC_HandleTypeDef hltdc; /* LTDC init function */ void MX_LTDC_Init(void) { /* USER CODE BEGIN LTDC_

I have a question about configuring pin D1 for UART1 TX (in conjunction with pin E2, UART1 RX).Pin D1 has the option for PA11, [PA9], PA8Pin E2 has the option for PA12, [PA10], PA71. To use pin D1 for UART1 TX, PA11 must be switched to PA9 (SYSCFG_CFGR1: PA11_RMP: = 1).2. To use pin E2 as PA12, E2 (PA7 default) must be switched to PA12 (SYSCFG_CFGR3: PINMUX4[1:0] = 1).3. To use pin E2 for UART1 RX, PA12 must be switched to PA10 (SYSCFG_CFGR1: PA12_RMP: = 1). Question:What is the default setting for pin D1 (PA11 or PA8)? How is PA11 bound to pin D1? I am missing a setting like (2.) for pin D1. I could not find anything in the manual.When I configure this setting with STM32CubeMX, the following code is generated:HAL_SYSCFG_EnableRemap(SYSCFG_REMAP_PA11); // (1.) HAL_SYSCFG_EnableRemap(SYSCFG_REMAP_PA12); // (3.) HAL_SYSCFG_SetPinBinding(HAL_BIND_WLCSP12_PINE2_PA12); // (2.)Where is the binding for pin D1? Many thanks in advance.Dirk    

Hello,I’m working on a custom board with STM32WB15CC, dual-core mode with BLE stack.I noticed an issue related to PESD (Program/Erase Suspend) when CPU2 enters STOP mode.In my application, I call Adv_Cancel(); and this makes CPU2 enter STOP autonomously.Then I call UTIL_LPM_EnterLowPower(); and CPU1 also goes to STOP correctly.My application uses reduced wake cycles, and sometimes I do not restart advertising after wake-up (so CPU2 stays stopped).Sporadically, in these reduced cycles, I see PESD=1 even though I am not accessing flash on CPU1.This causes CPU1 to block in while(LL_FLASH_IsActiveFlag_OperationSuspended()); inside ProcessSingleFlashOperation() in flash_driver.c (the official ST file for dual-core flash management with PESD).The situation looks like CPU2 goes to STOP with flash still occupied (PESD set).At that point, any flash write from CPU1 remains blocked forever.At the moment, my only workaround is:Before writing to flash, I check PESD, andIf PESD=1, I make BLE di

I understand that the STMCube environment doesn't function as a BSDL (Boundary Test) tool. Can anyone suggest a free tool that is compatible with the ST-LINK-V3SET?Keysight, Corsair, XJTAG are out of my rangeMy application is gather tools for board bring-up for our STM32MP255F prototype PCB.Thank you. 

Hi all,I am a newer STM32 programmer, and I have been working on the STM32H745 Discovery board for the last few months. Something that I would like to do is be able to switch into USB DFU Mode within a UI that I have made for this board. I took inspiration from this post and changed the address to the appropriate one for the STM32H745. I would like to prerequisite that the USB port is initially configured as a VCP/CDC device. Here is the code that I have:void (*SysMemBootJump) (void); void USB_BootloaderInit() { volatile uint32_t addr = 0x1FFF9800; //from AN2606 __disable_irq(); // Reset USB OTG_FS // Disable caches SCB_DisableICache(); SCB_DisableDCache(); // Remap vector table HAL_RCC_DeInit(); //Reset the system clock SysTick->CTRL = 0; //Reset the SysTick Timer SysTick->LOAD = 0; SysTick->VAL = 0; SysMemBootJump = (void (*)(void)) (*((uint32_t *)(addr + 4))); //Point the PC to the System Memory reset vector __set_MSP(*(uint32_t *)addr); //Set the M

I’m working with the NUCLEO-WL33CC2 development board and running ST’s CLI demonstration firmware. My goal is to retrieve raw baseband I/Q samples, but I can’t get any I/Q output using the demonstrator commands, specifically IQDump.  If you’ve successfully extracted I/Q from this board using the stock CLI demo, I’d love to know the exact command sequence and any quirks you ran into. Suggestions welcome on required modes, baud rates, or additional steps I might be missing.

Hi everyone,I'm currently working with the ST25DV04K NFC tag connected to a Nucleo board, and I need to read and write text data to the tag for application development. I'm looking for:Example code to perform text read/write operations.A middleware library that supports text data access from memory blocks.Compatibility with STM32 MCUs for future integration.I've explored the examples provided in X-CUBE-NFC4, but most of them focus on writing url using NDEF_URL. Unfortunately, I couldn't find any examples or libraries that support reading/writing plain text to the tag. Also, the read NDEF_URL example throws error.My goal is to read data from this NFC tag connected to the Nucleo board or STM32mcu via I2C  .The data can be written by an NFC tap Application, which works fine with the ST25DV04K IC. Any guidance, sample code, or library recommendations would be greatly appreciated.Thanks in advance!

Hi everyone,I’m working on an STM32 firmware project (HAL + CubeIDE). I’m trying to output debug messages to Tera Term via UART using printf and puts.Here’s the situation:Debug build: Both printf and puts work perfectly.Release build: Calling printf or puts causes the MCU to reset immediately. Maybe due to watchdog reset and these function call cause the MCU freezing.I also retarget the printf function by implemented the following: int __io_putchar(int ch) { while (!(huart1.Instance->ISR & USART_ISR_TXE)); huart1.Instance->TDR = (uint16_t)ch; return ch; } int _write(int file, char *ptr, int len) { for (int i = 0; i < len; i++) { __io_putchar(ptr[i]); } return len; }My questions:Why do printf and puts crash/reset in Release but work in Debug?Are there known issues with _write or __io_putchar in Release builds?Any recommended approach to safely use printf/puts in Release firmware for UART output?Thanks in advance! 

STM32CUBEMX is using very old version of FreeRTOS 10.3.1 for stm32 series microcontroller? Please can you update FreeRTOS version to latest version of FreeRTOS?  Do you shifting your focus from using FreeRTOS to some other OS for stm32?

Hello,I am trying to establish UART communication between STM32G070RBTX and ESP32 Devkit using AT commands.Connections: STM32 UART TX ESP32 RX, STM32 UART RX ESP32 TX, and common GNDPower ESP32 powered from 5V pin by usb or base boardBaud rate 115200On reset, ESP32 does not print ok or any AT response.Very rarely once in many tries I get a single AT command response,but after that no communication happens.Even pressing the reset button does not bring it back. When I connect the ESP32 module via USB  to Dockight and send AT commands, the communication works fine.

Hi Sir,We managed to use HS USB port as FS USB on our PCB(there is no external PHY), but our partner  comments that there is no driver available for that purpose. Indeed I only see USB examples for HS USB or FS USB at STM32H7 source tar ball. I believe that there must be such usage. Where can I get the example ? Thanks. Sincerely,Jimmy 

Hi there,I am using STM32G473CBT6, and work with a bootloader and application.When I set the application address at 0x08008000, everything works well.However, when I change the application address to 0x0800A000, the application download fails, except when I download the bootloader (configuring it as 'erase all chip') first.I checked the reference manual, and the flash is separated into 2K/4K on each page.That means both 0x08008000 and 0x0800A000 addresses are at the page edge.Why can't the application at 0x0800A000 work smoothly?Thanks for your help! 

HELLO ,In STM32F103C8T6, the RTC time is preserved after power off, but the date always resets to 01/01/2000 even if I set the current date and time.