IoTGateway/BSP/Linux/iMX6/Technical Specification - Revision history

Charles.huang at 06:13, 26 January 2017

2017-01-26T06:13:41Z

Charles.huang at 06:02, 26 January 2017

2017-01-26T06:02:58Z

Charles.huang at 05:59, 26 January 2017

2017-01-26T05:59:55Z

Charles.huang at 05:51, 26 January 2017

2017-01-26T05:51:59Z

Charles.huang at 05:25, 26 January 2017

2017-01-26T05:25:45Z

Charles.huang at 10:26, 25 January 2017

2017-01-25T10:26:13Z

Charles.huang at 10:05, 25 January 2017

2017-01-25T10:05:56Z

Charles.huang at 09:47, 25 January 2017

2017-01-25T09:47:10Z

Charles.huang at 09:46, 25 January 2017

2017-01-25T09:46:48Z

Charles.huang at 09:18, 25 January 2017

2017-01-25T09:18:31Z

← Older revision		Revision as of 06:13, 26 January 2017
Line 43:		Line 43:

	By default, the Yocto Project uses SysVinit as the initialization manager. However, support also exists for systemd, which is a full replacement for init with parallel starting of services, reduced shell overhead and other features that are used by many distributions.		By default, the Yocto Project uses SysVinit as the initialization manager. However, support also exists for systemd, which is a full replacement for init with parallel starting of services, reduced shell overhead and other features that are used by many distributions.
−
−	~~=== Networking ===~~

	=== SELinux ===		=== SELinux ===

@@ Line 46: / Line 46: @@
 === Networking ===
-SELinux
+=== SELinux ===
 SELinux will be enabled in enforcing mode, using the targeted policy.
 === Display manager & Graphics ===
@@ Line 67: / Line 61: @@
 [[File:Sdk-devtool-modify-flow.png|RTENOTITLE]]
 == Core Applications ==
-Web Browser
+=== Web Browser ===
 Chromium Browser on X11, XWayland and Wayland
@@ Line 85: / Line 77: @@
 Systemd is supported in this release but not enabled as default initialization manager. The enable systemd as default go to the<br/>fsl-imx-preferred-env.inc and uncomment the systemd section. The 4.1.X-2.X series is the last release series without systemd<br/>as default. The next release GA series will use systemd as the default initialization manager.
 == Core Package list ==

@@ Line 43: / Line 43: @@
 By default, the Yocto Project uses SysVinit as the initialization manager. However, support also exists for systemd, which is a full replacement for init with parallel starting of services, reduced shell overhead and other features that are used by many distributions.
 === Networking ===
+SELinux
 ===  ===
 SELinux will be enabled in enforcing mode, using the targeted policy.
@@ Line 62: / Line 56: @@
+?
-=== Display manager ===
+=== Display manager & Graphics ===
-=== Graphics ===
+• Graphics recipes reside in recipes-graphics folder.
 === Modify the Source of an Existing Component ===
@@ Line 78: / Line 72: @@
 == Core Applications ==
-Core applications are part of the Workstation product and can not be removed.
+Web Browser
+Chromium Browser on X11, XWayland and Wayland
-=== Web Browser ===
+The Yocto Project community has chromium-imx recipes to enable hardware acceleration for X11, XWayland and Wayland<br/>version Chromium Browser for i.MX SoC with GPU hardware. Note that NXP does not support or test the patches from<br/>community, either for VPU or GPU support. This section describes how to integrate Chromium into your rootfs and enable<br/>hardware accelerated rendering of WebGL. The Chromium browser requires additional layers added in the fsl-releasesetup.<br/>sh script automatically.<br/>In local.conf, you can perform the following operations:<br/>• Add Chromium into your image.<br/>CORE_IMAGE_EXTRA_INSTALL += "chromium libexif"<br/>• Add the commercial white list into local.conf.<br/>LICENSE_FLAGS_WHITELIST="commercial"<br/>This allows proprietary code to be included into your image. In fact, this allows a bunch of recipes flagged as "commercial"<br/>to be built and included in the final image. It is a huge set of commercial licensed packages, with different licenses each one.<br/>Therefore, this allows the build and the installation. Additional license obligations will need to be met for these additions.<br/>Make sure you know what they are and are in compliance.
+=== Qt 5 and QtWebEngine browsers ===
-=== Terminal emulator ===
+Qt 5 has both a commercial and an open source license. When building in Yocto Project the open source license is the<br/>default. Make sure to understand the differences between these licenses and choose appropriately. Once custom Qt 5<br/>development has started on the open source license it can't be used with the commercial license. Work with a legal<br/>representative to understand the differences between these licenses.<br/>There are three Qt 5 browsers available. QtWebEngine browsers can be found in /usr/share/qt5/examples/<br/>webenginewidgets/browser, /usr/share/qt5/examples/webenginewidgets/fancybrowser and /usr/<br/>share/qt5/examples/webengine/quicknanobrowser.<br/>To run any of these, after booting up Linux OS on your device, tell Qt 5 which graphics to use by setting the environment<br/>variable below. See Section "Qt 5" in the i.MX Linux® User's Guide (IMXLUG) for the information on the graphics for<br/>different graphical backends.<br/>$export QT_QPA_PLATFORM=$Graphics<br/>All three browsers can be run by going to the directory above and running the executable found there. Touchscreen can be<br/>enabled by adding the parameters -plugin evdevtouch:/dev/input/event0 to the executable. The DISPLAY variable<br/>may need to be set in the environment before beginning:<br/>export DISPLAY=:0.0<br/>The command line might look like one of these:<br/>./browser -plugin evdevtouch:/dev/input/event0<br/>./fancybrowser -plugin evdevtouch:/dev/input/event0<br/>./quicknanobrowser -plugin evdevtouch:/dev/input/event0
+=== Systemd ===
-=== Text Editor ===
+Systemd is supported in this release but not enabled as default initialization manager. The enable systemd as default go to the<br/>fsl-imx-preferred-env.inc and uncomment the systemd section. The 4.1.X-2.X series is the last release series without systemd<br/>as default. The next release GA series will use systemd as the default initialization manager.
+===  ===
 ===  ===

