# ttyTHS0 uart communication problem **URL:** \ **Category:** Jetson Xavier NX\ **Tags:** uart\ **Created:** [March 5, 2021, 8:40am UTC](https://forums.developer.nvidia.com/t/ttyths0-uart-communication-problem/170132 "2021-03-05T08:40:12Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![axililsz](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@axililsz](https://forums.developer.nvidia.com/u/axililsz)\ **Post date:** [March 5, 2021, 8:40am UTC](https://forums.developer.nvidia.com/t/ttyths0-uart-communication-problem/170132/1 "2021-03-05T08:40:12Z")
hello，I set up the a system to collect MCU information through serial port, whitch’s name is “/dev/ttyTHS0”, but I can’t read any data. The system is connected directly to the MCU through a serial port. The MCU serial port configuration is as follows. ![MCU serial configuration](https://global.discourse-cdn.com/nvidia/original/3X/7/9/793241db872b2bbad52b8477c8d372aca2d2f638.png) The “/dev/ttyTHS0” configuration is as follows. stty -F /dev/ttyTHS0 -a speed 115200 baud; rows 24; columns 80; line = 0; intr = ^C; quit = ^; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = ; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0; -parenb -parodd -cmspar cs8 -hupcl -cstopb cread clocal crtscts ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8 -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke -flusho -extproc ---
**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\ **Post date:** [March 5, 2021, 7:25pm UTC](https://forums.developer.nvidia.com/t/ttyths0-uart-communication-problem/170132/2 "2021-03-05T19:25:41Z")
Although `ttyTHS0` could be set up as a serial console in Linux, I would be surprised if it works in prior boot stages since those stages only have the legacy driver (which would use `ttyS0`, but be the same physical UART). However, one glaring problem which shows up is that your windows terminal setup is showing “`Baud rate: 460800`”, and it should be `115200`. ---
**Author:** ![axililsz](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@axililsz](https://forums.developer.nvidia.com/u/axililsz)\ **Post date:** [March 6, 2021, 3:37am UTC](https://forums.developer.nvidia.com/t/ttyths0-uart-communication-problem/170132/3 "2021-03-06T03:37:43Z")
> [@linuxdev](#): > > legacy Sorry, I posted the wrong picture. In fact, the MCU serial port configuration is as follows. The baud rate is “115200”. ![MCU serial configuration](https://global.discourse-cdn.com/nvidia/original/3X/9/e/9e5263a5fd4ce7afa23acfe826e92f4209aa3643.png) ---
**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\ **Post date:** [March 6, 2021, 5:11pm UTC](https://forums.developer.nvidia.com/t/ttyths0-uart-communication-problem/170132/4 "2021-03-06T17:11:33Z")
If the port is correct, and if the UART is using 3.3V TTL logic level, then the above should work. You might try with XON/XOFF flow control (software only flow control), but I suspect if it were a software flow control problem, then you’d at least have seen some activity and it wouldn’t be completely blank. If you happen to have an oscilloscope, then perhaps you could watch the RX and TX wires to see if it has a 3.3V square wave during times you expect data. ---
**Author:** ![nadeemm](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/nadeemm/32/367020_2.png) [@nadeemm](https://forums.developer.nvidia.com/u/nadeemm)\ **Post date:** [October 18, 2021, 6:41pm UTC](https://forums.developer.nvidia.com/t/ttyths0-uart-communication-problem/170132/5 "2021-10-18T18:41:54Z")