DESK-MX6UL-L/Development/Building Linux kernel

From DAVE Developer's Wiki
Jump to: navigation, search
ID# Issue Date Notes


21/07/2021 First DESK release


16/03/2022 DESK 3.0.0 release


05/05/2023 DESK 4.0.0 release

Building Linux[edit | edit source]

Quick reference[edit | edit source]

Repository Information
stable branch desk-mx6ul-l-4.x.x
stable tag desk-mx6ul-l-4.0.0

Build Information
defconfig imx_v7_desk_defconfig
Kernel binary UIMAGE_LOADADDR=0x80008000 uImage
Device trees Platform DTB
SBC Lynx imx6ul-lynx-som0013-cb002f.dtb
SDV04 imx6ul-axelulite-cb003a.dtb

Instructions[edit | edit source]

It is assumed that the development environment has been set up properly as described here.

  • start the Linux development VM and login into the system
  • open a terminal window and cd into Linux kernel source code
cd ~/desk-mx-l/linux
  • in case of needs you can update your local repository with the following git command
git pull
  • configure the build environment
source ~/desk-mx-l/
  • enter the source tree directory and run the following commands:
make imx_v7_desk_defconfig
make UIMAGE_LOADADDR=0x80008000 uImage imx6ul-lynx-som0013-cb002f.dtb imx6ul-axelulite-cb003a.dtb imx6ul-axelulite-cb006c.dtb

NOTE: this is the default configuration suitable for latest target.

The former command selects the default DESK-MX6UL-L configuration, while the latter builds the kernel binary image with the required u-boot header and the kernel device tree.

Default Linux kernel configuration can be changed by using the standard menuconfig, xconfig, or gconfig make target. Subsequent builds just require uImage make target to update the binary image. Once the build process is complete, the kernel binary image is stored into the arch/arm/boot/uImage file. Both this file and the kernel device tree can be copied to the tftp root directory /tftpboot/desk-mx-l/ with the following commands:

cp arch/arm/boot/uImage /tftpboot/desk-mx-l/
cp arch/arm/boot/dts/*.dtb /tftpboot/desk-mx-l/

Usually, kernel modules are installed with make modules_install command, but this method installs the modules into the /lib/modules directory of you MVM, which is not what you want.

A better way to deploy kernel modules while cross-compiling is

  • generate a .tar.gz archive
  • install this archive into the target root file system

User can create such an archive, for example, using the following commands:

make modules
mkdir modules-install
make INSTALL_MOD_PATH=modules-install modules_install

cd modules-install && tar cvzf ../modules.tar.gz . && cd ..

Now copy modules.tar.gz into the target root file system and install them as root with the following command

tar xvzf modules.tar.gz -C /