STM32 MCUs Embedded software

Dear all,we're creating a camera application and have successfully run and modified some of the demos available. ( State at time of writing: 800x600 30 fps full-frame encoding to SDCard).We have full-frame double-buffering code running but this is consuming extensive memory; from the documentation I saw that there is a hardware-linked mode available chaining DCMIPP and VENC cores. From the code, I see there is one implementation in VENC_USB example.The camera and venc middlewares on github miss the slice aka "HW Handshake mode" so I wonder which code-base is recent and will be supported in the future, especially as CubeMX does not (yet) support VENC configuration.We're trying to go beyond a proof of concept, so I'd like to base our project on a maintained code-base but that is hard to spot, could you give some indications?Many thanks,Simon  

As mentioned in the title already, the file core_cm4.h is not contained in the recent version of  https://github.com/STMicroelectronics/STM32CubeG4 anymore.Selecting the v1.6.1. in that repo the file is contained. Looks like there was an error genererating the new version.

Hi,programing NBOOT_SEL and WRP in the firmware leads to strange behavior of the MCU. After running the code below and reseting the MCU, I can still debug with CubeIDE to some extent by connecting without downloading the firmware, but I can only see that the MCU is stuck in a hard fault. CubeProgrammer cannot read either flash or option bytes. If I try to reset the option bytes anyway, I lose the connection to the MCU completely and it is no longer recognized by CubeProgrammer.The behavior is not always the same either. On my first attempt, I was able to debug the code several times and see that it works correctly in principle. Resetting the WRP with CubeProgrammer also worked. However, I have now lost my second MCU.I develop a minimal bootstub for STM32C011J6 and therefore do not use the HAL. Is there an error in the code, that can lead to such a behaviour?  Thank you in advance for any hints or guidance. typedef struct { volatile uint32_t ACR; uint32_t RESERVED1; vo

I have developed a custom board for STM32F469NIH6 and is loosely based on STM32F469i-DISCO, it uses an external QSPI Flash memory type MT25QL128A as does the DISCO board. For this setup I am using ST supplied external loader MT25QL128A_STM32F469I-DK.stldr which works fine.We have a requirement for a processor with a video codec, so the logical upgrade route is to STM32F769NIH6 to be used with external QSPI flash MT25QL512A. Both of these devices are pin compatible with the above MCU and QSPI, so the plan is to use the same custom PCB.The problem comes in writing an external loader for this combination because.While ST have a loader MT25QL512A_STM32769I-EVAL.stldr, this loader is not working in our setup, probably because of alternative QSPI I/O configuration which would likely be easy to alter in the loader code, however the source code is not in the github repository https://github.com/STMicroelectronics/stm32-external-loaderIs it available elsewhere?UM0892 says that the ST loade

Hello STM32 friends!I've previously used USB on an STM32G474RET6, and it was initialized with the function:MX_USB_Device_Init()The goal is to use it as a USB serial port to communicate with my device, and that worked.Now I'm using the STM32U5G7VJT6, and this time, the USB is initialized with the function:MX_USB_OTG_HS_PCD_Init()But this function hangs.I've enabled USB interrupts in the STM32CubeMX, but that doesn't help.I haven't been able to isolate the problem yet, but it's probably something very simple.Is this another new USB library?As requested, I attached my IOC file.What could be the problem?Sincerely, Jack

I'm still working my way around the DMA learning curve.  Having found the IOC approach to DMA configuration too confusing, I'm configuring the structs and calling the HAL_DMA_Init(...) method myself.Something I haven't been able to find clearly described is the "TransferAllocatedPort" field of the DMA_InitTypeDef struct.  I understand that it's there to specify source/destination port0/port1, but I don't understand the significance of that selection.One blog post I found seems to say that having two ports allows the DMA peripheral to assemble or disassemble transfers when source and destination have differing alignments.  Okay, I understand that explanation, but is that a correct explanation?If my source and destination have the same alignment, can (or should) I assign the same port to both?  Is there any advantage or disadvantage?  Since a "channel" is devoted to a particular path and direction, I wouldn't think the unused port would be useful for anything els

Hello, I am using a NUCLEO-H7A3ZI-Q to send and receive packets over serial. I have a varying payload size, so I am using: HAL_UARTEx_ReceiveToIdle_DMA(&huart3, rx_buffer, 4096); as this searches for an idle at the end of the frame to begin processing this data. To process this data and copy it into a look up table (LUT)  capable of being 0-4096 bytes long I have this following script; which comprises two uint8_t into one uint16_t to be represented by a 12-bit DAC, hence the clipping if they exceed 0FFF (4095).This receives and writes perfectly up to 512 bytes of memory (256 uint16_t within the LUT), however above this all remaining values in the LUT are left unpopulated. uint16_t length = 0; void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t size){ if (lut != NULL) { HAL_DAC_Stop_DMA(&hdac1, DAC_CHANNEL_1); free (lut); lut = NULL; } if(rx_buffer[0] == 0XAA) { length = rx_buffer[2] | (rx_buffer[1] <<8); frame_rate = rx_buffer[3

Hello, I am having a issue with HAL_UARTEx_ReceiveToIdle_DMA on a NUCLEO-H7A3ZI-Q, when using the following code:uint8_t rx_buffer [4096]; HAL_UARTEx_ReceiveToIdle_DMA(&huart3, rx_buffer, sizeof(rx_buffer)); void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t size){ /*code*/ } My rx_buffer is only populating the first 512 bytes, with the remaining data remaining as 0.__HAL_DMA_GET_COUNTER(huart3.hdmarx);Provides the incorrect amount of data being passed over serial.I have used serial plotter and CoolTerm to try and send packets but both hit this 512 byte limit.rx_buffer not populated past 512 byteslength correctly calculated as 640 bytes long

Hello,I’m trying to add the JPEG encoder to be able to save images in JPEG format to the SD card.While debugging with LEDs, I noticed that MX_JPEG_Init blocks the program, whereas HPDMA is working correctly.I have added all the necessary files for JPEG, but it doesn’t seem to activate.Interestingly, when I disable MX_JPEG_Init, I can see the images on the screen connected to the board without any issue.I’m wondering if there is a configuration problem with the JPEG or if I’m missing something.For reference, I’m using the STM32N6 Discovery Kit (STM32N6DK750).Thanks for any advice!

I am using the STM32N6570-DK and I want to use the external PSRAM to declare a large variable buffer. Here is what I have done: 1. Initialized XSPI1 and the External Memory Manager. The PSRAM parameters I got from How to execute code from the external PSRAM using the STM32N6 . 2. Set the XSPI1 clock to 200MHz. Here is my system clock configuration:    Here is my main code from the FSBL. I also added a `gpio_toggle` to turn the user LED on before `MX_EXTMEM_MANAGER_Init()` as a debug indicator.After adding the header and programming, the FSBL boots correctly — the user LED turns on — but then it gets stuck at `MX_EXTMEM_MANAGER_Init()` and never jumps into the `while` loop.int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MPU Configuration--------------------------------------------------------*/ MPU_Config(); /* Enable the CPU Cache */ /* Enable I-Cache---------------------------------------------------------*/ SCB_EnableIC

Hi,I am trying to get any communication with the source through VDM messages on my STM32G071RB + SNK1M1 setup and I am not able to. The source sends a request "VENDOR_DEFINED VDM:SVDM_DISCOVER_IDENTITY INIT" but PE on the sink responds with PE_SEND_NOTSUPPORTED. Power delivery works fine and manages to negotiate different power options.The code is generated with CubeMX following this step-by-step guide: https://wiki.st.com/stm32mcu/wiki/STM32StepByStep:Getting_started_with_USB-Power_Delivery_Sink I followed the manual (https://www.st.com/resource/en/user_manual/dm00598101-managing-usb-power-delivery-systems-with-stm32-microcontrollers-stmicroelectronics.pdf) chapter 4.5 and enabled these VDM features.To implement the VDM callbacks and some DPM callbacks I used this repo: https://github.com/STMicroelectronics/STM32CubeG0/blob/master/Projects/STM32G0C1E-EV/Demonstrations/Modules/ucpd/I am aware that there isn't sufficient hardware support for alternate modes on my current hardware but sh

Hi all,I’m using STM32H755 on a Nucleo board with FreeRTOS, the socket-API and CubeMX-generated LWIP. Sending a UDP packet immediately after network init works fine, but if I wait ~10 seconds before calling sendto(), it returns successfully, DMA descriptors OWN=0, ETH IRQs are triggered, yet no packet reaches the wire. Calling sys_check_timeouts() before sendto() does not help. The tcpip_thread has high priority, while the sender task runs at IDLE priority. In my tests, I disabled the Cache.It seems the issue is not PHY or DMA. It seems that sendto() copies data to the LWIP buffer, but the tcpip_thread does not process it after a long idle. How can UDP packets be reliably sent after idle without changing the network stack or manually triggering anything?Thanks for any insights!

Hi, I'm following the "Programming guidelines for IEEE 1588 timestamping" from page 2792 of the RM0481. I've been working on this specifically for quite a while and I cannot even get the timestamp nanosecond or second registers to move. It feels to me like a clock issue, but unless I'm mistaken, the PTP clock (clk_ptp_ref_i from the manual(p.456)) is the same as the ETH clock (PLL1Q), which I've verified is running because I'm successfully using NetXDuo to negotiate DHCP and send/receive UDP packets successfully. I've also tried initializing the PTP Timestamp without NetXDuo just in case there was some conflict there, but that was also unsuccessful.  Here is my initialization code: /*1. Mask the Timestamp Trigger interrupt by clearing bit 12 of Interrupt enable register(ETH_MACIER).*/ ETH->MACIER &= ~(ETH_MACIER_TSIE); PRINT_U32_BINARY(ETH->MACIER); // 2. Set bit 0 of Timestamp control Register (ETH_MACTSCR) to enable // timestamping. ETH->MACTSCR |= ETH_MACT

I created an issue on github here,  but wanted to post here as well for visibility.Copied below are the details of this linked content: Describe the set-upCustom hardware for our internal product.STM32L496.HAL version 1.13.5.2 devices on I2C bus, HTU21D and PCA9535.Describe the bugSome processors through our production have been coming across errata 2.19.4:   The HAL does not seem to address this errata and the timing for I2C transactions begin failing after the bus error occurs.Sometimes it has led to the I2C bus locking up because the components on the bus (besides the processor) are stuck waiting for a transaction to finish (the device responds properly with ACK/NACK or correct data when the bus error occurs). We have created some messy workarounds that do not fully solve this issue.Additional contextThe following is a diff of the changes I made to address the problem:diff --git a/STM32L4xx_HAL_Driver/Src/stm32l4xx_hal_i2c.c b/STM32L4xx_HAL_Driver/Src/stm32l

I want to implement a USBPD sink application with a 9V PDO and I am struggeling to set up a PD-contract with a source. I am using following components:STM32G0B1 MCUTCPP03-M20 PD controllerMy project is based on this example: https://github.com/STMicroelectronics/x-cube-tcpp/tree/main/Projects/NUCLEO-G071RB/Applications/USB_PD/DRP1M1_DRPX-Cube-TCPP v4.1.0 When I attach a PD-source, the DPM_Params[_port].PE_IsConnected variable is successfully set.After that I get in USBPD_DPM_Notification a USBPD_NOTIFY_POWER_STATE_CHANGE event and afterwards a USBPD_NOTIFY_HARDRESET_TX event.I also notice that I do not receive a message within PORTx_IRQHandler, as I do not jump intoif (UCPD_SR_RXMSGEND == (_interrupt & UCPD_SR_RXMSGEND))…Do you have any tips for me where I can start looking for my missing piece? Did i initialize something wrong?

Bonjour,J'utilise la suite CUBEMX et CUBEIDE  pour créer mon projet à partir d'une carte de développement NUCLEO-U575ZI-Q.J'ai réalisé mon projet sur CUBEMX en gardant et validant le BSP de la NUCLEO pour utiliser les leds et surtout le debug via ST-LINK embarqué.J'ai ajouté des IO pour effectuer une maquette avec SPI1 et OCTO-SPI1 plus quelques IO notamment une PWM.Pour commencer j'ai d'abord réalisé un bout de code pour faire clignoter une led (LED_GREEN); à une certaine fréquence réglée par HAL_Delay.Le souci est que cette fonction bloque car le Tick ne semble pas être validé, (HAL_GetTick  me retourne toujours 0)...Je crois pourtant avoir validé les interruptions :Hello,I am using the CUBEMX and CUBEIDE suite to create my project based on a NUCLEO-U575ZI-Q development board.I created my project on CUBEMX, keeping the NUCLEO BSP to use the LEDs and, above all, debugging via the embedded ST-LINK.I added I/Os to create a model with SPI1 and OCTO-SPI1, and a few I/Os, includi

Title edited - originally said, "sharing data between two boards"Good day y'all,I'm trying for the first time to have the two cores on a H7 board share data between one another on shared memory, in particular cm7 writing data and cm4 read it. From what I understand I need to use a semaphore to signal back and forth to alert the cm4 when there is new data in every iteration, the theory I get, but I'm not sure of the shared memory allocation and the semaphore correct availability. Is there any example code I can see to understand how it's supposed to go? I tried looking at the ide examples, but anytime I try to open the example folder the ide application just dies :\ Thx all for the advices, P.S. I'm also using FREERTOS but it's not supposed to cause any problem but you never know 

Hello, I've been following closely with the github while I work on the recording portion myself, and I saw that x-cube-azrtos-h7 was updated today.  I immediately looked for the recording project, and couldn't find it. Even this page shows up Error 404: https://github.com/STMicroelectronics/x-cube-azrtos-h7/tree/main/Projects/STM32H743I-EVAL/Applications/USBX/Ux_Device_Audio20_Recording Do I not have access to it?

I am testing Ethernet on STM32H723ZGT6 by transmitting UDP packets (1024 bytes) every 1 ms. Setup / Implementation: No CubeMX / HAL used Fully bare-metal Ethernet driver (lwIP integrated manually) Ethernet interrupts enabled and serviced RX handled inside while(1) loop Non-blocking transmit path MPU enabled Memory configuration: RX pool located in AXI RAM lwIP heap: 32232 bytes in D2_SRAM Observed Behavior: System runs normally for many hours (sometimes >12 hours) Eventually UDP transmit stops working Ping continues to work without issues Debugging shows failure occurs at: pbuf_alloc(PBUF_TRANSPORT, len, PBUF_RAM); After failure: 1) pbuf_alloc() returns NULL (ERR_MEM) 2) ETH->DMACSR reads 0 while (1) { sys_check_timeouts(); if (eth_rx_rdy) { eth_rx_rdy = 0; ethernetif_poll(&gnetif); ETH->DMACIER |= ETH_DMACIER_RIE; } if (sys_now() - udp_tx_timer >= 1) // 1 ms transmit interval { ret = udp_server_send(udp_tx, sizeof(udp_tx)); if (ret

Hi everyone,I am experiencing a strange discrepancy in the behavior of HAL_UARTEx_ReceiveToIdle_DMA between LPUART2 and LPUART3 on an STM32U083RCT6.Environment:MCU: STM32U083RCT6IDE: STM32CubeIDE v1.17.0Library: STM32CubeU0 Firmware Package V1.3.0 (Released 04-June-2025)The Issue: I am using HAL_UARTEx_ReceiveToIdle_DMA to handle asynchronous reception of variable-length packets.LPUART2: Works perfectly. When an IDLE line is detected, the DMA transfer stops as expected, and HAL_UARTEx_RxEventCallback is triggered.LPUART3: When an IDLE line is detected, the interrupt is generated and HAL_UARTEx_RxEventCallback is triggered correctly. I am able to handle and process the variable-length packets without any issues. However, the DMA transfer itself does not stop (it remains in an active state), unlike the behavior observed on LPUART2.Configuration: Both instances are configured in STM32CubeMX as follows:Baud Rate: * LPUART2: 230400 bpsLPUART3: 115200 bpsDMA: DMA1 [Channel configuration]Mode

Hi,we are trying to get SDMMC1 running on our evaluation boards (STM32H757-EVAL) but without any success so far.To further investigate the issue we started a new project from scratch, using CubeMX with sdmmc1 enabled. It doesn't work neither.btw: board and SD interface are OK. i.e.the demo that came with the board is reading video files from SD card successfully.Please, can someone provide a ruuning setup for Cube-MX (STM32H7 firmware 11 or 12) with the specific settings for Clock Configuration and SDMMC1.We are using CubeMX 1.15, STM32H7 firmware package V. 12.1.The error happens during SD PowerOn(), i.e. there is no response from CMD8, CMD55...Thanks for your helpTom  

I need gateway firmware binary for EU433 + Loriot.for my PNUCLEO LRWAN 3 gateway

I have setup HAL, systems clocks, etc.  ADC 1 & 2 work PC4 (channel 14).  ADC3 with PF3 (channel 9) PF4 (channel 14) or PF5 (channel 15) don't work with the same code.  Port C & F enabled, ADC1-3 clocks enabled. Thanks for your help!   { GPIO_TypeDef *ThePort; int ThePin, TheChannel; ADC_TypeDef *TheADC; ADC_HandleTypeDef hadc; __HAL_RCC_GPIOC_CLK_ENABLE(); __HAL_RCC_GPIOF_CLK_ENABLE(); //PF3 Thermisor ADC3_CHANNEL_9 //PF4 Thermisor ADC3_CHANNEL_14 //PF5 Thermisor ADC3_CHANNEL_15 //PC4 Power ADC12_CHANNEL_14 /* works ThePort = GPIOC; ThePin = GPIO_PIN_4; TheChannel = ADC_CHANNEL_14; TheADC = ADC1; // or ADC2; */ ThePort = GPIOF; ThePin = GPIO_PIN_4; TheChannel = ADC_CHANNEL_14; TheADC = ADC3; // Configure PF3 as Analog Input GPIO_InitTypeDef GPIO_InitStruct = {0}; GPIO_InitStruct.Pin = ThePin; GPIO_InitStruct.Mode = GPIO_MODE_ANALOG; GPIO_InitStruct.Pull = GPIO_NOPULL; HAL_GPIO_Init(ThePort, &GPIO_InitStruct); // Enable ADC3 Clock __HAL_RCC_ADC1_C

Hi all,I am a beginner working with the STM32N6570-DK development kit using STM32CubeMX(V6.16.1) and STM32CubeIDE (v2.0.0). I am looking to deploy an AI model from the ST model zoo and need guidance on the proper configuration for integrating the camera and display modules. Could anyone provide a step-by-step cub MX project configuration for camera and display interfacing. RegardsSradha

HiI am new to display and camera interfacing, as well as the STM32N6570-DK. For a project, I want to display the output from the camera (come along with STM32N6570-DK) into the display included with STM32N6570-DK. Could you explain the necessary configurations in STM32CubeMX and how to write the code in STM32CubeIDE to interface these components?My Tool version infoCube IDE 2.0.0Cube MX 6.16.0Best RegardsRanjith