IoTGateway/BSP/Linux/AM57xx/AM7xx User Guide - Revision history

Zhengguang.yang at 02:00, 15 May 2017

2017-05-15T02:00:16Z

Zhengguang.yang at 01:59, 15 May 2017

2017-05-15T01:59:42Z

Zhengguang.yang at 09:38, 12 May 2017

2017-05-12T09:38:41Z

Zhengguang.yang at 09:37, 12 May 2017

2017-05-12T09:37:56Z

Zhengguang.yang at 09:37, 12 May 2017

2017-05-12T09:37:33Z

Zhengguang.yang at 09:37, 12 May 2017

2017-05-12T09:37:09Z

Zhengguang.yang at 09:36, 12 May 2017

2017-05-12T09:36:39Z

Zhengguang.yang at 09:36, 12 May 2017

2017-05-12T09:36:21Z

Zhengguang.yang at 09:35, 12 May 2017

2017-05-12T09:35:59Z

Zhengguang.yang: change color

2017-05-12T09:23:18Z

change color

@@ Line 204: / Line 204: @@
 When needed, source code under the work directory (e.g., arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl/git) can be modified. After the modification is done, run the following commands to force recompilation with the new code and rebuilding of the recipe, e.g.,
-<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xx-evm bitbake opencl --force -c compile</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xx-evm bitbake opencl</div>
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xxrom7510a1&nbsp;bitbake opencl --force -c compile</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xxrom7510a1 bitbake opencl</div>
 === <span style="color:#0070c0;">Installing Package</span> ===

@@ Line 188: / Line 188: @@
 For example, the command below builds only the opencl recipe and all the dependencies it defines.
-<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xx-evm bitbake opencl</div>
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xxrom7510a1 bitbake opencl</div>
 After the bitbake command above is successfully done, arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl directory will be available including the original source code under the git folder, independent shared objects (.so files) under packages-split folder, and IPKs under deploy-ipks folder.

@@ Line 86: / Line 86: @@
 In addition to individual components packages, the following table provides a list of build targets supported. These are the &lt;target&gt; used in the command:
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=&lt;machine&gt; bitbake &lt;target&gt;</div>
 The "Build Output" is given relative to the arago-tmp-[toolchain]/deploy directory.
