Skip to content

feat: linux: Add compilation instructions for TI Apps Launcher #403

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cshilwant merged 2 commits into from
Jul 22, 2025
Merged

feat: linux: Add compilation instructions for TI Apps Launcher #403

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74e82d8
feat: linux: Add compilation instructions for TI Apps Launcher
jsuhaas22 Jul 21, 2025
1da7f9d
feat: linux: Add compilation instructions for EdgeAI GUI App
jsuhaas22 Jul 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 47 additions & 0 deletions source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,3 +139,50 @@
.. ifconfig:: CONFIG_part_variant in ('J784S4')

13. For more information on edge AI software stack, refer `Edge AI Documentation <https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-edgeai/AM69A/10_01_00/exports/docs/common/sdk_overview.html>`_

Compiling EdgeAI GUI App

Check warning on line 143 in source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.Headings] Use sentence-style capitalization in 'Compiling EdgeAI GUI App'.

Raw Output:
{"message": "[RedHat.Headings] Use sentence-style capitalization in 'Compiling EdgeAI GUI App'.", "location": {"path": "source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst", "range": {"start": {"line": 143, "column": 1}}}, "severity": "INFO"}
========================

The ideal way to compile EdgeAI GUI App is to trigger a Yocto
build. But for a quicker way to do it, especially during development,
TI provides a `debian-arm64
<https://github.com/TexasInstruments/ti-docker-images/pkgs/container/debian-arm64>`__
Docker image. This image already has all dependencies required
for compiling edgeai-gui-app.

First, clone EdgeAI GUI App on host:

.. code:: console

git clone https://git.ti.com/git/apps/edgeai-gui-app.git
export EDGEAI_GUI_APP_REPO="$(pwd)/edgeai-gui-app"
cd ${EDGEAI_GUI_APP_REPO}

Then, pull TI's debian-arm64 Docker image and run it:

.. code:: console

docker pull ghcr.io/texasinstruments/debian-arm64:latest
docker run -it -v ${EDGEAI_GUI_APP_REPO}:/root/ti-apps-launcher ghcr.io/texasinstruments/debian-arm64 bash

Finally, run:

.. code:: console

cmake -B build -S . -DRT_BUILD=0 # if target is RT image, make -DRT_BUILD=1
make -C build

The compiled binary should be ``build/edgeai-gui-app``.

Comment thread
cshilwant marked this conversation as resolved.
Copy the compiled binary to the :file:`/usr/bin` of the target:

.. code:: console

scp ${EDGEAI_GUI_APP_REPO}/build/edgeai-gui-app root@<ip-addr-of-device>:/usr/bin/

Check warning on line 181 in source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.UserReplacedValues] Separate words by underscores in user-replaced values.

Raw Output:
{"message": "[RedHat.UserReplacedValues] Separate words by underscores in user-replaced values.", "location": {"path": "source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst", "range": {"start": {"line": 181, "column": 57}}}, "severity": "INFO"}

.. note::

This is a quick and easy way to compile ti-apps-launcher during
development, but it is a good idea to validate with Yocto builds
often. There is a possibility that compiler mismatch could present
issues in the run up to production.
60 changes: 60 additions & 0 deletions source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -438,3 +438,63 @@
.. Image:: /images/ti-apps-launcher-powermenu2.png
:height: 400

Compiling TI Apps Launcher

Check warning on line 441 in source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.Headings] Use sentence-style capitalization in 'Compiling TI Apps Launcher'.

Raw Output:
{"message": "[RedHat.Headings] Use sentence-style capitalization in 'Compiling TI Apps Launcher'.", "location": {"path": "source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst", "range": {"start": {"line": 441, "column": 1}}}, "severity": "INFO"}
--------------------------

The ideal way to compile TI Apps Launcher is to trigger a Yocto
build. But for a quicker way to do it, especially during development,
TI provides a `debian-arm64
<https://github.com/TexasInstruments/ti-docker-images/pkgs/container/debian-arm64>`__
Docker image. This image already has all dependencies required
for compiling ti-apps-launcher.

First, clone TI Apps Launcher on host:

.. code:: console

git clone https://github.com/texasinstruments/ti-apps-launcher.git
export TI_APPS_LAUNCHER_REPO="$(pwd)/ti-apps-launcher"
cd ti-apps-launcher

Then, add the following line in :file:`CMakeLists.txt`:

.. code:: console

add_compile_definitions(SOC_AM62=1) # if target is AM62x or AM62SIP
add_compile_definitions(SOC_AM62_LP=1) # if target is AM62x-LP
add_compile_definitions(SOC_AM62P=1) # if target is AM62P

Then, pull TI's debian-arm64 Docker image and run it:

.. code:: console

docker pull ghcr.io/texasinstruments/debian-arm64:latest
docker run -it -v ${TI_APPS_LAUNCHER_REPO}:/root/ti-apps-launcher ghcr.io/texasinstruments/debian-arm64 bash

Finally, run:

.. code:: console

cmake -B build -S . -DRT_BUILD=0 # if target is RT image, make -DRT_BUILD=1
make -C build

The compiled binary should be :file:`build/ti-apps-launcher`.

Check warning on line 481 in source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.Slash] Use either 'or' or 'and' in 'build/ti'

Raw Output:
{"message": "[RedHat.Slash] Use either 'or' or 'and' in 'build/ti'", "location": {"path": "source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst", "range": {"start": {"line": 481, "column": 38}}}, "severity": "WARNING"}

Copy the compiled binary to :file:`/usr/bin/` directory of the target:

.. code:: console

scp ${TI_APPS_LAUNCHER_REPO}/build/ti-apps-launcher root@<ip-addr-of-device>:/usr/bin

Check warning on line 487 in source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.UserReplacedValues] Separate words by underscores in user-replaced values.

Raw Output:
{"message": "[RedHat.UserReplacedValues] Separate words by underscores in user-replaced values.", "location": {"path": "source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst", "range": {"start": {"line": 487, "column": 61}}}, "severity": "INFO"}

If you have modified the scripts in the :file:`scripts/` directory, then copy them too:

.. code:: console

scp -r ${TI_APPS_LAUNCHER_REPO}/scripts root@<ip-addr-of-device>:/opt/ti-apps-launcher

Check warning on line 493 in source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[RedHat.UserReplacedValues] Separate words by underscores in user-replaced values.

Raw Output:
{"message": "[RedHat.UserReplacedValues] Separate words by underscores in user-replaced values.", "location": {"path": "source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst", "range": {"start": {"line": 493, "column": 49}}}, "severity": "INFO"}

Comment thread
cshilwant marked this conversation as resolved.
.. note::

This is a quick and easy way to compile ti-apps-launcher during
development, but it is a good idea to validate with Yocto builds
often. There is a possibility that compiler mismatch could present
issues in the run up to production.
Loading