How to Set Static IPs using Command Line on Jetson AGX Xavier?

What is the proper way to configure static IPs for the Ethernet ports on a Jetson AGX Xavier using the command line? (My Jetson is headless, so GUI tools are not an option.)

Background:

  • My Jetson is running Ubuntu 18.04.
  • Contrary to the Ubuntu documentation, /etc/netplan/99_config.yaml does not exist.
  • etc/network/interfaces does not exist either.
  • I am able set set a static IP on one Ethernet port using the initial setup wizard which runs after flashing, however, I don’t know where this info is being stored so I can configure other ports

Thanks for your help!

Even using ifconfig can set the ip.

ifconfig eth0 172.16.25.125 netmask 255.255.255.224 broadcast 172.16.25.63

Also, I am not sure why there is no “etc/network/interfaces” on your side. If this is really our jetpack release, then it shall be there by default.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Getting Started with Jetson Xavier NX

Learn how to set up the new nvidia jetson™ xavier nx and install everything you need to use the full power of this tiny ai-ready embedded board..

set static ip jetson xavier

Prerequisites

  • Ubuntu host PC
  • Jetson™ Xavier NX Dev Kit with 30W power supply (recommended)
  • Display with HDMI input
  • Keyboard and mouse
  • Internet connection through Ethernet cable or USB Wi-Fi adapter

Flashing the OS Image

To setup the Jetson™ Xavier NX, you need to flash the Xavier NX kit with the latest version of the linux4tegra operating system (an Ubuntu derived OS) and install NVIDIA® drivers and libraries.

Install NVIDIA SDK Manager

  • Download NVIDIA® SDK Manager .
  • From a terminal, install the Debian package:

where [version] , [build] and [arch] represent the current version, the build number and the architecture of SDK Manager (e.g. sdkmanager_1.1.0-6343_amd64.deb ).

Run NVIDIA SDK Manager

When the installation is complete, start the SDK Manager from the Ubuntu launcher, or using the command:

Select the NVIDIA DEVELOPER tab, enter your developer credentials and click Login .

set static ip jetson xavier

Select your Development Environment

STEP 01 lets you select the board to flash, the version of the operating system and additional SDKs to be installed.

  • Click on “Target Hardware” and select “Jetson Xavier NX” from the list.
  • Click on “Linux” and select the latest version of operating system to install (e.g. “Jetpack 4.4 DP”).
  • Eventually select additional SDKs if you plan to use them

set static ip jetson xavier

Review Target Components

Review the components that will be installed on your system. We recommend installing Jetson SDK Components along the OS on your Xavier NX. You can also change the “Download folder” and “Target HW image folder”.

Accept the terms and conditions and click on CONTINUE TO STEP 03 to start the OS flashing process.

set static ip jetson xavier

Note:   We faced issues when using an external USB storage for the   “Target HW image folder” , so we suggest to use a folder located on the host internal storage.

Launch the Jetson OS Install

Before the installation can begin, you will need to enter your sudo password. The SDK Manager will then display the progress of the download and software installation.

At the top, you can toggle between the  Details  and  Terminal  tabs. The Terminal tab shows detailed information about the download and installation, highlighting errors (if any).

set static ip jetson xavier

Hardware Setup

The SDK Manager opens a dialog when it is ready to flash your target device. A prompt provides instructions for preparing your device to get it ready for flashing.

Connect a Micro USB cable to the USB connector.

set static ip jetson xavier

Insert a jumper to connect the PINs #9 and #10 of the connector J50 just under the Xavier NX module to Force Recovery on boot.

set static ip jetson xavier

Insert a jumper on the connector J48 (behind the power jack connector) to enable the power jack.

set static ip jetson xavier

Connect the USB cable to the host PC and insert the power jack to power on the Xavier NX board.

set static ip jetson xavier

The flashing process starts automatically.

After the SDK Manager completes the flashing process, you must remove the jumper on the PINs #9 and #10 of the connector J50 to be able to boot the Xavier in normal mode.

Connect an HDMI display, an USB keyboard and an USB mouse to the Jetson™ Xavier NX.

Now you can unplug and replug the power jack to restart the board and start configuring Ubuntu.

Note:   Do not close the SDK Manager, you will need it for the last step.

Ubuntu Initial Configuration

