For versions of L4T newer than L4T 32.3, please see jetson-linux-build https://github.com/jetsonhacks/jetson-linux-build
Scripts to help build the 4.9.140 kernel and modules onboard the Jetson TX2 (L4T 32.3.1, JetPack 4.3). For previous versions, visit the 'tags' section.
Note: The kernel source version must match the version of firmware flashed on the Jetson. For example, the source for the 4.9.140 kernel here is matched with L4T 32.3.1. This kernel compiled using this source tree will not work with newer versions or older versions of L4T, only 32.3.1.
Note: You will probably only use these scripts to build and install modules. Even though there are scripts provided to build and copy the new kernel to the boot directory of the device, there is no effect. In newer versions of L4T, the kernel Image is actually signed and stored in a different partition on disk. The copyImage.sh script is legacy. In order to place the newly created Image, you will need to copy it to the correct place on the host and flash the eMMC. It is probably easier to build it on the host in the first place. The flash process on the host signs the Image, and copies it to the appropriate partition.
As of this writing, the "official" way to build the Jetson TX2 kernel is to use a cross compiler on a Linux PC. This is an alternative which builds the kernel onboard the Jetson itself. These scripts will download the kernel source to the Jetson TX2, and then compile the kernel and selected modules. The newly compiled kernel can then be installed. The kernel sources and build objects consume ~3GB.
These scripts are for building the kernel for the 64-bit L4T 32.3.1 (Ubuntu 18.04 based) operating system on the NVIDIA Jetson TX2. The scripts should be run directly after flashing the Jetson with L4T 32.3.1 from a host PC. There are six scripts:
getKernelSources.sh
Downloads the kernel sources for L4T from the NVIDIA website and decompresses them. Note that this also sets the .config file to the current system, and also sets the local version to the current local version, i.e., -tegra
makeKernel.sh
Compiles the kernel using make. The script commands make the kernel Image file. Installing the Image file on to the system is a separate step. Note that the make is limited to the Image and modules.
The other parts of the kernel build, such as building the device tree, require that the result be 'signed' and flashed from the the NVIDIA tools on a host PC.
makeModules.sh
Compiles the modules using make and then installs them.
copyImage.sh
Copies the Image file created by compiling the kernel to the /boot directory. Note that while developing you will want to be more conservative than this: You will probably want to copy the new kernel Image to a different name in the boot directory, and modify /boot/extlinux/extlinux.conf to have entry points at the old image, or the new image. This way, if things go sideways you can still boot the machine using the serial console.
You will want to make a copy of the original Image before the copy, something like:
$ cp /boot/Image $INSTALL_DIR/Image.orig
$ ./copyImage.sh
$ echo "New Image created and placed in /boot"
editConfig.sh
Edit the .config file located in /usr/src/kernel/kernel-4.9 This file must be present (from the getKernelSources.sh script) before launching the file. Note that if you change the local version, you will need to make both the kernel and modules and install them.
removeAllKernelSources.sh
Removes all of the kernel sources and compressed source files. You may want to make a backup of the files before deletion.
The copyImage.sh script copies the Image to the current device. If you are building the kernel on an external device, for example a SSD, you will probably want to copy the Image file over to the eMMC in the eMMC's /boot directory. The Jetson will usually try to boot from the eMMC before switching to a different device. Study the boot sequence of the Jetson to properly understand which Image file is being used.
Special thanks to Raffaello Bonghi (https://github.com/rbonghi) for jetson_easy scripts. Special thanks to Shreeyak (https://github.com/Shreeyak) for discussing alternatives to get source directly from NVIDIA git repositories. Special thanks to Alexander Rashed (@alexrashed on Github) for vL4T32.1.0 release
January, 2020
- vL4T32.3.1
- L4T 32.3.1 (JetPack 4.3)
May, 2019
- vL4T32.1.0
- L4T 32.1.0 (JetPack 4.2)
July, 2018
- vL4T28.2.1
- L4T 28.2.1 (JetPack 3.2.1)
- Fix issue with scripts jetson_variables to determine L4T version. ** Special thanks to Shreeyak (https://github.com/Shreeyak)
- Refactored scripts/getKernelSources and getKernelSourcesNoGUI
April, 2018
- vL4T28.2r3
- L4T 28.2 (JetPack 3.2)
- Add removeAllKernelSources.sh
- Add checks to make sure kernel version matches L4T release
April, 2018
- vL4T28.2r2
- L4T 28.2 (JetPack 3.2)
- Add getKernelSourcesNoGUI.sh for cases where the user does not want to edit the .config file through a GUI.
March, 2018
- vL4T28.2
- L4T 28.2 (JetPack 3.2 DP)
- Removed patches for make file cleanup
July, 2017
- vL4T28.1
- L4T 28.1 (JetPack 3.1)
March, 2017
- vL4T27.1
- L4T 27.1 (JetPack 3.0)
- Developers Preview
MIT License
Copyright (c) 2017-2020 Jetsonhacks Portions Copyright (c) 2015-2018 Raffaello Bonghi (jetson_easy)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.