2026-04-27 8:12 AM - last edited on 2026-04-30 2:23 AM by KDJEM.1
Hie, according to the documentation of the board, USART1 can be used with db9 port by setting up JP7 and JP8 to 1 and 2 ( which I did). The second thing is to connect usart_tx and usart_rx to PB14 and PB15.
The problem is that nothing is showing up on the pc with DB3 port. I've check the tx port with an oscilloscope and I'm getting signal on data sending but only 1.1 V (in AC). I don't know if it's part of the issue but I hope someone has the solution
Thanks
Solved! Go to Solution.
2026-04-28 7:32 AM
After activating the usart1_de pin, it is now working. I don't know why it was the issue but it has solved the problem.
Thank's you for the help !
2026-04-28 7:41 AM
I don't see "usart1_de" anywhere in the schematics or User Manual ?
2026-04-28 7:44 AM
It is in STM32CubeMx
2026-04-28 7:55 AM
Hello,
@giorgio29 wrote:
After activating the usart1_de pin, it is now working. I don't know why it was the issue but it has solved the problem.
What do you mean by activating USART1_DE pin? Set? Reset?
But USART1_DE alternate function is available only on PA12 but on the board PA12 is connected to FDCAN and USB, no relation with USART1/RS232
I'm not sure USART1_DE pin is the root cause!
2026-04-28 7:57 AM
Oh sorry, that's the usart clock that I activated on PA8
2026-04-28 7:59 AM
USART clock would only be relevant in synchronous mode?
2026-04-28 8:00 AM
Sincerely I don't why it solved my issue
2026-04-28 8:05 AM
As @mƎALLEm said, it looks like this is just a coincidence - not the actual solution to the problem.
The board only uses PA8 as MCO to optionally clock the Ethernet.
But, hey - it's working now!
2026-04-28 8:28 AM - edited 2026-04-28 8:30 AM
@giorgio29 wrote:
Oh sorry, that's the usart clock that I activated on PA8
USART1_CK is used in synchronous mode while you are using asynchronous mode.. I don't see the relevance of activating USART1 clock output here.. Moreover PA8 is floating (MCO output to a board connector) on the board no relation to USART1/RS232 hardware!
To me the root cause is not identified yet..