I’m trying to flash and deploy my OS for through the Jetson SDKMANAGER. I cannot get passed 98.5% Can someone offer me some insight here? Thanks in advance.
This actually went through after I left it for about 45 minutes. However, after plugging in the HDMI I now get this error.
Then after reboot I get this.
what if you redo the flashing? does the issue reoccur?
make sure you have enough space at the Host PC when you are doing the flashing;
“it asks to complete system configuration setup on the serial port provided by Jetson’s USB device mode connection”
I did not see such a message before, but I assume that the Initial Ubuntu Setup step got missed somehow where the username and password are set initially.
Yea I tried flashing 3 times. It says successful. When I connect to the hdmi I get these screens.
when you are doing the installation, are you having at least 30-50 GB at your hard disk at the computer from where you are doing the installation? Did you try uninstalling sdkmanager and installing it again? With deletion of generated files e.g. rootfs? It will work out eventually, in my opinion.
When I was having an issue of similar nature it turned out that I had too few space while doing the installation;
Though your cause may be different.
In this earlier screenshot:
…the WiFi firmware would not have prevented normal operation (other than for WiFi). Most of what you see in this screenshot is also normal. The exception is the part about the EDID.
Is your monitor purely HDMI? Or did you use some sort of adapter? Quite often this error is because of an adapter which cuts the DDC wire of HDMI (e.g., VGA cannot provide this). If this was a valid HDMI monitor, then it probably means the i2c controller itself has issues, and this would make me wonder about the image which was actually flashed.
Regarding what @Andrey1984 just mentioned, if you don’t have enough disk space, then you can end up with flashing a truncated image…the flash might look correct, and parts of the system might work, but some parts would end up missing or corrupt. This could interfere with either the WiFi firmware or the i2c controller (the EDID data).
A good way to check disk space:
df -H -T
The monitor is a direct HDMI to HDMI cable connection. Even if I disconnect the HDMI the SDK manager can’t SSH into the box from the USB console port, https://photos.app.goo.gl/Akk9VVNheCupK2gf8
Plenty of free space, https://photos.app.goo.gl/AQJbEyBEAVZVoUGSA
It’s saying everything was successful, https://photos.app.goo.gl/aLniDU7aaoHCrKQt8
Is there a command I can run in the SDK Manager to force it to redownload firmware and OS?
I added the m.2 drive and an internal network adapter. I assume these wouldn’t cause issues?
Once flashed ssh will never work unless the first boot login account is created. See if you can “ping 192.168.55.1”. If this works, then the Jetson is up and running, and the next step is to be certain the account is created. If the account is created, assuming you chose the name “nvidia” for the account, then you should be able to log in via “ssh email@example.com”.
If you used the partition with the 400+ GB available, then you’re well covered for space :P However, I don’t know from the image if that was the partition used, nor if it is ext4. This is one reason for using “df -H -T” since it lists by mount point and shows file system type.
When flash is complete you shouldn’t need to keep flashing. The problem is likely the lack of an ssh account…ssh cannot succeed if the account does not exist, and it will not exist without intervention in the later releases.
It is unlikely that the added components would cause an issue. In theory a bad network setup could cause issues, but as long as you are using the virtual wired USB ethernet (the 192.168.55.1 address), then it shouldn’t matter.
Did you create your login account upon boot after the flash? This is absolutely critical and no optional software addition can be done without this step. You can try serial console to add that account if HDMI does not work. For serial console, see:
EDIT: Same settings for Xavier, but Xavier uses the micro-B USB cable, and the first ttyUSB shown upon plugging this in to the PC is the port for serial console.
So I have the Xavier AGX. I noticed the link you posted was to a different model. Also, when following this video it never references using a console cable to create an account. https://www.youtube.com/watch?v=Pncjv6FoQzU
You are correct I can ping 192.168.55.1 so it must be online. You are also correct that I cannot SSH into it using the nvidia creds so the account is missing. I just need to find the AGX Xavier reference for the pinout to determine which pins for console connectivity.
Appears the pinout is identical. Thanks @linuxdev going to give this a shot.
So I’m trying to console into the device now but I have no idea what the creds are.
Referenced in this post https://devtalk.nvidia.com/default/topic/1063003/-quot-incorrect-username-or-password-quot-when-flashing-xavier/ it’s saying I need to connect HDMI to run the initial setup to configure the username/password.
Referenced in these posts post https://devtalk.nvidia.com/default/topic/1017208/jetson-tx2-password/?offset=1 - https://devtalk.nvidia.com/default/topic/1025120/login-instructions-on-nvidia-jetson-tx1-developer-kit-quick-start-guide-not-working/ it says nvidia/nvidia or ubuntu/ubuntu. Neither of those work.
I’m back at square one.
Here is the data from df command.
This is what I get on the HDMI console if I do not power cycle the device after the SDK Manager finishes loading the OS.
I added a note to the serial console URL…you are correct, I gave the TX2 information. The settings will be the same, but your PC will use the micro-B USB cable, and if you monitor “dmesg --follow” as you plug in that cable, then the first serial port listed will be the correct one for serial console.
You have plenty of disk space, so no problem there.
The last picture says there is an EDID failure. This is the HDMI cable wire which provides video automatic configuration information. Thus, the video cannot function in graphical mode due to that error. Is the monitor purely HDMI without adapter? VGA cuts this wire because it predates automatic query/configuration. Some other adapters work, but not always.
So I did not have HDMI hooked up when I flashed the OS. I hooked it up after the device failed the step in which it needs to SSH into the box. My guess is that logged an HDMI error. I can try to hook up HDMI and flash it again. I’m willing to bet that error would go away.
So I figured this out. Thank you to everyone for pointing out the HDMI error or it never would have been possible. You have to have an HDMI cable connected while running the SDK Manager. Otherwise, if you try to flash and hook it up later it will never boot.