I want to archive this kernel supplements.tbz2 and place it on my target as I need to do third party driver kernel module build on my target and this is required. Here can I know what does the ‘modules_install_path’ in the below command ‘‘cd <modules_install_path>’’ mean. which is the folder they are speaking here?
Also want to know if the tar command in this step will archive even the folders pointed by the softlinks also, as I will get broken links on my target after flashing for the folders: /lib/modules/<kernel_version>/ build and /lib/modules/<kernel_version>/ source .
You mean we need to download the source from Nvidia website on the target directly and do the complete build process steps on the target itself?
If that is the case, how do flash command that we were executing from the host pc work?
how to use the flash command on the target itself?
I thought this tar command and taking kernel supplements zip file was used to solve this broken link issue on the target PC. I also read that if we use -h option for the tar command then this zip all the files for the symbolic linked ones also so that we can extract these on the target so that broken links are resolved and we dont have any build issue of third party drivers on the target.
Pls clarify. Thanks.
Could you please let us know your thoughts on using this tar command to compress the /lib/modules/ files and copy them to target and fix the broken links, so that we can build the third party drivers ( example, my frame grabber camlink driver source ) with out any issues.
I will try to flash generic kernel version( with out RT ) on my target first, as this one does not have broken link issues as per my current study and understanding.
If I can successfully build my camlink driver on the target with generic kernel version, then there is no need for me to build kernel on my target.
If non RT kernel version also fails to build my third part driver file, then will try RT kernel build on target and try my luck! THanks.
I have few questions regarding building kernel on the Jetson device itself:
I have my other interface like CAN, GPIO, Audio etc changes done through device configuration, pin muxing etc on host PC. If I flash these changes on to my target then the kernel build done for CAMLink third part driver compilation will get erased.
How to resolve this conflict?
If I can do kernel build on my target itself all the time, then I can do the changes for enabling my other interfaces like CAN, Audio etc on the target itself. What is the need of Host PC then?
After every thing is working, i need to flash the working image/modules etc on many boards. How to go about this ?
I meant some changes I have done on my host PC like modifying device tree files. pin muxing etc and later flashing to the target. But some third party drivers build I need to do it on the target always, as CROSS COMPILATION might not work, it may throw errors. In that case, the image on the target will be erased during flashing and my third driver compilation data on target will be lost.
Any work around for this?
If I do everything on my target, then how to flash the final working image/dtb etc from my target board to other new boards?
Ok fine. So I need to replace the built DTB/ image file with the image and DTB file under /boot/ directory and reboot the target right?
Please point me to the documentation where we can do this. My module is Jetson AGX Xavier Industrial.