How can I access directly to the filesystem when it can be booted?

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

Hi,
After I set the customed .target file as a default, I booted this Jetson orin NX 16GB(in more detail, it’s the IPC from Advantech, MIC-713 OX4A1 model). But the .target file has deleted and I didn’t know I deleted it. Eventually, the machine can’t be booted after UEFI screen.

I need to fix it so need to access filesystem.

I searched some info and I found out it’s impossible to modify or remove files in UEFI shell if the filesystem type is ext. (How to fix uefi shell mv command Status: Write Protected - #10 by KevinFFF)

It’s not easy to find info on how to make live USB for jetson PC.
Or is there any way to access the filesystem with the OTG port or something?

Can I get a way to resolve this issue?
Thank you!

3

Hi tae123890,

What’s your Jetpack version in use?

What is .target file? Is that provided by your vendor?

Can you share the full serial console log for further check?

4

I’m not sure I can check the Jetpack version even though I haven’t used the SDKmanager to flash the kernel. I flashed the RT-patched kernel with the command “sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal”
I tried the ‘sudo apt-cache show nvidia-jetpack’, it doesn’t show the version but
“N: Unable to locate package nvidia-jetpack
E: No packages found”

Is there any way to get the consol log even if the machine can’t be booted?

5

Please share the result of the following command on your board.

$ cat /etc/nv_tegra_release

You can just keep capturing the serial console if your board can not boot successfully.
There should be still message output until it gets failed. We want to check those messages

7

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