Solved

STM32C071GBU6 PA2 (pin 8 on the UFQFPN28 device) is configured as ADC_IN2.  What voltage can be expected when the pin is unloaded?

Title edited to be clear that this is on a NUCLEO-F303ZE board.Hello all.I'm trying to write a simple message via UART to Putty using stm32f303ze microcontroller. I'm using USART2, via ST-link. All the configurations have been confirmed (baud rate, COM port, bits, etc.) And they are right. I even tried using the STM32 Cube IDE Terminal with no luck. Now I'm not sure if the problem is the UART I'm using, or I'm doing something wrong in the code.Also I'm not sure about the UART that support VCP in STM32F303ZE microcontrollers. However I tried all the USART, and the were no response in the Terminals. Below is the simple message I'm trying to send and the full code./* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights re

HIUsing stm32f303veh6.Changed the option bytes with the CubeProgrammer. 2.20.0 to override the BOOT0 signal. ( its floating )nBOOT1 - > uncheckedBOOT_SEL -> unchecked I see that the address on start is 0x1FFFF.. and my FW on flash does not run. For debug, I I did some external wiring of the BOOT0 signal to GND, and now my FW boots fine.Looked in Errata for know issues, but could not find any related. Any reason for Option Bytes not to work?   

I have been attempting to interface a STM32U575 mcu to a dual HYPERRAM/Flash memory set up in multiplexed mode as shown in the following image taken from the STM32 Octo-SPI AN5050 application note. I am trying to implement a POSIX based RTOS and have thus been trying to create this setup in my project devicetree as follows: &octospi2 { pinctrl-0 = <&octospi_pins>; pinctrl-names = "default"; status="okay"; flash: ospi-nor-flash@0 { compatible = "st,stm32-ospi-nor"; reg = <0>; size = <DT_SIZE_M(512)>; ospi-max-frequency = <DT_FREQ_M(50)>; spi-bus-width = <OSPI_OPI_MODE>; data-rate = <OSPI_STR_TRANSFER>; status = "okay"; }; hram: ospi-nor-flash@1 { compatible = "st,stm32-ospi-nor"; reg = <1>; size = <DT_SIZE_M(512)>; ospi-max-frequency = <DT_FREQ_M(50)>; spi-bus-width = <OSPI_OPI_MODE>; data-rate = <OSPI_DTR_TRANSFER>; status = "okay"; }; }; and I have also tried: &octospi2

Hello,Regarding the STM32N657, I'm not using the internal SMPS.  My question is:  Do we need to put capacitors on the 6 VDDSMPS pins or can they be left as no connect?   Same question on the VLXSMPS pins... do we need the capacitors on these pins, or can they be left as no connect?Also, on the STM32N657-DK board, there is a snubber circuit on the VLXSMPS pins, why?Finally, when I say "No connect", I assume these pins are connected internally, so it does not require an external link on the PCB when not used.  Is this correct?  (this will probably make the routing of the PCB easier)We are dealing with a very Very VERY small PCB, and saving the space used by 12 x 0402 makes a difference.thanks

Hello Everyone,I am facing an issue with my MCU entering low-power mode.My idea is to freeze the Independent Watchdog (IWDG) counter in STOP mode so that the MCU will not reset due to the IWDG counter elapsing.From my understanding, this can be achieved by clearing bit 17 (IWDG_STOP) of the FLASH_OPTR register, if I am right. As per the reference manual, in STOP mode, the IWDG can be automatically frozen depending on the configuration of the IWDG_STOP bit in the FLASH_OPTR register.So, the IWDG should not reset the MCU during STOP (sleep) mode, correct?If both assumptions are correct, could you please share the steps or example code to:Configure the IWDG to operate (or be frozen) in STOP mode, andSet up the FLASH_OPTR register appropriately for this behaviour?

Hi,When configuring a DMA channel in Circular mode with the LL code generator for STM32H523, the generated initialization code is incorrect.It creates a DMA Link Node (LL_DMA_LinkNodeTypeDef) on the stack, which is invalid since the DMA continuously accesses this structure. The link node should be placed in persistent memory instead.Additionally, the generated code does not set the source address, destination address, or block length when the link node is created, although these can be manually set later.Regards,Peter

