Hi. So the long story short:
I use Nano as a logic centre for a few microcontrollers, for testing and self-studying processes. So I’ve decided to connect them by UARTS. Luckily, Nano has enough.
Custom application on Linux starts with sending a request via ttyTHS2 to STM32 for any data;
STM32 sends whatever it has, in a loop;
When the data arrives, Nano checks the ttyTHS2 port, but it is stuck expecting at least something.
I`ve checked all cords with FTDI, so I am sure the data comes as supposed. Turned out incoming data comes to the ttyTHS1 for some reason!
The second misunderstanding occurred when I decided to reconnect STM to ttyTHS1 alone. For some reason, Nano got stuck in the reboot sequence until all cords are disconnected from UART1(ttyTHS1).
ve been searching for a solution for a while, so Im leaving as much info as i can anticipate your requests.
Nano DEV kit (jetson-io-base-A)
Ubuntu: 18.04.6 LTS
Yes, i have used:
“system stop nvgetty.services”
“system disable nvgetty.services”
I checked nvgetty with “system status nvgetty.services” → Inactive as the result. Moreover, i changed in /nvgetty.sh line with ttyTHS1 to ttyTHS0;
“dmesg | grep THS” shows a completely usual picture:
“ls -l /dev/ttyTHS*” shows:
Yes, my account “dev” has access to “dialout” and “tty” groups;
Application: ports init works fine. I have made a lot of error handlers with custom print() so I am sure this behaviour wasn`t my fault;