I flashed AGX Orin dev kit with sdk manager since cuda has a bug.
I tried few time of the orin’s password, failed, So I set manual setup flashed it.
It’s successful, but When I try to log in from screen command or a keyboard and screen, it had changed the username but my password is wrong.
So I tried to manual flashed it again, but the username didn’t change afterwards. The software said flash successful. But it was suppose to change.
I suppose I followed the instructions in nvidia sdk, did everything from
select the “orin” flash preferences, turn orin force recovery mode then select manual setup, preconfig oem.
wait for it to process
the return is successful and the terminal seems alright.
unplug the orin, use it as a host machine, attach a screen and keyboard and mice to it.
the username left unchanged.
I’m doing reflash since I installed a wrong version of jetpack. I thought I could apt install it and making bigger mistakes.
But the first reflash is like this, so I tried multiple times.
should I change the storage device and try again? for example, turn emmc to nvme devices.
this time I tried to use the flash.sh to flush and it was successful in command line.
then I do : l4t_create_default_user.sh and set a new default user, successful in command line.
Then I tried to use it as a host, attached a monitor to Orin, and it is still using the last user before flashing.
I believe it is due to I flashed multiple times on nvme and emmc.
So I flashed nvme again as well, but there is more problems.
This time, after successful flash, Attaching to a screen, the Orin is not sending signal to the screen anymore.
I removed the vnme, connect it to the screen, still don’t work.
The screen had the same output as above, the current input is not supported by monitor.
Do I need to flash it again on emmc?
Or multiple flashes destroyed something inside this device?
Well I tried to attach Orin to the host PC again, with usb.
But this time the Orin without the nvme, is not showing anything.
no l4t usb drive GUI,
no 7020 or 7023 result in lsusb.
Please help me with what’s happening.
thank you for your patient explanation and detailed support. But the error became more severe:
When I attatched orin to host PC with USB, it can’t detect orin anymore.
No L4T drive disk GUI,
No 7020 and 7023 (the orin device number) after command: lsusb
the same usb cable was used for flashing but today no usb device found.
shall I try to use the serial port, USB micro-B port to check out console log? Maybe it’s cable
OK. thank you.
I solved most of the problems.
I also understand that jetson agx orin you can’t flash to nvme, only use emmc.
So what should I do to the nvme ssd that had another linux, but causing boot problems? format the nvme ssd with host PC first, then put it into Orin?
Thank you so much.
Last time I flashed I used sdkmanager and in it I picked nvme as the drive to install to and sdkmanager successfully installed everything on to the orin agx nvme drive.
But for me, when the nvme linux and emmc linux they have conflict, caused the problem.
I read the L4T documents, it seems that flashing NVME on AGX Orin wasn’t a good idea.
So should I format the NVME ssd drive before I use this thing, to avoid conflict again?
thank you.
