I am using the JP5.1.2 baseline version. The current version is also based on JP5.1.2, but the kernel, config, and ko have all changed. I also need to add ko and delete ko. Can I use the following OTA method to perform OTA operations?
The generated file is 318M in total, which is less than 2G. Is this wrong? Please help me find out what the problem is?
If I perform an OTA action, will the existing files under the / directory be lost? For example, the current configuration file is stored in the /etc directory. This is configured by the user later. It is not included in the image by default.
Hi, DavidDDD:
I think that by upgrading the following software package, you can also realize the kernel’s OTA bar? I’m re-installing a customized version, which includes our custom code and image modification.
That’s okay too?
The kernel and dtb have already been compiled and passed.
However, how to generate the following document package, we have guidance document?
Hi DavidDDD:
We developed based on JP5.1.2 and the device has been running for nearly 1 year.
We want to upgrade to the latest version of JP5.1.2 by the deb package.
I noticed that the main kernel files of our system are put in the following four files. Can I package the current compiled kernel version into us, and then upgrade the kernel directly to the latest state through the deb package.
$ ./nvdebrepack.sh -h
Usage: nvdebrepack.sh [-d <pkg>=<ver>,...] [-f <file>] [-h] [-i <src>:<dst>[:<perm>]] [-m <msg>]
[-n <maintainer>] [-v <ver>] package.deb
-d update the version number of a particular dependent package. The version number is specified
in the format <pkg>=<version>. Multiple packages can be specified with commas.
-f specify an injection file. Each line in the file represents a regular file to be injected and
should comply with the format: <source>:<destination>[:<permission>]. File permission must be
specified for a new file.
-h show this help.
-i specify a particular file to be injected. The file must be specified in the format mentioned
in '-f' otpion. Multiple files can be specified with multiple '-i' options.
-m specify a comment line to be added in the changelog. The default is "Custom version.".
-n specify maintainer info in the format: "full name <email-address>". This option is mandatory.
-v specify a custom version string. The string will be appended to the L4T package version
with a "+". The default is "default0".
Hi DavidDDD:
I modified the Image, kernel tega_config, and added d4xx.ko, so how do I use this script?
If tega_config is modified, it will affect many kos, but I can’t be sure which ones are affected.