Is there a way to flash AGX Xavier with whole Ubuntu system without manually system configuration system setup? The L4T version is R32.2.1.
For testing a customize carrier board, we need to flash AGX frequently.
It really helps if we could flash AGX the whole Ubuntu.
###############################################################################
./flash.sh: line 575: ./tegrarcm_v2: 沒有此一檔案或目錄
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
Linux_for_Tegra$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 006: ID 0955:7019 NVidia Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 003 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Linux_for_Tegra$ sudo ./l4t_create_default_user.sh -u nvidia -p nvidia
[sudo] password for
Creating: Username - nvidia, Password - nvidia, Autologin - false
Adding user nvidia' to group gdm’ …
Adding user nvidia to group gdm
Done.
Adding user gdm' to group video’ …
Adding user gdm to group video
Done.
The “no such file or command” at line 575 implies something is missing on the host. I don’t know which file or command it thinks is missing, but if you look at line 575 of flash.sh, it should say something like this (I’m looking at R32.2, and is likely the correct line, but not guaranteed):
Just before this line you might add something similar to this to find out what the rcmcmd is and the arguments (you can remove this line after testing to see what it does):
Then see if the command is actually there (flash.sh may have changed directories, so “./” might be the directory of flash.sh, or of “bootloader/”, so on). It seems like something is missing on the host.
###############################################################################
DEBUG:
ECID base command: ./tegrarcm_v2 --uid
END DEBUG
./flash.sh: line 581: ./tegrarcm_v2: 沒有此一檔案或目錄
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
Is there a way to revise the l4t_create_default_user.sh?
My host could not flash AGX now even I re-installed a Linux_for_Tegra.
All got the same error --“./flash.sh: line 575: ./tegrarcm_v2: 沒有此一檔案或目錄”
Is there a way to revise the l4t_create_default_user.sh?
My host could not flash AGX now even I re-installed a Linux_for_Tegra.
All got the same error --“./flash.sh: line 575: ./tegrarcm_v2: 沒有此一檔案或目錄”
l4t_create_default only updates the rootfs. It has nothing to do with your current error.
Please check why the pushd command in flash.sh cannot enter bootloader folder.
Are you running this from a non-standard location? Is there a space or non-English character anywhere in the file path leading up to the “Linux_for_Tegra/bootloader/” directory? Is the owner of that directory the same as the user who runs the flash.sh program?
(someone else needs to answer the qemu-user-static question, but if you are running in QEMU, then that would be important to know)
Did you unpack the driver package manually, and did you do so with sudo or root? If so, then permissions are probably wrong.
As background, normally the driver package is unpacked as a regular user, not with sudo or root. The sample rootfs and the apply_binaries.sh steps are performed with sudo, as well as actually running the flash.sh program. If the driver package itself is unpacked with root-only permissions, then there may be odd problems showing up in unusual ways.
Similar for installing JetPack/SDK Manager. The “.deb” file is installed with root permissions, but the actual sdkm command line is not run as sudo or root…when run as a regular user you would be asked for a password. If this ever ran as root and not as a regular user, then you’ll need to delete the “~/nvidia” content and start over since there are too many permissions to fix manually.