Hello,I'm using the STM32N657 processor and have the HEXASPI device running at 1.8V.  VDDIO2 is connected to 1V8 supply (which affects: PO[5..0] and PP[15..0]The FMC is placing the A23 line on pin PO1 (this is the only option for the FMC-A23) and the FMC device is running at 3.3V.   Can I place a pullup to 3.3V on PO1, or will this affect/blow  the GPIO connected to 1.8V -OR- do I need to place a voltage translator on that pin?  

Hello,I want to use the buffer program feature of my IS29GL064 NOR flash in order to increase the programming speed.For this I replaced HAL_NOR_Program() by HAL_NOR_ProgramBuffer() in the NOR flash demo and got a memfault. Did some debugging and doubt the code, especially because I found this post hereBUGS: HAL_NOR_ProgramBuffer() is riddled with them Has the reported bug, if any, been already fixed ?Second, I wonder if my ISSI flash is supported because of the following comment in stm32h7xx_hal_nor.cThis function must be used only with S29GL128P NOR memory.IMHO all devices which support the necessary commands, e.g. NOR_CMD_DATA_BUFFER_AND_PROG,  should be able to use this feature and HAL function.Any hints, news, updates or comments?Thank you

Hi, I am using three STM32 devices for CAN communication:HardwareDevice A: STM32G431 (FDCAN)Device B: STM32F303 (Classic CAN)Device C: STM32H7A3 (FDCAN)SetupA sends a continuous sequence of commands to B.B processes each command and replies to A over the same CAN bus.One specific command requires B to perform a synchronization sequence with C (also over CAN).While B is synchronizing with C, A continues to send commands to B.IssueDuring the B↔C synchronization, B intermittently misses some frames from A (i.e., A transmits, but B does not process/see a corresponding message).The failure is not immediate: A↔B + B↔C run together fine for a while (sometimes short, sometimes long), then a frame from A is skipped.When the synchronization with C is disabled, A↔B runs reliably with no missed frames.CAN ID from A to B: 0x12CCAN ID from B to A: 0x12DCAN IDs between B and C (sync purposes): 0x2BC, 0x2BD and 0x2BEAs you can see from the inserted can config the sampling point for 3 devices is a

why do I get these:Project setup failed with following error: No service available

Hi,I am trying to understand some features of STHV200 Dual channel ±100 V, high voltage 3 A linear amplifier and 2 A pulser transmitter.I could not find a detailed datasheet of the product. Only data brief. I want to use it to amplify the received low voltage signal. The data brief mentions an internal amplifier but I could not understand how it works. Am I able to amplify the received signal coming from the T/R switch? Or is the internal OP-AMP configurable for example as a differential amplifier?  

This is a custom-made PCB antenna board utilising the ST25R3911B chip, but I am unsure how to proceed with impedance matching debugging and parameter configuration. Could you offer some guidance? Below are the antenna dimensions, the calculated impedance matching values, and the original impedance matching diagram. Communication is currently possible at very close range. To increase communication distance and stability, what modifications should be made?   *This post has been translated from Chinese to comply with the ST Community guidelines.  

  Currently, we are developing a card reader featuring a circular NFC antenna. However, due to the lack of equipment for measuring antenna parameters, we are reliant solely on calculated theoretical values. The circuit board and antenna are depicted in Figure 1, impedance matching is shown in Figure 2, and simulation diagrams are presented in Figures 3 and 4. Is there any means to optimise the antenna design or draw the antenna? Alternatively, are any circular antennas readily available? The circular antenna requires a minimum diameter of 42mm and a maximum diameter of 50mm.   *This post has been translated from Chinese to comply with the ST Community guidelines.

