STM32 MCUs

Dear all, I would like to connect a camera to my Nucleo F756ZG board, with the goal to send images via the ethernet port. However, this board doesn't feature a 30-pin ZIF connector nor a 22‑pin FFC connector....Apparently, the STM32 F756ZG has a "DCMI". Is this accessible on the Nucleo board as well?Which module/camera do you recommend for the Nucleo F756ZG?Would you recommend Arducam? They seem suspiciously cheapThe B-CAMS-IMX is not compatible, right?Many thanks

Hello everyone,I’m working with the STM32U5G9J-DK2 and trying to implement a Bootloader + XIP (Execute-In-Place) application architecture using the external flash.Target setup:A minimal bootloader running from internal flashThe main application linked to and executing from external flash (memory-mapped at 0x90000000)The main motivation is to free internal flash and validate this approach for a future MCU with very limited internal flash.What I’m specifically looking for help withProper CubeMX / .ioc configuration for the bootloaderWhich peripherals must be enabled (RCC, PWR, ICACHE, OSPI, etc.)Which peripherals should not be enabled to avoid conflicts with the XIP appAny STM32U5-specific gotchas when initializing OSPI for XIPProper configuration of the application projectRecommended changes to the application .iocWhat initialization should be removed from the app (HAL_Init, clock, OSPI, FLASH, etc.)Reference samplesSTM32Cube examples that demonstrate a full bootloader + XIP app flow on

STM32G030F6P6 microcontroller CubeIDE environment when enabling interrupt for I2C an LL_I2C_EnableIT_RX (I2C2); error occurs _______stm32g030xx.h:618:29: error: expected declaration specifiers or '...' before '(' token error occurs when any I2C interrupt is enabled  

We are starting to develop a new hardware platform and are currently evaluating the STM32H7R/S series for the main controller.The question now is which RTOS is best suited here in terms of long-term support from ST. We're going to use a lot of communication interfaces (USB, Ethernet, external WiFi/BT module, CAN), an RTOS with an integrated communication stack would make our work easier.Zephyr: High initial training effort, but you get a great framework. The two available H7RS-Eval boards are already supported, but in the video Zephyr 4.1: Status of STM32 support – Erwan Gouriou // Zephyr Meetup Grenoble Mar. 26, 2025 by @Erwan Gouriou from March of this year you can see that Zephyr support for the H7RS is not yet complete. Can anyone give an estimate of the extent to which you can already work with it or how much effort is involved in porting drivers from the H7 to the H7RS that are not yet available? I'm new to Zephyr and can't estimate the effort involved.ThreadX: Support

