Timeline for Unable to display UART character data sent from STM32F407G Discovery Board (TX) to Ubuntu(or Raspian) on Rasperry Pi 3 Model B (RX)
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2021 at 6:48 | comment | added | Marcos G. | minicom...will auto adjust the baud rate...; are you sure you are not confusing it with something else? The one I have does not have any auto baud rate detection. | |
| Apr 6, 2021 at 3:13 | comment | added | cyber101 | 1) The definitive answer was MarcosG's loopback test that identified a faulty UART on my Pi. When Swiped my Pi with another Pi everything worked. Another smaller issue was extra "\n" in C's console output. However, I still appreciate the wisdom. Any thoughts on how STM to Pi communication over UART may go wrong in the production system (mission-critical) application? Strictly focusing on the UART aspect. | |
| Apr 6, 2021 at 3:07 | comment | added | cyber101 | appreciate the input all the things you mentioned I had already tried in the original post. I have already posted the solution. The problem as 1) faulty Pi UART 2) small bug in the C's console print logic. | |
| Apr 5, 2021 at 20:25 | history | answered | Voltage Spike♦ | CC BY-SA 4.0 |