Template:Yocto Toolchain installation AM62: Difference between revisions

From Variscite Wiki
(Created page with "{{#varexists:DEFAULT_IMAGE_BB_NAME | | {{ #vardefine:DEFAULT_IMAGE_BB_NAME | var-default-image }} }} <!-- --> {{#vardefine:BB_ENV | {{#var:BB_ENV|{{#varexists: B2QT_GIT | MACH...")
 
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{#varexists:DEFAULT_IMAGE_BB_NAME | | {{ #vardefine:DEFAULT_IMAGE_BB_NAME | var-default-image }} }} <!--
<includeonly>{{#varexists:DEFAULT_IMAGE_BB_NAME | | {{ #vardefine:DEFAULT_IMAGE_BB_NAME | var-default-image }} }} <!--
--> {{#vardefine:BB_ENV | {{#var:BB_ENV|{{#varexists: B2QT_GIT | MACHINE={{#var:MACHINE_NAME}} | }} }} }} <!--
--> {{#vardefine:BB_ENV | {{#var:BB_ENV|{{#varexists: B2QT_GIT | MACHINE={{#var:MACHINE_NAME}} | }} }} }} <!--
--> {{#vardefine:B2QT_OR_YOCTO | {{#varexists: B2QT_GIT | B2QT | Yocto }} }} <!--
--> {{#vardefine:B2QT_OR_YOCTO | {{#varexists: B2QT_GIT | B2QT | Yocto }} }} <!--
Line 22: Line 22:
{{Note|The SDK should match the rootfs image on the target, otherwise you may experience difficulties when trying to debug application failures.}}
{{Note|The SDK should match the rootfs image on the target, otherwise you may experience difficulties when trying to debug application failures.}}
{{#ifeq: {{#expr: {{#var:TI_RELEASE_SHORT}} < 9 }} | 1 |
{{#ifeq: {{#expr: {{#var:TI_RELEASE_SHORT}} < 9 }} | 1 |
{{Note|TI's Yocto Dunfell Arago distribution does not support building an internal toolchain using populate_sdk by default. For more information, please see [https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1202155/faq-am6x-am335x-am437x-using-a-yocto-internal-toolchain-for-target-image-builds-and-cross-development-sdk-installer-generation-with-yocto-dunfell-based-v8-x-sdks-for-sitara-mpus FAQ: AM6x/AM335x/AM437x: Using a Yocto-internal toolchain for target image builds and cross-development SDK installer generation with Yocto Dunfell-based v8.x SDKs for Sitara MPUs].<br><br>Starting in Yocto Kirkstone, populate_sdk will be supported.}}
{{Note|TI's Yocto Dunfell Arago distribution does not officially support building the complete SDK using populate_sdk by default.<br>To fix it, dedicated patches have been introduced in Variscite BSP and are available only in the latest source code. For more information, please see [https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1202155/faq-am6x-am335x-am437x-using-a-yocto-internal-toolchain-for-target-image-builds-and-cross-development-sdk-installer-generation-with-yocto-dunfell-based-v8-x-sdks-for-sitara-mpus FAQ: AM6x/AM335x/AM437x: Using a Yocto-internal toolchain for target image builds and cross-development SDK installer generation with Yocto Dunfell-based v8.x SDKs for Sitara MPUs].<br>Starting in Yocto Kirkstone, populate_sdk will be supported.}}
{{Note|When including some C++ headers, TI's Yocto Dunfell toolchain may not be able to automatically find the full header path.<br>To fix it, the expected paths can be manually added to the list of the include paths (either in the Makefile or in the target build environment), with
-I{{#var:TOOLCHAIN_TARGET_SYSROOT_LOCATION}}/usr/include/c++/{{#var:TOOLCHAIN_GCC_VER}} -I{{#var:TOOLCHAIN_TARGET_SYSROOT_LOCATION}}/usr/include/c++/{{#var:TOOLCHAIN_GCC_VER}}/{{#var:TOOLCHAIN_TYPE}}
}}
}}
}}
== Install the toolchain/SDK ==
== Install the toolchain/SDK ==
Install the tools by running the resulted script in {{#var:SDK_DIR}}.
Install the tools by running the resulted script in {{#var:SDK_DIR}}.


E.g.
E.g.
  $ tmp/deploy/sdk/{{#var:TOOLCHAIN_INSTALL_NAME}}
  $ {{#var:SDK_DIR}}/{{#var:TOOLCHAIN_INSTALL_NAME}}
Note: The toolchain/script name depends on your build machine and the bitbaked image/recipe, and may change.<br>
Note: The toolchain/script name depends on your build machine and the bitbaked image/recipe, and may change.<br>
<br>
<br>
Line 39: Line 43:
Each time you wish to use the toolchain in a new shell session, you need to source the environment setup script:
Each time you wish to use the toolchain in a new shell session, you need to source the environment setup script:
  $ source {{#var:TOOLCHAIN_LOCATION}}
  $ source {{#var:TOOLCHAIN_LOCATION}}
</includeonly>

Latest revision as of 00:10, 16 October 2023