VAR-SOM-MX6 Yocto Krogoth: Difference between revisions

From Variscite Wiki
No edit summary
No edit summary
Line 1: Line 1:
{{PageHeader|VAR-SOM-MX6 - Yocto fsl-yocto-L4.1.15_2.0.0-ga Krogoth Build Yocto release}} {{DocImage|category1=VAR-SOM-MX6|category2=Yocto}} __toc__
{{Software
= Installing required packages<br/> =
|image=Yocto.png
|description=Yocto project is a framework for creating a Linux distributions for embedded devices. Its layering mechanism makes it easy to add Linux to new target devices highly customized for a particular platform; it can include custom start-up scripts, software packages built with a high degree of optimization for a particular architecture, and different user interfaces from full Gnome desktop to a simple a serial console.
Freescale i.MX joined the Yocto Project community providing a release based on the Yocto Project framework. Variscite extend this framework to support our i.MX6 System On a Modules.
|category1=VAR-SOM-MX6
|category2=
|documentation=<nowiki></nowiki>
{{SoftBox
|title=General
|boxwidth=23
|content=<nowiki></nowiki>
=== General  ===
* [[VAR-SOM-MX6 Start Here|First Time? Start Here <span style="color:red"><---]]
* [http://variscite.com/support-forum/index.php Support forum]
* [[VAR-SOM-MX6_Yocto_NAND_Recovery_V60plus|'''Using the recovery SD card''']]


Follow the link below and install all required packages on your machine.
=== Programming ===
 
* [[VAR-SOM-MX6 Hello World|Hello World 'C' application]]
[http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html]
* [[VAR-SOM-MX6 QT Hello World|Building A QT Hello World]]
 
* [[VAR-SOM-MX6 Yocto Jethro Eclipse|Debugging with Eclipse]]
Please make sure you host PC is running Ubuntu 14.04 and install the following packages:
* [[VAR-SOM-MX6 Yocto Utilizing|TFTP & NFS]]
<pre>
sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev
sudo apt-get install autoconf libtool libglib2.0-dev libarchive-dev
sudo apt-get install python-git xterm sed cvs subversion coreutils texi2html
sudo apt-get install docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev
sudo apt-get install libglu1-mesa-dev mercurial automake groff curl lzop asciidoc u-boot-tools dos2unix mtd-utils
sudo apt-get install pv
</pre>
 
= Documentation =
Documentation are available for Download from [ftp://ftp.variscite.com/VAR-SOM-MX6/Software/Linux/Yocto/fsl-yocto-L4.1.15_2.0.0-ga-docs/fsl_yocto-L4.1.15_2.0.0-ga.tar.gz FreescaleKrogothDocuments]
 
= Download Yocto Krogoth for i.MX6 Freescale source =
<pre>
$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"
 
$ mkdir ~/bin (this step may not be needed if the bin folder already exists)
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH
 
$ mkdir ~/var-som-mx6-yocto-krogoth
$ cd ~/var-som-mx6-yocto-krogoth
$ repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1-krogoth
$ repo sync
</pre>
 
= Download Yocto Krogoth i.MX6 with Meta Variscite VAR-SOM-MX6 support =
<pre>
$ cd ~/var-som-mx6-yocto-krogoth/sources
$ git clone https://github.com/varigit/meta-variscite-mx6.git -b Krogoth-imx-4.1.15-var01 meta-variscite-imx
$ cp meta-variscite-imx/scripts/var-setup-release.sh ../
</pre>
 
= Setup and build Yocto =
The following distros can be used:
* fsl-imx-x11 - Only X11 graphics
* fsl-imx-wayland - Wayland weston graphics
* fsl-imx-xwayland - Wayland graphics and X11. X11 applications using EGL are not supported
* fsl-imx-fb - Frame Buffer graphics - no X11 or Wayland
<br>
<br>
Note: refer to ftp://customerv:Variscite1@ftp.variscite.com/VAR-SOM-MX6/Software/Linux/Yocto/fsl-yocto-L4.1.15_2.0.0-ga-docs/Freescale_Yocto_Project_User's_Guide.pdf <br>
Page 7 for further information. <br>
'''Sample build scenarios:'''
* [[#Build X11 GUI image|Build X11 GUI image (with or without Qt content)]]
* [[#Build Qt5 image without X11|Build Qt5 image without X11]]
== Build X11 GUI image ==
<pre>
$ cd ~/var-som-mx6-yocto-krogoth
$ MACHINE=var-som-mx6 DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11
</pre>
Optional: Direct downloads to /opt/yocto_downloads, make sure directory exists and all permissions are set
<pre>
$ sudo mkdir /opt/yocto_downloads
$ sudo chmod 777 /opt/yocto_downloads/
$ sed -i 's/DL_DIR ?= "${BSPDIR}\/downloads/DL_DIR = "\/opt\/yocto_downloads/g' conf/local.conf
</pre>
launch bitbake:
<pre>
Without Qt content:
$ bitbake fsl-image-gui
Or with Qt content:
$ bitbake fsl-image-qt5
</pre>
== Build Qt5 image without X11 ==
<pre>
$ cd ~/var-som-mx6-yocto-krogoth
$ MACHINE=var-som-mx6 DISTRO=fsl-imx-fb source var-setup-release.sh -b build-fb
</pre>
Optional: Direct downloads to /opt/yocto_downloads, make sure directory exists and all permissions are set
<pre>
sed -i 's/DL_DIR ?= "${BSPDIR}\/downloads/DL_DIR = "\/opt\/yocto_downloads/g' conf/local.conf
</pre>
launch bitbake:
<pre>
$ bitbake fsl-image-qt5
</pre>
== local.conf customization ==
Edit you local.conf file:
<pre>$ gedit conf/local.conf
</pre>
Modify download directory:
Change packages download directory. By default it is set to:
DL_DIR ?= "${BSPDIR}/downloads/"
change it to a global folder like
DL_DIR = "/opt/yocto_downloads/".
Don't forget to create the folder and make it available without a sudo permissions.
== Build Results ==
The resulted images are located in tmp/deploy/images/var-som-mx6.<br/>
{| class="wikitable"
|-
! scope="col" | Image Name<br/>
! scope="col" | How to use<br/>
|-
| style="padding: 5px;"| fsl-image-gui-var-som-mx6.sdcard
| style="padding: 5px;"| This image is for SD card boot.<br> It can be flashed as-is on an SD card that can then be used to boot your system,<br> according to the relevant startup-guide of your product<br> (usually requires to press the boot select button, or toggle a DIP switch).<br> For detailed information refer to the [[#Create_a_bootable_SD_card | Create a bootable SD card]] section below.
|-
| style="padding: 5px;"| fsl-image-gui-var-som-mx6.tar.bz2
| style="padding: 5px;"| Tarball with rootfs files.<br>Can be used to create an NFS root file system on the host.<br> See the [[ http://variwiki.com/index.php?title=VAR-SOM-MX6_Yocto_Utilizing | Setup TFTP/NFS Yocto system ]] section for more info.<br>Also used to create our extended SD card.<br>See the [[#Create_a_bootable_SD_card | Create a bootable SD card]] section below.
|-
| style="padding: 5px;"| fsl-image-gui-var-som-mx6.ubi
| style="padding: 5px;"| A complete UBI image containing a UBIFS volume, for writing to NAND Flash.
|-
| style="padding: 5px;"| uImage
| style="padding: 5px;"| Linux kernel image, same binary for SD card or NAND Flash.
|-
| style="padding: 5px;"| SPL-nand
| style="padding: 5px;"| SPL built for NAND-Flash.<br>The SPL is a pre-U-Boot SW component, required for DDR initialization.
|-
| style="padding: 5px;"| u-boot-nand-2015.04-r0.img
| style="padding: 5px;"| U-Boot built for NAND Flash.
|-
| style="padding: 5px;"| SPL-sd
| style="padding: 5px;"| SPL built for SD card boot, or eMMC boot in case of DART-MX6.
|-
| style="padding: 5px;"| u-boot-sd-2015.04-r0.img
| style="padding: 5px;"| U-Boot built for SD card boot, or eMMC boot in case of DART-MX6.
|-
! scope="col" | Device Tree Name<br/>
! scope="col" | SOM type<br/>
! scope="col" | Carrier Board type<br/>
! scope="col" | LCD Type<br/>
! scope="col" | Evaluation Kit name<br/>
|-
| style="padding: 5px;"| uImage-imx6q-var-som-cap.dtb
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad / Dual)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| VAR-DVK-MX6_V2-PRO<br>VAR-STK-MX6_V2
|-
| style="padding: 5px;"| uImage-imx6q-var-som-res.dtb
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad / Dual)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Resistive touch
| style="padding: 5px;"| VAR-DVK-MX6_V2-PRO<br>VAR-STK-MX6_V2
|-
| style="padding: 5px;"| uImage-imx6q-var-som-vsc.dtb
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad / Dual)
| style="padding: 5px;"| VAR-SOLOCustomBoard
| style="padding: 5px;"| Capacitive LVDS touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| uImage-imx6dl-var-som-cap.dtb
| style="padding: 5px;"| VAR-SOM-MX6_V2 (DualLite/ Solo)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| uImage-imx6dl-var-som-res.dtb
| style="padding: 5px;"| VAR-SOM-MX6_V2 (DualLite/ Solo)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Resistive touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| uImage-imx6dl-var-som-vsc.dtb
| style="padding: 5px;"| VAR-SOM-MX6_V2 (DualLite/ Solo)
| style="padding: 5px;"| VAR-SOLOCustomBoard
| style="padding: 5px;"| Capacitive LVDS touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| uImage-imx6dl-var-som-solo-vsc.dtb
| style="padding: 5px;"| VAR-SOM-SOLO / VAR-SOM-DUAL
| style="padding: 5px;"| VAR-SOLOCustomBoard
| style="padding: 5px;"| Capacitive LVDS touch
| style="padding: 5px;"| VAR-DVK-SOLO/DUAL<br>VAR-STK-SOLO/DUAL
|-
| style="padding: 5px;"| uImage-imx6dl-var-som-solo-cap.dtb
| style="padding: 5px;"| VAR-SOM-SOLO / VAR-SOM-DUAL
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| uImage-imx6dl-var-som-solo-res.dtb
| style="padding: 5px;"| VAR-SOM-SOLO / VAR-SOM-DUAL
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Resistive touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| uImage-imx6q-var-dart.dtb
| style="padding: 5px;"| VAR-SOM-SOLO / VAR-SOM-DUAL
| style="padding: 5px;"| VAR-DT6CustomBoard
| style="padding: 5px;"| Capacitive LVDS touch
| style="padding: 5px;"| VAR-DVK-DT6<br>VAR-STK-DT6
|-
|}
= Create a bootable SD card =
== SD card structure ==
This is the structure of our Recovery/Extended SD card:<br>
[[File:SD_card_part_v50.png]]<br><br>
The SD card is divided into 3 sections as shown in the picture above:<br>
* The first unallocated 4MiB are saved space for SPL and u-boot.img. They can be replaced with a dd command described in the [[VAR-SOM-MX6_Yocto_Krogoth_Build_u-boot_out_of_tree | Build U-Boot out of Yocto tree]] section.<br>
* The first partition is a fat16 partition used for the device tree files and Linux uImage file. You can copy them as described in the [[VAR-SOM-MX6_Yocto_Krogoth_Build_Linux_out_of_tree | Linux out of tree]] section.<br>
* The second partition is an ext4 partition that contains the complete file system and modules.<br><br>
Note:<br>
The last unallocated area is not used. It is there so that the rootfs will fit on any 4GB SD card, as not all 4GB SD cards are really the same size. If you want, you can use a program such as GParted to resize the roofs partition and make it end at the end of your specific SD card (of course, you can also use SD cards with much bigger capacity than 4GB, and then it makes more sense to resize the partition).<br>
Also, if you create the extended SD card yourself by following the [[#Create_an_extended_SD_card | Create an extended SD card]] section below, and you use the '-a' option, the rootfs partition will end at the end of your specific SD card automatically.<br>
==Yocto pre-built bootable SD card==
The Yocto build products contains many files as explained in the [[#Build_Results | Build Results section]]. For example, fsl-image-gui-var-som-mx6.sdcard, depending on your build. This is a complete image to be flashed directly to an SD card.<br>
Example usage:
<pre>
$ sudo umount /dev/sdX*
# For GUI-X11 & QT5-X11
$ cd ~/var-som-mx6-yocto-krogoth/build_x11
Or
# For QT5-FB
$ cd ~/var-som-mx6-yocto-krogoth/build-fb
# For fsl-image-gui image (GUI-X11)
$ sudo dd if=tmp/deploy/images/var-som-mx6/fsl-image-gui-var-som-mx6.sdcard of=/dev/sdX bs=1M && sync
Or
# For fsl-image-qt5 image (QT5-X11 & QT5-FB)
$ sudo dd if=tmp/deploy/images/var-som-mx6/fsl-image-qt5-var-som-mx6.sdcard of=/dev/sdX bs=1M && sync
Replace sdX with the right device name. This can be obtained by "dmesg" command on your host Linux PC, after the SD card reader is inserted.
</pre>
* <span style="color:red">Note:</span> Booting your system from an SD card requires pressing the boot-select button, or switching the relevant DIP switch to "Boot from SD card", according to the relevant start-up guide of your system"<br><br>
Drawbacks of the native .sdcard yocto-built image:
* The second partition size doesn't use the entire SD card.
* The second partition is not labeled as rootfs.
* The NAND and eMMC flashing scripts are not included.
== Create an extended SD card ==
Variscite provides the var-create-yocto-sdcard.sh script which creates our NAND/eMMC recovery SD card - an SD card based on the fsl-image-gui filesystem, which copies the NAND flash burning scripts and relevant binaries for your convenience.<br>
Later, you will be able to follow either the more automatic [[VAR-SOM-MX6 Yocto NAND Recovery V60plus|VAR-SOM-MX6 Yocto Recovery SD card]] guide or the more manual [[VAR-SOM-MX6 NAND Flash Burning| VAR-SOM-MX6 NAND flash burning]] guide to burn your images to NAND flash or eMMC.<br><br>
Note:<br>
This is essentially the same as our pre-built Recovery SD image, with the following main differences:<br>
* The Android recovery (Android-eMMC) is only present on the pre-built SD image, and not on the SD card built from the Yocto script.<br>
* The pre-built image's rootfs partition size is 3700MiB, which is also the default size when using the script, but the script also has an option to set the rootfs partition size to fill the whole free space of the used SD card. Anyway, you can always resize the partition later with an external tool such as gparted.<br>
Naturally, the pre-built image is more straight forward and easier to use, while the script method is easier to customize.<br><br>
Usage:<br>
* Follow the [[#Setup and build Yocto|Setup and build Yocto]] guide, and bitbake fsl-image-gui.
* Plug-in the SD card to your Linux HOST PC, run dmesg and see which device is added (i.e. /dev/sdX or /dev/mmcblkX)
<pre>
$ sudo MACHINE=var-som-mx6 ~/var-som-mx6-yocto-krogoth/sources/meta-variscite-imx/scripts/var_mk_yocto_sdcard/var-create-yocto-sdcard.sh <options> /dev/sdX
(Replace /dev/sdX with your actual device)
</pre>
<pre>
options:
  -h            Display help message
  -s            Only show partition sizes to be written, without actually write them
  -a            Automatically set the rootfs partition size to fill the SD card
  -r            Select alternative rootfs for recovery images (default: build_x11/tmp/deploy/images/var-som-mx6/fsl-image-gui-var-som-mx6.*)
If you don't use the '-a' option, a default rootfs size of 3700MiB will be used
The '-r' option allows you to create a bootable sdcard with an alternative image for the firmware to NAND or EMMC.
Example: "-r tmp/deploy/images/var-som-mx6/fsl-image-qt5-var-som-mx6" -- selected the "Qt5 image with X11" recovery image
</pre>
= Flash images to NAND =
Please refer to [[VAR-SOM-MX6 NAND Flash Burning Krogoth| VAR-SOM-MX6 NAND Flash burning]]
= Boot the board with a bootable SD card =
== Booting your specific Developer Kit ==
Select the one you are using.
=== MX6CustomBoard ===
Booting your MX6CustomBoard system from SD card requires while powering up the system. See picture below.
[[File:Mx6_boot.jpg|thumb|none|upright=2.0]]
To boot a board using an SD card, follow the steps below:<br>
* Power-off the board.
* Insert the SD card into the SD/MMC slot of the carrier board (DVK)
* Push the middle button (Boot Select) and hold
* Power-up the board
* Release the middle button (Boot Select) after system starts to boot.
* The board will automatically boot into Linux from the SD card
=== SoloCustomBoard ===
Booting your system requires switching the relevant DIP switch to "Boot from MMC". See picture below.
[[File:Solo_boot.jpg|thumb|none|upright=2.0]]
To boot board with SD card, Follow the steps below:<br>
*Power-off the board.
*Insert the SD card into the SD/MMC slot of the carrier board (DVK)
*Switch the relevant DIP switch to "Boot from MMC"
*Power-up board
*The board will automatically boot into Linux from SD card
=== DT6CustomBoard ===
Booting your system requires switching the relevant DIP switch to "Boot from SD card". See picture below.
[[File:Dart_boot.jpg|thumb|none|upright=2.0]]
To boot board with SD card, Follow the steps below:<br>
*Power-off the board.
*Insert the SD card into the SD/MMC slot of the carrier board (DVK)
*Switch the relevant DIP switch to "Boot from SD card"
*Power-up board
*The board will automatically boot into Linux from SD card
== Automatic Device Tree selection in U-Boot ==
As shown in the [[#Build_Results| Build Results]] table above, we have different kernel device trees, corresponding to our different H/W configurations (sometimes they are renamed without the "uImage-" prefix).<br>
We implemented a script in U-Boot's environment, which sets the fdt_file environment variable based on the detected hardware.
=== Enable/Disable Automatic Device Tree selection ===
To enable the automatic device tree selection in U-Boot (already enabled by default):
<pre>
$ setenv fdt_file=undefined
$ saveenv
</pre>
To disable the automatic device tree selection in U-Boot, set the device tree file manually:
<pre>
$ setenv fdt_file=YOUR_DTB_FILE
$ saveenv
</pre>
== What happen when you flash to eMMC/NAND ==
When you flash to NAND we use the same algorithm as the table above but we pick and choose specific device tree and flash it.
= QT5/Embedded environment variables =
The QT5/Embedded require environment variables to run correctly.
You need to have them avilable on the target. For example /etc/profile.d/tslib.sh can be edited.
export TSLIB_TSDEVICE=/dev/input/touchscreen0<br>
export TSLIB_CALIBFILE=/etc/pointercal<br>
export TSLIB_CONFFILE=/etc/ts.conf<br>
export QT_QPA_GENERIC_PLUGINS=tslib:/dev/input/event0<br>
export QT_QPA_EGLFS_PHYSICAL_HEIGHT=480<br>
export QT_QPA_EGLFS_PHYSICAL_WIDTH=800<br>
export QT_QPA_EGLFS_HEIGHT=480<br>
export QT_QPA_EGLFS_WIDTH=800<br>
export QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1<br>
export QT_QPA_EGLFS_DEPTH=24<br>
export QT_QPA_PLATFORM=eglfs<br>
= UBIFS =
By default we create ubifs image for 512MB NAND-flash size.
You can change the size by editing ~/var-som-mx6-yocto-krogoth/sources/meta-variscite-imx/conf/machine/var-som-mx6.conf <br>and comment / uncomment the relevant section based on size.
= DDR size and Contiguous Memory Allocator =
By default Freescale allocates 256MB of RAM to the Contiguous Memory allocator.
This is for proper operation of the IPU VPU, X11 etc.
On VAR-SOM-SOLO with 256MB DDR RAM size, it will cause a kernel freeze during boot.
Adding cma=32MB to the bootargs parameters is required to fix.
= Update Yocto Krogoth Meta-Variscite =
From time to time we will post updates to meta-variscite that will include new features and bug fixes.<br>
Follow the instructions below to update your tree:
<pre>
$ cd ~/var-som-mx6-yocto-krogoth/sources/meta-variscite-imx/
$ git fetch origin
$ git pull
$ git checkout Krogoth-imx-4.1.15-1.2.0_ga-var01-6QP
Setup your enviroment:
$ cd ~/var-som-mx6-yocto-krogoth
for X11 image
$ MACHINE=var-som-mx6 DISTRO=fsl-imx-x11 source var-setup-release.sh -b build_x11
for FB image
$ MACHINE=var-som-mx6 DISTRO=fsl-imx-fb source var-setup-release.sh -b build-fb
In order to update the kernel, u-boot and rootfs:
$ bitbake -c cleanall u-boot-variscite linux-variscite kernel-module-imx-gpu-viv ti-compat-wireless-wl18xx wl18xx-firmware cryptodev-module
for GUI image
$ bitbake -c clean fsl-image-gui
for Qt5 image
$ bitbake -c clean fsl-image-qt5
and build your image:
for GUI image
$ bitbake fsl-image-gui -f
for Qt5 image
$ bitbake fsl-image-qt5 -f
</pre>
= Useful Bitbake commands =
[http://elinux.org/Bitbake_Cheat_Sheet Bitbake Cheat Sheet]


[https://community.freescale.com/docs/DOC-94953 Useful bitbake commands]
|color=darkblue}}<nowiki>
</nowiki>{{SoftBox
|title=Build
|boxwidth=23
|content=<nowiki></nowiki>
===Build Yocto, Linux and U-Boot===
* [https://docs.google.com/spreadsheets/d/1hlW4K1X78D_n4UoiqjJ5lozhcvWFBp-F1e0vdPjmRkc/pubhtml Release Notes]
* [[VAR-SOM-MX6 Yocto Fido R2 Suported hardware and features|Supported hardware and features]]
* [[VAR-SOM-MX6 Development Environment|Set Development Environment]]
* [[VAR-SOM-MX6 Yocto Krogoth Build Yocto release|'''Build Yocto from source code''']]
* [[VAR-SOM-MX6_Yocto Common Errors|Yocto common build errors</span>]]
* [[VAR-SOM-MX6 Yocto Jethro R4 Build Linux out of tree|Build the Linux kernel from source code]]
* [[VAR-SOM-MX6 Yocto Jethro R4 Build u-boot out of tree|Build U-Boot from source code]]
* [[VAR-SOM-MX6 Yocto Jethro Customizing kernel and uboot|Customizing the Linux kernel and U-Boot]]
* [[VAR-SOM-MX6 NAND Flash Burning Jethro|Burning Yocto binaries to NAND flash/eMMC via SD card]]
* [[VAR-SOM-MX6 Yocto Flash From Net|Burning Yocto binaries to NAND flash/eMMC via Ethernet]]
* [[U-Boot 4.1.15 features#Flashing NAND using U-Boot|Burning Yocto binaries to NAND flash from U-Boot]]
* [[U-Boot 4.1.15 features|U-Boot features]]
* [[Adding yocto packages|Adding packages to Yocto]]


[https://community.freescale.com/docs/DOC-94874 i.MX Yocto Project: ltib versus bitbake]
|color=green}}<nowiki>
</nowiki>{{SoftBox
|title=How-to
|boxwidth=46
|content=<nowiki></nowiki>
=== Test and use an Interface ===
<div style="width:100%;">
<div style="width:50%; float: left;">
* [[VAR-SOM-MX6 Audio record play|Audio record/play]]
* [[IMX Backlight|Backlight]]
* [[IMX Bluetooth|Bluetooth]]
* [[VAR-SOM-MX6 Camera JehtroR1|Camera]]
* [[IMX CAN bus|CAN bus]]
* [[VAR-SOM-MX6 Dual Displays|Dual Displays: LVDS & HDMI]]
* [[VAR-SOM-MX6 Ethernet|Ethernet]]
* [[VAR-SOM-MX6 UART|External UART]]
* [[VAR-SOM-MX6 GPIO|GPIO]]
* [[U-Boot 4.1.15 features#HDMI auto-detection|HDMI]]
</div>
<div style="width:50%; float: right;">
* [[VAR-SOM-MX6 I2C|I2C]]
* [[VAR-SOM-MX6 LVDS Jethro|LVDS]]
* [[VAR-SOM-MX6 PCIE|PCIE]]
* [[IMX RTC|RTC]]
* [[VAR-SOM-MX6 SATA|SATA]]
* [[VAR-SOM-MX6 SPI|SPI]]
* [[IMX USB Host|USB Host]]
* [[VAR-SOM-MX6 USB OTG|USB OTG]]
* [[VAR-SOM-MX6 GSTREAM JETHRO|Video streaming - Playback/Capture]]
* [[VAR-SOM-MX6 Wireless LAN|Wireless LAN]]
</div>
</div>
|color=blue}}}}
__NONUMBEREDHEADINGS__

Revision as of 20:37, 27 November 2016

VAR-SOM-MX6 Yocto Krogoth
VAR-SOM-MX6 Yocto Krogoth Yocto project is a framework for creating a Linux distributions for embedded devices. Its layering mechanism makes it easy to add Linux to new target devices highly customized for a particular platform; it can include custom start-up scripts, software packages built with a high degree of optimization for a particular architecture, and different user interfaces from full Gnome desktop to a simple a serial console.

Freescale i.MX joined the Yocto Project community providing a release based on the Yocto Project framework. Variscite extend this framework to support our i.MX6 System On a Modules.

General

General

Programming


Build

Build Yocto, Linux and U-Boot

How-to

Test and use an Interface

__NONUMBEREDHEADINGS__

Retrieved from "https://variwiki.com/index.php?title=VAR-SOM-MX6_Yocto_Krogoth&oldid=6955"
Latest Modules
Support
Variscite Support Center
Contact Support
Product Longevity
Product Compliance Policy
Blog
Variscite Training
Variscite Website
This page was last edited on 27 November 2016, at 20:37.

© 2024 Variscite. All rights reserved