@@ Line 1: / Line 1: @@
 = Hardware =
@@ Line 59: / Line 57: @@
 SELinux will be enabled in enforcing mode, using the targeted policy.
 === Software updates ===
+?
 === Display manager ===
+QT5 with x11
 === Graphics ===
 === Modify the Source of an Existing Component ===

@@ Line 1: / Line 1: @@
 This document
 = Hardware =
 == iMX6 High-Performance, 3D Graphics, HD Video, ARM Cortex-A9 Core ==
@@ Line 14: / Line 16: @@
 *Advanced hardware-enabled security
-[[File:IMX6Q_BD_IMG.jpg]]
+[[File:IMX6Q BD IMG.jpg|RTENOTITLE]]
@@ Line 27: / Line 30: @@
 [[File:Yocto-environment.png|RTENOTITLE]]
-== Core Services and Features ==
+== Yocto Core Services and Features ==
-This section should describe the core services of the platform and their intended use. The items here should refer back to the PRD for a functional justification.
+This section should describe the core services of the platform.
 [[File:Sdk-environment.png|RTENOTITLE]]
@@ Line 37: / Line 40: @@
 === File system ===
-The default file system type for workstation installs should be ext3
+The file system type that the build is being performed on can also influence performance. Using&nbsp;<code>ext4</code>&nbsp;is recommended as compared to&nbsp;<code>ext2</code>&nbsp;and&nbsp;<code>ext3</code>&nbsp;due to&nbsp;<code>ext4</code>&nbsp;improved features such as extents
 === Service management ===
-Systemd provides ways to control and monitor the activity and status of system services, resources they require, etc. System services are expected to provide systemd units. See the systemd [http://0pointer.de/public/systemd-man/systemd.unit.html documentation].
+By default, the Yocto Project uses SysVinit as the initialization manager. However, support also exists for systemd, which is a full replacement for init with parallel starting of services, reduced shell overhead and other features that are used by many distributions.
 === Logging ===
@@ Line 107: / Line 110: @@
 [[File:Sdk-devtool-modify-flow.png|RTENOTITLE]]
-=== Other ===
+===  ===
 == Core Applications ==
@@ Line 137: / Line 138: @@
+?
-=== Virtualization frontend ===
+===  ===
 == Core Package list ==
@@ Line 2,244: / Line 2,238: @@
 </pre>
-=== TODO ===
+=== Policies for software add-ons ===
-*Add fonts, non-core applicatoins
+SUSI4
-=== Policies for software add-ons ===
+When developers want to write an application that involves hardware access, they have to study the specifications to write the drivers. This is a time-consuming job and requires lots of expertise. Advantech has done all the hard work for our customers with the release of a suite of Software APIs, Application Programming Interfaces, which is&nbsp;''a Bridge to Simplify & Enhance H/W & Application Implementation Efficiency''. Nowadays, Advantech provides our sample application demos, HW drivers and APIs. The drivers which are keeping in maintain included Secured & Unified Smart Interface (SUSI) 4.0, 3.02 and iManager 2.0. The only SUSI4 driver is on developing, so we recommend SUSI4 to new customers.
-General rules and policies for how extra software is installed and what requirements are put on that software.
+WISE Agent
-*Optional software must not interfere with the regular functionality of mandatory components. E.g. installing optional audio software must not prevent other applications from using pulseaudio and gstreamer for media playback.
+'''WISE Agent – a software development framework to communicate between device and RMM Server.'''<br/>Advantech provides a software development framework to communicate and exchange information between a device and RMM Server called a WISE Agent framework.<br/>The WISE Agent framework provides a rich set of user-friendly, intelligent and integrated interfaces, which speeds development, enhances security and makes agent application easier and simpler to communicate with RMM Server.
 == Installation methods and media ==
@@ Line 2,269: / Line 2,256: @@
 == Hardware requirements ==
-We
+Please get ELAA ROM-3420DK and ROM-7421DK start kit &nbsp;
-== Engineering Roadmap ==
+== Software user guide ==
-document.
+[[IoTGateway/BSP/Linux/iMX6/Yocto_LBV8_User_Guide|Yocto 2.1 software user guide]]

@@ Line 20: / Line 20: @@
 = Software =
-[[File:Yocto-environment.png|RTENOTITLE]]
+The Yocto Project is an open-source collaboration project whose focus is developers of embedded Linux systems. Among other things, the Yocto Project uses a build host based on the OpenEmbedded (OE) project, which uses the&nbsp;[http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#bitbake-term BitBake]&nbsp;tool, to construct complete Linux images. The BitBake and OE components are combined together to form a reference build host, historically known as&nbsp;[http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#poky Poky].
 == Core Services and Features ==

@@ Line 114: / Line 114: @@
 == Core Package list ==
-List the core packages of the product. This list includes all packages that will be shipping on the core media. This is the mandatory minimal list of packages that needs to be installed on a system at all times for it to qualify as a Fedora workstation install. This package list will be the priority focus for QA and bug fixing.
+List the core packages of the product. This list includes all packages that will be shipping on the release image. This is the mandatory minimal list of packages that needs to be installed on a system at all times. This package list will be the priority focus for QA and bug fixing.
 === Package list ===