• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 101 subscribers
  • Views 1406 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.

TDA4VM: Problems with fetching of components from TI git for Yocto build and question about Device Tree configs

John H. Gardner
Guru 51461 points

Have 3 customer questions below, after working with our TDA4 EVM - they have run into some problems regarding Yocto build and device trees:

  1. After running TOOLCHAIN_BASE=$HOME MACHINE=j7-evm bitbake -k tisdk-rootfs-image

they managed to successfully execute 84% of the tasks from the script. However, with some of them (428 remaining) they were not able to proceed due to errors during fetching of the components from the TI’s git repository (log file attached), even after completely omitting their internal network firewalls and proxies (they used private connection for that) and nothing has changed.

Here is the log file:

Fullscreen 8080.log_yocto_git.txt Download 
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 browser-layer should set LAYERSERIES_COMPAT_browser-layer in its conf/layer.conf file to list the core layer names it is compatible with.
NOTE: Started PRServer with DBfile: /home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 46619, PID: 6579
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 browser-layer should set LAYERSERIES_COMPAT_browser-layer in its conf/layer.conf file to list the core layer names it is compatible with.
Loading cache...done.
Loaded 4091 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.40.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-18.04"
TARGET_SYS           = "aarch64-linux"
MACHINE              = "j7-evm"
DISTRO               = "arago"
DISTRO_VERSION       = "2019.07"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta-psdkla          = "HEAD:b220cffa909010ee669554cb1ba4da7e0acb30e9"
meta-arago-distro    
meta-arago-extras    = "HEAD:6cfafa6f79daf77c7b30fece0f5c8780c4f235ea"
meta-browser         = "HEAD:26d50665e2f7223c5f4ad7481a8d2431e7cb55fb"
meta-qt5             = "HEAD:1520d5b2b2beec5e1c3209d3178219e93ef08bca"
meta-virtualization  = "HEAD:bbc38dc9d6d02e73c08df289bb22a292c2264e9b"
meta-networking      
meta-python          
meta-oe              
meta-gnome           
meta-filesystems     = "HEAD:9b3b907f30b0d5b92d58c7e68289184fda733d3e"
meta-ti              = "HEAD:850d2b608c2d9d4d1c03396cc61e443b364a6b4e"
meta-linaro-toolchain 
meta-optee           = "HEAD:615ea7561b844a3867cee4299d83d605c10b02ab"
meta                 = "HEAD:d3d3f443039b03f1200a14bfe99f985592632018"

