Debian Build Release: Difference between revisions

From Variscite Wiki
(Undo revision 27596 by Pitchaiah (talk))
Tag: Undo
 
(74 intermediate revisions by 7 users not shown)
Line 1: Line 1:
<!-- Set release according to "release" parameter in URL and use RELEASE_STRETCH_V3.0_DART-6UL as default
<!-- Set release according to "release" parameter in URL and use RELEASE_STRETCH_V3.0_DART-6UL as default
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!--
--> {{INIT_RELEASE_PARAM|RELEASE_STRETCH_V3.0_DART-6UL}} <!--
--> {{#lst:Debian_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_STRETCH_V3.0_DART-6UL}}}} <!--
--> {{#lst:Debian_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!--
--> {{PageHeader|{{#var:HARDWARE_NAME}} - Debian {{#var:DEBIAN_NAME}} {{#var:DEBIAN_VERSION}} with {{#var:KERNEL_BRANCH}} Linux release}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Debian}}
--> {{PageHeader|{{#var:HARDWARE_NAME}} - Debian {{#var:DEBIAN_NAME}} {{#var:DEBIAN_VERSION}} with {{#var:KERNEL_BRANCH}} Linux release}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Debian}}


Line 8: Line 8:
= Overview =
= Overview =
This page describes how to build and install Debian distribution ({{#var:DEBIAN_NAME}}) on Variscite boards with {{#var:HARDWARE_NAME}}.
This page describes how to build and install Debian distribution ({{#var:DEBIAN_NAME}}) on Variscite boards with {{#var:HARDWARE_NAME}}.
These instructions were tested on an '''Ubuntu 16.04 x64 host PC'''. When using other distributions, there may be problems.


Please note that the build script is based on ''debootstrap''. As described in the following instructions, it's kindly suggested to '''create the build folder on the main Ubuntu volume on your host PC''' rather than an external media.<br>
Please note that the build script is based on ''debootstrap''. As described in the following instructions, it's kindly suggested to '''create the build folder on the main Ubuntu volume on your host PC''' rather than an external media.<br>
Line 15: Line 13:


= Create build environment =
= Create build environment =
These instructions were tested on '''Ubuntu {{#ifexpr: {{#var:DEBIAN_VERSION}} < 10 | 16.04/18.04 | {{#ifexpr: {{#var:DEBIAN_VERSION}} < 12 | 18.04/20.04 | 20.04/22.04 }} }} x64 host PCs'''. When using other distributions, there may be issues.
{{Note|'''Note:''' Variscite provides Docker containers that can be used for a development environment as an alternative to using a virtual machine or a dedicated computer.
To learn more, please see Variscite's [[Docker_Build_Environment | Docker Build Environment]] guide.
Windows with WSL/WSL2 is not supported for development}}


== Installing required packages ==
== Installing required packages ==
Line 21: Line 24:


  $ sudo apt-get install binfmt-support qemu qemu-user-static debootstrap kpartx \
  $ sudo apt-get install binfmt-support qemu qemu-user-static debootstrap kpartx \
  lvm2 dosfstools gpart binutils bison git lib32ncurses5-dev python-m2crypto gawk wget \
  lvm2 dosfstools gpart binutils bison git lib32ncurses5-dev libssl-dev gawk wget \
  git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev \
  git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev \
  autoconf libtool libglib2.0-dev libarchive-dev python-git xterm sed cvs subversion \
  autoconf libtool libglib2.0-dev libarchive-dev xterm sed cvs subversion \
  kmod coreutils texi2html bc docbook-utils python-pysqlite2 help2man make gcc g++ \
  kmod coreutils texi2html bc docbook-utils help2man make gcc g++ \
  desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial automake groff curl \
  desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial automake groff curl \
  lzop asciidoc u-boot-tools mtd-utils device-tree-compiler flex
  lzop asciidoc u-boot-tools mtd-utils device-tree-compiler flex cmake zstd udisks2  libgnutls28-dev \
python-pysqlite2 python-git python-m2crypto python-pyelftools
 
{{#ifexpr: {{#var:DEBIAN_VERSION}} >= 10 |<br>
While installing the packages, Ubuntu 20.04 users may receive the warning
<pre>
Package python-git is not available, ...
</pre>
Since the package is only available in up to Ubuntu 18.04, just ignore it and run:
<pre>
$ sudo apt-get install python3-git python3-m2crypto python3-pyelftools
</pre>
 
Note: If you are using Ubuntu 20.04 the QEMU package must be updated to latest version (>= 1:4.2-3ubuntu6.19). <br>
To check the currently installed version of the qemu-user-static package on Ubuntu 20.04 LTS, use the below command:<br>
$ apt list qemu-user-static
|}}


== Deploy source ==
== Deploy source ==
 
{{DEBIAN_CODEAURORA_MIGRATION_NOTE}}
Download archive containing the build script and support files for building Debian {{#var:DEBIAN_NAME}} for this board:
Download archive containing the build script and support files for building Debian {{#var:DEBIAN_NAME}} for this board:


Line 56: Line 75:
Or, to build for i.MXQXP SOC revision B0:
Or, to build for i.MXQXP SOC revision B0:
  $ cd {{#var:BUILD_FOLDER}}
  $ cd {{#var:BUILD_FOLDER}}
  $ {{#var:BUILD_SCRIPT_B0}} -c all
  $ sudo {{#var:BUILD_SCRIPT_B0}} -c all
|}}|}}
|}}|}}


Line 70: Line 89:
|}}|}}
|}}|}}


=== Build kernel, dtb files and kernel modules ===
{{#ifexpr: {{#var:DEBIAN_VERSION}} >= 12
|
=== Build Linux kernel packages ===
 
$ cd {{#var:BUILD_FOLDER}}
$ sudo {{#var:BUILD_SCRIPT}} -c kernelpackage
|
=== Build kernel, dtb files, kernel modules, and kernel headers ===


  $ cd {{#var:BUILD_FOLDER}}
  $ cd {{#var:BUILD_FOLDER}}
  $ sudo {{#var:BUILD_SCRIPT}} -c kernel
  $ sudo {{#var:BUILD_SCRIPT}} -c kernel
  $ sudo {{#var:BUILD_SCRIPT}} -c modules
  $ sudo {{#var:BUILD_SCRIPT}} -c modules
$ sudo {{#var:BUILD_SCRIPT}} -c kernelheaders
{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8X |{{#ifeq: {{#var:MACHINE_NAME_B0}} | imx8qxpb0-var-som |
{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8X |{{#ifeq: {{#var:MACHINE_NAME_B0}} | imx8qxpb0-var-som |
Or, to build kernel, dtb, kernel modules for i.MXQXP SOC revision B0:
Or, to build kernel, dtb, kernel modules for i.MXQXP SOC revision B0:
  $ sudo {{#var:BUILD_SCRIPT_B0}} -c kernel
  $ sudo {{#var:BUILD_SCRIPT_B0}} -c kernel
  $ sudo {{#var:BUILD_SCRIPT_B0}} -c modules
  $ sudo {{#var:BUILD_SCRIPT_B0}} -c modules
|}}|}}
$ sudo {{#var:BUILD_SCRIPT_B0}} -c kernelheaders
|}}|}}}}


=== Build rootfs ===
=== Build rootfs ===
Line 86: Line 114:
  $ cd {{#var:BUILD_FOLDER}}
  $ cd {{#var:BUILD_FOLDER}}
  $ sudo {{#var:BUILD_SCRIPT}} -c rootfs
  $ sudo {{#var:BUILD_SCRIPT}} -c rootfs
{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8X |{{#ifeq: {{#var:MACHINE_NAME_B0}} | imx8qxpb0-var-som |
Or, to build rootfs for i.MXQXP SOC revision B0:
$ sudo {{#var:BUILD_SCRIPT_B0}} -c rootfs
|}}|}}


=== Pack rootfs ===
=== Pack rootfs ===
Line 93: Line 125:
  $ sudo {{#var:BUILD_SCRIPT}} -c rtar
  $ sudo {{#var:BUILD_SCRIPT}} -c rtar
  {{#ifeq: {{#var:PROVIDE_UBIFS}} | NO ||$ sudo {{#var:BUILD_SCRIPT}} -c rubi}}
  {{#ifeq: {{#var:PROVIDE_UBIFS}} | NO ||$ sudo {{#var:BUILD_SCRIPT}} -c rubi}}
{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8X |{{#ifeq: {{#var:MACHINE_NAME_B0}} | imx8qxpb0-var-som |
Or, to pack rootfs for i.MXQXP SOC revision B0:
$ sudo {{#var:BUILD_SCRIPT_B0}} -c rtar
|}}|}}
{{#ifeq: {{#var:TIGHT_NAND}} | true |
Note: <span style="color:red">The NAND filesystem is console only and may not have all the features as eMMC/SD card</span> <br>
To fit the NAND UBIFS filesystem as per your need, optimize the UBIFS by removing the packages.
|}}


= Create boot SD card =
= Create boot SD card =
Line 101: Line 142:
  $ cd {{#var:BUILD_FOLDER}}
  $ cd {{#var:BUILD_FOLDER}}
  $ sudo {{#var:BUILD_SCRIPT}} -c sdcard -d /dev/sdX
  $ sudo {{#var:BUILD_SCRIPT}} -c sdcard -d /dev/sdX
{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8X |{{#ifeq: {{#var:MACHINE_NAME_B0}} | imx8qxpb0-var-som |
Or, to build sdcard for i.MXQXP SOC revision B0:
$ sudo {{#var:BUILD_SCRIPT_B0}} -c sdcard -d /dev/sdX
|}}|}}


where '/dev/sdX' path to the block SD device in your system.
where '/dev/sdX' path to the block SD device in your system.
== Create a boot SD card image using a loop device ==
It is also possible to use the "{{#var:BUILD_SCRIPT}}" script to create a boot SD card image, while using a loop device instead of attaching a real SD card.<br>
<br>
Create an empty file using the following command:
$ dd if=/dev/zero of={{#var:MACHINE_NAME}}-debian-sd.img bs=1M count=3720
The above command creates a 3700MiB file representing the SD card.<br>
<br>
Attach the first available loop device to this file:
$ sudo losetup -Pf {{#var:MACHINE_NAME}}-debian-sd.img
To find the actual loop device being used, run:
$ losetup -a | grep {{#var:MACHINE_NAME}}-debian-sd.img
Write the content to the loop device to generate the SD card image:
$ sudo {{#var:BUILD_SCRIPT}} -c sdcard -d /dev/loopX
(Replace /dev/loopX with your actual loop device, e.g. /dev/loop0)<br><br>
Detach the loop device from the file:
$ sudo losetup -d /dev/loopX
To compress the SD card image file use the following command:
$ gzip -9 {{#var:MACHINE_NAME}}-debian-sd.img
To write the SD card image to a real SD card device use the following command:
$ zcat {{#var:MACHINE_NAME}}-debian-sd.img.gz | sudo dd of=/dev/sdX bs=1M && sync
(Replace /dev/sdX with your actual SD device, e.g. /dev/sdb)


= Boot the board with a bootable SD card =
= Boot the board with a bootable SD card =
Line 180: Line 254:
where the "-b" option provide the carrier board used (MX6CustomBoard/SOLOCustomBoard/DART-MX6) and the "-t" option provide the touch type when using MX6CustomBoard (ignored otherwise).
where the "-b" option provide the carrier board used (MX6CustomBoard/SOLOCustomBoard/DART-MX6) and the "-t" option provide the touch type when using MX6CustomBoard (ignored otherwise).
|
|
{{#ifeq: {{#var:HARDWARE_NAME}} | DART-MX8M-MINI |
{{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX8 |
<pre>
<pre>
# install_debian.sh
# install_debian.sh -d <lvds|hdmi|dp>
</pre>  
</pre>  
where the "-d" option set display type, default is lvds.
|
|
{{#ifeq: {{#var:HARDWARE_NAME}} | DART-MX8M |
{{#ifeq: {{#var:HARDWARE_NAME}} | DART-MX8M |
Line 189: Line 264:
# install_debian.sh -d <lvds|hdmi|dp|dual-display>
# install_debian.sh -d <lvds|hdmi|dp|dual-display>
</pre>
</pre>
where the "-d" option set display type, default is lvds.
|
|
{{#ifeq: {{#var:HARDWARE_NAME}} |VAR-SOM-MX8M-NANO |
<pre>
<pre>
# install_debian.sh
# install_debian.sh
</pre>
|
<pre>
# install_debian.sh -d <lvds|hdmi|dp>
</pre>
</pre>
}}
}}
}}
where the "-d" option set display type, default is lvds.
}}
}}
}}
}}
Line 244: Line 313:
  9. $ sudo cp defconfig arch/{{#var:ARCH}}/configs/{{#var:KERNEL_DEFCONFIG}}
  9. $ sudo cp defconfig arch/{{#var:ARCH}}/configs/{{#var:KERNEL_DEFCONFIG}}
  10. Follow the instructions above to rebuild kernel and modules, repack rootfs images and recreate SD card
  10. Follow the instructions above to rebuild kernel and modules, repack rootfs images and recreate SD card
{{#ifexpr: {{#var:DEBIAN_VERSION}} >= 10 |
= How-to: Build and install a custom device tree =
To build and install a custom device tree, add the filename to G_LINUX_DTB in https://github.com/varigit/debian-var/blob/{{#var:DEBIAN_BRANCH}}/variscite/{{#var:MACHINE_NAME}}/{{#var:MACHINE_NAME}}.sh}}
{{#ifeq: {{#var:SOC_SERIES}} | imx8 |
= Upgrading Debian Packages =
To update the packages either at runtime or build time, refer to {{Varlink|IMX8_Debian_Package_Update|{{#var:RELEASE_LINK}}|Upgrading Debian Packages}}
|}}


= Build a sample C "Hello, world!" program =
= Build a sample C "Hello, world!" program =
Line 264: Line 342:
Now you should have an app called myhello, that can be run on your target board.<br>
Now you should have an app called myhello, that can be run on your target board.<br>
You can add it to your rootfs image or copy it directly to the rootfs on the board (using scp, for example).
You can add it to your rootfs image or copy it directly to the rootfs on the board (using scp, for example).
{{#ifeq: {{#var:LIBC_WORKAROUND}} | true |
= Installing packages which depend on libc =
NXP Provides the Vivante GPU driver in binary form and it requires a specific minimum version of libc.<br>
Due to this requirement from the GPU user space libraries, this Debian release uses an updated version of libc from the newer Debian Bullseye repository.<br>
Therefore, if you need to install packages which depend on libc (like build-essentials, gcc, libc6-dev, etc.) please use their "testing" version (from Debian Bullseye).<br>
For example:
apt-get update
apt-get install build-essential/testing gcc/testing g++/testing libc6-dev/testing
|
}}


{{#ifeq: {{#var:SUPPORT_X11}} | NO |
{{#ifeq: {{#var:SUPPORT_X11}} | NO |
Line 270: Line 360:
refer to {{Varlink|IMX8_Debian_XWayland|{{#var:RELEASE_LINK}}|XWayland Example}}
refer to {{Varlink|IMX8_Debian_XWayland|{{#var:RELEASE_LINK}}|XWayland Example}}
|
|
}}
{{#ifeq: {{#var:TI_RELEASE}} | 09.02.01.10 |
<!-- Set release according to "release" parameter in URL and use am62-debian-bookworm-6.1.83_09.02.01.10-v1.0 as default
--> {{INIT_RELEASE_PARAM|am62-debian-bookworm-6.1.83_09.02.01.10-v1.0}}<!--
--> {{#lst:Debian_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!--
--> {{SoftwareEx
|title={{#var:HARDWARE_NAME}} Debian {{#var:DEBIAN_NAME}} {{#var:DEBIAN_VERSION}}
|image=Debian.png
|description=Debian project is a  Linux distributions for embedded devices. Debian big varities of pre-built packages
and easy to customization provides rapid prototyping with minimal efforts.
This release is based on TI's [{{#var:TI_RELEASE_NOTES}} {{#var:TI_RELEASE}}] Release. Variscite extends TI's release to support its VAR-SOM-AM62 System On Module.
Release version: '''{{#var:RELEASE_NAME}}'''
|category1=VAR-SOM-AM62
|category2=Yocto
|documentation=
{{OS_Overview_General_Column}}<!--
-->{{OS_Overview_Build_Column_AM62}}<!--
-->{{OS_Overview_HowTo_Column_AM62}}}}
{{NONUMBEREDHEADINGS}}
}}
}}

Latest revision as of 18:11, 20 November 2024

Warning: This page is designed to be used with a 'release' URL parameter.

This page is using the default release RELEASE_STRETCH_V3.0_DART-6UL.
To view this page for a specific Variscite SoM and software release, please follow these steps:

  1. Visit variwiki.com
  2. Select your SoM
  3. Select the software release
DART-6UL - Debian Stretch 9.3 with imx_4.14.78_1.0.0_ga_var01 Linux release
DART-6UL in this wiki refers to both the Variscite DART-6UL and VAR-SOM-6UL SOMs.

Overview

This page describes how to build and install Debian distribution (Stretch) on Variscite boards with DART-6UL.

Please note that the build script is based on debootstrap. As described in the following instructions, it's kindly suggested to create the build folder on the main Ubuntu volume on your host PC rather than an external media.
Using an external media, although automatically mounted, will cause debootstrap to complain about access rights (even when running the script with sudo).

Create build environment

These instructions were tested on Ubuntu 16.04/18.04 x64 host PCs. When using other distributions, there may be issues.

Note: Variscite provides Docker containers that can be used for a development environment as an alternative to using a virtual machine or a dedicated computer.

To learn more, please see Variscite's Docker Build Environment guide.

Windows with WSL/WSL2 is not supported for development

Installing required packages

On Ubuntu building machine: 

$ sudo apt-get install binfmt-support qemu qemu-user-static debootstrap kpartx \
lvm2 dosfstools gpart binutils bison git lib32ncurses5-dev libssl-dev gawk wget \
git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev \
autoconf libtool libglib2.0-dev libarchive-dev xterm sed cvs subversion \
kmod coreutils texi2html bc docbook-utils help2man make gcc g++ \
desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial automake groff curl \
lzop asciidoc u-boot-tools mtd-utils device-tree-compiler flex cmake zstd udisks2  libgnutls28-dev \
python-pysqlite2 python-git python-m2crypto python-pyelftools


Deploy source

Download archive containing the build script and support files for building Debian Stretch for this board: 

$ cd ~
$ git clone https://github.com/varigit/debian-var.git -b debian_stretch_mx6ul_var03 var_mx6ul_dart_debian

Create environment (Internet connection should be available): 

$ cd ~/var_mx6ul_dart_debian
$ ./make_var_mx6ul_dart_debian.sh -c deploy

This environment prepared to build.

Make Debian

Build all

Internet connection should be available 

$ cd ~/var_mx6ul_dart_debian
$ sudo ./make_var_mx6ul_dart_debian.sh -c all |& tee build.log


Build by parts

Build bootloader

$ cd ~/var_mx6ul_dart_debian
$ sudo ./make_var_mx6ul_dart_debian.sh -c bootloader


Build kernel, dtb files, kernel modules, and kernel headers

$ cd ~/var_mx6ul_dart_debian
$ sudo ./make_var_mx6ul_dart_debian.sh -c kernel
$ sudo ./make_var_mx6ul_dart_debian.sh -c modules
$ sudo ./make_var_mx6ul_dart_debian.sh -c kernelheaders

Build rootfs

Internet connection should be available 

$ cd ~/var_mx6ul_dart_debian
$ sudo ./make_var_mx6ul_dart_debian.sh -c rootfs


Pack rootfs

To create the root file system archive (rootfs.tar.gz) and UBI image (rootfs.ubi.img), run the following commands: 

$ cd ~/var_mx6ul_dart_debian
$ sudo ./make_var_mx6ul_dart_debian.sh -c rtar
$ sudo ./make_var_mx6ul_dart_debian.sh -c rubi



Create boot SD card

  1. Follow the above steps for make rootfs, kernel, bootloader;
  2. Insert the SD card to card reader connected to a host system;
  3. Run the following commands (Caution! All data on the card will be destroyed):
$ cd ~/var_mx6ul_dart_debian
$ sudo ./make_var_mx6ul_dart_debian.sh -c sdcard -d /dev/sdX


where '/dev/sdX' path to the block SD device in your system.

Create a boot SD card image using a loop device

It is also possible to use the "./make_var_mx6ul_dart_debian.sh" script to create a boot SD card image, while using a loop device instead of attaching a real SD card.

Create an empty file using the following command: 

$ dd if=/dev/zero of=imx6ul-var-dart-debian-sd.img bs=1M count=3720

The above command creates a 3700MiB file representing the SD card.

Attach the first available loop device to this file: 

$ sudo losetup -Pf imx6ul-var-dart-debian-sd.img

To find the actual loop device being used, run: 

$ losetup -a | grep imx6ul-var-dart-debian-sd.img

Write the content to the loop device to generate the SD card image: 

$ sudo ./make_var_mx6ul_dart_debian.sh -c sdcard -d /dev/loopX

(Replace /dev/loopX with your actual loop device, e.g. /dev/loop0)

Detach the loop device from the file: 

$ sudo losetup -d /dev/loopX

To compress the SD card image file use the following command: 

$ gzip -9 imx6ul-var-dart-debian-sd.img

To write the SD card image to a real SD card device use the following command: 

$ zcat imx6ul-var-dart-debian-sd.img.gz | sudo dd of=/dev/sdX bs=1M && sync

(Replace /dev/sdX with your actual SD device, e.g. /dev/sdb)

Boot the board with a bootable SD card

Note: The WiFi is not operational when booting from SD card, as the WiFi and SD card are using the same SDIO interface.
A typical use-case is to boot from an SD card, flash the eMMC/NAND flash, and re-boot from the eMMC/NAND flash to have the WiFi operational.

Setting the Boot Mode

Booting your system from an SD card requires switching the Boot DIP switches. See picture below.
On the VAR-6ULCustomBoard (with a DART-6UL):

Boot switch 6ul1.jpg
  • "00" The current position in the picture will set the system to boot from SD card
  • "01" Moving the right switch will set the system to boot from eMMC
  • "10" Moving the left switch will set the system to boot from NAND flash
  • "11" is illegal.
Be aware that your system has eMMC or NAND but never both.



On the Concerto-Board (with a VAR-SOM-6UL):

Boot switch concerto.jpg
  • ON-EXT: Boot from the external storage (SD card) - the current position in the picture
  • OFF-INT: Boot from the SOM's internal storage (eMMC/NAND flash)


Automatic device tree selection in U-Boot

Enable/Disable Automatic Device Tree selection

To enable the automatic device tree selection in U-Boot (already enabled by default): 

$ setenv fdt_file undefined
$ saveenv

To disable the automatic device tree selection in U-Boot, set the device tree file manually: 

$ setenv fdt_file YOUR_DTB_FILE
$ saveenv
Comment:
Make sure you don't set an inappropriate dtb file, like a dtb with nand on a SOM that has eMMC, or a dtb for mx6ull on a SOM with an mx6ul SOC.

Build Results

The resulted images are located in ~/var_mx6ul_dart_debian/output/.

Image name
 How to use
rootfs.tar.gz Root filesystem tarball used for installation on SD card and eMMC
rootfs.ubi.img Use for flash to NAND
zImage Linux kernel image
SPL.nand SPL built for NAND. The SPL is pre-U-Boot SW component, required for DDR initialization
SPL.mmc SPL built for SD card and eMMC boot. The SPL is pre-U-Boot SW component, required for DDR initialization
u-boot.img.nand U-Boot built for NAND flash
u-boot.img.mmc U-Boot built for SD card or eMMC
Device Tree name
 Details
imx6ull-var-dart-6ulcustomboard-emmc-sd-card.dtb Device tree blob for DART-6UL with i.MX6ULL SOC, eMMC & SD card enabled. (NAND flash & WiFi disabled)
imx6ull-var-dart-6ulcustomboard-emmc-wifi.dtb Device tree blob for DART-6UL with i.MX6ULL SOC, eMMC & WiFi enabled. (NAND flash & SD card disabled)
imx6ull-var-dart-6ulcustomboard-nand-sd-card.dtb Device tree blob for DART-6UL with i.MX6ULL SOC, NAND flash & SD card enabled. (eMMC & WiFi disabled)
imx6ull-var-dart-6ulcustomboard-nand-wifi.dtb Device tree blob for DART-6UL with i.MX6ULL SOC, NAND flash & WiFi enabled. (eMMC & SD card disabled)
imx6ul-var-dart-6ulcustomboard-emmc-sd-card.dtb Device tree blob for DART-6UL with i.MX6UL SOC, eMMC & SD card enabled. (NAND flash & WiFi disabled)
imx6ul-var-dart-6ulcustomboard-emmc-wifi.dtb Device tree blob for DART-6UL with i.MX6UL SOC, eMMC & WiFi enabled. (NAND flash & SD card disabled)
imx6ul-var-dart-6ulcustomboard-nand-sd-card.dtb Device tree blob for DART-6UL with i.MX6UL SOC, NAND flash & SD card enabled. (eMMC & WiFi disabled)
imx6ul-var-dart-6ulcustomboard-nand-wifi.dtb Device tree blob for DART-6UL with i.MX6UL SOC, NAND flash & WiFi enabled. (eMMC & SD card disabled)
imx6ulz-var-dart-6ulcustomboard-emmc-sd-card.dtb Device tree blob for DART-6UL with i.MX6ULZ SOC, eMMC & SD card enabled. (NAND flash & WiFi disabled)
imx6ulz-var-dart-6ulcustomboard-emmc-wifi.dtb Device tree blob for DART-6UL with i.MX6ULZ SOC, eMMC & WiFi enabled. (NAND flash & SD card disabled)
imx6ulz-var-dart-6ulcustomboard-nand-sd-card.dtb Device tree blob for DART-6UL with i.MX6ULZ SOC, NAND flash & SD card enabled. (eMMC & WiFi disabled)
imx6ulz-var-dart-6ulcustomboard-nand-wifi.dtb Device tree blob for DART-6UL with i.MX6ULZ SOC, NAND flash & WiFi enabled. (eMMC & SD card disabled)
imx6ull-var-som-concerto-board-emmc-sd-card.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULL SOC, eMMC & SD card enabled. (NAND flash & WiFi disabled)
imx6ull-var-som-concerto-board-emmc-wifi.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULL SOC, eMMC & WiFi enabled. (NAND flash & SD card disabled)
imx6ull-var-som-concerto-board-nand-sd-card.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULL SOC, NAND flash & SD card enabled. (eMMC & WiFi disabled)
imx6ull-var-som-concerto-board-nand-wifi.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULL SOC, NAND flash & WiFi enabled. (eMMC & SD card disabled)
imx6ul-var-som-concerto-board-emmc-sd-card.dtb Device tree blob for VAR-SOM-6UL with i.MX6UL SOC, eMMC & SD card enabled. (NAND flash & WiFi disabled)
imx6ul-var-som-concerto-board-emmc-wifi.dtb Device tree blob for VAR-SOM-6UL with i.MX6UL SOC, eMMC & WiFi enabled. (NAND flash & SD card disabled)
imx6ul-var-som-concerto-board-nand-sd-card.dtb Device tree blob for VAR-SOM-6UL with i.MX6UL SOC, NAND flash & SD card enabled. (eMMC & WiFi disabled)
imx6ul-var-som-concerto-board-nand-wifi.dtb Device tree blob for VAR-SOM-6UL with i.MX6UL SOC, NAND flash & WiFi enabled. (eMMC & SD card disabled)
imx6ulz-var-som-concerto-board-emmc-sd-card.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULZ SOC, eMMC & SD card enabled. (NAND flash & WiFi disabled)
imx6ulz-var-som-concerto-board-emmc-wifi.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULZ SOC, eMMC & WiFi enabled. (NAND flash & SD card disabled)
imx6ulz-var-som-concerto-board-nand-sd-card.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULZ SOC, NAND flash & SD card enabled. (eMMC & WiFi disabled)
imx6ulz-var-som-concerto-board-nand-wifi.dtb Device tree blob for VAR-SOM-6UL with i.MX6ULZ SOC, NAND flash & WiFi enabled. (eMMC & SD card disabled)


Linux console access

User name User password User descriptor
root root system administrator
user user local user
x_user used for X session access


Flash images to NAND / eMMC

In case you are using a SOM with NAND flash, run the following command as root to install Debian on it: 

# debian-nand.sh

In case you are using a SOM with eMMC, run the following command as root to install Debian on it: 

# debian-emmc.sh

The above scripts are located in /usr/sbin in the rootfs of the SD card used to boot Debian.

How-to: Test and use an interface

Please see this section in the Yocto developer guide page. It is the same for Debian.

How-to: Modify the kernel configuration

To modify the kernel configuration (add/remove features and drivers) please follow the steps below: 

1. $ cd ~/var_mx6ul_dart_debian/src/kernel
2. $ sudo make ARCH=arm mrproper
3. $ sudo make ARCH=arm imx_v7_var_defconfig
4. $ sudo make ARCH=arm menuconfig
5. Navigate the menu and select the desired kernel functionality
6. Exit the menu and answer "Yes" when asked "Do you wish to save your new configuration?"
7. $ sudo make ARCH=arm savedefconfig
8. $ sudo cp arch/arm/configs/imx_v7_var_defconfig arch/arm/configs/imx_v7_var_defconfig.orig
9. $ sudo cp defconfig arch/arm/configs/imx_v7_var_defconfig
10. Follow the instructions above to rebuild kernel and modules, repack rootfs images and recreate SD card



Build a sample C "Hello, world!" program

Create a file called myhello.c with the following content: 

#include <stdio.h>

int main() {
	printf("Hello, World!\n");
	return 0;
}

Export the C (cross-)compiler path: 

$ export CC=~/var_mx6ul_dart_debian/toolchain/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-gcc

Compile: 

$ $CC myhello.c -o myhello

Now you should have an app called myhello, that can be run on your target board.
You can add it to your rootfs image or copy it directly to the rootfs on the board (using scp, for example).




Retrieved from "https://variwiki.com/index.php?title=Debian_Build_Release&oldid=27611"
Latest Modules
Support
Variscite Support Center
Contact Support
Product Longevity
Product Compliance Policy
Blog
Variscite Training
Variscite Website
This page was last edited on 20 November 2024, at 18:11.

© 2024 Variscite. All rights reserved