Host OS: Ubuntu 20.04 Product: Jetson Orin Development kit NVMe drive: Samsung 980 pro 2TB
I am trying to setup boot from nvme by using sdkmanager. I followed the instructions at this link to put my Orin in recovery mode and configure manual setup. See screenshots below.
The monitor connected to the orin wakes up from sleep like the module is about to boot but the screen is blank. I can still reboot and boot into ubuntu from the emmc storage.
Any ideas on what could be causing this? The factory configured OS was able to detect and format the ssd. I have attached logs below.
Orin is the only Jetson board I possess so no. I’m terms of validation of the SSD, I was able to format the drive with an ext4 file system after attaching it to Orin so I assume it works.
Can you validate that too? If that goes wrong then flashing nvme may also go wrong.
We are sure that nvme could be flashed by sdkmanager because we just tested that today. But if you are totally new to this, then you better validating sdkmanager can even flash the emmc case first.
emmc flash success. I can boot into the OS and Ubuntu starts the OEM setup process. I can also see the ssd in disk manager (UUID and serial number present).
What’s odd is sdkmanager now always knows the serial device is present… Before this flash serial was never connected until I manually put it in recovery mode.
Gonna try a reflash of nvme now… Maybe the solution is to always flash the latest known good image to emmc?
During the timeout loop waiting for the board to boot up, My module start softly beeping (fan appears to be trying to rotate every time it beeps) and the monitor woke up from sleep again.
Sure I can try and collect that. When I plug in the micro b cable I get ttyACM0-3 on my host OS. I’m guessing the debug console is ACM0? Also do you have insight on if hardware/software flow control should be enabled in the minicom config file?
I solved this actually by unplugging my 4K monitor during the flash process as per this post (UART log showed the same error as OP. Only issue is I have to keep the DP cable unplugged until the system is booted fully:
How often is sdkmanager updated and will the next update include this fix?