• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 430 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-DRA8X-TDA4X: Questions about Arago

Thomas Dorsch
Expert 2611 points

Part Number: PROCESSOR-SDK-DRA8X-TDA4X

Hi,

I dive into the PSDKLA 7_00_01 and building linux images with arago.

I've worked in the past with openembedded/yocto, and I would like to know what are the major differences between arago and yocto?

For example, I noticed that arago lacks in terms of support for extensible SDK and devtool - which I think are helpful tools during development.

Is it possible to "port" ti/arago-layers to yocto?

Best regards,
Thomas

  • 0
    TI__Guru** 113810 points

    Hi Thomas,

    Arago is the branding of the TI offering of the BSP and Distro. A write up is available here: http://arago-project.org/wiki/index.php/Main_Page

    Arago is already Yocto compliant and therefore you can use all of the Yocto tools. 

    I'm not aware of the limitations that you mention but if you can provide further details then I can help you along.

    Regards
    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 2611 points

    Hi Karthik,

    thank you very much for your answer. I worked in 2018 a little bit with arago and I remember there were some major issues with the tool "devtool".
    I hoped that this has been improved meanwhile.

    Some information (which may be outdated) here in E2E forum, leads to "it could work, but we are not supporting it":

    or

    I try to understand exactly what Arago is. For now, I understand that it is "just" a stack of layers. Like any other layer. Even offical yocto compatible.

    So there should be no technical issue with starting from a fresh yocto installation, adding TI/Arago-Layers and setting up the local configuration, right?

    But why are some yocto tools like "devtool" and "eSDK" not supported or known as not working?

    I was thinking about starting with a fresh yocto installation and adding TI/Arago-Layers to it. My hope was, that in the end I could use for example devtool and eSDK successfully. But now I'm not sure if that will work better than using arago as it is.

    Best Regards,
    Thomas

  • 0 in reply to Thomas Dorsch
    TI__Guru** 113810 points

    Hi Thomas,

    I reviewed the thread references that you provided and I'm reasonably sure that we have not done any specific work related to devtool in the recent past since those threads were updated.

    I'm still checking and will update if I hear back differently.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 2611 points

    Hi Karthik,

    are there any updates? Could you address my other questions please?

    Best regards,
    Thomas

  • 0 in reply to Thomas Dorsch
    TI__Guru** 113810 points

    Hi Thomas,

    We have not done any work to enable devtool and we do not have plans to add support for devtool in the near future.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 2611 points

    Okay, thank you Karthik.

    One last short question: When I build the tisdk-default-image, I got following output:

    thomas@dt-tda4:~/tda4vmx/psdk-linux-automotive-j7-evm-07_00_01/yocto-build/build$ MACHINE=j7-evm bitbake -k tisdk-default-image
