STM32 MCUs Embedded software

Hi! I am working with a stm32h743zit6 + ov5640 combo. I am using STM32CUBEMX + Makefile on Ubuntu.Currently I am at the state of:- Camera setup is successful- Code gets into HSYNC event callback- Code gets into VSYNC event callback- Code doesn't get into Frame event callback Currently I am unable to capture any images. I would really appreciate your help! Thank you in advance!

helloDescription:I'm currently working with the STM32U585 and encountered an issue related to USART3Most of the time the code works fine, but it occasionally gets trapped in HAL_UART_IRQHandlerI am using the DMA Receiver Timeout (RTO) and DMA TX, may code is:void uart_tx_complete_cb(UART_HandleTypeDef *huart) { if (...) HAL_UART_Transmit_DMA(huart, buf, len); } void uart_rx_error_cb(UART_HandleTypeDef *huart) { HAL_UART_AbortReceive(huart); if (huart->ErrorCode & HAL_UART_ERROR_RTO) { ... } HAL_UART_Receive_DMA(huart, rx_buf, rx_buf_len); } HAL_UART_RegisterCallback(&huart3, HAL_UART_ERROR_CB_ID, uart_rx_error_cb); HAL_UART_ReceiverTimeout_Config(&huart3, 100); HAL_UART_EnableReceiverTimeout(&huart3); HAL_UART_Receive_DMA(&TD_UART_HANDLE, rx_buf, rx_buf_len); HAL_UART_RegisterCallback(&huart3, HAL_UART_TX_COMPLETE_CB_ID, uart_tx_complete_cb); When the issue occurs, I found that the TC (Transmission Complete) flag is not being cleared:an

Hi, I need to update the firmware of my MCU from the UART. I mean without physically touching the BOOT pin, but only via serial commands (classic FW update of a product).I'm not an expert, but I tried searching on the internet and I saw that for these things it is necessary to write a bootloader. It doesn't seem impossible, but for a non-expert it's not exactly simple.What I wanted to ask is, I think this is a very common need among users, has STM created anything official to support this feature? Is there something already given and official that I can use without necessarily writing my own custom bootloader? Maybe even supported directly in CubeMX.I've seen that there are dozens of amateur/community bootloaders available, but not knowing how to write it, I can't even evaluate whether it's done well or whether it's suitable for my application, which is why I'm looking for an official STM solution.

Hello!I am writing a program for STM32F769I-DISCO board that uses FreeRTOS and LwIP to communicate with the server and send data to it. It generally works, but unplugging and plugging Ethernet cable (especially doing it several times within a few seconds) usually causes Ethernet DMA errors which make program stop calling HAL_ETH_IRQHandler and thus board can't even try to reconnect to server. I don't know how I should handle those errors and where to look for information that could offer a solution to my problem.Any kind of help, whether a direct response or a link to helpful resources, is appreciated. Ethernet DMASR registerheth error codeMPU and Ethernet descriptors EDIT 1: Added ethernetif.c and lwip.c files to attachments and screenshot of MPU configuration. 

Hello,I have filed an issue but thought I would post this here for reference, this bug took me quite a while to hunt down and hope to save others time possibly:I have found a memory-safety defect in EEPROM_Emul on STM32U5 128-bit flash-line config.Config:- FLASH_LINES_128B enabled- EE_ACCESS_32BITS enabledIssue:- EE_ReadVariable32bits() passes a single EE_DATA_TYPE buffer:Core/EEPROM_Emul/Core/eeprom_emul.c:758, :762- In FLASH_LINES_128B mode, ReadVariable() writes two words:Core/EEPROM_Emul/Core/eeprom_emul.c:1184, :1185- This writes beyond the caller’s single-word buffer and can corrupt stack/register state (we observed HardFault with corrupted stacked PC).Why “wrong API usage” is not a valid dismissal:1) The API is publicly exposed in this build mode (Core/EEPROM_Emul/Core/eeprom_emul.h:126 with FLASH_LINES_128B APIs also present at :130).2) An exported API must not corrupt memory under any call pattern; unsupported combinations must fail explicitly.3) This component already uses st

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

Hi,I am using the application core of the STM32WB55VGY6 (not the radio core). I created a CubeMX project and added a simple HAL_GPIO_TogglePin() call. Literally just 2 lines of code in the entire project.When I use a for loop as a delay, the code works as expected. However, when I use HAL_Delay(), it does not.For some reason the SysTick_Handler() is never called... I’ve attached the full project, including the .ioc file. The application code itself is minimal (only two lines).From the configuration:The timebase source is set to SysTickInterrupts are enabledThe SysTick_Handler() is generated, but it is never triggeredHas anyone encountered this on the STM32WB application core, or have any suggestions on what might be missing or misconfigured?Thanks. 

