JetPack4.6.2 using its own compiled Image is invalid

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
1

I use SDK Manager to flash JetPack 4.6.2 to Jetson Xavier NX. Then replace the Image in the /boot directory with the Image I compiled myself.

After restarting, use the dmesg | head command to find that the system still uses the built-in Image.

JetPack4-6-2
JetPack4-6-21358×317 69.6 KB

Here is the compile command I use:

make -C kernel/kernel-4.9/ ARCH=arm64 O=$TEGRA_KERNEL_OUT BUILD_NUMBER= LOCALVERSION=-tegra CROSS_COMPILE=${TOOLCHAIN_PREFIX} tegra_defconfig
make -C kernel/kernel-4.9/ ARCH=arm64 O=$TEGRA_KERNEL_OUT BUILD_NUMBER= LOCALVERSION=-tegra CROSS_COMPILE=${TOOLCHAIN_PREFIX} -j$(nproc) --output-sync=target zImage
make -C kernel/kernel-4.9/ ARCH=arm64 O=$TEGRA_KERNEL_OUT BUILD_NUMBER= LOCALVERSION=-tegra CROSS_COMPILE=${TOOLCHAIN_PREFIX} -j$(nproc) --output-sync=target dtbs

Do you need to set anything else？

3

There is a bug for this on jp4.6.2 because extlinux.conf is not loaded correctly.

You can flash the image instead of replacing the one under /boot/Image to workaround this issue.

4

OK, thanks.

5

Hi, has the problem of extlinux.conf not being loaded correctly has been fixed?

6

Yes, please check

https://elinux.org/Jetson/L4T/r32.7.x_patches

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.