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.

SK-TDA4VM: Are WIC files part of the build? boot image for an SD card

Part Number: SK-TDA4VM


Hi I've run the build for the ti edgeai image. In the < ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/deploy/images/j7-evm>

folder I don't see the WIC file.   What files do I need from this folder to make an SD card boot image?

cheers,

Adam

  • Hi Adam,

    The WIC file for SK-TDA4VM can be found here: PROCESSOR-SDK-LINUX-SK-TDA4VM Software development kit (SDK) | TI.com

    Software setup steps for this device are outlined here: 2. Getting Started — Processor SDK Linux for SK-TDA4VM Documentation

    I hope this answered your question.

    Thank you,

    Fabiana Jaimes

  • Hi Fabiana,

    this is not what i'm looking for. 

    I'm looking for how to do either of the following after a build:

    1. Create a WIC file from the new build to program the SD card.

    or

    2. How to create an SD card image from the new build. I don't know what files to load on the the SD card for boot.

  • Any update on the above question?

  • I think this is what i'm looking for

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1165229/tda4vm-yocto-generated-output-did-not-boot-up-the-board-no-traces-visible-in-the-console-to-diagnose/4382388?tisearch=e2e-sitesearch&keymatch=generate%252520wic#4382388

    #####

    After that created the bootable SD card with below command

    unxz ./tisdk-bootstrap-base-image-j721s2-evm-20221021080513.rootfs.wic.xz  

    sudo dd if=./tisdk-bootstrap-base-image-j721s2-evm-20221021080513.rootfs.wic of=/dev/sda bs=4M status=progress && sync

    ######

  • Hi Adam,

    Apologies for the delayed response. Yes, that is correct.

    Thank you,

    Fabiana

  • I see part of the problem. I don't have any rootfs.wic.xz files in my deploy/images/j7-evm folder.

    1. Is this a build issue?

    or 

    2. is there something that needs to be enabled?

    or

    3. Am I in the wrong folder?

    [linux-devkit]:~/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/deploy/images/j7-evm> ls
    bl31.bin
    bl31.bin.unsigned
    bl31.elf
    bl31-k3.bin
    bl31-k3.elf
    bl32.bin
    bl32.bin.unsigned
    bl32.elf
    fitImage
    fitImage--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.bin
    fitImage-its--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.its
    fitImage-its.its
    fitImage-its-j7-evm.its
    fitImage-j7-evm.bin
    fitImage-linux.bin--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.itb
    fitImage-linux.bin.itb
    fitImage-linux.bin-j7-evm.itb
    Image
    Image--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.bin
    Image-j7-evm.bin
    k3-j721e-common-proc-board--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtb
    k3-j721e-common-proc-board.dtb
    k3-j721e-common-proc-board-infotainment--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-common-proc-board-infotainment.dtbo
    k3-j721e-common-proc-board-infotainment-j7-evm.dtbo
    k3-j721e-common-proc-board-j7-evm.dtb
    k3-j721e-cpb-csi2-ov5640--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-cpb-csi2-ov5640.dtbo
    k3-j721e-cpb-csi2-ov5640-j7-evm.dtbo
    k3-j721e-edgeai-apps--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-edgeai-apps.dtbo
    k3-j721e-edgeai-apps-j7-evm.dtbo
    k3-j721e-fpdlink-cpb-fusion--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-cpb-fusion.dtbo
    k3-j721e-fpdlink-cpb-fusion-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-0-0--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-0-0.dtbo
    k3-j721e-fpdlink-imx390-cm-0-0-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-0-1--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-0-1.dtbo
    k3-j721e-fpdlink-imx390-cm-0-1-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-0-2--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-0-2.dtbo
    k3-j721e-fpdlink-imx390-cm-0-2-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-0-3--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-0-3.dtbo
    k3-j721e-fpdlink-imx390-cm-0-3-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-1-0--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-1-0.dtbo
    k3-j721e-fpdlink-imx390-cm-1-0-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-1-1--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-1-1.dtbo
    k3-j721e-fpdlink-imx390-cm-1-1-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-1-2--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-1-2.dtbo
    k3-j721e-fpdlink-imx390-cm-1-2-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-cm-1-3--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-cm-1-3.dtbo
    k3-j721e-fpdlink-imx390-cm-1-3-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-0--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-0.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-0-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-1--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-1.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-1-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-2--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-2.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-2-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-3--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-3.dtbo
    k3-j721e-fpdlink-imx390-rcm-0-3-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-0--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-0.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-0-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-1--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-1.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-1-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-2--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-2.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-2-j7-evm.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-3--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-3.dtbo
    k3-j721e-fpdlink-imx390-rcm-1-3-j7-evm.dtbo
    k3-j721e-fpdlink-sk-fusion--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-fpdlink-sk-fusion.dtbo
    k3-j721e-fpdlink-sk-fusion-j7-evm.dtbo
    k3-j721e-proc-board-tps65917--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtb
    k3-j721e-proc-board-tps65917.dtb
    k3-j721e-proc-board-tps65917-j7-evm.dtb
    k3-j721e-sk--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtb
    k3-j721e-sk-csi2-ov5640--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-sk-csi2-ov5640.dtbo
    k3-j721e-sk-csi2-ov5640-j7-evm.dtbo
    k3-j721e-sk.dtb
    k3-j721e-sk-j7-evm.dtb
    k3-j721e-sk-rpi-cam-imx219--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-sk-rpi-cam-imx219.dtbo
    k3-j721e-sk-rpi-cam-imx219-j7-evm.dtbo
    k3-j721e-sk-rpi-hdr-ehrpwm--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-sk-rpi-hdr-ehrpwm.dtbo
    k3-j721e-sk-rpi-hdr-ehrpwm-j7-evm.dtbo
    k3-j721e-vision-apps--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.dtbo
    k3-j721e-vision-apps.dtbo
    k3-j721e-vision-apps-j7-evm.dtbo
    modules--5.10.162+gitAUTOINC+76b3e88d56-r0b.arago5_psdkla_97.4.0-j7-evm-20230726173447.tgz
    modules-j7-evm.tgz
    optee
    tispl.bin
    tispl.bin-j7-evm
    tispl.bin-j7-evm-2021.01+gitAUTOINC+62a9e51344-r33_psdkla_20
    u-boot.img
    u-boot-j7-evm-2021.01+gitAUTOINC+62a9e51344-r33_psdkla_20.img
    u-boot-j7-evm.img
    u-boot-spl.bin
    u-boot-spl.bin-j7-evm
    u-boot-spl.bin-j7-evm-2021.01+gitAUTOINC+62a9e51344-r33_psdkla_20
    [linux-devkit]:~/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/deploy/images/j7-evm>

  • Hi Adam,

    Which SDK instructions have you been following? For the device you are using, please follow this doc to ensure that you are setting up the layers properly and building for the right target: 1.2. Building the SDK with Yocto — Processor SDK Linux for J721e Documentation

    Thank you,

    Fabiana

  • yup following that one. Do see some errors during build. Currently working on this one.

    ERROR: ti-tisdk-firmware-1.0-r8 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="3745"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/sources/oe-core/scripts:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/bin/aarch64-linux:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot/usr/bin/crossscripts:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/sbin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/bin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/sbin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/bin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/linux-devkit/sysroots/x86_64-arago-linux/usr/bin//gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/sources/bitbake/bin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/hosttools"; export HOME="/home/addupuis"; /usr/bin/env repo init -m vision_apps_yocto.xml -b refs/tags/REL.PSDK.JACINTO.08.06.00.08 -u git://git.ti.com/processor-sdk/psdk_repo_manifests.git failed with exit code 1, output:

    Downloading Repo source from https://gerrit.googlesource.com/git-repo

     

    fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle

    fatal: error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)

    fatal: double check your --repo-rev setting.

    fatal: cloning the git-repo repository failed, will remove '.repo/repo'

  • Hi Adam,

    Apologies for the delayed response. Are you working behind a network proxy?

    Thanks,

    Fabiana

  • I was out on vacation. I've set the build machine up at my home to help avoid any corporate firewall/proxy issues... So no i'm not... I'm hoping to have more time this week to look at it with some internal experts.

  • Hi Adam,

    To chime in, I also recently saw a similar error log on my PC when running repo init. I tried a couple of things and setting this environment variable worked for me:

    export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt

    However, I also ran a couple of other commands like sudo apt-get install ca-certificates and sudo update-ca-certificates, so I am not quite sure if setting this environment variable was enough, or whether it was a combination of installing the latest ca-certificates through apt and then explicitly pointing SSL to use the new certificate. Reason being, after running update-ca-certificates again with this environment variable set, I can no longer reproduce the error logs.

    Could you try setting this environment variable and see if that resolves the error message?

    Regards,

    Takuma

  • It may have worked... but still exploring. I don't see that specific error anymore however it required me to also use   git config --global http.sslverify "false". 

    The error that I'm working on now is:

    ERROR: ti-tisdk-firmware-1.0-r8 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="3745"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/addupuis/yocto-build/sources/oe-core/scripts:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/bin/aarch64-linux:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot/usr/bin/crossscripts:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/sbin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/bin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/sbin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/bin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/linux-devkit/sysroots/x86_64-arago-linux/usr/bin//gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin:/home/addupuis/yocto-build/sources/bitbake/bin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/hosttools"; export HOME="/home/addupuis"; /usr/bin/env repo sync failed with exit code 1, output:
    error: command 'sync' requires repo to be installed first.
    Use "repo init" to install it here.

    ERROR: ti-tisdk-firmware-1.0-r8 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'repo://git.ti.com/processor-sdk/psdk_repo_manifests.git;protocol=git;branch=refs/tags/REL.PSDK.JACINTO.08.06.00.08;manifest=vision_apps_yocto.xml')
    ERROR: Logfile of failure stored in: /home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/temp/log.do_fetch.1563115
    ERROR: Task (/home/addupuis/yocto-build/sources/meta-psdkla/recipes-tisdk/ti-tisdk-firmware/ti-tisdk-firmware.bb:do_fetch) failed with exit code '1'

    looks to be because of 

    error: command 'sync' requires repo to be installed first.
    Use "repo init" to install it here.

  • Nope does work and I'm back to the original error with repo...

    ERROR: ti-tisdk-firmware-1.0-r8 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="3745"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/addupuis/yocto-build/sources/oe-core/scripts:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/bin/aarch64-linux:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot/usr/bin/crossscripts:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/sbin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/bin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/sbin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/bin:/home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/linux-devkit/sysroots/x86_64-arago-linux/usr/bin//gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin:/home/addupuis/yocto-build/sources/bitbake/bin:/home/addupuis/yocto-build/build/arago-tmp-external-arm-glibc/hosttools"; export HOME="/home/addupuis"; /usr/bin/env repo init -m vision_apps_yocto.xml -b refs/tags/REL.PSDK.JACINTO.08.06.00.08 -u git://git.ti.com/processor-sdk/psdk_repo_manifests.git failed with exit code 1, output:
    Downloading Repo source from gerrit.googlesource.com/git-repo

    fatal: Cannot get gerrit.googlesource.com/.../clone.bundle
    fatal: error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)
    fatal: double check your --repo-rev setting.
    fatal: cloning the git-repo repository failed, will remove '.repo/repo'

  • Hi Adam,

    I have a few ideas for what might be happening. Could you try the following experiments out:

    1. For the SSL error that started popping up again, could you run "echo $SSL_CERT_FILE" to check if this environment variable is set? Running export SSL_CERT_FILE in the terminal only sets the environment variable for that particular terminal session, so closing out the terminal would unset the variable. If you would like for it to automatically be set, then editing the ~/.bashrc would make it so that the export command runs every time a new terminal is started. I suspect the reason why it is popping up again is because the variable is unset.
    2. For the second error about the sync, could you run the following two commands without bitbake to verify that repo can be installed outside of bitbake?
      1st command: /usr/bin/env repo init -m vision_apps_yocto.xml -b refs/tags/REL.PSDK.JACINTO.08.06.00.08 -u git://git.ti.com/processor-sdk/psdk_repo_manifests.git
      and
      2nd command: /usr/bin/env repo sync

    My suspicion for the second error about the sync, since bitbake errored out during repo init for the first run it might have left the bitbake process in a bad state. And later when the issue was resolved it resumed from the bad state and did not initialize the repo completely which would in turn fail repo sync.

    Therefore, manually installing the repo using the bolded commands above in my second point, or cleaning out the build after verifying that the above commands can be manually ran successfully individually and rebuilding would be my recommendation (although, rebuilding would probably be much longer than manually trying to run the repo init command).

    Regards,

    Takuma

  • 1. [linux-devkit]:~/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build> echo $SSL_CERT_FILE

    /etc/ssl/certs/ca-certificates.crt

    2. I get the following:

    [linux-devkit]:~/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build> /usr/bin/env repo init -m vision_apps_yocto.xml -b refs/tags/REL.PSDK.JACINTO.08.06.00.08 -u git://git.ti.com/processor-sdk/psdk_repo_manifests.git

    ... A new version of repo (2.35) is available.
    ... New version is available at: /home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/.repo/repo/repo
    ... The launcher is run from: /usr/bin/repo
    !!! The launcher is not writable. Please talk to your sysadmin or distro
    !!! to get an update installed.

    repo: reusing existing repo client checkout in /home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build

    repo has been initialized in /home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build
    [linux-devkit]:~/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build>

    2. 

    [linux-devkit]:~/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build> /usr/bin/env repo sync

    ... A new version of repo (2.35) is available.
    ... New version is available at: /home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/.repo/repo/repo
    ... The launcher is run from: /usr/bin/repo
    !!! The launcher is not writable. Please talk to your sysadmin or distro
    !!! to get an update installed.

    Fetching: 100% (10/10), done in 1m20.838s
    imaging/concerto: Shared project processor-sdk/concerto found, disabling pruning.
    ti-perception-toolkit/concerto: Shared project processor-sdk/concerto found, disabling pruning.
    tiovx/concerto: Shared project processor-sdk/concerto found, disabling pruning.
    vision_apps/concerto: Shared project processor-sdk/concerto found, disabling pruning.
    Checking out: 100% (10/10), done in 3.659s
    repo sync has finished successfully.
    [linux-devkit]:~/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build>

  • running those commands seem to have helped. but now it get the following and more but i've cut it short. 

    how do i upgrade the repo to 2.35? 

    failed with exit code 1, output:

    ... A new version of repo (2.35) is available.
    ... You should upgrade soon:
    cp /home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/.repo/repo/repo /home/addupuis/ti-processor-sdk-linux-j7-evm-08_06_01_03/yocto-build/build/arago-tmp-external-arm-glibc/work/aarch64-linux/ti-tisdk-firmware/1.0-r8/recipe-sysroot-native/usr/bin/repo

  • Hi Adam,

    Could you run the cp command from that log and see if that resolves the error?

    Regards,

    Takuma

  • oops missed this post. Guess during the maintenance window didn't get notified. Ok will try.