After the Jetson™ Xavier NX boots up for the first time, it will start system configuration as a common Ubuntu installation.

  • Accept the EULA license.
  • Choose language, keyboard and time zone.
  • Choose a username/password.

Jetson SDK Components Installation

If you selected to install Jetson SDK Components, follow the step below to complete the installation.

  • Go back to the SDK Manager and enter the username and password you chosen in the previous step while configuring Ubuntu on the Xavier NX board.

Make sure that the microUSB cable is still plugged between the host and the Xavier NX, that way a virtual ethernet connection is created and the host can directly communicate with the board to continue the installation process.

The IP address of the board is 192.168.55.1, the host will get the default IP address 192.168.55.100.

  • Click Install and wait for installation completion.

Now you can close the SDK Manager and start using your Jetson™ Xavier NX board!

Enable Maximum Performance

If you are using at least a 20W power supply and want to have access to the full power of the Jetson™ Xavier NX, you can enable the Max performance model:

This will maximize the performance of your application at the expense additional power consumption.

Troubleshooting

Jetson™ Xavier NX shuts   down   as soon as my app opens the ZED camera .

This is also a power-related issue. Make sure you are using a DC power jack with 12V 2A power (3A or more is recommended). You can also use this command to enter low-performance mode and reduce power consumption:

Adding a ZED camera

set static ip jetson xavier

Your Jetson Xavier NX will need an Internet connection to install the ZED SDK as it downloads a number of dependencies. You can use an Ethernet cable or the included Wi-Fi adapter.

Download the  ZED SDK for Jetson Xavier NX  and install it by running this command and following the instructions that appear:

NVIDIA Jetson AGX Xavier Setup

Introduction

Recently, I got an NVIDIA Jetson AGX Xavier Developer Kit . It turns out that setting up Jetson AGX Xavier is slightly more complicated than setting up Jetson Nano.

In this blog post, I would like to discuss some of the notes and the caveats that I found when I was setting up the device.

NVIDIA SDK Manager

The JetPack SDK and L4T OS can only be installed via NVIDIA SDK Manager. The SD Card image method is not supported for Jetson AGX Xavier.

We have to use a Ubuntu 16.04 LTS or Ubuntu 18.04 LTS machine to install NVIDIA SDK Manager. As of March 23rd 2021, Ubuntu 20.04 LTS is not supported by NVIDIA SDK Manager.

There are few available ports. It is thus recommended to have a USB-C hub.

Display Output

It only has a HDMI output port and no DP output port. Be prepared to have a HDMI to DP connector if the monitor only accepts DP cable. Some USB-C hubs have DP output port as well.

There is no on-board WIFI. It is recommended to prepare a USB WIFI adapter. After the USB WIFI adapter is connected to Xavier, we might have problem SSH to Xavier over WIFI. sudo apt-get update && sudo apt-get upgrade -y should solve the problem if the USB WIFI adapter is supported by the OS.

External Hard Drive

Be prepared to have an external hard drive, as there is only 32GB storage space on the device.

Power Model

Jetson AGX Xavier supports different power models. The default 15W model is the most suitable for usages with display. To switch power models, we have to run nvpmodel .

The power model IDs are explained on the L4T guide.

WIFI Connection Dropping Problem

My Edimax rtl8192cu USB WIFI chipset does not work very well with the L4T OS, as it drops quite frequently and it will not reconnect.

It looks like that it is not the power management problem.

After some quick googling, I found it is possible that the rtl8192cu Linux driver is problematic. I disabled the driver by running the following command.

After reboot, we found that the legacy universal driver rtl8xxxu is being used instead.

Although the bit rate becomes much slower, the connection is quite stable.

Enable WIFI at Startup

Because we often want to work with Jetson AGX Xavier headlessly, it is necessary to SSH to Xavier over WIFI at startup. However, the WIFI is not enabled at startup by default.

To enable the WIFI at startup, in the Network Connections , we have to make sure that options Automatically connect ... and All users may connect ... are checked.

  • Raspberry Pi rtl8192cu Driver

https://leimao.github.io/blog/NVIDIA-Jetson-AGX-Xavier-Setup/

Licensed under

Like this article support the author with.

  • 1 Introduction
  • 2.1 NVIDIA SDK Manager
  • 2.2 USB-C Hub
  • 2.3.1 USB WIFI
  • 2.4 External Hard Drive
  • 2.5 Power Model
  • 3.1 WIFI Connection Dropping Problem
  • 3.2 Enable WIFI at Startup
  • 4 References

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

  • Notifications