@@ Line 153: / Line 151: @@
 The following platforms are supported in Processor SDK. These are the &lt;machine&gt; in the command:
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=&lt;machine&gt; bitbake &lt;target&gt;</div>
 {| border="1" cellspacing="0" cellpadding="0"
 |-

@@ Line 192: / Line 192: @@
 For example, the command below builds only the opencl recipe and all the dependencies it defines.
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xx-evm bitbake opencl</div>
 After the bitbake command above is successfully done, arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl directory will be available including the original source code under the git folder, independent shared objects (.so files) under packages-split folder, and IPKs under deploy-ipks folder.
@@ Line 210: / Line 208: @@
 When needed, source code under the work directory (e.g., arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl/git) can be modified. After the modification is done, run the following commands to force recompilation with the new code and rebuilding of the recipe, e.g.,
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xx-evm bitbake opencl --force -c compile</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE=am57xx-evm bitbake opencl</div>
 === <span style="color:#0070c0;">Installing Package</span> ===
 To install a modified and rebuilt package, copy the new IPKs from the deploy-ipks folder (e.g., arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl/[version]/deploy-ipks) to the target system and then run the following command to install the IPKs:
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">opkg install [package_ipk].ipk</div>
 == <span style="color:#0070c0;">Common Variations</span> ==

@@ Line 226: / Line 226: @@
 In Processor SDK delivered today the graphics hardware acceleration is enabled by default for device families with SGX (e.g. AM335x, AM437x, AM57xx). As a result, some of the applications with graphics dependencies will not run properly on device variants in those families that do not contain the SGX accelerator (e.g. AM3352, AM4372, etc.). The Processor SDK has been enhanced to provide the same OOB experience with software rendering provided by QT5/Weston. The non-SGX software rendering build will be enabled by adding the following to the bottom of conf/local.conf immediately before invoking bitbake.
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">MACHINE_FEATURES_remove=”sgx”</div>
 === <span style="color:#0070c0;">Rebuilding without Wayland</span> ===
 If a full Window system is not needed, i.e. if you simply want apps to run full screen using EGLFS then you can remove Wayland by adding the following to the bottom of conf/local.conf immediately before invoking bitbake:
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">DISTRO_FEATURES_remove = "wayland"</div>

@@ Line 176: / Line 176: @@
 == <span style="color:#0070c0;">Using the snapshot of the source packages in Processor SDK release</span> ==
 Using the snapshot of the arago source packages can avoid fetch errors during the build when external URLs become unavailable. To use the snapshot of sources distributed with a given Processor SDK release, you must download a script from the SDK download page and then execute it on your host to fetch all the packages from TI servers. For example, see am57xx-evm-linux-sdk-arago-src-03.03.00.04.tar.xz file in AM57xx-Linux-SDK-Download-page. Once this package is downloaded, there are just a few extra steps in the build process to fetch all the corresponding packages. The extra steps are shown in red below:
 &nbsp;
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ ./oe-layertool-setup.sh</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ mkdir downloads</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ # You should already have downloaded CCS via web browser.&nbsp; Assuming location at ~/Downloads.</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cp $HOME/Downloads/CCS6.1.3.00034_linux.tar.gz downloads/</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ touch downloads/CCS6.1.3.00034_linux.tar.gz.done</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cd downloads</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ # Assuming src file downloaded to $HOME/Downloads</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ tar xvf $HOME/Downloads/&lt;target-board&gt;-linux-sdk-arago-src-##.##.##.##.tar.xz</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ &lt;target-board&gt;-linux-sdk-arago-src-##.##.##.##/get_build_sources.sh &lt;target-board&gt;-linux-sdk-arago-src-##.##.##.##/source_pkg_list.txt</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ # When it displays “Would you like to continue? [y/n]” string, type “y”</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cd ..</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cd build</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ . conf/setenv</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ MACHINE=&lt;target-board&gt; bitbake arago-core-tisdk-image</div>
 &nbsp;

@@ Line 78: / Line 78: @@
 Processor SDK uses the following oe-layersetup configs to configure the meta layers.
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ ./oe-layersetup.sh</div>
 &nbsp;

@@ Line 28: / Line 28: @@
 To pull ubuntu 14.04 image from Docker Hub
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ docker pull advrisc/u14.04-am57lbv1</div>
 To create container
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ docker run -it --name ${CONTAINER_NAME} -v ${WORKSPACE}:yocto_bsp:rw advrisc/u14.04-am57lbv1 /bin/bash</div>
 &nbsp;

@@ Line 44: / Line 44: @@
 Please download a script from the SDK download page and then execute it on your host to fetch all the packages from TI servers. For example, see am57xx-evm-linux-sdk-arago-src-03.03.00.04.tar.xz file in AM57xx-Linux-SDK-Download-page. Once this package is downloaded, there are just a few extra steps in the build process to fetch all the corresponding packages.
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ sudo chown adv:adv -R yocto_bsp</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cd yocto_bsp/</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ mkdir tisdk</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cd tisdk/</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ repo init -u [[|[git://github.com/ADVANTECH-Corp/adv-ti-yocto-bsp.git git://github.com/ADVANTECH-Corp/adv-ti-yocto-bsp.git]]] -b processor-sdk-03.01.00.06</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ repo sync</div>
 Due to lots of company firewalls/proxies only permitting HTTP traffic this is what our default repo manifest is using. At times the loading of repository server might be too heavy or for other reasons. You may be experience the following issues:
@@ Line 72: / Line 60: @@
 cd .repo/projects/sources/meta-arago.git
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">git gc</div>
 If the error(s) persist try removing your local git/repo cache before attempting to sync again, e.g. if the error indicates an issue in the meta-openembedded repository:
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">rm -rf .repo/projects/sources/meta-arago.git</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">rm -rf .repo/project-objects/meta-arago.git.git</div>
 Additionally you can limit the number of git repositories which are downloaded in parallel by using the additional parameter "-jX". e.g. to download one repository at a time:
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">repo sync -j1</div>
 Additionally the following tweak to your IP settings maybe helpful:
@@ Line 92: / Line 72: @@
 <remote fetch="[[|[git://git.arago-project.org git://git.arago-project.org]]]" name="meta-arago"/>
+<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ ./oe-layertool-setup.sh</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ mkdir downloads</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ # You should already have downloaded CCS via web browser.&nbsp; Assuming location at ~/Downloads.</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cp $HOME/Downloads/CCS6.1.3.00034_linux.tar.gz downloads/</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ touch downloads/CCS6.1.3.00034_linux.tar.gz.done</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ cd build</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ . conf/setenv</div><div style="background:#eee;border:1px solid #ccc;padding:5px 10px;">$ MACHINE=&lt;target-board&gt; bitbake arago-core-tisdk-image</div>
 &nbsp;

@@ Line 115: / Line 115: @@
 The following sections provide information for configuration, build options, and supported platforms of the Processor SDK.
-== Layer Configuration ==
+== <span style="color:#0070c0;">Layer Configuration</span> ==
 Processor SDK uses the following oe-layersetup configs to configure the meta layers.
@@ Line 123: / Line 123: @@
 &nbsp;
-== Build Options ==
+== <span style="color:#0070c0;">Build Options</span> ==
-=== '''Images''' ===
+=== <span style="color:#0070c0;">Images</span> ===
 In addition to individual components packages, the following table provides a list of build targets supported. These are the &lt;target&gt; used in the command:
@@ Line 192: / Line 192: @@
 &nbsp;
-=== '''Platforms''' ===
+=== <span style="color:#0070c0;">Platforms</span> ===
 The following platforms are supported in Processor SDK. These are the &lt;machine&gt; in the command:
@@ Line 217: / Line 217: @@
 &nbsp;
-== Using the snapshot of the source packages in Processor SDK release ==
+== <span style="color:#0070c0;">Using the snapshot of the source packages in Processor SDK release</span> ==
 Using the snapshot of the arago source packages can avoid fetch errors during the build when external URLs become unavailable. To use the snapshot of sources distributed with a given Processor SDK release, you must download a script from the SDK download page and then execute it on your host to fetch all the packages from TI servers. For example, see am57xx-evm-linux-sdk-arago-src-03.03.00.04.tar.xz file in AM57xx-Linux-SDK-Download-page. Once this package is downloaded, there are just a few extra steps in the build process to fetch all the corresponding packages. The extra steps are shown in red below:
@@ Line 255: / Line 256: @@
 &nbsp;
-== Recipes ==
+== <span style="color:#0070c0;">Recipes</span> ==
-=== '''Recipe Basics''' ===
+=== <span style="color:#0070c0;">Recipe Basics</span> ===
 One or more recipes can be specified for the &lt;target&gt; for greater granularity of recipe development and debug. Specifying a recipe name, minus the version (if the version is appended to the name), will build the recipe and all its dependencies.
@@ Line 277: / Line 278: @@
 &nbsp;
-=== '''Forced Re-compilation''' ===
+=== <span style="color:#0070c0;">Forced Re-compilation</span> ===
 When needed, source code under the work directory (e.g., arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl/git) can be modified. After the modification is done, run the following commands to force recompilation with the new code and rebuilding of the recipe, e.g.,
@@ Line 285: / Line 286: @@
 MACHINE=am57xx-evm bitbake opencl
-=== '''Installing Package''' ===
+=== <span style="color:#0070c0;">Installing Package</span> ===
 To install a modified and rebuilt package, copy the new IPKs from the deploy-ipks folder (e.g., arago-tmp-[toolchain]/work/am57xx_evm-linux-gnueabi/opencl/[version]/deploy-ipks) to the target system and then run the following command to install the IPKs:
@@ Line 291: / Line 292: @@
 opkg install [package_ipk].ipk
-== Common Variations ==
+== <span style="color:#0070c0;">Common Variations</span> ==
-=== '''Rebuilding without SGX''' ===
+=== <span style="color:#0070c0;">Rebuilding without SGX</span> ===
 In Processor SDK delivered today the graphics hardware acceleration is enabled by default for device families with SGX (e.g. AM335x, AM437x, AM57xx). As a result, some of the applications with graphics dependencies will not run properly on device variants in those families that do not contain the SGX accelerator (e.g. AM3352, AM4372, etc.). The Processor SDK has been enhanced to provide the same OOB experience with software rendering provided by QT5/Weston. The non-SGX software rendering build will be enabled by adding the following to the bottom of conf/local.conf immediately before invoking bitbake.
@@ Line 299: / Line 300: @@
 MACHINE_FEATURES_remove=”sgx”
-=== '''Rebuilding without Wayland''' ===
+=== <span style="color:#0070c0;">Rebuilding without Wayland</span> ===
 If a full Window system is not needed, i.e. if you simply want apps to run full screen using EGLFS then you can remove Wayland by adding the following to the bottom of conf/local.conf immediately before invoking bitbake:
 DISTRO_FEATURES_remove = "wayland"