STM32 MCUs Products

In the RM0456 at 33.4.31 Oversampler it say:The division coefficient M consists of a right bit shift up to 10 bits, and is defined using the OVSS[3:0] bits in the ADC_CFGR2 register.But at 33.6.5 ADC configuration register 2 (ADC_CFGR2), it allow up to 11 bits:Bits 8:5 OVSS[3:0]: Oversampling right shift1011: 11-bit right shift

IssueHigher ambient temperatures cause communication malfunctions with XSPI memories.DetailsOur design is heavily adopted from STM32H7S78-DK which also has the same issue described below.The application uses memory-mapped mode for both Flash and RAM as the main operational units. These memories are configured in the bootloader and everything generated using CubeMX. According to the datasheets, all three components (CPU, Flash, and RAM) are specified to operate reliably under the given conditions, and they do function correctly under normal temperatures.The problem arises when the ambient temperature increases from 25°C to 60°C. These temperatures are within the acceptable operating range for all components, as stated in their specifications. Upon reaching higher temperatures, the memories start to exhibit failures. However, further investigation revealed that the issue is not with the memories themselves. When the mem

Can somebody please help me.   The code below is initializing the RTC.   The clock works I can set and read time and date no problem.   Somehow if I change these register:   hrtc.Init.AsynchPrediv = 131; hrtc.Init.SynchPrediv = 10;   It has no impact on the clock accuracy I keep on gaining time.   I would have thought by "tweaking" the values it will either speed up or slow down the RTC.    Code was generated by using the STM32 cube IDE.     /** Initialize RTC */ hrtc.Instance = RTC; hrtc.Init.HourFormat = RTC_HOURFORMAT_24; hrtc

We're using the following circuit to measure a battery voltage @ 20 kHz for use in motor control.We are having some issues though, where the ADC suddenly starts measuring 0 V (0 in the data register) and gets locked in this state. In this state, we also measured 0 V at the MCU pin on the board, and a resistance < 20 Ohm between the pin and GND, both using a multimeter. The issue is not fixed by a reset (pulse on the NRST pin), only removing the battery and power cycling the MCU.How and why can/does this happen?We initially thought it was overvoltage and tried connecting a PSU directly to an ADC pin on the STM32G474RE NUCLEO board. We only started seei

In our project I use STM32H573VIT6 LDO uC. We have a problem with the PB14 pin. We use 3 pins for LED control (PB10, PB13 and PB14, see photo). The problem with the PB14 is that the LED lights up dimly without code initialization. If PB14 is initialized as Output, Open Drain, No Pullup-Pulldown, it lights up dimly in the OFF state and normally in the ON state. With Output Push-Pull initialization it works normally, i.e. in the OFF state the LED does not light up and in the ON state it lights up normally.  1. What could be the problem? 2. Should I use PB14 at all and is there a potential risk of later problems?

Hi,I'm attempting to write to an SD Card using a Riverdi STM32U5A9 display board.  Since TouchGFX natively uses FreeRTOS, I'm attempting to keep it within FreeRTOS.  Porting to ThreadX has caused it's own issues which I have in a separate thread.  In the Configurator, there is no longer an option for FATFS, so I'm using the STM32U5 Classic MW Git Repository as recommended by the FAE.  I copy over and update the templates as required, but am still getting a Hard Fault during f_mkfs while the HAL library is initializing the SDMMC.  I believe that my configuration is incorrect, but th

Hi, I am trying to configure my STM32G071GBU6 to enable reprogramming  the flash throguh USART1. I check the datasheet of STM32G071x8/xB, reference manual RM0444, and application note AN2026. It says I am supposed to configure the PA9 (USART1_Tx) and PA10 (USART1_Rx) pins. The problem is when I configure the USART1 as asynchronous mode in STM32CubeMX, the software automatically set PB6 and PB7 pins as USART1_Tx and USART1_Rx. There are no available options like USART1_Tx and USART1_Rx for PA9 and PA10.I am wondering why the manual is inconsistent to the STM32CubeMX and how should I configure the MCU to correctly reprogram through USART1?

