Xavier Update Difficulties

I am having significant difficulties with my Jetson Xavier. After a period of sitting on the shelf due to other obligations, I set about working with my (early release) Xavier Dev kit.

When set up normally (attached to an HDMI monitor) the device seemed to fail to boot. I had gone through the process of installing at least one, maybe two Jetpack releases since I received it, and all seemed well as far as I went with things. I never got time to do any serious work however, but just explored the environment and perhaps some demos.

I realized that it was appearing with the original hostname on my network. So I tried using Putty to connect to it, and logged in without problem. Just the video configuration seemed to be messed up.

I decided to install the latest Jetpack (4.3) using SDK Manager (1.0.0.5517). That seemed to go OK, though I didn’t watch the terminal. It ended by saying “INSTALLATION COMPLETED SUCCESSFULLY”. It still would not come up graphically. Looking at the network, it was being handed an IP address by DHCP, but the hostname was now ‘localhost.localhost’ and it would not accept SSH login.

I repeated this entire process a couple more times and realized that I was consistently getting write errors during the early parts of the flash process. This does not seem to be noticed by the SDK manager.

To me it looks as if critical ranges of the eMMC flash have failed, probably taking my display configuration and who knows what else with them. Reinstalling the OS is not correcting the problem.

As SSH is not set up, I do not know how to get in to do more investigation. I gather that there is a serial port way in, but trying to get in through the /dev/ttyACM0 that appears on my host does not seem to work (I don’t know the port parameters to use).

I am at a loss. Can anyone help me?

Dave

Also, I meant to include what seem to be the logs from my efforts. But I don’t see how to do it.

Dave
JetPack_4.3_Linux_logs_2020-1-14.tar.gz (22.6 KB)

Hi Dave,

In general, when we don’t know whether the device boots fine or not, we dump the uart log.

https://developer.ridgerun.com/wiki/index.php?title=Xavier/In_Board/Getting_in_Board/Serial_Console

When set up normally (attached to an HDMI monitor) the device seemed to fail to boot.
Are you able to see nvidia boot logo?

Thanks for the info about serial debug ports and great documentation pages!

Unfortunately for me the four devices (/dev/ttyUSB0 etc.) appear when I plug in the USB2 cable but give me a frozen blank console using either minicom or Putty. This is exactly the behavior as with SSH as well. The connection is valid, but no prompt of any kind.

And no, at this point I do not even get the Nvidia Logo on the monitor. HDMI recognizes that it is active, but nothing gets displayed at all.

Dave

The first device in the list should be the correct device. Monitor “dmesg --follow” and look for the first name during plug-in. Settings should be “115200 8N1”. I recommend “gtkterm” (“sudo apt-get install gtkterm”). Using this, and assuming ttyUSB0:

sudo gtkterm -b 8 -t 1 -s 115200 -p /dev/ttyUSB0

Notice that unless your user is a member of group “dialout” that “sudo” will be required. If your user is a member of dialout, then you can exclude “sudo”.

Unfortunately while the port devices appear in /dev, connecting to any of them with the suggested settings gives a blank screen with no prompt. Same with gtkterm, minicom, putty. My account is a member of ‘dialout’ but using sudo yields the same result. The Xavier allows the connection, but whatever normally responds with a login prompt simply does not proceed.

We could try some simple cases.

Are you able to see “Linux_for_Tegra” on your ubuntu host? If so, please

  1. Put your Xavier into recovery mode
  2. On your host, use command “lsusb” to see if you could see a device with name Nvidia.
  3. cd Linux_for_Tegra and run “sudo ./flash jetson-xavier mmcblk0p1”

The flash process should start. Please see if it can run successfully.

In the meanwhile, the uart should also have flash log spew. Please check.

I did exactly that twice today. I followed the directions for a manual flash from your documentation pages. Same results.

These are my ‘notes to self’ for this:

Manually flashing Xavier with L4T
===================================
Power down - unplug.
Connect monitor, kbd, mouse ETH0 to Xavier.
power on.
plug USB-C from Host into FRONT USB-C port.
press 'recover' button (Middle) and 'reset' (most towards center).
release 'reset', 2 seconds later release 'recover'.

