Can you elaborate more on how to prepare my own deb file for OTA?
For example, I’m trying to install qemu-user-static, how can I prepare my own deb file for this pacakge? (see the errors below)
Hi,
Please use the deb file provided by us on host and modify the script inside it.
Which deb file exactly are you talking about?
And what to I need to modify in the script?
Hi shir,
Sorry that I didn’t notice you are newbie to this thread. Please forget about any deb related stuff here.
Just tell us what was your flash command for this board?
I followed the instructions here:
http://connecttech.com/resource-center/kdb373/
In the link you will see TX2 → JetPack 4.2.1 And Above
and then I followed this instructions(automatic flash script):
Hi,
Please rename the cti carrier profile config file to jetson-xavier.conf and reflash your board.
I have a TX2 board(sorry for posting in the xavier forum but I couldn’t find any other related thread)
Will it work to change to a different config file even though I got the orbitty carrier board?
There is no other way without re-flashing my board, I have a lot of important things I want to keep?
Hi,
Please get more familiar with the flash procedure first.
For example, have you ever run the command “sudo ./flash.sh jetson-tx2 mmcblk0p1” by yourself to flash the board?
If you have, then did you ever wonder how does this flash.sh read this “jetson-tx2”? Why not “jetson-tx2-123456” or something else?
To find the answer, please check those .conf files under Linux_for_Tegra folder and you shall know.
The same is applicable to the CTI carrier board profile too. What I want you to do is locate which config file you are using to flash, rename it to jetson-tx2.conf and flash the board.
OK, thanks.
As I understand you want me to do the following commands:
cd ~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_TX2/Linux_for_Tegra/cti/tx2
mv orbitty.conf jetson-tx2.conf
cd ~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_TX2/Linux_for_Tegra
./flash.sh cti/tx2/jetson-tx2 mmcblk0p1
But still there is no other solution for this problem without re-flashing the board and erase all my files?
Correct, but minor error here. Sorry that the flash.sh is not smart enough to get the file path.
./flash.sh cti/tx2/jetson-tx2 mmcblk0p1 → sudo ./flash.sh jetson-tx2 mmcblk0p1
But still there is no other solution for this problem without re-flashing the board and erase all my files?
You could try the clone first. This shall reserve your userspace partition.
https://elinux.org/Jetson/Clone
So to summarize, I will need to do the following:
cd ~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_TX2/Linux_for_Tegra/cti/tx2
mv orbitty.conf jetson-tx2.conf
cd ~/nvidia/nvidia_sdk/JetPack_4.4_DP_Linux_DP_JETSON_TX2/Linux_for_Tegra
#Clone
sudo ./flash.sh -r -k APP -G backup.img jetson-tx2 mmcblk0p1
#Flash
sudo cp backup.img bootloader/system.img
sudo ./flash.sh -r -k APP jetson-tx2 mmcblk0p1
Update:
I did all this steps and still I’m getting the same error:
Yes, looks correct.
I did all the steps I mentioned above and still the same error:
BTW:
cat /etc/nv_boot_control.conf:
TNSPEC 3310-D00-1000-E.0-1-0-cti/tx2/orbitty-mmcblk0p1
COMPATIBLE_SPEC 3310-B01---1--cti/tx2/orbitty-mmcblk0p1
TEGRA_CHIPID 0x18
TEGRA_OTA_BOOT_DEVICE /dev/mmcblk0boot0
TEGRA_OTA_GPT_DEVICE /dev/mmcblk0boot1
cat /opt/ota_package/bl_update_payload.log:
Nvidia A/B-Redundancy Update tool Version 1.2
current slot 0
Start updating slot 1
Tegra User Block Device: /dev/disk/by-partlabel
Tegra Boot Block Device: /dev/mmcblk0boot0
HEADER: MAGIC NVIDIA__BLOB__V2
HEX_VALUE 131072
BLOB_SIZE 12144017
HEADER_SIZE 48
NUMBER_OF_ELEMENTS 53
HEADER_TYPE 0
UNCOMP_SIZE 12144017
MB1_RATCHET_LV 0
MTS_RATCHET_LV 0
ROLLBACK_FUSE_LV 0
Device TN Spec: 3310-D00-1000-E.0-1-0-cti/tx2/orbitty-mmcblk0p1
Device Compatible Spec: 3310-B01---1--cti/tx2/orbitty-mmcblk0p1
Can't find matching TN Spec in OTA Blob!
OTA Blob update failed. Status: 3
/usr/sbin/nv_bootloader_payload_updater --no-dependent-partition failed.
Slot 1 update failed
Hi,
3310-D00-1000-E.0-1-0-cti/tx2/orbitty-mmcblk0p1
3310-B01—1–cti/tx2/orbitty-mmcblk0p1
Unfortunately, I guess you cannot use the clone during flash. There are still orbitty board name and it causes error.
BTW, why do you need to run nvidia-l4t-bootloader on orbitty-board? It is kind of not making sense.
Do you want to OTA upgrade?
I need to install jetpack(4.3/4.4)
Hi shir,
You have to ask vendor of Orbitty carrier board if they supports the official sdkmanager.
If they say “no”, then we don’t need to discuss current issue anymore. In that case, even after we resolve all these problems and make you flash the board, your board will still not boot up because incompatibility.
Hello @WayneWWW I am having the similar issue as @shir , I am also using the Carrier board alongside the TX2, and i am having this issue with the bootloader. I have few questions regarding this.
- I am having this bootloader issue at the time of fresh install without any of the above fixes that you have mentioned, post normal installation with the configuration from the supplier I am able to bootup properly, but whenever I install any applications, I have the following bootloader error as expected.
Setting up nvidia-l4t-bootloader (32.4.3-20200803161246) …
3310-B01—1–cti/tx2/quasar-mmcblk0p1
Starting bootloader post-install procedure.
ERROR. Procedure for bootloader update FAILED.
Cannot install package. Exiting…
dpkg: error processing package nvidia-l4t-bootloader (–configure):
installed nvidia-l4t-bootloader package post-installation script subprocess returned error exit status 1
-
Even though I apply the fix as you said replace the original configuration of the board with that of the supplier and do a fresh install.(I haven’t done this yet, but going to). Let’s say that I won’t have the above error, but then when an update to any of these packages arrive will I have any issues, I hope not, but it’s better to confirm?
-
What effects will I see in future, if I leave the TX2 with the above error?, because I couldn’t get the usage of this package as I am able to boot correctly as expected.
Sorry if the questions are super basic, but it does really help me to better understand the issue. I hope you don’t mind.
Thank you
Hi, I’m using TX2 with Jatpack 4.4, L4T 32.4.2. I’m downloading pytorch 1.4 which is for 32.4.2 , to be specific, I use the command line in the instruction guide, which I attached below
wget https://nvidia.box.com/shared/static/1v2cc4ro6zvsbu0p8h6qcuaqco1qcsif.whl -O torch-1.4.0-cp27-cp27mu-linux_aarch64.whl
sudo apt-get install libopenblas-base libopenmpi-dev
pip install future torch-1.4.0-cp27-cp27mu-linux_aarch64.whl
However, I’m getting that error like shown in the screenshot, I have already posted the question under the forum of Downloading pytorch. However, they said it’s not related to pytorch downloading, but rather nvidia-l4t-bootloader. Is there anyway I can solve this? Thanks a lot!
Hi,
I think you could remove nvidia related source from your source list.
/etc/apt/sources.list.d/nvidia-l4t-apt-source.list
This issue is due to the board name check in NVIDIA official bootloader updater. This is a reasonable design because currently we don’t support OTA upgrade on custom carrier board.
We need to put a check here to prevent custom carrier board failing to work anymore.
@WayneWWW Thanks for the info. If I remove these sources, it will only prevent it to install only following l4t packages right?. Will I loose access to any other packages other than the following ones?. Please let us know.
saikishor@jetson:~$ dpkg -l | grep nvidia
ri libnvidia-container-tools 0.9.0~beta.1 arm64 NVIDIA container runtime library (command-line tools)
ri libnvidia-container0:arm64 0.9.0~beta.1 arm64 NVIDIA container runtime library
ri nvidia-container-runtime 3.1.0-1 arm64 NVIDIA container runtime
ri nvidia-container-toolkit 1.0.1-1 arm64 NVIDIA container runtime hook
ii nvidia-cudnn8 4.4-b186 arm64 NVIDIA CUDNN8 Meta Package
ri nvidia-docker2 2.2.0-1 all nvidia-docker CLI wrapper
ri nvidia-l4t-3d-core 32.4.3-20200625213407 arm64 NVIDIA GL EGL Package
ri nvidia-l4t-apt-source 32.4.3-20200625213407 arm64 NVIDIA L4T apt source list debian package
iF nvidia-l4t-bootloader 32.4.3-20200803161246 arm64 NVIDIA Bootloader Package
ri nvidia-l4t-camera 32.4.3-20200625213407 arm64 NVIDIA Camera Package
ri nvidia-l4t-configs 32.4.3-20200625213407 arm64 NVIDIA configs debian package
ri nvidia-l4t-core 32.4.3-20200625213407 arm64 NVIDIA Core Package
ii nvidia-l4t-cuda 32.4.3-20200625213407 arm64 NVIDIA CUDA Package
ri nvidia-l4t-firmware 32.4.3-20200625213407 arm64 NVIDIA Firmware Package
ri nvidia-l4t-graphics-demos 32.4.3-20200625213407 arm64 NVIDIA graphics demo applications
ii nvidia-l4t-gstreamer 32.4.3-20200728225313 arm64 NVIDIA GST Application files
ri nvidia-l4t-init 32.4.3-20200625213407 arm64 NVIDIA Init debian package
ri nvidia-l4t-initrd 32.4.3-20200625213407 arm64 NVIDIA initrd debian package
ri nvidia-l4t-jetson-io 32.4.3-20200625213407 arm64 NVIDIA Jetson.IO debian package
ri nvidia-l4t-kernel 4.9.140-tegra-32.4.3-20200805-CTI-TX2-V001 arm64 Connect Tech Jetson TX2 Kernel Package
ri nvidia-l4t-kernel-dtbs 4.9.140-tegra-32.4.3-20200805-CTI-TX2-V001 arm64 Connect Tech Jetson DTB Package
ri nvidia-l4t-kernel-headers 4.9.140-tegra-32.4.3-20200805-CTI-TX2-V001 arm64 Connect Tech Jetson Headers Package
ri nvidia-l4t-multimedia 32.4.3-20200625213407 arm64 NVIDIA Multimedia Package
ri nvidia-l4t-multimedia-utils 32.4.3-20200625213407 arm64 NVIDIA Multimedia Package
ri nvidia-l4t-oem-config 32.4.3-20200625213407 arm64 NVIDIA OEM-Config Package
ii nvidia-l4t-tools 32.4.3-20200803161246 arm64 NVIDIA Public Test Tools Package
ri nvidia-l4t-wayland 32.4.3-20200625213407 arm64 NVIDIA Wayland Package
ri nvidia-l4t-weston 32.4.3-20200625213407 arm64 NVIDIA Weston Package
ri nvidia-l4t-x11 32.4.3-20200625213407 arm64 NVIDIA X11 Package
ri nvidia-l4t-xusb-firmware 32.4.3-20200625213407 arm64 NVIDIA USB Firmware Package
Thank you,