-
Notifications
You must be signed in to change notification settings - Fork 1
Jetson Configuration
The Jetson is configured and administered remotely via a set of Ansible playbooks in tools/installer in the root repository. The goal is to have a reproducible way to flash the Jetson in case it gets misconfigured or the flash gets corrupted.
Basically it should give you a clean slate Jetson with all the necessary software installed.
The Ansible entry point is install.yml. It just imports all the necessary playbooks in the same directory. To add a piece of software, you can either add its install steps to an existing playbook or create a new playbook and import it in install.yml. Ansible is used because all actions run are designed to be "idempotent" meaning if they have already been done, it'll skip that task. Read more about Ansible elsewhere if you're interested in learning more.
The Jetson is assigned the static IP address 10.0.0.2 on its ethernet interface. Any computer with a static IP address that follows 10.0.0.* should be able to connect. It has it's DNS hardcoded to the Google 8.8.8.8 DNS. Network manager is disabled because it tries to handle the DNS nameservers and fails miserably. There is probably some configuration that I missed.
Nvidia distributes an installer for the base operating system and Nvidia packages. We've made some Ansible playbooks for installing it automatically. Run jetpack-tx*.sh and follow the instructions to run the Jetpack installer.