Hello Nvidia team,
-
we are using Orin Nano(8GB) with custom carrier board with 36.3 L4T.
-
we were able to customize drivers and all and device was working fine,
-
when we were trying to optimize the boot time, by doing config changes kernel for disabling degbugging, we are not able flash, getting error as below
and attached the flash logs,
logs.txt (4.0 KB)
-
Below are the configs we disabled by referring this link
CONFIG_DEBUG_KERNEL=n
CONFIG_FTRACE=n
CONFIG_TRACING=n
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/SD/Kernel/BootTimeOptimzation.html?highlight=optimization
DEBUG logs attachedProcessing: logs.txt…
please help us to resolve this, are we missing any steps here.
the log upload seems failed. Please upload again.
I mean I need your UART console log…
Host_logs.txt (306.0 KB)
OrinNano_device_logs.txt (105.8 KB)
Hello @WayneWWW , please find attached logs for device and host
I saw some exec format error in your log.
modprobe: ERROR: could not insert ‘tegra_mce’: Exec format error
modprobe: ERROR: could not insert ‘spi_tegra210_quad’: Exec format error
Did you remember to build the kernel modules too after you build the image?
yes @WayneWWW ,
we followed this steps for kernel compile and module loading, before flashing.
The driver in use in initrd flash is in use in the initrd. Are you sure you decompress initrd and put your new modules in it?
yes, we followed the same procedure we use to follow earlier also for kernel compilation, we are seeing this issue only after making changes for
CONFIG_DEBUG_KERNEL=n
CONFIG_FTRACE=n
CONFIG_TRACING=n
I mean did you put your new kernel modules into initrd…
yes @WayneWWW ,
we put new kernel modules in initrd.
below are the commands used
-
export INSTALL_MOD_PATH=<path to install>/rootfs
-
sudo -E make install -C kernel
-
cp kernel/kernel-jammy-src/arch/arm64/boot/Image /home/bharath.gk@happiestminds.com/projects/EADEN/OrinNano/36.3_rev2/Linux_for_Tegra/kernel/Image
Your command did not put anything into initrd.
Initrd image is under Linux_for_Tegra/bootloader and you need to unpack it…
ok @WayneWWW .
as per my observation those steps are not mentioned anywhere in BSP development documents. thats why i got diverted.
do meen this step to do?
if not, can u please share us steps we are missing apart from the previous comment ones.
Yes, that command is needed. Make sure initrd image got updated after you ran this command.
yes, but
build linux kernel having only these steps,
but out of tree modules compilation is having that step,
so got confused weather we are doing right steps, we request please help us here to choose among those steps.
Always take kernel image and kernel modules as pairs. If you rebuild kernel image, you have to rebuild kernel modules to make sure they are matched.
1 Like
but untill today we were able to add our new drivers and customize kernel drivers as per our requirement, but w.r.t DEBUG-KERNEL option only we are facing this issue,
yes our initrd.img is old one
i will use that script to update and see
hi @WayneWWW ,
even after doing that still getting error while flashing,attached the logs for reference.
here is the flash error, kindly help us to know what mistake we are doing.
OrinNano_device_logs2.txt (128.2 KB)
Host_logs2.txt (306.5 KB)
Looks like error is still same.
modpro[ be: ERROR: c.58ould not insert ‘tps:egrsagce’: Exec format errors a
t version of symbol minsmod /lodumodle_s/5.15.136-tegra/updates.60ivers/spi/spi-tegra210-quad.ko mce
isagremodprobe: ERROR: could not insut ‘spi_tegverra210_n od’: Exec format errormod
Please manually unpack your initrd image and see if the ko files there are really the one that built by you.
Are you sure your kernel modules are really built from ARM64?
BTW, I am not sure why your UART console looks so out of order. Maybe you should fix that first. Only one console should be opened at one time.
we will do that and let you know. can you please share us the command for doing above.
Yes, we have set cross compilation environment.
is that flash error is not about the partition/size issue?
