I’m following the instructions to upgrade (from 5.1.3) with the flashing method. After flashing upgrading the QSPI, the system did not boot into JetPack 5 (as intended), but when I flashed and tried to boot into JetPack 6, the system gets stuck at boot.
There are a few failures to start I see in the displayed logs, including (but not limited to) “Network Manager”, “nvpmodel service”, and “End-user configuration after initial OEM installation.” One of the messages that I see is “Please complete system configuration setup on the serial port provided…” I would post the full logs, but I don’t know how to get them off of the system.
I’ve tried re-flashing the SD card, to the same effect. I didn’t use SDK Manager because of organizational obstacles in getting a Linux computer.
It is the expected message you would see in the first boot after flash. Please connect the DP to a physical monitor to configure the username/password in system configuration.
If by DP, you mean the DisplayPort port, then I already have the Jetson connected to a monitor. That’s how I could see these messages. From past experience, I know that the oem-config GUI should pop up, but that simply isn’t happening here. Keypresses don’t seem to do anything, either.
It’d be difficult for me to run l4t_create_default_user.sh since, as I mentioned, I don’t have access to a Linux computer.
Could you tried to connect the USB-C port to your host (Windows is also fine) and open the serial console port(through putty or MobaXterm) to configure the oem-config there?
For Ubuntu, you may use /dev/ttyACM0 for it.
For Windows, you should check which comport number showing in device manager.