Hi,
I just flashed my Xavier AGX with latest Jetpack 4.4.
I completed the first boot procedure, setting user name, host name ecc.
Then Ubuntu automatically proposed an update to me via pop-up. I confirmed yes.
The update failed, and now every apt-get install command complains with the following error:
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up nvidia-l4t-bootloader (32.4.3-20200803161246) ...
2888-400-0001-E.0-1-2-cti/xavier/rogue-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
Errors were encountered while processing:
nvidia-l4t-bootloader
E: Sub-process /usr/bin/dpkg returned an error code (1)
Some additional info (commands copied from similar threads in the forum, I’m not sure about their meaning)
I am not sure if you want to understand why this issue happens, but still let me clarify it.
First, our upgrade/update only recognizes the board name of official nvidia devkit.
It means it will only work if you flash with official board name in original Linux_for_Tegra.
Second, the vendor like Connect Tech should share their own package to do OTA but not rely on NV. Currently, they don’t do this so the apt upgrade/update still uses the package from NV which causes the problem.
Luckily, the check in first point seems only with the board name. It means you could just rename the board config name from"rogue.conf" to the original board name provided NV and it should work.
Different hardware is often available at different addresses, and to avoid hard coding every possible combination into the Linux kernel, a device tree can be used (hot plug devices, e.g., USB, do not need this). Basically this can pass addresses of hardware and various settings which drivers can use. Two different carrier boards might use the same drivers, but the device tree would need to be altered to tell the drivers about how the hardware is arranged. This is part of “firmware”. The device tree (and other firmware) is part of the “board support package” (“BSP”).
The BSP which NVIDIA provides is specific to their development kit carrier board. When using a third party carrier board the base module content does not change, but the part of the BSP related to carrier board layout does change, and only the third party manufacturer can provide this. CTI will provide a BSP for the combination of module type and carrier board. Often using this BSP is basically an overlay on top of the standard install software. CTI will have instructions for this particular board on their website.
The mentioned CTI-L4T-AGX-32.4.3-v001.tgz is basically that overlay. I don’t know where the “./install” file is from, but if it is from CTI, then this is likely to unpack CTI-L4T-AGX-32.4.3-v001.tgz. If the “./install” is something else, then perhaps the content of their BSP was missed and not actually installed.