-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy tarball for Xavier NX target does not work #34
Comments
I would say that l4t_generate_soc_bup.sh needs to be executed with root permission :
Regards, |
I can corroborate this, there are a couple of bugs: In
"nx" isn't quoted. Not sure if this is actually consequential in sh. Then in |
Hi @amarburg, Best Regards, |
Interesting. I'm not running |
Hi @amarburg , |
Hm. I wonder if I'm getting a silent failure when I don't run as root. I'll have to look. |
Hi again,
I'm still working with master and l4t-32.5.1. When I ran deploy.sh command to generate the tarball for Jetson Xavier NX as target, I got following error :
Generate Multi-Spec BUP Tool
Error: Invalid target board - jetson-nano-devkit.
...
Error: Invalid target board - jetson-nano-devkit-emmc.
...
Error: Invalid target board - jetson-nano-2gb-devkit.
...
Error: Invalid target board - jetson-tx1-devkit.
...
t21x payload generation complete with 10 failure(s)
^M
FAILURE: error cleaning BUP tmp files^M
FAILURE: no payload made for config "boardid=3448;fab=000;boardsku=0000;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-nano-devkit;rootdev=mmcblk0p1"^M
FAILURE: no payload made for config "boardid=3448;fab=100;boardsku=0000;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-nano-devkit;rootdev=mmcblk0p1"^M
FAILURE: no payload made for config "boardid=3448;fab=200;boardsku=0000;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-nano-devkit;rootdev=mmcblk0p1"^M
FAILURE: no payload made for config "boardid=3448;fab=300;boardsku=0000;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-nano-devkit;rootdev=mmcblk0p1"^M
FAILURE: no payload made for config "boardid=3448;fab=200;boardsku=0002;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-nano-devkit-emmc;rootdev=mmcblk0p1"^M
FAILURE: no payload made for config "boardid=3448;fab=300;boardsku=0002;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-nano-devkit-emmc;rootdev=mmcblk0p1"^M
FAILURE: no payload made for config "boardid=3448;fab=300;boardsku=0003;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-nano-2gb-devkit;rootdev=mmcblk0p1"^M
FAILURE: no payload made for config "boardid=2180;fab=100;boardsku=;boardrev=;fuselevel_s=1;chiprev=0;board=jetson-tx1-devkit;rootdev=mmcblk0p1"^M
FAILURE: error cleaning BUP tmp files
cp: cannot stat '/devel/RTR/SW/alliedvision_linux_nvidia_jetson/avt_build/nx-workdir/Linux_for_Tegra/bootloader/payloads_t21x/bl_update_payload': No such file or directory
It seems that NX is not really taken into account in the createDeployTarball() function :
createDeployTarball()
{
rm -rf "$PATH_TARGET_DEPLOY_TMP_FOLDER"
mkdir -p "$PATH_TARGET_DEPLOY_TMP_FOLDER"
}
It looks like targets other than Xavier and TX2 would be considered as Nano/TX1 (t21x). Do you confirm?
Thanks and best regards,
Pascal.
deploy.log
The text was updated successfully, but these errors were encountered: