Stm32 mat target UART example USART_3_Receive_Send, difficulty

[vlal]

I have generated MDK-ARM project from the USART_3_Receive_Send example from stm32 mat target example, I have successfully compiled all and burned to stm32f103 board, when connected to terminal it finds, it is sending unknown chartacters to terminal

I have attached the project files with this message, kindly someone check

[Tesla DeLorean]

What STM32 board?

USART1 PA9 / PA10

Perhaps test the USART functionality outside all the buffering, then debug the rest of it.

[vlal]

Custom STM32 board, I am using

USART1 connected to PA9 PA10

Will test the USART functionality outside buffering and update here

[vlal]

I have tried with USART_3_Receive example, still the result is same

I have used Rx and Tx pins, any other pin needs to be used?

[Tesla DeLorean]

Async serial on USART1 would just need the PA9(TX) and PA10(RX)

If the hardware hasn't otherwise been validated, you might want to sit in a loop transmitting 'U' characters, and scope the signals. PA9 would have the signal, it will be at CMOS levels, and not directly compatible with RS232 levels.

Not familiar with your design.

[vlal]

I have connected PA9(TX) STM32 to FT232 (RX) and PA10(RX) STM32 to FT232 (TX) (No level shifting is done) (Baud-rate 115200)

This setup worked with some programs compiled with mikroC..

I have attached my terminal output..

I will check with the 'U' loop as you advised..

[vlal]

I have tried another character loop in UART

Model that I used to send the character is attached, is it correct?

I intended to send 'U"

[Tesla DeLorean]

Try just coding a simple app, in C, without involving STM32-MAT

[TDK]

Sure seems like a protocol issue. Same baud rate, parity, and stop but settings in your code and in the terminal? If you have a parity bit, you need to set 9 data bits in the code instead of 8.

[vlal]

Yes, it same baud rate 115200, no parity, 1 stop bit

I have changed the data bit 8 and 9 checked, no improvement