Can we SCP module.ko file directly into Target

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

Hello,

I have flashed linux kernel version 4.9 (L4T 32.4.4) Ubuntu 18.04 , in my Jetson NX SOM module carrier board.
I have successfully compiled and build a gpio driver and prepared a .KO file
About Module
$ file gpio-ls1-led.ko
gpio-ls1-led.ko: ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), BuildID[sha1]=0443c6a1aafdc00a92c45feaf51800058a56a178, with debug_info, not stripped

**$ modinfo gpio-ls1-led.ko**
filename:       /kernel/Linux_for_Tegra/source/public/kernel/kernel-4.9/kernel_build/drivers/gpio/gpio-ls1-led.ko
license:        GPL
depends:
intree:         Y
vermagic:       4.9.140 SMP preempt mod_unload modversions aarch64

MY DOUBT IS
As i want to test this module in target machine , so instead of preparing a SD card image and flashing it in SOM . Can i directly scp this gpio-ls1-led.ko file from (linux) to Target board (nvidia som) and try inserting module (sudo insmod gpio-ls1-led.ko).

If yes , then please tell me how to do it,
If no, then please tell me why can;t.

Thanks in advance

2

If the module were compiled correctly (including CONFIG_LOCALVERSION matching the running system), then you can just copy it like a regular file. There is no need to flash to add a module. The location of modules starts here:
/lib/modules/$(uname -r)/kernel

Note that the running kernel determines the output of “uname -r”, and you should run this on the Jetson and take note of this. The basic idea is that “uname -r” starts with the base kernel version, and then appends the “CONFIG_LOCALVERSION” (which is usually “-tegra” on a Jetson). This determines where a running kernel looks for its modules.

Note that if you cd to “/lib/modules/$(uname -r)/kernel”, and then run ls, that the directories are a match for some of the directories in your actual kernel source. The specific module is placed in that matching subdirectory. So if your module in kernel source building ends up at subdirectory “gpio/gpio-ls-led.ko”, then the correct module location would be:
/lib/modules/$(uname -r)/kernel/gpio/gpio-ls-led.ko

You might have to use sudo mkdir /lib/modules/$(uname -r)/kernel/gpio first, but then any file copy method (including scp) which places the file there would work (assuming once again that the module was compiled correctly using the right CONFIG_LOCALVERSION).

3

does find or locate find the file at all at the filesystem? is it present or deleted?