A recent project required the use of an embedded system. Considering that image recognition will be required in the future, Jetson nx was chosen as the hardware. After buying it, I did some development. Later, I hoped to develop using remote development methods, so I tried two of them.
X display：
Jetson NX originally comes with ssh. You don’t need to install it on the client to directly install putty xshell and other ssh terminal software to connect. If you need x display, you need to make some settings;
sudo apt install xorg //install x11
sudo apt install tightvncserver //Install vnc server
Install xming on windows 10, and then connect with putty.
Set up putty Putty There is an X11 in the ssh option. To select it, fill in localhost: 0.0 under
Putty has problems connecting:
1） failed to connected to X dispaly ；
Solution: run xming first;
2） X11 connection rejected because of wrong authentication.
Authentication problem: The reason is that Xauthority changes after you switch users or change user permissions, causing confusion;
Solution: In the root directory of the login account
The ll -x command finds Xauthority, etc., if found, use rm -fr .xauthority*
reboot
Just reconnect.
Configuration file problem
Workaround: sudo vim /etc/ssh/sshd_config
Modified in the file to be available: x11forwarding yes
Usage effect: Using qtcreator within the local area network is very slow to develop, and there is basically no development significance. It is used for remote graphics setting parameters;
Remote Desktop:
There are many remote desktop programs, such as vnc, etc. Because Windows 10 is used as the client, remote desktop can be used directly.
sudo apt install xrpd (nx comes with it already installed. For xrdp settings, please see the article ubuntu, jetson nano remote desktop xrdp configuration tutorial_Guo Qingru's blog-CSDN blog_ubuntu xrdp configuration )
Set the account for authentication: sudo adduser yourname ssl-cert
Open the built-in remote desktop connection on Windows 10 and enter the IP account password
Problem: crash
Reason: Logged in with the same account on Jetson;
Solution: Add an account on Jetson and add authentication to the account;
Evaluation effect: Log in as an account, and the interface is displayed; if used, you need to log in with root on Jetson. Then the client logs in with its own account. The whole screen freezes. It is also problematic for remote graphics development. Exiting the remote desktop will also cause some other problems for Jetson, such as being unable to enter the terminal, sometimes causing a blue screen, etc.
Others: Have not tried other methods of remote desktop