Instructions and resources on preparing and using Nvidia Jetson Xavier NX for deployment

Nommas/nvidia-jetson-setup

Contributors 2.

  • Shell 100.0%

A site for solving at least some of your technical problems...

The Linux Page

Unix Commands to remember by heart date; touch; unzip; strip; finger; ifup; mount; make love; dig; gasp; yes; uptime; ifdown; file;

  • Pronounce it right!
  • The Fox Trot story of Bill Amend

Setup static network on the Jetson TX2

My Jetson TX2 see from the top, the area with the heat sink and the fan is the actual Jetson card.

Introduction

I just received my Jetson TX2 so I had to test it!

First I needed to setup the network since by default it wants DHCP which I don't allow by default on my server.

Since it's running Ubuntu, I thought it would be dead easy, but I ran in two interesting settings I hadn't seen before.

When you are about to edit an interface, you probably want to first bring it down. If you forget to do this step first, you may have to reboot to get the status back to normal. So run this one:

You may want to verify that your interface is indeed eth0 and not somthing else. I would imagine that all Jetson cards use eth0 , but it may change in the future. I have another computer that uses p4p1 , for example.

You can see the list of available network cards using ifconfig .

Note: newer boards may use netplan instead of the if interface. In that case, you do not need to take it down first. You just edit the netplan YAML file and run an update.

Edit eth0 settings

First, you want to edit the interface file named eth0 as follow:

