VAR-SOM-MX6 Yocto: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- | --> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!-- | ||
--> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_MORTY_BETA_VAR-SOM-MX6}}}} <!-- | --> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_MORTY_BETA_VAR-SOM-MX6}}}} <!-- | ||
--> {{SoftwareEx | --> {{SoftwareEx | ||
|title=VAR-SOM-MX6 Yocto {{#var:YOCTO_NAME}} | |title=VAR-SOM-MX6 Yocto {{#var:YOCTO_NAME}} | ||
|image=Yocto.png | |image=Yocto.png |
Revision as of 11:19, 14 May 2017
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. This release is based on Freescale/NXP Community BSP layer for Yocto framework. Variscite extends this layer to support its i.MX6 System On Module products: VAR-SOM-MX6, VAR-SOM-SOLO/DUAL and DART-MX6 (all of which are under the VAR-SOM-MX6 category of this Wiki).
General
Programming
Support
- Variscite Customer Portal
Register at Variscite Customer Portal to get high quality engineering support for Variscite products - Variscite Support Forum
Build Yocto, Linux and U-Boot
- [ Release Notes]
- Setting a Development Environment
- Build Yocto from source code
- Yocto common build errors
- Toolchain installation for out of Yocto builds
- Build the Linux kernel from source code
- Build U-Boot from source code
- Customizing the Linux kernel and U-Boot
- Burning Yocto binaries to NAND flash/eMMC via SD card
- Burning Yocto binaries to NAND flash/eMMC via Ethernet
- Burning Yocto binaries to NAND flash from U-Boot
- U-Boot features
- Adding packages to Yocto
- Replace the Linux logo
Test and use an Interface
__NONUMBEREDHEADINGS__