I corrupted the Ubuntu on my Jetson TX2 and need to boot it again. However, the SDK Manager on my host machine can’t find the necessary JetPacks to download. Does anyone have any tips on what to do? I can’t find any JetPack versions newer than 1.93 to test.
I also tried manually installing Jetson Linux R32.7.6, but I get the error “UnicodeDecodeError: 'ascii” codec can’t decode byte 0xe2. Does my host machine need to have Ubuntu 18.04?
I need to recover this board as soon as possible, so any tips on how to boot it again would be appreciated.
Mostly what you’ve noted seems correct. I’ll be a bit more verbose though before asking a question.
I’m not sure of that version, it sounds more like an SDK Manager version. For terminology, L4T is what we call Ubuntu after the NVIDIA content is added to it. L4T is what actually gets flashed, and JetPack is a GUI front end to that. SDK Manager is a “smart” network layer added on top of that. If you go here and check for the most recent L4T release compatible with a TX2, then you will find it is one of the L4T R32.x series: https://developer.nvidia.com/linux-tegra
If you go to the most recent L4T R32.x, then that URL will have everything you need for a TX2 dev kit. There will be a link to the JetPack download (which also downloads SDKM). Incidentally, one can flash on command line without JetPack, but it isn’t as automatic and there are a few optional software packages it won’t install.
The question is what version or release of Ubuntu is your host PC (see “cat /etc/issue” from the host PC)? Also, when you run this command, what do you see from the host PC? printenv | grep 'LANG'
(using the user login which runs the flash)
I can’t say that I know an answer, but it sounds like some part of the host PC is marking its character set is not quite right. ASCII is rather limited in characters it knows about, and different UTF-8 encodings extend that; if you get really far out there, some languages use UTF-16 and greatly expand alphabets. When you say you tried manually installing, I suspect something related to this got mixed up.