Custom kernel compilation - Jetson orin nano

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

Hi, i’m using jetson orin nano development kit to enable and test CSI to HDMI(Toshiba chip). Hence trying to include TC35843 driver in my kernel which is disabled by default in the tegra_defconfig. I did the following:
make ARCH=arm64 tegra_defconfig menuconfig
Enabled the driver
make ARCH=arm64 CROSS_COMPILE=$(CROSS_COMPILE_PATH)
The build goes through fine. I flashed the image with the flash script.
./flash.sh jetson-orin-nano-devkit mmcblk1p1
Flashing went through fine but the kernel doesnt boot.
I tried editing the boot order in extlinux.conf and placed my own kernel image in the boot directory. Still the kernel doesnt boot, neither does it revert to the working kernel.

What are my options to debug this ?

3

hello srinivas.bakki1,

may I know which release version you’re working with?
you may check release tag, i.e. $ cat /etc/nv_tegra_release for confirmation.

BTW,
please setup serial console to share the UART logs, we need to understand the root cause.

4

Im using jetson 5.1.2. R35.4.1
How to get uart logs?

5

please see-also Orin Nano serial console log.

6

Manually place the Image on the target.

Do Image.bak first then swap out the new kernel and reboot to see if the kernel actually does run.

We are building working kernels however their flash instructions are omitting critical details or just don’t function.

So much of the content in the manual is missing detail and clarity, it is beginning to look like intentional omissions. I post on here and only get bits and pieces, no one is posting a real working solution. Thought old age was getting the best of me, however reading so many posts by others here and other sites it might not be old age getting the best of me.

7

Ok, i could hook up serial console and found that it is unable to switch to rootfs, below are logs:

mmcblk1: mmc1:aaaa SD64G 59.5 GiB
[ 11.761987] mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15
[ 11.796228] Found dev node: /dev/mmcblk1p1
[ 11.973345] EXT4-fs (mmcblk1p1): recovery complete
[ 11.978301] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
[ 12.129576] Rootfs mounted over mmcblk1p1
[ 12.140905] Switching from initrd to actual rootfs
[ 12.151011] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 12.161755] CPU: 2 PID: 1 Comm: chroot Not tainted 5.10.120 #1
[ 12.170301] Hardware name: Unknown NVIDIA Orin Nano Developer Kit/NVIDIA Orin Nano Developer Kit, BI3
[ 12.184621] Call trace:
[ 12.189598] dump_backtrace+0x0/0x1d0
[ 12.196057] show_stack+0x30/0x40

I replaced only the Image in the kernel directory to run the flash.sh script. Anything i missed ?

Thanks

8

I tried flashing with nvsdkmanager_flash.sh . It flashed successfully and also the logs on the serial console didn’t show any panic. The console showed some license agreement and asked to finish jetson initialization but then i couldn’t control or input anything in the console.
On the display no screen, all blank.

9

hello srinivas.bakki1,

you don’t need to re-flash if you’re going to apply kernel change.
you may copy Image to your target to overwrite the binary file under… /boot/Image, performing a warm-reboot $ sudo reboot to have changes take effect.

please refer to developer guide, Skipping oem-config to creates a default user.

11

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