Board: NUCLEO-N657X0-Q, revision CI'm trying to communicate with an I2C sensor (VL53L7CX) using the I3C1 peripheral. I have written small routines to try this out based on this tutorial (chapter 9.10.). The problem is: no signal appears on the data pins (measured by an oscilloscope). Not even the slave address. They seem completely dormant.I have tried the "I3C Direct Command DMA" example project on the board. I don't have I3C devices, but measurement yielded digital signal waveforms, as expected. This confirms that the peripheral is in fact operational.What have I missed in my code or hardware setup? Any help is appreciated! Thank you!(I attached the mixed bus code and the .ioc file)

Hi,I would appreciate any guidance or best practices for minimizing code size by eliminating unused functions when using the STM32 extension for VS Code with CubeMX generated code (bare metal) as some code I'm writing has become very large.What is the recommended way to configure the compile/build process so that unused functions are not compiled or linked into the final image flashed to the microcontroller, in order to save flash space?I am not familiar with CMake, so if this can be achieved without using CMake, that would be preferred.If custom configuration text is required (for example Makefile edits or similar), could you please outline them in detail and whether these changes are generally safe, or if they require careful consideration.Any clarification on the recommended approach would be greatly appreciated.Thank you

Hi,I am using a STM32C031G6U6 and I would appreciate some clarification regarding HAL timebase and SysTick timebase selection.I want to use SysTick as a 1ms interrupt so in CubeMX I selected SysTick as timebase (see screenshot): None of the other timers - including TIM3 - are not enabled as shown here: These are the other settings:  I then generated the code. But there is no sign of any SysTick related functions/handlers in the interrupt file stm32c0xx_it.c as you can see here: /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file stm32c0xx_it.c * @brief Interrupt Service Routines. ****************************************************************************** * @attention * * Copyright (c) 2026 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * I

I am using STM32G491RE - NUCLEO. connected to the ADM3055e CAN Transceiver Currently I am trying to send 12 Bytes of Data from IXXAT Terminal over to FDCAN1 which receives the message fine and then Output the Message on FDCAN2 though a buffer. So My logic is when a message pass the filter it gets called by the Fifo0Callback and push it to a buffer below. This works fine the buffer also get the full 12Bytes of data same FD format and everything checked out.But when I try to add the message to HAL_FDCAN_AddMessageToTxFifoQ(&hfdcan2, &TxHeader2, TxData2). Where TxData is the dequeued message from the buffer and copys the 12Bytes. The message somehow gets truncated to 8Bytes on output. Heck, when I add "if (HAL_FDCAN_GetTxFifoFreeLevel(&hfdcan2) > 0)", It somehow says it is full even when starting the code.I have been suspecting because I cant set the HAL_FDCAN_ConfigTxBufferElementSize and HAL_FDCAN_ConfigRxBufferElementSize or even the messageRam offset

Hi all,during testing a custom project with NETXDUO on NUCLEO-H563ZI I've noticed that sometimes web server response is rather slow.Wireshark shows rather frequent TCP retransmissions and other problems.To be sure, I've tried an example from ST (Nx_Iperf) with the same result.It seems that problem is in ETH_Prepare_Tx_Descriptors(), in check of Tx Descriptor: /* Current Tx Descriptor Owned by DMA: cannot be used by the application */ if ((READ_BIT(dmatxdesc->DESC3, ETH_DMATXNDESCWBF_OWN) == ETH_DMATXNDESCWBF_OWN) || (dmatxdesclist->PacketAddress[descidx] != NULL)) { return HAL_ETH_ERROR_BUSY; }I removed this check and TCP retransmissions became much less frequent.Is there a better solution?

Dear all, We are using the STM32N6570-DK to encode a video stream (800x600px) and store that at a reasonable data rate to an external sd-card.I have extended the VENC_SDCARD_ThreadX example to a certain extent to cover the obvious timing differences between the video capture loop and a disk write loop. The sample code is a great way to go forward, but at the moment we reach a data write rate of about 25kb/s when using FileX.We have initially used the HAL implementation but I have changed the fx_stm32_sd_driver_glue.c code slightly to use the BSP layer for card speed negotiation that is not present in the HAL layer; debug output shows that we're at least using 4-bit wide data transfers>:CardInfo type 1, version 1, class 1461, spd 0 Inst PWR 00000013 CLKCR 00004004  It seems that just before reaching down to the HAL layer, the single transaction (~200blocks at once, typically), is split  into single sector writes in the sd_write_data function (fx_stm32_sd_driv

I need to create a UART driver that works reliably in all conditions.The driver must use DMA, and since the incoming messages are NOT fixed-length, I need to use idle line detection.My question is: how can I use a callback to store the received message when an idle line is detected and then restart the reception using the STM32 HAL idle-line API?

