Now as per your comment, I want to confirm that instead of following this steps , I can directly replace the currect image in /boot folder with the new image and reboot the target.
Is my understanding correct?
If yes , I have one more concern that what if i fail in rebooting ,Is there any way to boot with old image then?
With respect to above steps I have one thing to ask that is there any way to check the version of the current original image in the target?
Like to know that whether it is r32.7.1 or some other. So that I can build new image also with right kernel source version.
In the above you would want to replace “LABEL primary” of the second entry to be “LABEL backup”.
FYI, I don’t think there is a direct way to tell which L4T release a kernel is from. The “signature” would be the combination of the output of “uname -r” and the configuration (which is “/proc/config.gz”).
I did all the above steps and replaced Image in /boot/ folder. Then I rebooted using command
“sudo shutdown -r now” but it took only 2 mins to reboot and my config changes are also not reflecting in zcat /proc/config.gz.
I think the image is not flashed and I am not able to get where is the mistake.
No my issue is not ressolved yet. As told by me in the last comment, I have got the image , then I tried to reboot my target after placing this image inside /boot/ folder on target but the image is not flashed it rebooted as normal, it just took 2 mins to reboot and everthing was same as before and my config changes also not reflecting. It seems that the new image is not flashed.
I can’t verify it, but what @user100090 says makes sense. If you replaced the Image file in “/boot”, and if extlinux.conf names that file in the “LINUX” key/value pair, then your kernel should have booted. It is indeed possible that the conf file itself was not read, and in that case the kernel would have been read only from a partition. A full serial console boot log should verify where the kernel was read from.