Hello everyone, Some time ago I asked on this website information about jitter on a PWM : Solved: PWM jitter - STMicroelectronics CommunityThe problem was that when generating a PWM, it wasn't very stable. At the time changing the source clock to the external clock of the nucleoboard worked and stabilized everything.Since then, I created my own board using an STM32G474QE (128 pins) with an 8MHz (+/-50ppm) external oscillator.I tried to generate the PWM and I am encountering the same exact problem again, the jitter is back. This time, I directly setup the clock as the external one. I checked it up and it feels to me that the problem could be coming from the stability of my oscillator (I have frequency variation on it's output ranging from 7,999,950 to 8,000,050Hz). Now my question is, could this really be the problem

Hello everyone i had today while working with the NUCLEO H753ZI board and when i try to upload the code i had faced this error message when i try to connect with the cube programmer i faced this error and my LD6 pin is glowing with low intensity can you please tell me why i facing this issue whethere this could be any short problem or anything else 

I have two boards, both with the G473.I am using the ROM bootloader on SPI1. On one board, the bootloader works.  On the other, it only responds with 0xA5 during the initialization sequence.The MCU can program and run if I load it through the SWD port.I have checked the SPI signals, both digital and analog, they look great.  The MCU pins are firmly soldered to the board.  The other board works.  My code works.  If you can actually get the bootloader to synchronize, it works.I have gone through every forum post I can find, and it is sounding like there is a possible consensus that the ST bootloader is bugged and will sometimes initialize the wrong interface.  Is that... really true?  It selects the wrong interface and all of these people are having problems with it?  Can any one from ST talk about this?  This sounds like a really serious problem if true!  What else could it be?AN26

Hello, I am facing an issue with my code on my STM32F411I have a function that is starting a timer TIM5 I want to be able to handle channel 1, Channel 2, Channel 3 interrupt on output compare no output uint32_t ticks = ms * 10U; /* 10 kHz tick -> 10 ticks per ms */ if (ticks == 0) ticks = 1; TIM5->CR1 = 0; TIM5->CR2 = 0; TIM5->DIER = 0; TIM5->CCER = 0; TIM5->CCMR2 = 0; // Channel 3 and 4 CCMR register // Set prescaler and auto-reload as needed TIM5->PSC = 96; // No prescaler TIM5->ARR = 0xFFFF; // Auto-reload max for full range TIM5->CCMR2 &= ~TIM_CCMR2_CC3S; // CC3S=00 output TIM5->CCMR2 &= ~TIM_CCMR2_OC3M; // Clear OC3M bits TIM5->CCMR2 |= (0x3 << TIM_CCMR2_OC3M_Pos); // OC3M=011 toggle mode // Enable Capture/Compare Channel 3 output (optional for toggling output pins) TIM5->CCER |= TIM_CCER_CC3E; // Enable interrupt on Capture/Compare 3 event T

Hello ST Community,I am working on an STM32U585AII6Q microcontroller with TrustZone enabled. My goal is to revert the RDP level from 2 (0xCC) back to 0 (0xAA) using STM32CubeProgrammer GUI.#### Steps I Followed:1. Defined OEM2KEY in the "Secure Programming" menu.2. Set RDP to Level 2 successfully.3. Tried to unlock RDP2 using the "Unlock RDP2" option in STM32CubeProgrammer.- Log shows: "Unlock RDP2 password successfully done."4. Gave power cycle and attempted to change RDP value from 0xCC to 0xAA in the "Read Out Protection" menu.#### Issue:- When I try to apply the change, I get the error:**DEVICE NOT HALTED**- The debugger cannot connect to the MCU after this step.#### Hardware Setup:- BOOT0 pin connected to VDD for RSS boot.- Using STM32CubeProgrammer v2.19.0.#### Questions:1. What is the correct sequence to regress from RDP Level 2 to Level 0 when TrustZone is active?2. How