Hello,  I'm using STM32CubeIDE 2.0.0 + STM32CubeMX 6.16.1 + FW_H7 V1.12.1 I have a problem with USBX RNDIS.The generated code on file ux_device_descriptor.h  at line 308 is: #define USBD_RNDIS_EPINCMD_ADDR 0x81U In the exemple code of STM32H735-DK find on stm32-usbx-exemple repo I have this #define USBD_RNDIS_EPINCMD_ADDR 0x82U The USB device is well recognized be my computer (windows 11) only if the value is 0x82U. My questions:  - why it doesn't work with 0x81 - is there is a tips to modify this value on Cube ? Actually I add an error at the end of the file if value is 0x81..   Thanks for help !  

I am implementing a TCP Server on an STM32H563ZI (Nucleo-144) using NetXDuo. The software initialization part is working perfectly; the ThreadX kernel starts, and NetXDuo reports that the IP instance (192.168.2.55) and TCP are successfully enabled.The Implementation Logic:The system is designed to initialize the network interface, assign a static IP, and start listening on Port 80 for incoming commands. Physically, the link is established as the Ethernet LEDs are active.The Problem:Despite the stack reporting a "Ready" state:There is no ICMP (ping) response from the board.TCP connection attempts via Hercules or Telnet on Port 80 fail with a timeout.It feels like the MCU is either not receiving packets from the PHY or failing to transmit them back to the wire.I am looking for guidance on why the communication fails even though the software reports success. Is there a specific configuration for the H5 series regarding the RMII interface or internal memory management that could prevent pa

hello everybody I am programming 10 addressable Leds with PWM with DMA using the M7 cortex of an STM32H747 in a custom board.Characteristics:Clocks: SysClk 480 MHz, TIM kernel clock 240 MHzTimer: TIM3, Channel 4, internal clockPWM base frequency: ~770 kHz (period ≈ 1.3 µs).ARR: 312‑1 (312 ticks → 240 MHz/312 ≈ 769.23 kHz).DMA: Peripheral = TIM3_CCR4, Memory in RAM_D2, half‑word alignment (16‑bit duty), MemInc enabled, PeriphInc disabled, Mode = Normal.What worksIf I run the timer alone (fixed duty), the PWM is correct and stable.The problemWhen I enable PWM + DMA, the waveform becomes random/discontinuous. On the oscilloscope I see “splits” and gaps; the PWM is not continuous. For example, the first 8 bits might be high and the following 16 low (intended to represent RED), but the stream breaks unpredictably. The data buffer looks correct when inspected in the debugger.The configurationI am using channel 4 timer 3. with internal clock source.and DMA is configured as:where data wid