Heyho,strange things happening that I'd like to understand for a STM32L073 (Nucleo for now).Setup on a L073 @ 32MHz:- ADC is clocked by PCLK/4- ADC prescaler = 2 -> divide by 4 -> 2 MHz- 12 bit right aligned- ref V = VDDA = 3.3V- hardware oversampling + shift is used (great feature!)- 7 ADC channels sequenced- DMA, with buffer for 8 samples per channel -> u16AdcDmaBuf[56] In non-circular mode (CIRC neither set in DMA- nor in AD-registers), after each DMA's transfer complete interrupt, DMA and ADC are restarted, everything is as it should be, and as it is set in the sequencing registers.Here's what the DMA buffer looks like, and all this makes sense:buffer[0] = 2031 is the DAC output set to 2047,buffer[1] & buffer[2] = 4095 are connected to VDDA -> 4095 ok,buffer[5] is internal VREF = 1.2V -> perfect,buffer[6] is internal temperature sensor -> ~24°C -> perfect1) ADC & DMA: not circular DmaBuf [00] 2031 4095 4095 1926 3083 1524 0604 [07] 2031 4095 4095

I am using STM32CubeIDE as my development environment,and the board is STM32F429I-Discovery (MCU: STM32F429ZITx). I created an LCD display program using the BSP drivers (such as stm32f429i_discovery_lcd.c).The project builds successfully and flashes without any errors. However, after powering on the board, the LCD remains completely white and nothing is displayed. I downloaded the official firmware package from ST’s website:https://www.st.com/en/embedded-software/stm32cubef4.htmland imported the necessary BSP files from stm32cubef4-v1-28-0.zip into my CubeIDE project. Current situation: The folders Drivers/BSP/STM32F429I-Discovery and Utilities/Fonts are properly included in the project The build and flashing process complete successfully The LCD backlight turns on, but the screen stays white all the time I used the example project LTDC_Display_2Layers as a reference I would like to know what kind of initialization or configuration might be missing,or what are the common ca

Hello,How can I attach to running microcontroller in the STM32CubeIDE?The IAR has the Attach to running target function. The STM32CubeIDE have not this function.

I am working with STM32H747I -DISCO board I am using CubeMx version 6.15, firmware: H7_V1.12.2, Freertos CMSIS2 - V10.3.1configuration 1 : Generating from touchgfx and configuring Eth other all parameters commented in code (Touchgfx parameters).Here ETH is working fine configuration 2 : only configuring ETH with same configurating as above but generating from cubemx Here Eth Communication worked for abt 10 to 20 min and then MCU stucked.I compared both projects : it's all same (MPU configuration Linker script DMA Descriptor and RAM Heap pointer) ...middleware package, CMSIS files, Freertos config files, Lwip folder(lwip.c .h and ethernetif.c and lwipopt.h),LAN files all are same but still I am facing this issue. I have attached wireshark snip when MCU got stucked and IOC files 1. Touchgfx generated 2. CubeMx Generated  @STea @STackPointer64 

Hello, I am using the x-nucleo-67W61M1 and the supported STM32N6 nucleo and I run the HTTPS Server application. The sample works well. I want to transfer loads of data and I do it through cJSON. I understand that i need to set a different get command and add an if statement in the HTTP_process_response that will handle the request and it will respond accordingly. I have set also a script in Matlab that does continuous gets and after a while i see that the STM is stuck and is no longer responding (I have the LEDs toggling in a different RTOS task) the log when that happens is:[ERROR] [114031] [HTTP_00000001] (w61_at_net.c:441) W61_AT_SetExecute: W61_STATUS_TIMEOUT. It can lead to unexpected behavior. [ERROR] [114031] [HTTP_00000001] (httpserver.c:524) [1] *****> SEND ERROR <***** [ERROR] [116031] [HTTP_00000001] (w61_at_net.c:351) W61_AT_SetExecute: W61_STATUS_TIMEOUT. It can lead to unexpected behavior. [ERROR] [118033] [defaultTask] (w61_at_net.c:1130) W61_Net_GetSocketInfo

