Jetson AGX Xavier - BSP custom changes are gone and reset to defaults

Hi,

We have our custom BSP (based on L4T32.4.3) for AGX Xavier and custom carrier board.
Our customer recently done a system update(aptdaemon role=‘role-commit-packages’ sender=’:1.45’,apt upgrade,apt autoremove,apt install python3-pip) and all the changes we made in the dtb and kernel are gone and the custom interefaces are not working, it has been reset to default.

As by default, apt upgrade has NVIDIA OTA update package inside. So, it will install the jetpack back to your board defaults again. So after discussing with Nvidia support team we had asked them to remove nvidia source from your apt source list during updates or remove it from update packages.

they have a query below:

they would like to use the apt preference file to explicitly block the updates for the kernel packages that can’t be overwritten. This way they can receive relevant updates from nvidia’s repositories without risking the kernel or dtb being overwritten.

The following packages are listed for update from nvidia’s repo:

jetson-gpio-common

nvidia-l4t-apt-source

nvidia-l4t-bootloader

nvidia-l4t-configs

nvidia-l4t-core

nvidia-l4t-initrd

nvidia-l4t-jetson-io

nvidia-l4t-kernel

nvidia-l4t-kernel-dtbs

nvidia-l4t-kernel-headers

nvidia-l4t-oem-config

nvidia-l4t-tools

nvidia-l4t-xusb-firmware

python-jetson-gpio

python3-jetson-gpio

they have already blocked the three kernel packages, are there any others that will cause problems with the system? what all the packages they need to block if they don’t want to lose the custom dtb/kernel changes?

Is there any other method to avoid resetting to default?

any updates?

I don’t know what kind of customization you’ve done.

If you want to prevent fully erase, create your own deb files and use your own binary.