I am creating a program that jumps from the bootloader to the application program using the STM32F410.The bootloader uses 0x08000000 to 0x08003FFF.The application uses 0x08004000 to 0x08007FFF.The bootloader program jumps to the application program successfully,but after entering the application program, the USART interrupts do not function.The SPI in the application program continues to operate after the jump. I'm posting the jump-related program.Can you figure out what the cause might be? I'd appreciate your help.【Bootloader main.c】 void jump_main(){ __disable_irq(); // Clear all interrupt bits for (uint8_t i=0; i<8; i++) { NVIC->ICER[i] = 0xFFFFFFFF; NVIC->ICPR[i] = 0xFFFFFFFF; } int * address = (int *)0x08004004; __set_MSP(*(int*)0x08004000); *(int*)0xE000ED08 = 0x08004000; ((void (*)())(*address))(); } 【Application main.c】 int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MCU Configuration---------------------------------

Hello ST Community,We are working with STM32N6 (STM32N6570-DK) and an IMX335 camera sensor, and we would like to confirm whether our intended pipeline is supported and feasible on this platform.What we are trying to doOur goal is to enumerate the device as a standard USB UVC camera on a PC and stream live video:- IMX335 sensor outputs RAW10- STM32 ISP processes RAW10 (demosaic, color processing)- DCMIPP outputs RGB565- Firmware converts RGB565 → YUY2- USB Device enumerates as UVC (Uncompressed YUY2)- Live video displayed on Windows camera applicationThe USB device enumerates correctly and is detected as a UVC camera on Windows, but the live video stream currently appears black.Current Observations- USB descriptors and UVC configuration (Uncompressed format, payload handling, FID/EOF toggling) appear correct- DCMIPP and USB pipelines run without errors- The camera frame buffer contains all zeros, indicating that the ISP may not be producing valid RGB outputMain Questions1- Is live USB U

Hello everyone, I'm having issues with the Heap of the LWIP that is used/full, and I can't do any mem_malloc. I have dig a bit on why the log of LWIP tells me that  it couldn't allocate memory ("etharp_raw: could not allocate pbuf for ARP request"). As far as i understand, the mem_malloc used the struct mem *lfree variable to handle the allocation for the LWIP and which is the next/previous chuck and also if the next chunk is being used or not.     struct mem { /** index (-> ram[next]) of the next struct */ mem_size_t next; /** index (-> ram[prev]) of the previous struct */ mem_size_t prev; /** 1: this area is used; 0: this area is unused */ u8_t used; #if MEM_OVERFLOW_CHECK /** this keeps track of the user allocation size for guard checks */ mem_size_t user_size; #endif };     My issue is that the variable used in the mem struct is never null or zero. Which lead to the mem_malloc to always return NULL even after a fresh upload or power

LINK TO THE CODEHello everyone,I'm working on a data logging project using a NUCLEO-L432KC board and a standard Micro-SD card module.I have a very frustrating issue: Reading from the SD card works perfectly, but Writing fails immediately.Hardware Setup:MCU: STM32L432KC (Nucleo-32 board)SD Module: Generic MicroSD Card Module (with 5V to 3.3V regulator and level shifter).Power: Module is powered via the 5V rail from the Nucleo. I added a 1000µF / 25V electrolytic capacitor in parallel on the breadboard to prevent any power drops (brown-outs) during write operations.Pinout: * SCK: PB3MISO: PB4MOSI: PA7CS: PB6 (Software managed)Software / CubeMX Setup:Library: FatFS R0.12c (via STM32CubeIDE).FatFS Config: _FS_READONLY = 0 (Disabled), _FS_LOCK = 0.SPI Config: MSB First, CPOL Low, CPHA 1 Edge, Baud Rate 125.0 Kbits/s for init.GPIO: SPI pins are set to "High" output speed.The Problem:My code successfully initializes the SD card. f_mount returns FR_OK, and f_getfree correctly reports the total

I am using below component tools MCU: STM32H750IBT6 IDE: STM32CubeIDE Version: 1.20.0 GUI: TouchGFX Version: 4.26.0 SDRAM: IS42S32400J-6TLI FLASH: MT25QL512ABB8ESF-0SIT (QUADSPI) QUADSPI With the following pin out:   QUADSPI Configuration:   Thank you in advance!  

I'm currently using an STM32H7S78-DK, and I'm correctly able to run TouchGFX with FreeRTOS and everything. I also an error handler function that, in case of a crash of TouchGFX it writes directly to the framebuffer.Now, I would like to do a similar thing but on the boot code, so basically before the classic jump if (BOOT_OK != BOOT_Application())I have an external RAM mapped at the address 0x90000000 which works correctly in TouchGFX with .icf likedefine symbol __region_EXTRAM_start__ = 0x90000000; define symbol __region_EXTRAM_end__ = 0x91FFFFFF; define region EXTRAM_region = mem:[from __region_EXTRAM_start__ to __region_EXTRAM_end__]; place in EXTRAM_region { first section TouchGFX_Framebuffer , section Video_RGB_Buffer , section Nemagfx_Stencil_Buffer };I wanted to use the same section of memory in the Boot, accessing the framebuffer directly, so I edited the .icf of the boot withdefine symbol __region_EXTRAM_start__ = 0x90000000; define symbol __region_EXTRAM_end_

Hi,I just wanted to check if is it dangerous to move the isr_vector inside the text section like this:.text :{. = ALIGN(4);KEEP(*(.isr_vector)). = ALIGN(4);FILL(0x00000000);. = ALIGN(4);*(.text) /* .text sections (code) */*(.text*)*(.glue_7) /* glue arm to thumb code */*(.glue_7t) /* glue thumb to arm code */*(.eh_frame)KEEP (*(.init))KEEP (*(.fini)). = ALIGN(4);_etext = .; /* define a global symbols at end of code */} >FLASHI implemented a CRC32 integrity check and it doesn't work because the gap between the isr_vector and text section is always Fs when I debug with the CubeIDE, but if I download the .elf with CubeProgrammer, the gap is filled with 0s, and in that case it works.TY for your help.

Hi everyone,I am trying to get a USBX CDC ACM device running on an STM32F407ZGT6, using a project generated by STM32CubeMX. I'm basing my work on the example provided for the STM32F469 (DEVICE_CDC_ACM).Problem DescriptionThe device is partially working. When I plug it in, Windows Device Manager recognizes it and assigns a COM port. However, when I try to connect using any terminal software (Tera Term, PuTTY, etc.), the connection fails. The software cannot open the port.Debugging FindingsThrough debugging, I've identified a key issue in the initialization sequence:Instance Activator Not Called:​ The callback function I set for cdc_acm_parameter.ux_slave_class_cdc_acm_instance_activate(which is CDC_Init_FS) is never triggered. This prevents the proper initialization of my CDC ACM instance.Null Pointer in Thread:​ The usbx_cdc_acm_read_thread_entryfails because it encounters a null pointer. Specifically, the comparison ux_utility_memory_compare(data_interface->ux_slave_interface_class