I guess I’m at an advantage that I use my host as a DHCP server on a second private network card (this makes it easy to look up DHCP requests).
On Xfinity I can see under “Connected Devices” the MAC addresses currently connected, as well as known MAC addresses which are not currently connected. Unfortunately, this doesn’t help since it has no time stamp to show when that last address assignment occurred. When I went to actual logs it only logs router DHCP information (Jetsons would be client, not router), and thus you can’t see any history of the devices connected/disconnected.
So far as the “tar: write error” issue goes I cannot find this listed in my logs. However, I am fairly sure I’ve seen this before when manually unpacking some part of the flash software without JetPack such that this was not an issue. I cannot confirm the error message has no effect, but my feeling is that this is not really an issue (there is a small chance the error is significant). My JetPack logs are incomplete since I normally use command line flash. For anyone wanting to see this look at the “Terminal_installation.log” attached in #41.
What was the operation being performed during the “gtkterm_log2.log”? What I see is a successful boot and serial console was working as expected. If you can get this same setup to log anything at all from a normal cold boot you might be in business. If this has become completely missing when you know serial console setup is otherwise valid, then I’m inclined to go with hardware failure. I realize you’ve flashed many times now, but if you flash again and can get to this point after flash completes, then you know the hardware itself is working (and perhaps it was the tar error). Log excerpt from your log:
tegra-ubuntu login: nvidia (automatic login)
Welcome to Ubuntu 16.04 LTS (GNU/Linux 4.4.38-tegra aarch64)
* Documentation: https://help.ubuntu.com/
618 packages can be updated.
301 updates are security updates.
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
nvidia@tegra-ubuntu:~$ [ 17.139461] fuse init (API version 7.23)
The flash log itself shows success. The excerpt I gave above would be from the serial console after the flash completed and the unit rebooted. It really seems like the system is running other than no network and no serial console (I keep hoping that serial console issues might be something other than hardware failure).
So here is what I’m going to recommend: Do a manual flash without JetPack to simplify things as much as possible. Keep the serial console going during the flash, but be careful to not accidentally hit any keystrokes (during reboot this could halt things). The following instructions are for R28.2, but other than packages now being R28.2.1 there is no difference:
https://devtalk.nvidia.com/default/topic/1031769/jetson-tx2/unable-install-any-jetpacks-jetson-tx2/post/5249710/#5249710
At the point where it says this on the flash.sh output the actual flash is done and the Jetson should reboot by itself (this is from the flash.sh output, you do not need to manually force reboot, but you could force this if nothing shows after several minutes):
*** The target t186ref has been flashed successfully. ***
Reset the board to boot from internal eMMC.
…any further serial console output is from boot…any previous serial console output is from flash. Any output there at all from serial console during flash says the serial console was correctly set up. Any output at all from after reboot begins says the Jetson is booting and is alive. What is needed is to determine if a known good serial console has any output at all during boot which follows flash.
Be sure to set your serial console terminal for logging. Note that the URL I gave above for command line flash shows an option for logging the flash itself…you will want to do this:
sudo ./flash.sh -S 29318MiB jetson-tx2 mmcblk0p1 2>&1 | tee log_flash.txt
…but I’m going to modify this in a way which will cut down on progress bar spamming the log (the progress bar is actually a major part of the log size):
sudo ./flash.sh -S 29318MiB jetson-tx2 mmcblk0p1 2>&1 <b>| gawk '{gsub("[0-9][0-9]+[/][0-9[0-9]+ bytes sent..",".");print}'</b> | tee log_flash.txt
(the “gawk” will just cut out parts of the progress bar and substitute a single “.”)
If you notice a tar error on command line flash I can look that up.