Hello everyone,I am working on shifting sensored FOC to sensorless FOC for a BLDC motor using STM32F103C8T6. I have successfully implemented all necessary transformations (Clark, Park, and Inverse Park), and the waveforms appear correct.To estimate the rotor angle, I am using a Sliding Mode Observer (SMO). However, since the STM32F103 lacks an FPU, So function like atan2f() increase execution time. Instead, I implemented an alternate method for angle calculation. I am using position detected by hall sensor as reference, but output of my sensorless algorithm is having some differences from hall sensor signal.This is output waveformHere is the code I am using for angle calculation: void SMOcalcalculation(int32_t Valpa, int32_t Vbeta, int32_t Ialpa, int32_t Ibeta){ // this is for approximated or predicted values of motor phase currents // this is need to reconstant bemf :The error between the actual and estimated currents (error_alpa and error_beta) is used to compute the Slid

I am using the STM32U585RIT6 microcontroller with the B-U585I-IOT02A development kit. I need to implement USB functionality using an interrupt-based approach. In my project, I have configured USB_OTG_FS in Device-only mode, enabled the NVIC global interrupt, and enabled USBX CDC-ACM. I am using bare-metal code (no RTOS or ThreadX). After completing all the USB configurations, inside the MX_USBX_Device_Init() function I added the following initialization: RX FIFO and TX FIFO configurations USBX DCD initialization using _ux_dcd_stm32_initialize() Started the PCD using HAL_PCD_Start() In the main while loop, I am calling ux_device_stack_tasks_run(). With this setup, the USB device starts correctly and is detected as a Virtual COM Port. Now, I want to handle USB connect and disconnect events using interrupts. For this, VBUS sensing may need to be enabled. While referring to the B-U585I-IOT02A schematic, the USB_VBUS_SENSE pin is shown as PF14. However, in the MCU datasheet and in STM32Cube

i am using nucleo-h753zi and i need to integrate external flash via spi, MX25L6433F this is my flash ic. i was struggling to integrate this flash so please guide me to achieve it also if possible please give any example code for this project

Right now, if there are any widgets on a page the Designer automatically creates a canvas buffer for it.  The following code is created in the ViewBase .hpp/.cpp files static const uint32_t CANVAS_BUFFER_SIZE = 12000; uint8_t canvasBuffer[CANVAS_BUFFER_SIZE]; touchgfx::CanvasWidgetRenderer::setupBuffer(canvasBuffer, CANVAS_BUFFER_SIZE);   This gets set up for each view that has widgets.  I want it to STOP DOING THAT.  I want to allocate my own buffer to it, in a piece of ram that I choose.  Please, please, please give me the option to tell the Designer that I will handle it myself.I can allocate my own buffer in the TouchGFXHAL::initialize() function, but it's just going to get overridden as soon as a View gets, as that constructor will set up it's own function. This is especially important, because I have give it a buffer at the start of time anyways, otherwise it crashes.  When the view page is changed to, it calls StatusContainer, which calls an I

 When using the STM32H743ZI Nucleo board as the I²C master and two STM32 Blue Pill boards as I²C slaves with different addresses, the master requests data from the slaves and the slaves respond accordingly. However, I²C communication  is unreliable during initial startup, and intermittent I²C errors are observed during runtime.Is there anyone to help me with this issue.Thank you.

I tried to use the Build analyzer in VSCode, but there are some important allocations missing:VSCode:STM32CubeIDE (using *.elf file produced by VSCode):This is probably because the VSCode plugin is using the *.map file while the STM32CubeIDE uses the *.elf file.Is there any chance to have the same Analyzer in VSCode?

I am developing with STM32CubeMX and generating initialization code for an STM32N6 device. In my FSBL (First Stage Boot Loader), I use USART10 to connect to the ST-LINK V3’s Virtual COM Port (VCP). However, it seems that CubeMX does not correctly generate the peripheral clock initialization code for USART10.After a series of investigations, I found that when generating USART10’s clock initialization code, only the kernel clock for USART10 is set to IC14, but the PLL source and divider for IC14 are missing. This happens with both LL and HAL libraries. For USART6, there is no such problem — its clock configuration is generated correctly.This behavior is very strange. During debugging, I also encountered an issue where PLL2 was not initialized, but that problem disappeared later.To work around this, I manually added IC14 configuration code for USART10 following the pattern used for USART6, setting IC14 = 96 MHz. After that, USART10 worked normally at the maximum baud rate of 12 Mbps.Has a

So as the title suggests, I have been trying to get the LCD screen to work on the STM32F469i-DISCO board. Currently I just want it to turn on at all. I found the BSP drivers in this link as well as the OTM8009A drivers in this other link  When I run the code however, it gives me the following error:../Drivers/BSP/STM32469I-Discovery/stm32469i_discovery_lcd.c:402:5: error: too few arguments to function 'OTM8009A_Init'402 | OTM8009A_Init(OTM8009A_FORMAT_RGB565, orientation); I noticed that the function prototype for that function is int32_t OTM8009A_Init(OTM8009A_Object_t *pObj, uint32_t ColorCoding, uint32_t Orientation);so I am not sure why the lcd drivers call the function in that way. Are there better/newer drivers that I should be using instead?

Dear Sir/Madam, We are using the STM32WLE5CCU6 LoRa MCU for our custom LoRa application project. We are able to detect the MCU successfully, and flashing/programming is also working without any issues. However, with our LoRa application, we were initially unable to establish a link with the LoRa gateway. After investigation, we identified an issue related to the 32 MHz clock circuit. We replaced the crystal on our custom board with the crystal used on the STM32WLE5 evaluation board, and after this change the issue was resolved. We were able to communicate with the gateway, and packets were received correctly. Later, we ordered the same evaluation board crystal again and assembled it on our board. However, this time we are once again unable to link with the gateway, even though the crystal part number is the same. This behavior is confusing, as the evaluation board crystal had previously worked on our board. We would like to understand: Is there any register or configuration option in

 

I want to use DMA with SPI in slave receive mode with words longer than 8 bits :I launch the DMA with the function: HAL_SPI_Receive_DMA( &HSPI_ADS, (uint8_t*)ads_dma_buffer, ADS_BUFFER_MAX_SIZE );Unfortunately in this function the following test fails:  /* Packing mode management is enabled by the DMA settings */ if (((hspi->Init.DataSize > SPI_DATASIZE_16BIT) && (hspi->hdmarx->Init.DestDataWidth != DMA_DEST_DATAWIDTH_WORD) && \ (IS_SPI_FULL_INSTANCE(hspi->Instance))) || \ ((hspi->Init.DataSize > SPI_DATASIZE_8BIT) && (hspi->hdmarx->Init.DestDataWidth == DMA_DEST_DATAWIDTH_BYTE))) { /* Restriction the DMA data received is not allowed in this mode */ errorcode = HAL_ERROR; __HAL_UNLOCK(hspi); return errorcode; } Because the structure "hspi->hdmarx->Init" is never initialized. It is not initialized, but the structure associated with the nodes is indeed initialized.In the case where the data size is 8 bits, the test i

ST‑LINK Mini V3E not detecting STM32H7 (Core ID error, high current when VTARGET connected)I’m debugging an issue with a custom STM32H7 board and an ST‑LINK Mini V3E. The setup includes a main PCB and a separate power PCB. So far:Power & Basic Checks3.3 V and 24 V rails are correct.Board current consumption is low when powered from either an 8 V or 24 V supply.Connections between the ST‑LINK Mini V3E and the main PCB have been verified.ProblemWhen I connect VTARGET from the ST‑LINK to the board’s 3.3 V rail, the current spikes and something starts to smell hot.STM32CubeProgrammer shows no target voltage, no device ID, and fails to read the core ID.The ST‑LINK is detected by the PC normally.Additional TestsTried a second main PCB and a different ST‑LINK Mini V3E, powering only through the ST‑LINK (no external supply). Same result: STM32CubeProgrammer cannot detect the STM32H7.I’m aware that VTARGET on the Mini V3E is an input, so I’ve tied it to the board’s 3.3 V rail as required.Ne

Hi, I’m working on an STM32H7S78‑DK project that uses FreeRTOS, with STM32CubeIDE v2.0.0 on Windows. The ST‑LINK debugger works normally as long as RTOS Proxy is disabled, but cannot be launched once I enable RTOS Proxy. Error message and Console prints as below: My debugger configuration: The exact same project used to run fine with RTOS Proxy enabled, but it suddenly started failing one day without any changes to my debug settings. The board itself should be good, as it works normally on another development setup.Has anyone seen this issue before, or is there any known limitation with RTOS Proxy on the H7S series? Any pointers would be appreciated.

Hi everyone,I'm working with an STM32F401CCU6 and trying to transmit 2 bytes over I2C3 using DMA1 Stream 5 Channel 6, which is the correct mapping according to RM0368 Table 28:DMA1 Channel 6 Stream 5 -> I2C3_TXThe DMA configuration appears correct, and I do receive the DMA Transfer Complete (TC) interrupt. So the DMA request is generated, the stream runs, and the transfer completes.However, it seems like the I2C slave device (AW9523) never receives the register and data bytes. Unfortunately my osci is currently broken.The same write sequence works perfectly when I use a blocking I2C write (polling SB, ADDR, TXE, etc.). Only the DMA‑driven version fails.What I observe:START condition is generatedAddress is sent and ACKedADDR flag is cleared correctlyDMA TC interrupt firesSTOP is generatedBut the slave never sees the register or data byteDMA is configured as:DMA1, Stream 5, Channel 6Direction: Memory -> PeripheralMemory increment enabledPeripheral increment disabledByte transfersNo

Dear Sir/Mam, As LCD, i.e., RK043FN48H-CT672B Rocktech of STM32F746 Discovery Board is obselete hence can we change to RK043FN66HS-CTG Rocktech without any implication in the firmware of Discovery board? Please respond me as soon as possible. Best Regards Sushant Verma

Moved from STM32 MCU products forum board to MCU embedded software as the main question is about how to run the demo vs LCD versions. I got STM32U5G9J-DK2 and this Discovery is still assembled with LCD board MB1860A version. But the documentation suggesting this DK have LCD board MB1860B version and share only B version scheme. I taked damage of my LCD board MB1860A and replaced it to MB1860B LCD board version from my next Discovery Kit STM32H7S78-DK. And here arising some problems: For example the BSP demo from example pack working flawlesly, but the main demo embedded from factory doesn't work with STM32U5G9J-DK2  and MB1860B version of LCD board. The LCD is dark and look as dead.   So my questions  which could be provide the answer about incorrectly work of LCD sounds like: 1. Why doesn't the main demo work, despite of the docimentation suggestion that this kit is assembled with the MB1860B LCD version board? 2. How I can obtain the scheme for M

Hello.I'm working on setting up a brand new Nucleo STM32U5A5Z development board and have some issues.My project is a completely bare-bones default with no security or BSP enabled. The application fails in SystemClock_Config() and enters the error handler. The issue seems to be related to the HSE as SystemClock_Config returns HAL_TIMEOUT here: /* Check the HSE State */ if (pRCC_OscInitStruct->HSEState != RCC_HSE_OFF) { tickstart = HAL_GetTick(); /* Wait till HSE is ready */ while (READ_BIT(RCC->CR, RCC_CR_HSERDY) == 0U) { if ((HAL_GetTick() - tickstart) > HSE_TIMEOUT_VALUE) { return HAL_TIMEOUT; } } }Thanks!

Hi, I'm trying to implement USBPD EPR Source with DisplayPort Alt Mode on a STM32G071. I use the latest https://github.com/STMicroelectronics/stm32-mw-usbpd-core, which seems to support EPR, but I couldn't find any complete examples with a working EPR source. Now I successfully enter EPR mode, and Sink receives EPR PDOs, but can't negotiate any PDO except the 1st. Even SPR PDOs The stack sends REJECT after PE_SRC_NEGOTIATE_CAPABILITY. It works perfectly in SPR mode and can switch between PDOs, but fails the same PDO in EPR mode 1st PDO in EPR mode ACCEPT: 2nd PDO REJECT: How can I debug these things inside the stack? What am I missing? Spoiler (Highlight to read)uint32_t PORT0_PDO_ListSRC[USBPD_MAX_NB_PDO] = { /* PDO 1 */ ( USBPD_PDO_TYPE_FIXED | /* Fixed supply PDO */ USBPD_PDO_SRC_FIXED_SET_VOLTAGE(5000U) | /* Voltage in mV */ USBPD_PDO_SRC_FIXED_SET_MAX_CURRENT(1000U) | /* Max current in mA */ USBPD_PDO_SRC_FIXED_PEAKCURRENT_EQUAL | /* Peak Current info */

Hello,We have procured a STM32U5G9J-DK1 discovery kit. We are in need of the default pre-loaded program that comes with the kit as this will help us to understand how to use Touch display and its other features. We see that this pre-loaded program is not available in the repository downloaded for STM32U5G. Therefore, request you to kindly share it here.With regard,Sudarshan Chaudhary

In this documentation, I can find a detailed description of the torque/flux (current) PI controller implementation, but there is no clear explanation of the speed PI controller design or tuning. Could you please explain how the speed PI (KP, KI) is derived, and what criterion ST MC Workbench uses to compute these parameters automatically? 

DearsWe used STM32G431CBT3 in 5000W Three-phase Permanent Magnet Synchronous Motor Driver projects, now facing some issues below, could you help check and advise this, thanks!1. There are some issues encountered in the project of driving with a three-phase permanent magnet synchronous motor. Please assist in resolving them. The attached file contains the design materials. If any other materials are needed, please inform us promptly. Thank you!1. Driver parameters:Rated power: 5000W (continuous operation with approximately 100A)Peak power: 13500W (300A current flow for about 3 seconds)Carrier frequency: 16kHzWorking voltage: 18 series lithium batteries (54V - 78V)Operating environment temperature: -10℃ to 50℃Motor slot-pole number: 36N, 42PTest topology:2. Problem Description: During the pulse experiment, the following issues were encountered. The double pulse parameters were (pulse current 400A, bus voltage 80V, auxiliary test inductance 5.6uH). Regarding the following severa