Initialising tasks...done.
Sstate summary: Wanted 428 Found 0 Missed 428 Current 2316 (0% match, 84% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 906 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-kernel/linux/linux-ti-staging_4.19.bb:do_fetch)
NOTE: Running task 971 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb:do_fetch)
NOTE: recipe ti-img-rogue-umlibs-1.10.5371573-r0_psdkla: task do_fetch: Started
NOTE: recipe linux-ti-staging-4.19.59+gitAUTOINC+50ceb3c6e7-r0a.arago5_psdkla: task do_fetch: Started
NOTE: Running task 1407 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/cadence-mhdp-fw/cadence-mhdp-fw_git.bb:do_fetch)
NOTE: recipe cadence-mhdp-fw-1.2.15-r0: task do_fetch: Started
NOTE: Running task 1968 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb:do_fetch)
NOTE: Running task 2062 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-linaro/meta-optee/recipes-security/optee/optee-os_git.bb:do_fetch)
NOTE: recipe arm-trusted-firmware-2.1+gitAUTOINC+ce3f1512bf-r0: task do_fetch: Started
NOTE: recipe optee-os-3.6.0+gitAUTOINC+e5a8779a6f-r0.arago0: task do_fetch: Started
NOTE: Running task 2294 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/u-boot/u-boot-ti-staging_2019.01.bb:do_fetch)
NOTE: recipe u-boot-ti-staging-2019.01+gitAUTOINC+a280dd38e1-r23_psdkla: task do_fetch: Started
WARNING: linux-ti-staging-4.19.59+gitAUTOINC+50ceb3c6e7-r0a.arago5_psdkla do_fetch: Failed to fetch URL git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git;protocol=git;branch=ti-linux-4.19.y, attempting MIRRORS if available
WARNING: arm-trusted-firmware-2.1+gitAUTOINC+ce3f1512bf-r0 do_fetch: Failed to fetch URL git://git.ti.com/atf/arm-trusted-firmware.git;branch=ti-atf, attempting MIRRORS if available
WARNING: ti-img-rogue-umlibs-1.10.5371573-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/graphics/ti-img-rogue-umlibs.git;branch=linuxws/thud/k4.19/1.10.5371573, attempting MIRRORS if available
WARNING: cadence-mhdp-fw-1.2.15-r0 do_fetch: Failed to fetch URL git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=ti-linux-firmware, attempting MIRRORS if available
WARNING: optee-os-3.6.0+gitAUTOINC+e5a8779a6f-r0.arago0 do_fetch: Failed to fetch URL git://git.ti.com/optee/ti-optee-os.git;branch=ti-optee-os, attempting MIRRORS if available
WARNING: u-boot-ti-staging-2019.01+gitAUTOINC+a280dd38e1-r23_psdkla do_fetch: Failed to fetch URL git://git.ti.com/ti-u-boot/ti-u-boot.git;protocol=git;branch=ti-u-boot-2019.01, attempting MIRRORS if available
NOTE: recipe ti-img-rogue-umlibs-1.10.5371573-r0_psdkla: task do_fetch: Failed
NOTE: Running task 2373 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-bsp/rpmsg-char-helper/rpmsg-char-helper.bb:do_fetch)
NOTE: recipe rpmsg-char-helper-1.0-r0_psdkla: task do_fetch: Started
WARNING: rpmsg-char-helper-1.0-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/rpmsg-char-helper.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe rpmsg-char-helper-1.0-r0_psdkla: task do_fetch: Failed
NOTE: Running task 2815 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-arago/meta-arago-distro/recipes-bsp/u-boot/u-boot-k3-r5_2019.01.bb:do_fetch)
NOTE: recipe u-boot-k3-r5-2019.01+gitAUTOINC+a280dd38e1-r23_psdkla: task do_fetch: Started
NOTE: recipe optee-os-3.6.0+gitAUTOINC+e5a8779a6f-r0.arago0: task do_fetch: Failed
NOTE: Running task 3011 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb:do_fetch)
NOTE: recipe ti-img-rogue-driver-1.10.5371573-r0a: task do_fetch: Started
NOTE: recipe arm-trusted-firmware-2.1+gitAUTOINC+ce3f1512bf-r0: task do_fetch: Failed
NOTE: Running task 3026 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-arago/meta-arago-distro/recipes-bsp/ti-sci-fw/ti-sci-fw_2019.07.bb:do_fetch)
NOTE: recipe ti-sci-fw-2019.07-r0_psdkla: task do_fetch: Started
WARNING: ti-img-rogue-driver-1.10.5371573-r0a do_fetch: Failed to fetch URL git://git.ti.com/graphics/ti-img-rogue-driver.git;branch=linuxws/thud/k4.19/1.10.5371573, attempting MIRRORS if available
NOTE: recipe ti-img-rogue-driver-1.10.5371573-r0a: task do_fetch: Failed
NOTE: Running task 3234 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-kernel/jailhouse/jailhouse_git.bb:do_fetch)
NOTE: recipe jailhouse-0.10+gitAUTOINC+6dce20f902-r0: task do_fetch: Started
NOTE: recipe u-boot-ti-staging-2019.01+gitAUTOINC+a280dd38e1-r23_psdkla: task do_fetch: Failed
NOTE: Running task 3263 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/cockpit-fw/cockpit-bootstrap-fw_git.bb:do_fetch)
NOTE: recipe cockpit-bootstrap-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla: task do_fetch: Started
WARNING: jailhouse-0.10+gitAUTOINC+6dce20f902-r0 do_fetch: Failed to fetch URL git://git.ti.com/jailhouse/ti-jailhouse.git;protocol=git;branch=ti-jailhouse-0.10, attempting MIRRORS if available
NOTE: recipe jailhouse-0.10+gitAUTOINC+6dce20f902-r0: task do_fetch: Failed
NOTE: Running task 3412 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-arago/meta-arago-extras/recipes-graphics/img-pvr-sdk/img-pvr-sdk_3.3.2.bb:do_fetch)
NOTE: recipe img-pvr-sdk-3.3.2-r16_psdkla: task do_fetch: Started
WARNING: u-boot-k3-r5-2019.01+gitAUTOINC+a280dd38e1-r23_psdkla do_fetch: Failed to fetch URL git://git.ti.com/ti-u-boot/ti-u-boot.git;protocol=git;branch=ti-u-boot-2019.01, attempting MIRRORS if available
WARNING: cockpit-bootstrap-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-cockpit-firmware-binaries.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe cockpit-bootstrap-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla: task do_fetch: Failed
NOTE: Running task 3461 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb:do_fetch)
NOTE: recipe ti-display-sharing-fw-00.09.00.00-gitAUTOINC+4a86f16df9-r0: task do_fetch: Started
WARNING: img-pvr-sdk-3.3.2-r16_psdkla do_fetch: Failed to fetch URL git://git.ti.com/graphics/img-pvr-sdk.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe cadence-mhdp-fw-1.2.15-r0: task do_fetch: Failed
NOTE: Running task 3470 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb:do_fetch)
NOTE: recipe ti-img-encode-decode-1.0.0-r0b: task do_fetch: Started
WARNING: ti-img-encode-decode-1.0.0-r0b do_fetch: Failed to fetch URL git://git.ti.com/jacinto7_multimedia/ti-img-encode-decode.git;protocol=git;branch=master, attempting MIRRORS if available
WARNING: ti-sci-fw-2019.07-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=ti-linux-firmware, attempting MIRRORS if available
NOTE: recipe ti-img-encode-decode-1.0.0-r0b: task do_fetch: Failed
NOTE: Running task 3471 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/ti-img-encode-decode/vxd-dec-fw_git.bb:do_fetch)
NOTE: recipe vxd-dec-fw-1.0-gitAUTOINC+0acbf1d0a7-r0: task do_fetch: Started
WARNING: vxd-dec-fw-1.0-gitAUTOINC+0acbf1d0a7-r0 do_fetch: Failed to fetch URL git://git.ti.com/jacinto7_multimedia/ti-img-encode-decode.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe vxd-dec-fw-1.0-gitAUTOINC+0acbf1d0a7-r0: task do_fetch: Failed
NOTE: recipe u-boot-k3-r5-2019.01+gitAUTOINC+a280dd38e1-r23_psdkla: task do_fetch: Failed
NOTE: Running task 3506 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-ti/recipes-bsp/ti-img-encode-decode/viddec-test-app_1.0.0.bb:do_fetch)
NOTE: Running task 3507 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-openembedded/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.16.0.bb:do_fetch)
NOTE: recipe viddec-test-app-1.0.0-r0: task do_fetch: Started
NOTE: recipe v4l-utils-1.16.99+1.17-rc+gitAUTOINC+9343eaf543-r0: task do_fetch: Started
NOTE: recipe img-pvr-sdk-3.3.2-r16_psdkla: task do_fetch: Failed
NOTE: Running task 3530 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/ti-heartbeat/ti-heartbeat-ivi-vm.bb:do_fetch)
NOTE: recipe ti-heartbeat-ivi-vm-1.0-r0_psdkla: task do_fetch: Started
WARNING: viddec-test-app-1.0.0-r0 do_fetch: Failed to fetch URL git://git.ti.com/jacinto7_multimedia/viddec-test-app.git;protocol=git;branch=master, attempting MIRRORS if available
WARNING: v4l-utils-1.16.99+1.17-rc+gitAUTOINC+9343eaf543-r0 do_fetch: Failed to fetch URL git://linuxtv.org/v4l-utils.git, attempting MIRRORS if available
NOTE: recipe viddec-test-app-1.0.0-r0: task do_fetch: Failed
NOTE: Running task 3532 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/cluster/cluster.bb:do_fetch)
NOTE: recipe cluster-1.0-r0_psdkla: task do_fetch: Started
WARNING: ti-heartbeat-ivi-vm-1.0-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-ivshmem-heartbeart-apps.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe ti-heartbeat-ivi-vm-1.0-r0_psdkla: task do_fetch: Failed
NOTE: Running task 3533 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-arago/meta-arago-extras/recipes-devtools/util-scripts/glsdk-util-scripts.bb:do_fetch)
NOTE: recipe glsdk-util-scripts-1.0-r1_psdkla: task do_fetch: Started
WARNING: cluster-1.0-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-cluster-linux-application.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe cluster-1.0-r0_psdkla: task do_fetch: Failed
NOTE: Running task 3534 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/gateway-fw/gateway-fw_git.bb:do_fetch)
NOTE: recipe gateway-fw-1.0-gitAUTOINC+0fdbe5abaa-r0_psdkla: task do_fetch: Started
NOTE: recipe v4l-utils-1.16.99+1.17-rc+gitAUTOINC+9343eaf543-r0: task do_fetch: Failed
NOTE: Running task 3536 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/gateway-fw/eth-switch-fw_git.bb:do_fetch)
NOTE: recipe eth-switch-fw-1.0-gitAUTOINC+546f79347f-r0_psdkla: task do_fetch: Started
WARNING: glsdk-util-scripts-1.0-r1_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/util-scripts.git, attempting MIRRORS if available
NOTE: recipe ti-sci-fw-2019.07-r0_psdkla: task do_fetch: Failed
NOTE: Running task 3537 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/cockpit-fw/cockpit-can-fw_git.bb:do_fetch)
NOTE: recipe cockpit-can-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla: task do_fetch: Started
WARNING: gateway-fw-1.0-gitAUTOINC+0fdbe5abaa-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-eth-fw.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe gateway-fw-1.0-gitAUTOINC+0fdbe5abaa-r0_psdkla: task do_fetch: Failed
NOTE: Running task 3540 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/ti-heartbeat/ti-heartbeat-cluster-vm.bb:do_fetch)
NOTE: recipe ti-heartbeat-cluster-vm-1.0-r0_psdkla: task do_fetch: Started
NOTE: recipe glsdk-util-scripts-1.0-r1_psdkla: task do_fetch: Failed
NOTE: Running task 3541 of 7722 (/home/u20470/ti/j7/ti-processor-sdk-linux-automotive-j7-evm-06_00_01_00/yocto-build/sources/meta-psdkla/recipes-benchmark/cockpit-fw/cockpit-fw_git.bb:do_fetch)
NOTE: recipe cockpit-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla: task do_fetch: Started
WARNING: ti-display-sharing-fw-00.09.00.00-gitAUTOINC+4a86f16df9-r0 do_fetch: Failed to fetch URL git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=ti-linux-firmware, attempting MIRRORS if available
WARNING: cockpit-can-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-cockpit-firmware-binaries.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe cockpit-can-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla: task do_fetch: Failed
WARNING: ti-heartbeat-cluster-vm-1.0-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-ivshmem-heartbeart-apps.git;protocol=git;branch=master, attempting MIRRORS if available
WARNING: eth-switch-fw-1.0-gitAUTOINC+546f79347f-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-eth-fw.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe ti-heartbeat-cluster-vm-1.0-r0_psdkla: task do_fetch: Failed
NOTE: recipe eth-switch-fw-1.0-gitAUTOINC+546f79347f-r0_psdkla: task do_fetch: Failed
WARNING: cockpit-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla do_fetch: Failed to fetch URL git://git.ti.com/glsdk/ti-cockpit-firmware-binaries.git;protocol=git;branch=master, attempting MIRRORS if available
NOTE: recipe cockpit-fw-1.0-gitAUTOINC+60fec9c5b4-r0_psdkla: task do_fetch: Failed
NOTE: recipe ti-display-sharing-fw-00.09.00.00-gitAUTOINC+4a86f16df9-r0: task do_fetch: Failed

  1. After recording the Linux image provided by TI and trying to run the board from the uSD card, they were stuck at “Waiting for root device PARTUUID=dd8d2221-02...”. They have changed the Device Tree configuration in uEnv.txt file to:

