We are working on a custom board with the AGX Orin SOM using L4T R35.5.0.
After running the system update with the following commands:
sudo apt-get update
sudo apt-get upgrade
We encountered an issue where our custom-developed drivers and images reverted to the default settings. As a result, we are unable to detect any cameras, and the custom-developed code is no longer reflecting on the system. Before the update, everything was functioning perfectly.
I have attached the upgrade log for your reference. update.log (116.7 KB)
Your assistance in resolving this issue would be greatly appreciated.
This issue is not limited to the camera. Several other interfaces we developed, such as GPIOs, temperature sensors, IMU sensors, and others, are no longer functioning after the upgrade. Please forget the camera, as the problem affects multiple interfaces. everything has reverted to the default L4T BSP.
I checked that even the configuration file has been reset. I had previously enabled the device driver for the LM75 sensor, but after the upgrade, it reverted to the default state. I verified this using the command:
zcat /proc/config.gz | grep LM75
Additionally, our custom wallpaper, lock screen, and boot logos have all been changed by the default NVIDIA logo after the upgrade.
We are currently developing applications using CUDA, TensorRT, and several other packages, and upgrading the system is necessary for keeping these dependencies up to date. How can we manage these mandatory upgrades during development while ensuring our custom drivers, configurations, and interfaces are not overwritten? Is there a recommended approach to protect these custom elements during the upgrade process?
Even are using the Nvidia SOM from last 5 years never seen this kind of issues.
This is part of OTA upgrade. This feautre was not there 5 years ago but already been there for like at least 3 years.
If you have BSP related change for a custom board, then please do not arbitrarily upgrade BSP. You have to evaluate whether you need to upgrade it or not.
That is why each vendor has their own schedule to upgrade and do the driver porting.
CUDA/TensorRT are also Jetpack version specific. For example, CUDA A version might be only work on Jetpack5.1.2 while CUDA B version might only work with Jetpack5.1.1.
If you want to always keep the dependencies, then you need to prepare the driver to get porting again each time. We won’t know what got customized you’ve done on your side so we just provide a basic update here.
How can we ensure that the system doesn’t upgrade to the latest BSP during the update process? Is there a specific file or configuration we can modify to prevent the BSP from being upgraded when we run the apt-get upgrade? We want to make sure that the currently flashed BSP package is not affected by system updates.
We have used the Nano, TX2i, and AGX Xavier previously and never encountered this issue. However, we are facing it now on the AGX Orin.
We have used the Nano, TX2i, and AGX Xavier previously and never encountered this issue. However, we are facing it now on the AGX Orin.
All of above platforms have this mechanism… It could be some coincidence that you just didn’t notice this upgrade happen or just that thing didn’t happen because jepack major version is same.
As I already told, go to apt source list and remove NVIDIA related source repo.
If you want direct path, it should be /etc/apt/sources.list.d/nvidia-l4t-apt-source.list