Yes, the ability to continue depends on the ssh working, and the ssh depends on first boot account setup (unless you use a script to fill this in ahead of time…more on that later since it isn’t the “standard” approach).
So up until this point things are now correct, the flash part is complete as soon as you create the account. Once that is done you will have the operating system working, although the extras (such as CUDA) won’t be there yet. This step can be completed at any time without flashing again just by unchecking flash.
So on to the error you are getting. That i2c error is from an attempt to query an HDMI monitor for its configuration data (the EDID data). During flash, or in that particular screen, was there some sort of adapter and the monitor was not actually HDMI? There are some adapters which work, such as HDMI to DisplayPort, or some DVI (the digital DVI-D). Other adapters do not provide the plug-n-play of that automatic configuration (the i2c wiring).
First, if this is not true/native HDMI (or something equivalent…VGA guarantees failure, there is no possibility of VGA configuring automatically), then getting true HDMI would help.
I’m not positive, but there may be differences in what is flashed if the Jetson does not have HDMI and keyboard connected during the flash. Although there may be ways to deal with this on non-GUI console, I’m not positive, but this appears to be why end user configuration is failing. This will somewhat explain, and the script associated with this is for applying an account to the “Linux_for_Tegra/rootfs/” content prior to flash (first boot would not be required because this is equivalent to first boot prior to flash to the Jetson…this script was for the Nano, but the content is the same for the other Jetsons in the R32.x releases):
Although that script could get you through first boot without an actual first boot it would require you to flash again. Then when you go to use the Jetson you will once more run into issues of missing HDMI. You have to go through special steps to run headless and there is a learning curve to that. Add to this that although you can use xrandr to change modes after being in the GUI, you won’t be able to manually specify (via config files in “/etc/X11/”) an alternate resolution since the driver will demand that only EDID modes will be used as a source of configuration (this is from that wire which VGA is missing).
So the simplest route would simply be to use an HDMI monitor (correct me if I am wrong and you already used HDMI, as this would be a different error) and complete the first boot. You’d check that ssh to the account works, and then you’d start SDK Manager again with all of the flash steps removed (e.g., try to add only CUDA). Alternately, you could use that script, and then flash again…first boot setup would no longer be required.
Oh, almost forgot: I think there is a way to do first boot setup on serial console, but I have not tried doing that myself. Was your screenshot from a monitor attached to the Jetson, and not via serial console?