Type:
------
cd ~/nvidia/nvidia_sdk/JetPack_4.3_Linux_P2888/Linux_for_Tegra
sudo ./flash.sh jetson-xavier mmcblk0p1 | tee flash_2020-01-15.out

Unplug USB-C cable

When prompted:
---------------
press reset

System should boot normally.

I will attach the file: flash_2020-01-15.out

Thanks,
Dave
flash_2020-01-15.out.tar.gz (10.6 KB)

Something I am wondering about:

I have been downloading the L4T components using sdkmanager. At one point I am getting lots of errors in the terminal window like

12:06:23 ERROR : Flash Jetson AGX Xavier : 4131: SKP: 1988886528( 485568 blks) ==> 1825894848:12
12:06:23 ERROR : Flash Jetson AGX Xavier : 4133: SKP: 57344( 14 blks) ==> 1825903064:12
12:06:23 ERROR : Flash Jetson AGX Xavier : 4134: RAW: 4096( 1 blks) ==> 1825903076:4108
12:06:23 ERROR : Flash Jetson AGX Xavier : 4135: SKP: 61440( 15 blks) ==> 1825907184:12
12:06:23 ERROR : Flash Jetson AGX Xavier : 4136: RAW: 49152( 12 blks) ==> 1825907196:49164
12:06:23 ERROR : Flash Jetson AGX Xavier : 4137: SKP: 33505280( 8180 blks) ==> 1825956360:12
12:06:23 ERROR : Flash Jetson AGX Xavier : 4139: SKP: 100524032( 24542 blks) ==> 1825964576:12
12:06:23 ERROR : Flash Jetson AGX Xavier : 4140: RAW: 20480( 5 blks) ==> 1825964588:20492
12:06:23 ERROR : Flash Jetson AGX Xavier : 4141: SKP: 4194304( 1024 blks) ==> 1825985080:12
12:06:23 ERROR : Flash Jetson AGX Xavier : 4142: RAW: 2981888( 728 blks) ==> 1825985092:2981900
12:06:23 ERROR : Flash Jetson AGX Xavier : 4144: RAW: 188416( 46 blks) ==> 1828967004:188428
12:06:23 ERROR : Flash Jetson AGX Xavier : 4146: RAW: 2908160( 710 blks) ==> 1829155444:2908172
12:06:23 ERROR : Flash Jetson AGX Xavier : 4148: RAW: 5312512( 1297 blks) ==> 1832063628:5312524

I thought that this was coming from the flashing process, but could not find these errors in any log.

I do not see these errors when I manually use the flash.sh script (see flash_xxxxx. out above). Are these part of some earlier stage of preparation of the system image? Is stuff messed up before I even try to flash it?

Dave

Sorry for the log you saw in #9. It was a stupid mistake that we put it as “stderr” so it outputs as “ERROR”. Actually, it is not.

I saw the flash process is done in your log. Are you able to see any uart log during flash?

Some workarounds come to my mind

Method 1. please find different HDMI monitor and see if any of them can work or not.

Method 2. Please use this script on your host before flash.
https://devtalk.nvidia.com/default/topic/1054926/jetson-nano/jetson-nano-all-usb-ports-suddenly-stopped-working/post/5356153/#5356153

After this configuration, reflash the board and keep the type-c usb cable connected and see if there is a new network interface (you could check it through ifconfig) on your host with ip 192.168.55.100.

“Sorry for the log you saw in #9. It was a stupid mistake that we put it as “stderr” so it outputs as “ERROR”. Actually, it is not.”

Those 'ERROR’s are what have been scaring me the most.

#7:“In the meanwhile, the uart should also have flash log spew. Please check.”
#9:“I saw the flash process is done in your log. Are you able to see any uart log during flash?”

I’m not clear what you mean by uart log. A uart.log file under ~/.nvsdkm/logs? or output from a /dev/ttyUSBx device while doing the flash process? (not sure how), or something else?

I will try your other suggestions tomorrow.

Thanks,

Dave

A uart log means the serial log from /dev/ttyUSBx. (more precisely /dev/ttyUSB3).

Ok resolved! I wasted lots of time by not checking monitor/cable combination sooner… Switching monitor & cable seems to have solved the problem.

I could swear that I was using at least the same monitor (23" Samsung, no adapters, etc.) as in the past.

Anyway, I am happy, and a tiny bit wiser.

Thanks for the help!

Dave