[Bug]: The LoRaWAN middleware uses USART DMA for trace

[shiwzhi]

Bug Summary

If DMA TX request for USART not configured there will be no output from console

Detailed Description

I was trying to test End Node LBM skeleton, I've configured ADC, RTC, USART, SUBGHZ and LoRaWAN middleware, and there was no output from console, the generated usart_if.c uses vcom_Trace_DMA for trace, if DMA for USART not configured there will be no trace output.

Expected Behavior

No response

Actual Behavior

No response

Environment

STM32CubeMX, STM32CubeIDE for VSCode, STM32CubeWL v1.5.0

Severity

None

[ASAHSTM]

Hello @shiwzhi,

Thank you for your report.

This behavior is consistent with the current implementation. When trace output is handled through vcom_Trace_DMA, data is transmitted over UART using DMA mode. Therefore, the UART TX DMA must be properly configured; otherwise, it is expected that the transfer will not work.

For reference, you can check the example LoRaWAN_End_Node_LBM, which includes the required DMA configuration for USART2: the USART2 TX DMA is initialized in usart.c, the DMA handle is linked to the UART in usart.c, and the DMA interrupt is enabled in dma.c

With Regards,

[ASAHSTM]

Hello,

Any update please?

With Regards,