overlay_files=

fdtfile=k3-j721e-proc-board-beta.dtb

and only after that they were able to boot to desktop.

Can you give them some further details (other than the ones contained in TI docs at docs/linux/How_to_Guides_Target.html#how-to-change-dtb-and-dtbo-files) on which device tree to choose if they want to utilize things like the CAN interface(s)?

  1. Finally, they were wondering what are the possibilities for running two systems simultaneously on TDA4 – a POSIX OS at performance side and a safety OS on safety side? Is that possible? What config is required in terms of flash memory (MMC card) for that?

  • 0
    TI__Guru** 113810 points

    Answers below:

    1.  This certainly looks like a proxy issue (although it has been reported that they are not using any firewalls or proxies). I would like the customer to do two things : a) Try to clone the repo by using the command "git clone git://git.ti.com/glsdk/ti-cockpit-firmware-binaries.git" if this is  unsuccessful then it is a proxy settings issue. Else if this is successful then rerun the Yocto build and share the do_fetch log of a particular failure, we will need to analyze this further.

    2. It seems like the customer has the Beta board in possession and therefore it was required to change the uenv.txt. This is documented in the Release Notes. The prebuilt binaries support Alpha boards by default.

    3. Yes, it is possible to run the requested configuration (Posix OS + Safety OS). The default SDK images already runs Linux on the A72 cores and the TI-RTOS on the R5F cores. This can be replaced by any other OS that is required. There is no special configuration required from MMC card etc. But may be I don't understand this part of the question and will need to be explained for further discussions.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1055 points

    Hi Karthik,

    1. Indeed, we concluded that the information about usage of external network was misleading (different setup than expected) and it is happening due to our proxy/firewall config.

    2. Thanks for confirming this. Still I would like to know which Device Tree Overlay is to be used for usage of CAN interface.

    3. To our knowledge, when we have run Linux image from TI - both of the systems present there (Linux+RTOS) are running on the performance side. The TI-RTOS does not run on safety cores in that setup.

    The question is then - how to run Linux on performance side of the SoC and simultaneously have the TI-RTOS on the safety part?

    Regards,

    Piotr 

  • 0 in reply to Piotr Cerba
    TI__Guru** 113810 points

    Hi Piotr,

    Regarding 2: This depends on the board that you have, this is documented in processor-sdk-linux-docs/docs/linux/How_to_Guides_Target.html#uenv-txt-options

    This has information on the uenv.txt that needs to be used along with the DTB and the overlay files.

    3. Yes, you make a good point. I verified this, there are no firmware binaries that actually are running on the safety MCUs in the current Linux SDK context.

    However, this can be achieved with some changes. Are you looking for this? May be we can provide you with some instructions on how this can be achieved.

    Regards
    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1055 points

    Hi Karthik,

    Ad. 2 - thanks, when I have further questions about those Device Tree configs I will create new topic.

    Ad. 3 - we will be very interested in how to achieve this (bootloader config, etc.)

    Regards,

    Peter

  • 0 in reply to Piotr Cerba
    TI__Guru** 113810 points

    Hi Peter,

    About 3 - thanks for confirming.

    This would require some additional work and I will try to provide an update for you before next Tuesday.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    TI__Genius 9905 points

    Hi Peter,

    The Processor SDK Linux Automotive release does not include any IPC example for running on MCU R5.

    However, you can build and install the ipc-lld-fw package using yocto.

    Note that these binaries use a memory map which is different from the automotive binaries. So make sure to not apply the auto-common.dtbo

    Regards,

    Nikhil D

  • 0 in reply to Karthik Ramanan
    Prodigy 40 points

    Hello Karthik,

    we are facing the same issue that was explained in point number two from our colleagues but just changing the uenv.txt file an the DTO doesn't do it for us. I want to discuss/know a two points here:

    1. How can I check if I'm using an alpha or beta board? What is the exact difference?

    2. In case we have an beta board: Where can I find the documentation on how to get this board running with Linux (we just have documentation for the alpha board)? Do we just have to download the new DTB, copy this to the pre flashed sd card and change the uenv.txt to convert an alpha compatible sd card image to an beta one?
    Do we miss something here? Because we are now getting the kernel panics after changing the uenv.txt file.

  • 0 in reply to Lukas Dudichum
    TI__Guru** 113810 points

    Hi Lukas,

    1. You can check the difference between Alpha and Beta EVM by two methods :
      1. Physical inspection - you will notice a sticker called Interim PMIC on the Alpha board and this will not be present on the Beta EVM 
      2. u-boot will present the Board information from the EEPROM - on the Alpha EVM this will read as "Board: J721EX-PM1-SOM" whereas on the Beta EVM this will read as "Board J721EX-PM2-SOM"
    2. Beta EVM is supported only from SDK release 06.00.01.00
      1. There is an updated release on the mySecureSoftware – the release number is 06.00.01.00.
      2. Request you to download this SDK and the corresponding documentation (which is a separate tar ball).
      3. The SDK documentation contains a section that has detailed instructions to use the same SDK with both Alpha and Beta EVM. processor-sdk-linux-docs/docs/linux/How_to_Guides_Target.html#uenv-txt-options. Please note that this is only supported with 06.00.01.00 release.

    Regards

    Karthik