Hello! I am working on a custom OTA bootloader system on a STM32G473RBT6 MCU in a custom board I have been using maybe for 3 years with no problem. My board is connected to a Raspberry Pi over RS485 network. My idea is this:There are 3 virtual sections: 24 KB OTA Bootloader starting from 0x0800 0000. 52 KB Storage space starting from 0x0800 6000 and 52 KB Application space starting from 0x0801 3000. In total 128 KB as the STM32G473RB MCU has.The custom bootloader reads incoming data, erases storage space and stores this new data in storage space, check CRC32, etc. Then the bootloader erases previous application in application space, and copies storage space to application space and starts from new application address.The problem is that the bootloader only succeeds if the following condition met (basically full flash erase):I have a fully erased chip and only bootloader loaded. If I want to load a simple LED blink application which FLASH.lb file configured as following:MEMORY{RAM (xrw)

Hello, I’m trying to perform ADC measurements with the STM32H563ZIT. I’ve shared my configuration settings from the .ioc file below. The ADC reading fluctuates by about ±40. When I short the ADC pin to GND, the reading varies between 0 and 30 instead of staying stable. I can’t get a constant value. What could be causing this issue?static void MX_ADC1_Init(void) { /* USER CODE BEGIN ADC1_Init 0 */ /* USER CODE END ADC1_Init 0 */ ADC_ChannelConfTypeDef sConfig = {0}; /* USER CODE BEGIN ADC1_Init 1 */ /* USER CODE END ADC1_Init 1 */ /** Common config */ hadc1.Instance = ADC1; hadc1.Init.ClockPrescaler = ADC_CLOCK_ASYNC_DIV10; hadc1.Init.Resolution = ADC_RESOLUTION_12B; hadc1.Init.DataAlign = ADC_DATAALIGN_RIGHT; hadc1.Init.ScanConvMode = ADC_SCAN_DISABLE; hadc1.Init.EOCSelection = ADC_EOC_SINGLE_CONV; hadc1.Init.LowPowerAutoWait = ENABLE; hadc1.Init.ContinuousConvMode = DISABLE; hadc1.Init.NbrOfConversion = 1; hadc1.Init.DiscontinuousConvMode = DISABLE; hadc1.Init.

Hello,as a first time user of STm32CubeIDE, I wanted to toggle a few IOs with a serial output.I used the JTAG port to connect to the STM32 and program it BUT after the first programing, I can't connect to it anymore.....Here is the pinout that I used:Afterwards, I discovered that I should have activated the JTAG debug.... but it is too late.....What can I do to access/program the STM32 again?This might be a simple question but I would appreciate the help.Thank you

In the default configuration, the SMPS on the development board is disabled.  As such the VDDA18PMU appears to be floating.  According to the spec sheet, it says that the pin MUST be tied to Vss when the SMPS in not used.  Is there an internal pull down?

Post edited by ST moderator to be inline with the community rules for the code sharing. In next time please use </> button to paste your code. Please read this post: How to insert source code. Hello there, I have a simple one, I have run the exmaple project on camera dcmipp continous mode and snapshot mode for the stm32n6570 development kit, how, the image feed on the screen is blurred on the first run with out any edits, I have tried to play with the downsizing that is configured in the project in vain, hoping to get a clearer image.these are the default settings that I that come with the example  DonwsizeConf.HRatio = 25656; DonwsizeConf.VRatio = 33161; DonwsizeConf.HSize = 800; DonwsizeConf.VSize = 480; DonwsizeConf.HDivFactor = 316; DonwsizeConf.VDivFactor = 253; if(HAL_DCMIPP_PIPE_SetDownsizeConfig(&hdcmipp, DCMIPP_PIPE1, &DonwsizeConf) != HAL_OK) { Error_Handler(); } if(HAL_DCMIPP_PIPE_EnableDownsize(&hdcmipp, DCMIPP_PIPE1) != HA

I’m working with an STM32G0 running ThreadX (Azure RTOS).The system UART is configured in circular DMA mode with an IDLE event interrupt for data reception.SymptomsIntermittently, after hundreds of successful receptions, the system enters HardFault_Handler.The fault always occurs at the same point in the code (on a C division instruction, inside a function unrelated to DMA).The register values at the HardFault are shown in Image 1.When it runs without triggering a hard fault, the registers are:xPSR = 0x01000000 and CONTROL = 2.When the hard fault occurs, these registers are:xPSR = 0x00000000 and CONTROL = 0.The failure does not depend on the received data.The thread stack (PSP) has sufficient space.I believe the intermittent HardFault is not related to the operation itself:If I modify the code—adding new instructions or removing code—sometimes it reproduces, and other times it still reproduces but in different parts of the code.QuestionWhat can I do to determine the root cause of this