Update: I found out that HAL_PWR_EnableWakeUpLine() must be enabled to wake up the system.The system now wakes up correctly from Stop3 mode. With the SMPS enabled and all pins configured as analog, the current draw is approximately 5 µA, which matches the values given in the datasheet./**********************************************************************************************************************************/ Hello everyone,I am working with NUCLEO-U385RG-Q board and using the RTC wake-up timer as the wake source for low-power modes. I noticed consistent differences between STOP2 and STOP3:IssueThe RTC wake-up interrupt works reliably in STOP2.The exact same configuration does not wake the system from STOP3.

I am trying to measure DC output of an RF detector (AD8363) using STM32H723's ADC. The Signal that is to be measured has about 80 mV - 90 mV of high frequency noise embedded on it. Due to inaccuracies in the measurement I am probing the measurement circuitry and therefore would like to know:The 5 pF capacitance of ADC is total capacitance of the 12 or 16 capacitors inside ADC or just that of one capacitor?What is the resistance of the ADC's sample and hold switch?Is there any model of ADC Circuitry, that includes parasitic as well?What is the tracking bandwidth of the ADC?

Hi -I am trying to bring up a new design - a 3 phase forward converter, using the HRTIM to fire six gate drives.  Under normal design loads it works great, but for normal loading I have the CONT bits set for master and subs.   For light loading, I need to keep a minimum on-time, so must drop the frequency. I could reduce the resolution by using a smaller PLL multiplier (presently using x8 with a 150 MHz sysclock for a 1.2 GHz HRTIM), but that is unsatisfactory.  I tried setting different PLL multipliers for the master and the three sub timers, but found that different PLL settings precludes cross-channel event messaging, so I could not phase the three sub clocks with the master anymore.   I suspect I could use the burst mode, but have not researched that yet.The technique I am trying now is linking to TIM1 to start the master for one cycle in one-shot mode.  This gives me a proper fixed on-time burst for all six phases, bu

