How does PX2 refresh the kernel?

Autonomous Vehicles DRIVE PX 2 DRIVE - Linux
1

How does PX2 refresh the kernel?

  1. Back up the original kernel binaries’ Image and zImage files.
  2. Copy the updated Image and zImage files to the directory:
    /drive-t186ref-linux/kernel-rt_patches
  3. Enter this command to update the partition:
    ./bootburn.sh -b <p3407-t186|p2379c01-t186a|p2379c01-t186b> -u kernel
  4. To identify the partition name, consult the configuration file used for flashing.

Following the above steps, the kernel has not been replaced. Is the replacement address incorrect?

For Linux:
cd /drive-t186ref-foundation
make -f Makefile.bind PCT=linux BOARD=

./bootburn.sh -b p2379c01-t186a -u kernel

This method does not work either. I saw the path in the cfg file is correct.

./bootburn.sh -b p2379c01-t186a -s -l
It is now only possible to burn the kernel and device tree in this way but it takes 5 minutes to burn.
Is there any way to directly write the kernel or device tree, or can it be the same as TX2, directly SCP or dd?

2

Dear Calmcar-Bao,

Could you please try to use RCM boot or the “-R” option in bootburn – i.e., “./utils/scripts/bootburn/bootburn.sh -b p2379c01-t186a -R?

This assumes you following the instructions in the System Programming section of the docs to build the kernel and copy to the correct directory

http://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%2520Vibrante%2520Linux%2520DPX%2520Development%2520Guide%2FSystem%2520Programming%2Fsys_programming_kernel_toolchain.html%23

3

./bootburn.sh -b p2379c01-t186a -R

After the burning is successful, the kernel is indeed replaced, but the original kernel is restored after the restart. What’s happening here?

4

Dear Calmcar-Bao,

Could you please refer to below link for bootburn options?
https://docs.nvidia.com/drive/nvvib_docs/index.html#page/NVIDIA%2520DRIVE%2520Linux%2520SDK%2520Development%2520Guide%2FFlashing%2Fflashing_lnx.html

5

There is a reference to this link, most of the brush parameters are tested, but the strange thing is that

./bootburn.sh -b p2379c01-t186a -s
      ./bootburn.sh -b p2379c01-t186a 
      ./bootburn.sh -b p2379c01-t186a -s -l

This kind of large-scale brush writing method is still a new kernel after restarting.

./bootburn.sh -b p2379c01-t186a -u kernel
      ./bootburn.sh -b p2379c01-t186a -R

The kernel is written separately, and the kernel will restore the original kernel after restarting.

Is it possible to relate to the way I write?

Copy the updated Image and zImage files to the directory:
  /drive-t186ref-linux/kernel-rt_patches
tegrarecovery ab on
tegrareset
./bootburn.sh -b p2379c01-t186a -R
tegrarecovery ab off
tegrareset

Is it wrong?