STM32 MCUs Products

Hiya. I'm having some trouble understanding how an STM32 MCU communicates with an image sensor via DCMI if they operate on different voltages.My STM32U5Gxxx operates on 3V3, whereas my selected image sensor has its VDDIO at 2V8 (max input of 3V1). How can I make sure that all the signals I send to the sensor are at 2V8 instead of 3V3? Is there a certain VDDIOx pin to be tied?Are there any reference designs or schematics that are helpful?

As addicated in DataSheet and CubeMX, there are two FDCAN1_Tx and two FDCAN1_RX in STM32G431CBT6. In my Prj, I used PA12 for Tx and PB8-BOOT0 for Rx, and my chip can only work in FDCAN_MODE_Ext._Loopback, and without any receive func be implemented. After I changed the FDCAN pin from PA12&PB8 to PB9&PB8 and adjusted my wire routing, the problem has be handled. so If the STM32G4 can use FDCAN pin from different port in some case? If not. I think it should be fixed in CubeMX, because CubeMX allows users to select CAN pin from different ports without any warning.​

How to configure the sysTick_Handler(), when we are setting the HCLK 386MHz in CubeMX and systemClock() is generated, but while configuring sysTick(), uint32_t SystemCoreClock = 64000000; already there in system_stm32h7xx_dualcore_boot_cm7_cm4.c(void)SysTick_Config((SystemCoreClock) / 10000);Will it effect mine overall MCU speed and performance, because after all I'm using FMC NAND Flash to communicate with the external Micron Flash, because there I need to calculate the clock cycles need to the write enable (WE), Setup time, Address Latch Enable (ALE) time etc, will be effected, or it is completely independent, should I only consider FMC_CLK which is coming from PLL clock source 2.

Hi,  I'm using a STM32F072's DAC to output a SIN and a COS wave. The problem is I can only output values up to approx. VDDA / 2. The DAC drives unity gain amplifiers to drive a 50 Ohm load. The DAC is connected directly to the amps, using the buffer does not help. VDDA = 3.3 V. Here, CH4 is connected directly to the DAC output via a 10:1 probe. The black things on the scope inputs are 50 Ohm termination, so the CH2 and CH3 signals having only half the amplitude of CH4 is expected. All channels are DC coupled. I'm writing to the DAC using the DHR12L1/2 registers (using the STM32Cube HAL): uint16_t value = (uint16_t) (ltbDacSinLut(ltb_dac_ch1_counter_) ^ 0x8000) & 0xFFF0; HAL_DAC_SetValue(&hdac, DAC_CHANNEL_1, DAC_ALIGN_12B_L, (uint32_t)value);where ltbDacSinLut returns values in the range of [-32768, 32767].  Dividing the value by 2 before writing to the DAC results in undistorted SIN / COS output, but of course the output swing

Hello,Can anyone tell me how to measure pulse width with the HRTIM? I need to measure a very short pulse from my time domain reflectometer. I am thinking of using the NUCLEO-H753ZI board with the STM32H753ZI MCU. All I know about measuring pulses with the HRTIM is that I need to use the external event registers and that the minimum pulse width must be >2.5 ns. Any help would be greatly appreciated.

We need further clarification regarding the difference between the above ICs.We recently purchased the mentioned STM32 MCU, but received two different variants. In one IC, the ST logo on the right side has the marking “e3” with “L” outside the circle. In the other IC, the ST logo on the right side has the marking “e4” with “L” outside the circle.Kindly clarify the difference between the “e3” and “e4” markings and confirm whether both ICs are equivalent in specification and performance.

