Unable to flash to NVMe

Hi,

Got a Jetson Orin Nano 8GB developers kit. Installed a NVMe. put the device in to recovery mode and started flashing using the Nvidia SDK manager.

at 99% the flash fails and outputs →

14:03:38 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:03:40 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:03:41 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:03:42 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:03:55 INFO: Flash Jetson Linux - flash: Waiting for device to expose ssh ...RTNETLINK answers: File exists
14:03:55 INFO: Flash Jetson Linux - flash: RTNETLINK answers: File exists
14:03:55 INFO: Flash Jetson Linux - flash: Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
14:03:55 INFO: Flash Jetson Linux - flash: SSH ready
14:03:56 INFO: Flash Jetson Linux - flash: blockdev: cannot open /dev/mmcblk0boot0: No such file or directory
14:03:56 INFO: Flash Jetson Linux - flash: max_index=57
14:03:57 INFO: Flash Jetson Linux - flash: [ 2]: l4t_flash_from_kernel: Successfully create gpt for emmc
14:03:58 INFO: Flash Jetson Linux - flash: max_index=16
14:03:58 INFO: Flash Jetson Linux - flash: writing item=1, 9:0:primary_gpt, 512, 19968, gpt_primary_9_0.bin, 16896, fixed--0, 73ac48881383ebdb57073b8d7097efd290f2807b
14:03:58 ERROR: Flash Jetson Linux - flash: Error: Could not stat device /dev/nvme0n1 - No such file or directory.
14:03:58 INFO: Flash Jetson Linux - flash: Cleaning up...
14:03:58 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
14:03:58 ERROR: Flash Jetson Linux - flash: command terminated with error
14:03:58 SUMMARY: Flash Jetson Linux - flash: First Error: No such file or directory

Any pointers to what can be wrong?

I just want to flash the NVMe using any tool so if there are alternative ways please let me know as the SDK manager already stole about two days of my life.

/A

14:03:58 ERROR: Flash Jetson Linux - flash: Error: Could not stat device /dev/nvme0n1 - No such file or directory.

The error is nvme not able to be detected.

Another way to check this is you boot from a usb drive first. Then check if your nvme is really not able to be detected.

Hi,

Just booted using a mictoSD card. Looked in ‘disks’ the NVMe is named ‘nvme0n1p1’. It’s visible to the OS and works as expected. Did format to ext4 and moved some files around.

Is there any way to ‘force’ the name.

I looked into the ~/nvidia/././. folder and found a flash.sh script… Did → ./flash.sh jetson-oron-nano-devkit-nvme nvme0n1p1 (When the jetson orin nano was in recovery mode and connected via USB)

It’s finished successfully. However removing the microSD card and selecting the NVMe disk by pressing F11 at boot-up just stalls. Meaning when i select the NVMe disk the screen goes black and then my monitor says ‘no signal’ and then nothing…

Hi,

I explained this in another post long time ago. So let me directly share it.

→ point 4 * flash.sh will not flash anything to your external drive.**

flash.sh will not work for nvme. Need to use initrd flash tool. The quick start section in the developer guide shall show you the example.

I am surprised that sdkmanager cannot see this device but you can see it after boot from other drive.

Please, follow the page here. Use the “micro usb port” on your devkit to dump the log.
Then restart the flash process from sdkmanager and share me the log.

Please be aware that you have to use micro usb port. You cannot use type C port. That guidance provides 2 methods, but actually only micro usb port can give the info I need.

OK.

It seems to me the SDK manager would be the simplest way ‘forward’ however it’s not working as expected (it gives me the error I see in the first post) is there a way to ‘fix’ the error I’m seeing?

Just so I get it right if the SDK manager was able to successfully flash the NVMe would I be able to boot the system without a microSD or is that for some reason still needed?

Thanks for helping.

Hi,

We need to figure out what error shown in the log so that I can figure out how to fix.

Just so I get it right if the SDK manager was able to successfully flash the NVMe would I be able to boot the system without a microSD or is that for some reason still needed?

If it can flash nvme, then sdcard is no longer needed.

OK… Thanks! Please let me know if you need more log info. I was just copying the last part.

Sorry, I don’t know what last part you are talking about.

You didn’t share any log I just mentioned. The log in your first comment is not what I need. Please do read the comment I shared few mins ago carefully…

The first post contains the last couple of log-lines from SDK manager when failing. I was just curious if you’re interested in more data prior to the failure.

Ahh… never mind… (my fault)

Saw you asked me to →

Please, follow the page here. Use the “micro usb port” on your devkit to dump the log.
Then restart the flash process from sdkmanager and share me the log.

Yes, basically flashing a board is two side work. One side is host side log (what you shared on first comment).

The other side is device (jetson) side log. We need jetson side log to see why it cannot see the nvme.

If you want to attach full host side log, then it is okay to me. Full log is always better. But the most important part is the device side log.
Thanks.

1 Like

Ah… sorry. I just notice it is orin nano board. But the document is for Orin AGX.

Then it is not micor usb port… need to use special cable.

Yes. Was just about to post that I was unable to connect to the serial interface according to that (previous) guide. Well… Phew… that new guide kind of levels up the game for me to mode extreme. Will have to see how far I get.

Did order a TTL to USB cable (3.3v) it arrives after this weekend. I’ll get back later.

SDKM_logs_JetPack_5.1.1_(rev._1)_Linux_for_Jetson_Orin_Nano_modules_2023-04-26_09-45-29.zip (140.4 KB)
device_flash.txt (104.6 KB)
device_failed_boot.txt (82.8 KB)

Here is all data you requested.

the zip file is the generated from SDK manager
device_flash.txt is during the flashing from the device terminal
device_failed_boot.txt is when booting the device removing the recovery mode (normal boot mode)

/A

The issue seems to be same as what we checked previously.

The nvme drive indeed not able to get detected by the pcie driver.

[   18.714216] LUN: removable file: (no medium)
Connection timeout: device /dev/nvme0n1 is still not ready.
[   18.717842] rndis0: HOST MAC be:d6:45:66:73:1d
[   18.717980] rndis0: MAC 26:41:e3:06:5b:e1

Do you have other nvme drive to test? Looks like a weird situation.

Got another M.2 (Firecuda 520) and that one worked as expected, so for me case closed.

1 Like

Could you share what nvme was not working as a record here?

We will check it if we have same NVMe drive.

Sure.

WD Blue SN570 (1TB)
nvme.pdf (2.4 MB)

1 Like

I would love to know if there is a way to boot from NVME without having to use SDK Manager, because I do not have a suitable Intel-based computer in my home. I tried using VirtualBox to run Ubuntu 20.04 on my daughter’s old Intel MacBook, and that was a very long exercise in futility.

Sorry, that is not possible. The flash process needs another native x86 host.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.