Hi -    I have an application running a 1 kW 500VDC to 25V DC supply for a klystron filament heater.  I am using a 3 phase forward converter - each phase driven by a FET half bridge to a transformer primary returning to input mid-point.    I drive the six gate drives using six HRTIM pins.I have programmed this so that each of the gate drive pulses is turned on at a fixed time in the master cycle, and turned off by one of two things:   either a timer counter (thus setting duty cycle %) or an event connected to an internal comparator.  The comparators use an internal DAC for the -IN reference, and are pinned out to a rectified current transformer on the primary.   This then gives me both duty cycle and peak current control for continually adjusting providing regulation.What I would like is a continual running diagnostic where I can read the status from the HRTIM and determine what caused the most recent commutat

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. Hi, I am using stm32c071 MCU to store data into flash. I have erased page 63 wrote data into 0x0801F800 then locked the flash and then again unlocked it erased page 63 wrote data in 0x0801F820, but the contents of 0x0801F800 is still there even after page erase. Is this expected? My flash write code eFLASH_ErrorType_t WriteDataToFlash(uint64_t *data, uint32_t address, uint8_t page, uint8_t length) { eFLASH_ErrorType_t err_code = e_SUCCESS; uint32_t *addr = (uint32_t*)address; // Check if flash is busy err_code = CheckFlashBusy();

Hello,I am experiencing an interesting problem on the STM32F303VET:UART1 is used to receive and transmit messages (460800 Baud), DMA1 Channel 4 is used for memory to UART TX buffer transfer, DMA1 Channel 5 for UART RX buffer to memory transfer.Under situations of high load (both reception and transmission) UART1 will stop outputting messages after two bytes. The majority of transmissions work out fine, however the error happens in every test case, though the time to failure differes between approximately 5s and 120s. The problem seems to be caused by an unintended reset of the DMA enable transmitter (DMAT) Bit in UART 1 control register 3 (USART_CR3).

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 everyone, I have designed a custom PCB using the STM32L031K6 microcontroller. The board includes an external 32.768 kHz crystal oscillator (LSE - Low Speed External). The Problem: I am flashing code to the board using an ST-Link. When running a simple LED blinking application (which uses HAL_Delay), the LED either blinks only once or gets stuck indefinitely within the HAL_Delay function. This strongly suggests an issue with the microcontroller's clock configuration or the LSE activation. Hardware and Code Details:

Hello community,I am running in an issue with the VREFINT calibration value of the ADC.For calculation I use the __LL_ADC_CALC_VREFANALOG_VOLTAGE function from the stm32u0xx_ll_adc.h file and I'm getting wrong values.The Chip is powered with 3.3V and so I expect a reading of approx. 3300 from this function, but what I'm getting is a value of around 2993.The measured voltage at the VDDA/VREF+ pin (48-pin package) is 3.296V, the reading of the VREFINT Channel is approx. 1660.If I change the supply voltage to 3V, I get around 1820 from the VREFINT Channel.The readout of the VREFINT address (0x1FFF6EA4) is 1654 (0x0676) so point 2.1.2 of the errata sheet is not applicable.If I change the value VREFINT_CAL_VREF in stm32u0xx_ll_adc.h from 3000UL to 3300UL the return values are plausible.For me it looks like the calibration was done using 3.3V instead of 3.0V as stated in the datasheet.The marking of the controller reads like

Could it be time for ST to reveal such an MCU at the summit in a few weeks? Or maybe a Cortex-M55 that actually have integrated flash or MRAM or similar? (STM32N6 is interesting, but I would like to see flash/MRAM/something else integrated...

When using PLL3Q as input with a frequency of 32MHz for USBPHY I have a RCC_CCIPR1 register initialized at value 0x2a00 when entreing USB_CoreReset function that is not correct (should be 0x2b00).

HI,I am working on a board using STM32H573V and have a working solution with UCPD detecting an inserted memory stick and running the MSC class. In an other part of the software I am using PC9 as an GPIO push-pull, low speed output and as soon as I set it to high, the voltage at PB14 (UCPD CC2) drops from 3.3V to 1.5V and my UCPD handler signals a device attached and turns VBUS on even though nothing is attached. There is no other electrical connection between PC9 and PB14 on the board. I am using a TCPP03-M20 for VBUS switching. The board is acting as VBUS source.

I'm working with an STM32F411 and trying to run two I2S master-receiver interfaces (I2S1 and I2S2) at the same time, each receiving data from a pair of PDM microphones using DMA circular transfers.However, I found a very strange and extremely hard-to-debug issue:Observed abnormal behaviorWhen only one DMA is enabled, both I2S1 and I2S2 work correctly.When both I2S + DMA are enabled at the same time, the following happens:If I2S1 has no microphone connected, it correctly receives all zeros.If I2S2 does have a microphone connected, then I2S1 suddenly starts receiving non-zero data, even though no microphone is connected to I2S1.It looks like I2S1 is receiving data that actually belongs to I2S2’s DMA buffer.Som

Hello everyone, I’m new to STM32 and I’m currently stuck with using timers.I’m working with an STM32F303RE, and the goal of my project is to generate 6 signals at 100 kHz (high time between 100 and 500 ns), each phase-shifted by 60°. These signals will be used to phase-shift power commands, in order to limit current spikes by staggering their switching times. For now, I’m focusing on generating just a single 100 kHz signal with a longer high time so I can easily observe it on an oscilloscope (precise timings are not important at this stage). To generate the signal, I thought about using the combined PWM mode of Timer 1. If I understand correctly, this mode allows the output to go high when the timer reaches CCR1, then go low when it reaches CCR2, and remain low until the ARR is reached or the timer restarts. This method has the advantage of potentia