I am developing a device that implements the USB device class.According to application note AN4879 "Introduction to USB Hardware and PCB Design Considerations Using STM32 Microcontrollers" it is written as follows:Based on the USB specification, a USB device must use VBUS sensing detection. When the device detects the host presence, it connects its pull-up resistor to either a D+ or D- data signal. This allows the host to detect the device presence on the bus. There are two cases: • The USB device is bus-powered. VBUS sensing is not mandatory (USB is always connected when the device is powered)• The device is self-powered. VBUS sensing is mandatory. Pin PA9, a five volt-tolerant pin, which includes an additional function natively dedicated to VBUS sensing. I have an option when the device is self-powered. Therefore, VBUS sensing is mandatory.It is also written that the user must avoid the situation when the MCU is not powered, and a 5 V VBUS is connected to PA9.The absolute maximu

I got another strange issue with a STM32F3, as usual related to DMA.The problem relates to an "old" DAC / DMA example I tried to port to a different MCU.The original is called "DMA_RAM_DAC", and is part of the V1.1.0 firmware package for the F303 discovery board.(.../STM32F3-Discovery_FW_V1.1.0/Project/Peripheral_Examples/DMA_RAM_DAC)Building and running it on this target, it works fine.However, my actual target hardware is the F3 Nucleo32. This board has a STM32F303K8T, instead of the 'huge'  STM32F303VCT on the F3-Discovery.The relevant difference here is, the mentioned example uses DMA2 channel3, which does not exist on smaller devices like the STM32F303K8. According to the reference manual, the relevant DMA request can be mapped to DMA1, by setting corresponding bits in SYSCFG (RM0316 Rev.10, page 267, 269).To do this DMA request mapping, bit 13 in SYSCFG->CFGR1 needs to be set.And here is were the problem starts.No attempt to write to this register seems to have any effect

I'm using the LCD of the STM32U073K8, but the program failed to initialize the LCD. After checking, I found that the STM32U073K8 doesn't have the VLCD pin. Is the STM32U073K8 not compatible with the LCD peripheral? Or are there other settings?  

Hi All,I've this requirement, can someone suggest how do I proceed.I'm using stm32u535 and over usart it's connected to Silicon labs chip. Silicon labs chip has Wi-Fi and I want to update firmware of STM32U535. This silicon labs chip is connected to cloud over Wi-Fi. 

We are currently working with a custom PCB using an STM32N6 chip and an MX25UM512G flash chip. The flash is connected identically to the Nucleo development board.When powering up the board in Dev Boot mode, it is not possible to read the flash chip using CubeProgrammer. The MCU crashes, which we assume based on the reduced power consumption observed afterward.If we first load a firmware image into SRAM using CubeIDE (which successfully connects to and reads the flash memory), then reading and writing the flash via CubeProgrammer works as expected.However, after a power cycle without reloading the firmware into SRAM, the flash becomes inaccessible again.Additionally, after flashing the firmware using this workaround (i.e., initializing the flash via our own firmware and then booting in Flash mode), the software is not executed from flash and the system does not boot.Our assumption is that the flash is not correctly initialized by the boot ROM. Any help or suggestions would be highly app

Hello everyone. I am running into a USB Host <--> Device connectivity issue. I have 2 STM32L496 MCUs, one as Host and other as Device. I cannot get the CDC connectivity to work for some reason. The connections are as follows: D+ <> D+, D- <>D-, GND<>GND.I have VBUS, SOF and NOE disabled. CubeMX forces to set Drive_VBUS as well over a GPIO, however, I am not using that in my circuit. Even though it is a recommendation in USB connectivity in AN4879, I believe it is possible for a simple connectivity without it as well. Would this be a wrong assumption (and hence the culprit)? As a connection stability, I tested both MCUs individually as Devices, connecting to my PC and it sent data over USB just fine. The attached code has NucleoL496 as the host. Would appreciate your support.

Hi,   I am implementing a Dual Active Bridge (DAB) DC-DC converter on an STM32L476RG Nucleo board. The goal is to generate 8 complementary PWM signals using TIM1 (Bridge 1) and TIM8 (Bridge 2), both at 5 kHz with 50% duty cycle, and to control the power transfer by adjusting the phase shift between the two timers.   The phase shift must be adjustable at runtime (via button, potentiometer, or PID controller) without affecting the 50% duty cycle.   I tried three synchronization approaches, all of which failed:   1. Reset Mode (SMS=100): TIM1 sends a TRGO at the end of each period. TIM8 receives it and resets CNT to 0, which cancels any preloaded phase offset every 200 µs. The phase shift cannot be maintained.   2. Trigger Mode (SMS=110): TIM8 starts on the first TRGO then runs freely. The initial phase is correct but there is no ongoing synchronization, which could cause drift over time.   3. CCR1 as TRGO source (MMS=011): Using CCR1 to time the trigger woul

