getting started with TX1 from unknown state


I recently inherited a TX1 from another project. We aren’t sure whether there is anything currently on the TX1, or even what state it is in. Unfortunately, I did not receive any sort of documentation. Are there any recommended resources to see how to completely restart the board and then install software needed to get it to a usable state? Thanks!!

This would depend on the carrier board. If it is the default development kit carrier board, then just the default software flash would produce a running system. If there is a custom carrier board, then the third party carrier board’s board support package (a BSP is mostly a device tree) would need to be added. Third party carrier boards without the update to device tree may have missing or broken functionality to an unknown extent. Any third party updates apply to the flash software prior to flashing.

If you hover your mouse over the quote icon in the upper right of your existing post, then other icons will show up. The paper clip icon is for attaching files. You might include a picture of the carrier board if you do not know which it is.

The TX1 development kit is no longer sold so far as I know, but the module itself is. The TX2 carrier board would look the same (the modules use the same socket and much is inherited), and here is a picture of the carrier board:

Some useful information:

You will see references to “L4T” (“Linux for Tegra”), “JetPack”, and possibly “SDK Manager”. L4T is the actual operating system running on the Jetson, and is Ubuntu Linux with drivers added for direct hardware access. JetPack is a front end to the installer software and runs on an Ubuntu PC, which in turn can either be used to flash the Jetson or to add extra software packages to either the host PC or the Jetson. SDKM is just a newer front end for JetPack and the naming is often interchangeable despite being somewhat different software (SDKM is just newer). You can see a list of current software releases here (you may need to go there, log in, then go there again since redirect does not work):