• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 2 answers
  • Subscribers 102 subscribers
  • Views 528 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Problem with first install of SK-TDA4VM

Sagi Sheer
Prodigy 70 points
Part Number: SK-TDA4VM
Other Parts Discussed in Thread: TDA4VM

Hi,

I am using TDA4VM processor starter kit for Edge AI vision systems for the first time.

I am using the getting started guide in the following link:

software-dl.ti.com/.../getting_started.html

When I am running the command to install dependencies (./setup_script.sh) I get some errors.

I attach here a print screen of the problem:

What is the problem? How can I fix it?

Thanks,

Sagi

  • 0
    TI__Mastermind 25380 points

    Hi Sagi,

    I was able to reproduce the following issue:

    cc1: error: /usr/include/processor_sdk/imaging/algos/ae/include/: No such file or directory [-Werror=missing-include-dirs]
    cc1: error: /usr/include/processor_sdk/imaging/algos/awb/include/: No such file or directory [-Werror=missing-include-dirs]
    cc1: error: /usr/include/processor_sdk/imaging/ti_2a_wrapper/include/: No such file or directory [-Werror=missing-include-dirs]
    cc1: all warnings being treated as errors

    It seems like changes to the build dependencies had been updated on the Edge AI SDK application level, but not in the underlying Linux+RTOS PSDK level.

    As a workaround, please revert to an older commit for the Edge AI SDK application level by doing the following:

    • cd /opt/edgeai-gst-plugins/
    • git checkout 60960c3011ba5550cba3f70b379125c2286dce9e
    • Rerun the ./setup_scripts command

    I will let the team know about this issue.

    Regards,

    Takuma

  • 0 in reply to Takuma Fujiwara
    TI__Mastermind 25380 points

    Hello,

    The fix for this issue has been implemented in SDK 8.1. 

    Regards,

    Takuma