kywwilson11 opened a new pull request, #16776: URL: https://github.com/apache/nuttx/pull/16776
## Summary stm32_serial.c - 1. Removed incompatible defines left over from STM32L4 implementation. L4 was used as a reference. 2. Removed DMAMAP defines. STM32H5 uses DMA requests. 3. Replaced rxdma_channel with rxdma_req. 4. Other adaptations to work with stm32h5 gpdma driver. Used the STM32H7 serial driver as a reference when developing. stm32_uart.h - Remove warning and allow SERIAL_HAVE_DMA1 to be assigned to 1. stm32h56x_dmasigmap.h - Changed UART10 and UART11 to USART10 and USART11 stm32_dma.c - Added stm32_dmaresidual - This returns the number of beats remaining in the dma transfer. Used in serial dma driver. ## Impact STM32H5 Architecture. Serial Driver and minor changes / additions to GPDMA driver. Note: There is some flow control logic in the dma functions, but that has not been tested yet. A compiler warning will display if CONFIG_SERIAL_IFLOWCONTROL is defined. ## Testing OS: Ubuntu 24.04 Configuration: nucleo-h563zi:nsh + Enable DMA1 + Enable USART3 RX DMA Used RXDMA_BUFFER_SIZE of 32 bytes Admittedly, testing is minimal. The test below is just me typing in characters. After typing every 16 characters, I would see the characters displayed to the screen. This made sense because the buffer was 32-bytes and I am using half transfer interrupts in circular dma mode. I also copied and pasted large sections of text into the console and confirmed they showed up in the console. I also tested by debugging with GDB. I confirmed the dma setup, callback, receive, and supporting functions were all performing as expected. I've attached an image of a call stack to show dmareceive being accessed. If the reviewers have any suggestions for better test methods, I would be interested. ``` NuttShell (NSH) NuttX-12.10.0 nsh> abcdefghijklmnopqrstuvwxyz012345 ``` <img width="546" height="334" alt="Screenshot 2025-07-25 152437" src="https://github.com/user-attachments/assets/eb6d8302-13fa-4ef5-90bc-c4310daf6143" /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org