WARNING: Layer meta-psdkla should set LAYERSERIES_COMPAT_meta-psdkla in its conf/layer.conf file to list the core layer names it is compatible with.
WARNING: Layer meta-psdkla should set LAYERSERIES_COMPAT_meta-psdkla in its conf/layer.conf file to list the core layer names it is compatible with.                   
NOTE: Started PRServer with DBfile: /home/thomas/tda4vmx/psdk-linux-automotive-j7-evm-07_00_01/yocto-build/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 33127, PID: 76611
WARNING: Layer meta-psdkla should set LAYERSERIES_COMPAT_meta-psdkla in its conf/layer.conf file to list the core layer names it is compatible with.
WARNING: Layer meta-psdkla should set LAYERSERIES_COMPAT_meta-psdkla in its conf/layer.conf file to list the core layer names it is compatible with.
Loading cache: 100% |###################################################################################################################################| Time: 0:00:03
Loaded 8134 entries from dependency cache.
Parsing recipes: 100% |#################################################################################################################################| Time: 0:00:02
Parsing of 2885 .bb files complete (2884 cached, 1 parsed). 8136 targets, 1176 skipped, 0 masked, 0 errors.
WARNING: No recipes available for:
  /home/thomas/tda4vmx/psdk-linux-automotive-j7-evm-07_00_01/yocto-build/sources/meta-arago/meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend
  /home/thomas/tda4vmx/psdk-linux-automotive-j7-evm-07_00_01/yocto-build/sources/meta-arago/meta-arago-distro/recipes-connectivity/iproute2/iproute2_4.19.0.bbappend
  /home/thomas/tda4vmx/psdk-linux-automotive-j7-evm-07_00_01/yocto-build/sources/meta-arago/meta-arago-distro/recipes-support/opencv/opencv_3.1.bbappend
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-18.04"
TARGET_SYS           = "aarch64-linux"
MACHINE              = "j7-evm"
DISTRO               = "arago"
DISTRO_VERSION       = "2020.05"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta-arago-distro
meta-arago-extras    = "HEAD:41cfd83e13955178bffae84ebbe5a915b79181fd"
meta-qt5             = "HEAD:fdd19517e17240b0b61765bd02fc483a1bde986f"
meta-virtualization  = "HEAD:237879d59e11187a49216a88b73a057408e4b3f7"
meta-networking
meta-python
meta-oe
meta-gnome
meta-filesystems     = "HEAD:e413c1ef621688e69bb7830bb3151ed23b30b73e"
meta-ti              = "HEAD:f2b2b2095f1a9d3ef705f7518d9db1e3141da2fb"
meta-arm
meta-arm-toolchain   = "HEAD:f8ea9ac3a06f543bd3dc259ffc1b60eb197a132d"
meta                 = "HEAD:c88cf750f26f6786d6ba5b4f1f7e5d4f0c800e6e"
meta-psdkla          = "HEAD:d81cf4a3dc12d918086cdec9b5833b24e6afd9d6"
meta-aws             = "HEAD:481c8793caf861b97415156c69dc4767f92e9c8f"


Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-18.04"
TARGET_SYS           = "arm-linux-gnueabi"
MACHINE              = "j7-evm-k3r5"
DISTRO               = "arago"
DISTRO_VERSION       = "2020.05"
TUNE_FEATURES        = "arm armv7a vfp thumb callconvention-hard"
TARGET_FPU           = "hard"
meta-arago-distro
meta-arago-extras    = "HEAD:41cfd83e13955178bffae84ebbe5a915b79181fd"
meta-qt5             = "HEAD:fdd19517e17240b0b61765bd02fc483a1bde986f"
meta-virtualization  = "HEAD:237879d59e11187a49216a88b73a057408e4b3f7"
meta-networking
meta-python
meta-oe
meta-gnome
meta-filesystems     = "HEAD:e413c1ef621688e69bb7830bb3151ed23b30b73e"
meta-ti              = "HEAD:f2b2b2095f1a9d3ef705f7518d9db1e3141da2fb"
meta-arm
meta-arm-toolchain   = "HEAD:f8ea9ac3a06f543bd3dc259ffc1b60eb197a132d"
meta                 = "HEAD:c88cf750f26f6786d6ba5b4f1f7e5d4f0c800e6e"
meta-psdkla          = "HEAD:d81cf4a3dc12d918086cdec9b5833b24e6afd9d6"
meta-aws             = "HEAD:481c8793caf861b97415156c69dc4767f92e9c8f"

Initialising tasks: 100% |##############################################################################################################################| Time: 0:00:07
Sstate summary: Wanted 9 Found 0 Missed 9 Current 2760 (0% match, 99% complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 8264 tasks of which 8244 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 7 seconds
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

Summary: There were 5 WARNING messages shown.

    Could you please explain, why there show two "Build Configuration" up? I've noticed that there are different MACHINES (j7-evm and j7-evm-k3r5)

    Thank you very much and best regards!

    Thomas

  • 0 in reply to Thomas Dorsch
    TI__Guru** 113810 points

    Hi Thomas,

    If you refer to the Linux bootflow that is documented here: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/j721e/README?h=ti-u-boot-2020.01#n23, you can see that there is a part of the SPL that runs on the R5F and there is a dependcy with the SYSFW that runs on the DMSC.

    So these recipes are included in the Yocto build and they are machine dependent on the k3r5.

    If you grep for k3r5 from the source directory of Yocto you will see two recipes that are relevant to j7-evm-k3r5.

    meta-ti/recipes-bsp/ti-sci-fw/ti-sci-fw_2020.04a.bb:COMPATIBLE_MACHINE = "k3r5"
    meta-ti/recipes-bsp/u-boot/u-boot-ti.inc:SPL_UART_BINARY_k3r5 = ""

    Regards

    Karthik