Note 1: The default root password (when you use sudo you become root) is nvidia for the nvidia user (although you should change it if you don't setup your board behind a strong firewall!) Note 2: Newer boards do not have a default password, instead they force you to create your own account and enter a password at that point. This is much safer. If you get an older board model, you probably still have to go to the new process (old boards support new software). Although I liked the old scheme, the new scheme is definitely much safer but it comes at a cost: your very first boot needs to be without a network connection (at least for me it caused problems on an AGX).

Inside the file, enter the usual info so eth0 gets setup with a static IP address:

You want to change the 10.1.1.2 and other IPs with your LAN IPs, obviously.

Up to here... nothing too bad outside of the fact that it was in a sub-directory in a file named eth0 . (I saw that before, it's just the first time I had to deal with this in this way. Usually I just edited the /etc/network/interfaces file directly.)

Restart eth0

Okay, to have the new IP taken in account, we have to restart the network interface, the opposite of the ifdown we ran earlier:

Verify Static IP Address in eth0

Now you've got the correct IP address. You can verify that with ifconfig :

As we can see, the inet addr field has the IP address as defined in our edits.

On newer versions you can use the ip command like so:

This gives you a list of configured interface slightly different from the ifconfig command, but the content is the same. This is becoming the preferenced command to see your interfaces.

Verify Static IP Address Gateway on eth0

To verify the gateway, use the route command:

We see that the default destination has the Gateway IP address we defined in our eth0 interface file and the Flags say "UG" (the 'U' stands for Up and the 'G' stands for Gateway, for more info, check out the manual page: man route ).

Notice that there is an Iface column that says the Gateway is on eth0 .

The ip command can also be used to see the routes. The output is not shown in a table with nice columns, but in most cases the number of routes is pretty limited so it's rarely an issue.

Note that you can also access the different route lists or all the lists this way:

Now this command may output many entries. Instead of "all" you can list each individual table. Checkout the help to have a more complete list of route options:

and use the manual to get more details. It has beena  long time since I had to tweak routes on my own. 99.99% of the time, the Linux system figures it out properly so you hardly ever have to do anything about these.

Testing Internet Connection

Now we're probably interested by the Internet... can we access the Internet?

I will assume that your Gateway computer is correctly setup. If you have an intermediate computer, you'll need to have the FORWARD and POSTROUTING correctly defined in your Linux firewall . Also, if you're like me, you'll have to "pierce" a hole in your firewall so the IP address you just assigned to your Jetson works as expected.

What I do to test whether I can access the Internet, is to test the DNS system. To do that, I simple ping an IP address by hostname. For example:

IBM may or may not allow the ping itself, but at least you should see the hostname www.ibm.com replaced with an IP address. When I tried today, I got this one:

Please hit Ctrl-C quickly to not abuse the ping system offered by IBM or any other company (unless you have your own DNS servers and can ping your own servers.)

Chances are, that won't work first time on Jetson TX1 or Jetson TX2.

Fixing the "Nameserver" Configuration

What you need to do is help the OS with the nameserver resolution. Somehow, it does not work out of the box. All I had to do to fix this was to create the /etc/resolv.conf file with:

You actually probably saw a warning about that file missing when you ran the ifup and ifdown commands:

Okay, now that you are editing the resolv.conf file, type your name servers there instead (that is, it's probably not necessary in the /etc/network/interfaces.d/eth0 file, although I would suggest you leave it in both places.) Like me, enter a couple of DNS entries:

These are from Google. If you have others from your Internet Provider, you may want to use theirs. The Google DNS server is probably further away from you, so it's not a bad idea to your use Internet Provider IPs. If you're at work, ask your IT guy what DNS IPs you should be using or check your other computer(s) and reuse those IPs.

Save this file and now you're ready to rock. Try the ping as shown above and you should see the hostname converted to a corresponding IP address. If so, you're connected to the Internet via a static IP address.

Why should I use a static IP address?

My point of view is that with a static IP address there is no guessing. You can write scripts that directly access your device and make it work as expected.

The DHCP networking protocol introduces some latency that doesn't exist at all with a static IP. Also once in a while you lose the IP address for some time . Usually the IP is renewed before it goes out of business, but if for whatever reason that renewal doesn't work, then you're hosed!

Finally, if you want to setup a strong firewall, a DHCP system means any one of your computer that access the network using DHCP may end up with any one of the allowed DHCP IP address. This means that the firewall has to be "wide open" in a similar way for all the computers using DHCP.

Although, obviously, you can force a specific IP address even with DHCP, which I do for my WiFi devices. For example, my Jetson could have been setup using an entry like this in my /etc/dhcp/dhcpd.conf file:

You will have to replace the IP address on the fixed-address field and for the DHCP to make that selection, it uses the MAC address which is defined by the hardware ethernet field.

Note that in most cases the MAC address will have 2 or 4 other numbers to the left. Often it looks like 00:80 or something like that. Just use the last 6 numbers. These are always Hexadecimal numbers. The letters are case insensitive.

To find the MAC address when you have access to a computer, use the ifconfig command. It will display the MAC as the hardware address:

The numbers after the HWaddr are those you are interested in.

From the system where you are setting up the DHCP, you can find the hardware IP address in the arp file as follow:

(the ... represents other entries removed here to keep my own network top secret!)

We recognize the exact same HW address field.

See Also: Playing a video with your Jetson TX1/TX2 from the command line  

  • Add new comment

Recent Posts on The Linux Page:

     

   

Copyright © 2004-2024 by Alexis Wilke See the License for more info Terms & Conditions     Privacy Policy

set static ip jetson xavier

NVIDIA Jetson Xavier - Performance Tuning by Setting CPU, GPU, and Frequency Values Manually

Manage cpu state.

The Tegra will always boot from one CPU denominated the master CPU, this cannot be turned off, and all other CPUs can be turned off.

To manually turn on/off slave CPUs

1) Run the following command to turn on the slave CPU:

2) Run the following command to turn the slave CPU off:

To check the CPU state run the following commands:

3D Frequency Scaling

Frequency scaling allows the Tegra to change the CPU frequency according to the load in order to reduce power consumption, 3D frequency scaling is enabled by default.

To disable 3D frequency scaling run the following command:

To enable 3D frequency scaling run the following command:

Change CPU Frequency

To print the CPU lower boundary, upper boundary, and current frequency run the following commands:

To change the CPU upper boundary run the following command:

To change the CPU lower boundary run the following command:

To set the static CPU frequency run the following commands:

Where CPU_FREQ must be among the values in /sys/devices/system/cpu/$CPU/cpufreq/scaling_available_frequencies

Change GPU Frequency

To print the GPU lower boundary, upper boundary, and current frequency run the following commands:

To change the GPU upper boundary run the following command:

To change the GPU lower boundary run the following command:

To set the static GPU frequency run the following command:

Where GPU_FREQ is the value available in: /sys/devices/17000000.gv11b/devfreq/17000000.gv11b/available_frequencies

Change Memory Frequency

To print the EMC lower boundary, upper boundary, and current frequency run the following commands:

To change the EMC upper boundary run the following command:

To change the EMC lower boundary run the following command:

To set static EMC frequency run the following commands:

Where EMC_FREQ in kHz is the value available in: /sys/kernel/debug/bpmp/debug/emc/tables/regular/

  • NVIDIA Xavier
  • Pages using sidebar with the child parameter
  • Jetson AGX Xavier Series
  • View page source

Jetson AGX Xavier Series ¶

NVIDIA ® Jetson™ Linux supports these software features, which provide users a complete package to bring up Linux on targeted NVIDIA ® Jetson AGX Xavier™ series.

Bootloader ¶

Toolchain ¶, debug interface ¶, camera interface ¶, displayport ¶, sata-marvel (over pcie) ¶, security engine ¶, ethernet controller features (eqos) ¶, power modes (profiles) ¶, egl details ¶.

EGL is an interface between Khronos rendering APIs, such as OpenGL   ES, and the underlying native platform window system. It handles graphics context management, surface/buffer binding, and rendering synchronization. EGL enables high-performance, accelerated, mixed-mode 2D and 3D rendering using other Khronos APIs.

Jetson Linux Driver Support supports the EGL 1.5 specification , Khronos Native Platform Graphics Interface (EGL 1.5 Specification) .

GL and Vulkan Details ¶

The OpenGL driver in this release supports OpenGL 4.6. See the Khronos ® Group page OpenGL4.6 Core Profile .

All details related to GL/GLX and other related specifications can be found on the Khronos ® Group page Khronos OpenGL® Registry . Conformance details for both X11 and Wayland Windowing System are on the Khronos Group page Conformant Products: OpenGL .

The OpenGL ES driver in this release supports OpenGL ES Common Profile Specification 3.2. For more information on OpenGL ES, see the Khronos OpenGL ES API Registry.

Conformance details for both X11 and Wayland Windowing System are on the Khronos Group page Conformant Products: OpeGL ES .

All details related to the specification can be found on the Khronos Group page Khronos Vulkan Registry . Conformance details are on the Khronos Group page Conformant Products: Vulkan .

Multimedia ¶

The following tables list the several classes of multimedia features.

Use the gst-inspect-1.0 utility to understand feature details. For example, either of these commands:

Provides feature details of the H.264 encoder.

For additional information about supported features, see the following sections of the topic Accelerated GStreamer .

Video Format Conversion with GStreamer-1.0

Video Scaling with GStreamer-1.0

Video Cropping with GStreamer-1.0

Video Rotation with GStreamer-1.0

For additional information about CSI and USB Camera supported features, see the section nvgstcapture-1.0 Reference in the topic Accelerated Gstreamer Reference .

Control Area Network (CAN) ¶

IMAGES

  1. NVIDIA Jetson AGX Xavier Developer Kit

    set static ip jetson xavier

  2. NVIDIA Jetson AGX Xavier

    set static ip jetson xavier

  3. Getting Started With Jetson Xavier NX Developer Kit

    set static ip jetson xavier

  4. NVIDIA Jetson AGX Xavier Developer Kit

    set static ip jetson xavier

  5. NVIDIA Jetson AGX Xavier Delivers 32 TeraOps for New Era of AI in

    set static ip jetson xavier

  6. NVIDIA Jetson Xavier NX Developer Kit

    set static ip jetson xavier

COMMENTS

  1. How to Set Static IPs using Command Line on Jetson AGX Xavier?

    What is the proper way to configure static IPs for the Ethernet ports on a Jetson AGX Xavier using the command line? (My Jetson is headless, so GUI tools are not an option.) Background: My Jetson is running Ubuntu 18.04. ... I am able set set a static IP on one Ethernet port using the initial setup wizard which runs after flashing, however, I ...

  2. 1. Configuring the NVIDIA Jetson NX

    To set a static IP address, you will need to know the subnet, IP address range, and gateway of your wifi network. To get the currently-assigned IP address use the command ip addr show dev wlan0. ... To verify that you can SSH into the NVIDIA Jetson Xavier NX Developer Kit, ...

  3. How te set a static IP for a Jetson Nano?

    Recent Jetsons nano use linux network-manager to manage network interfaces. you have to, either use the UI to modify the settings or use cli as below : show network connections with : nmcli con show nmcli con show

  4. NVIDIA Jetson Xavier

    NVIDIA Jetson Xavier - Using SSH. To access the Xavier board via SSH, you'll need to find the IP address of your board first. If you have serial console access, use the ifconfig command to get the required information: inet 192 .168.0.174 netmask 255 .255.255. broadcast 192 .168.0.255. inet6 fe80::1d2b:ff54:4538:7592 prefixlen 64 scopeid 0x20 ...

  5. Getting Started with Jetson Xavier NX

    Select your Development Environment. STEP 01 lets you select the board to flash, the version of the operating system and additional SDKs to be installed. Click on "Target Hardware" and select "Jetson Xavier NX" from the list. Click on "Linux" and select the latest version of operating system to install (e.g. "Jetpack 4.4 DP").

  6. 1. Configuring the NVIDIA Jetson NX

    In the next steps, we will configure the WiFi connection with a static IP address so you can SSH into the Developer Kit reliably. To set a static IP address, you will need to know the subnet, IP address range, and gateway of your wifi network. \n \n; To get the currently-assigned IP address use the command ip addr show dev wlan0. \n\n

  7. NVIDIA Jetson AGX Xavier Setup

    Recently, I got an NVIDIA Jetson AGX Xavier Developer Kit. It turns out that setting up Jetson AGX Xavier is slightly more complicated than setting up Jetson Nano. In this blog post, I would like to discuss some of the notes and the caveats that I found when I was setting up the device. Setup NVIDIA SDK Manager

  8. Nommas/nvidia-jetson-setup

    Instructions and resources on preparing and using Nvidia Jetson Xavier NX for deployment - Nommas/nvidia-jetson-setup ... Medium article: The Newbie Guide to Setting Up a Jetson Nano on JP4.4 Part 1: Running Jupyter Lab Headless Using SSH ... Try accessing the Jetson's USB IP which should be fixed (different boards have different USB IP ...

  9. networking

    I use the following to setup my static IP address. You were close, but you must have a valid gateway. "255" is the broadcast address, not the gateway... auto eth0 iface eth0 inet static address 192.168.1.192 netmask 255.255.255. network 192.168.1. broadcast 192.168.1.255 gateway 192.168.1.1 dns-nameservers 75.75.75.75 75.75.76.76 dns-search ...

  10. Setup static network on the Jetson TX2

    Although, obviously, you can force a specific IP address even with DHCP, which I do for my WiFi devices. For example, my Jetson could have been setup using an entry like this in my /etc/dhcp/dhcpd.conf file: host jetson_tx2 { next-server jetson.example.com; hardware ethernet 12:34:56:78:9a:bc; fixed-address 10.1.1.2; }

  11. NVIDIA Jetson Xavier

    To set static EMC frequency run the following commands: ... NVIDIA Xavier; Jetson; Hidden category: Pages using sidebar with the child parameter; Cookies help us deliver our services. By using our services, you agree to our use of cookies. OK. This page was last edited on 13 February 2023, at 17:00.

  12. Jetson AGX Xavier Series

    EGL is an interface between Khronos rendering APIs, such as OpenGL ES, and the underlying native platform window system. It handles graphics context management, surface/buffer binding, and rendering synchronization. EGL enables high-performance, accelerated, mixed-mode 2D and 3D rendering using other Khronos APIs.

  13. Manual Network Configuration in Linux and How to Set a Static IP

    a specific IP address; full control over the address assignment; Since the Dynamic Host Configuration Protocol (DHCP) can take the Media Access Control (MAC) address into account when assigning the network-layer address, we might still automatically receive the same IP on each connection with that protocol.

  14. How to set up static IP addresses?

    FMS is not going to keep those reservations for your jetson. You will need to figure out directly on the jetson how to disable dhcp and assign a static IP. Here is what I found on how to do this from a quick search: Please note that I cannot test this since I do not have a Jetson. You should backup all files before making any changes!

  15. How to setup desktop remote access to Jetson over the internet

    To accomplish this we open the porthole app, login and click on "Add new" button. This will open a window where we select the remote device, the port from the selected device that which will ...

  16. 2. Connecting the Pit/Host and the NVIDIA Jetson NX

    On the NVIDIA Jetson NX, open a terminal and type: ping 192.168.1.151 (This is the IP address of the Pit computer.). On the Pit computer, open a terminal and type ping 195.0.0.5 (This is the IP address of the NVIDIA Jetson NX). Remember to replace the IP addresses in the two lines above with your specific addresses.