Before compile, what do you see from: echo $CROSS_COMPILE_AARCH64_PATH
If you don’t see this set, what happens if you use this command instead:
CROSS_COMPILE_AARCH64_PATH=...your /home/...path...adjust for your case... ./nvbuild.sh ...your arguments...
So basically, avoiding writing long lines from screenshots, combine the CROSS_COMPILE_AARCH64_PATH=...content... in front of the nvbuild.sh with a space between them; combine them into a single line which no longer depends on .bashrc.
Incidentally, screenshots are hard to work with (copy and paste isn’t so good with that). Any command line that you want a log file of to attach is simple. Example: echo "just testing" 2>&1 | tee log_testing.txt
(the result of the echo, and any errors, are then recorded in log_testing.txt and you can simply attach it to the forum; this extends to all commands on command lines, just append " 2>&1 | tee log_something.txt")
Now if an environment variable you’ve set is not pointing to correct content, then it might also give a similar error to having not set the variable. This includes the location of the environment variable if that location is expected to already exist.
Thank you for your reply.And I have another question,what is the command of Orin nano L4T flashing?
I can see someone using “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 jetson-orin-nano-devkit internal” from a forum. Is it one command or two?
Can I use “sudo ./apply_binaries.sh” and “sudo ./flashsh ietson-agx-orin-devkit as nano8gb mmcblk0p1” to flash?