Hi.I'm using an STM32G051 and would like to use 12 ADC channels which are not sequential. I have thus set up the ADC for 'sequencer set to not fully configurable' as show below:Ignore for the moment that IN9 is red, I think I was trying something with one of the comparators to see if that helped.I'm using the DMA to kick off a new conversion and the callback reports back raw values which I print out as seen below.If I enable IN0, IN9 or IN10 then I get bad data from the ADC (possibly mixed up channels) as seen below where the VREF+ is being reoprted as over 5V when it should be 3.3V.VREF+: 5362 mV.CPU Temperature (STM32): 1870.0 °C.Sample Temperature: 0.0 °C.LED feedback current: 0 mV.raw vref ADC value: 0x3a5.raw DET0 ADC value: 0x184.raw DET1 ADC value: 0xfff.raw DET2 ADC value: 0xffe.raw DET3 ADC value: 0xffd.raw DET4 ADC value: 0xfff.raw DET5 ADC value: 0xffe.raw DET6 ADC value: 0x5e4.raw STM32 temp value: 0xffe.raw LED feedback current value: 0x00e.If I disable IN8, IN9 and IN10 (

Hello, Is my understanding correct that it's impossible to internally detect short (<100ns) drops of VCORE internally? Reading RM0481 page 154 it seems impossible to directly monitor VCORE through the tamper mechanism which I assume forces the use of an ADC+WDG, which probably puts the detection range in the µs? Which means the target is sensitive to fault injections?

I realise one cannot disable the watchdog, short of a full reset.One method would be to leave a "magic number" somewhere, say in one of the RTC locations, do a reboot, and if that is found at power-up, you don't enable the watchdog and you perform a shutdown, using the WFI etc method.But that's not really the point, and it is not safe.I wonder what would be the most effective thing possible. The watchdog will still be tripping so probably the best way would be to select slowest clock (I have a 25MHz external xtal and a 32768Hz external RTC xtal) and stay in a loop pulsing the watchdog. What is the best way to do this? Perhaps switching to the 16MHz internal oscillator and setting the PLL for the slowest clock?Any tips much appreciated.

Heyho,playing with the L073, partitioned the flash for bootloader "BL" (bank 1) and application (bank 2).No writing of app yet, just testing jumping back and forth.I just added a no-init variable for communication between BL and app, mainly to tell the BL to not jump back to app if the app requested so.at power up / reset, the uninitialized variable "u32AppRqstBootloader" is 0, so the BL jumps to the app, and just for checking: before the jump the BL sets u32AppRqstBootloader = 0xB0072ABBin the app u32AppRqstBootloader is printed via UART, and it shows the expected 0xB0072ABB, the printf is done immediately and takes ~ 2 ticks (1 tick = 1 ms)now I let the app jump to BL, before the jump the app sets u32AppRqstBootloader = 0xABB1B007 so the BL does not jumpSo far so good...But when the BL now jumps back to the app, all of a sudden in the app there's a ~ 1 second delay before u32AppRqstBootloader is printed - everything else is working fine - or so I think... (the next pri

I am currently working on the STM32N6570-DK board for a camera-based project.Development SetupIDE: STM32CubeIDE (Version 2.1.1)Tool: STM32CubeMX (with STM32N6 package installed)Issue 1: Flashing & Boot BehaviorI tested the example GPIO_IOToggle programThe program is flashing and running properlyHowever, after pressing reset, the code is not running againTo make it run:I set BOOT1 = LOW and BOOT2 = LOWAfter reset, the AI demo code runs insteadMy requirement:How to properly flash the user application into internal flash memoryAfter reset, the same user code should run automaticallyIssue 2: Required Examples / GuidanceI need guidance or reference examples for the following:1. ST-LINK V3EC configurationSerial communication setup for debugging (UART / Virtual COM)Camera InterfaceCamera bring-up2. How to read camera dataEthernet & StreamingEthernet initialization (bring-up)UDP socket configurationStreaming camera data to display over EthernetProject GoalCapture camera data and stream

AN2606 indicates that I should be able to activate the built in boot loader by jumping to the correct address in ROM, but I can't work out what that address is for the STM32U535CB. 

Hello everyone,I develop a project with STM32U575 and I want to use LPUART with LPDMA, normally I use LPUART with normal DMA in my other stm32L4 projects but here I couldnt work with this peripherals. Low power is not a critical issue of this part of project. So I just want to use LPUART with LPDMA in a normal way. First picture is my old settings in L4 series and second picture ise for current U5 mcu. Do I miss something ? Where can I find and example for LPDMA and LPUART for Standart Request Mode. Thanks

Dear STMicroelectronics Team,I am looking for an STM32 microcontroller for a new project. My main requirements are:At least 4 SPI interfacesAt least 2 USB interfacesCould you please suggest suitable STM32 part numbers that meet or come close to these requirements?Thank you for your support.Best regards,DZ

Hi all,We have a product using a STM32L451CEU6. We have gone through low rate initial production and it has met requirements but the customer has requested a change. We are experimenting with increasing the system clock speed the device is running at by changing the internal PLL settings. The device is running from the HSE, a 25 MHz crystal oscillator. It works without issue in the baseline clock configure shown below. When we try and change the N multiplication values in the PLLs to any other value, something appears to go wrong during the setup phase of our application code, and it appears to lock up. We have a custom serial bootloader but we cannot access it at this point, so we have to reflash completely using STM32 ST-LINK Utility and a STLINK-V3 programmer. This occurs whether we increase or decrease the N values e.g. N values of 15 or 17 do not work. This occurs whether we edit the N values in the code directly, or change them via CubeMX and regenerate the code. If we chang

Hi. I'm looking for an STM32 with a lot of GPIO triggered DMA channels. I need 8 channels that trigger when a pin changes state, and which can read/write to GPIO registers and DMA registers. It's for implementing a bus interface where I need to read address pins and write them into the lower 16 bits of DMA address registers, and use pin transitions to trigger GPIO state changes (GPIO data values, GPIO direction bits). Are there any parts that can do that? The M0+ series doesn't have enough DMA channels that can be triggered by GPIOs. The M3 and M4 doesn't seem to allow triggering from GPIOs.

Hi,Any reason why the GBW of the OPAMP is having such a wide tolerance? Is it purely because the values are best-worst case design calculations?In comparison, the Gx and Fx variants has better limits.

Hi,I am using STM32G070RB for a modbus based product. The code is complete but i am facing issues that on some of the controller the code does not work and it gets stuck in the HAL_DELAY() function because the systick interrupt are not getting through.Strange and concerning thing is that the code works on many controllers without problem but on few of them random controllers we are facing this issue.I have tried setting the nBOOT_SEL, nBOOT1 and nBOOT0 in the code so that the vector table address get set correctly.void ConfigureBootToUserFlash(void) { // Unlock the Flash memory control register if (HAL_FLASH_Unlock() == HAL_OK) { // Unlock the Option Bytes if (HAL_FLASH_OB_Unlock() == HAL_OK) { FLASH_OBProgramInitTypeDef obInit = {0}; // Read current option bytes HAL_FLASHEx_OBGetConfig(&obInit); // Check if nBOOT_SEL and nBOOT0 are already configured if (!(obInit.USERConfig & FLASH_OPTR_nBOOT_SEL) || // nBOOT_SEL not set (obInit.USERConfig & FLASH_OPTR_nBOOT0