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.

  • Resolved

Compiler/TDA2PXEVM: Not able compile sources for A15 core alone.

Intellectual 410 points

Replies: 32

Views: 691

Part Number: TDA2PXEVM

Tool/software: TI C/C++ Compiler

Hi,

 I was not able to compile my sample sources file which is part of an Vision_SDK module for A15 core.

Changes Made:

  1. As Posix support is only there for A15 core added
    var Settings = xdc.useModule('ti.sysbios.posix.Settings');
    Settings.supportsMutexPriority = true;

    in links_fw/src/rtos/bios_app_common/tda2px/a15_0/a15_0.cfg file.
  2. Made "PROC_A15_0_INCLUDE=yes" under "cfg.mk" file in source/vision/platform/ti/tda2/apps/configs/MakeConfig directory
  3. Made the changes under SRC_FILES.MK fie “SRCS_a15_0 += Sample.c

 

With the above changes in place I do see the Sample.c file is not getting compiled.

 

By reverting the changes under SRC_FILES.MK file to “SRCS_IPU1_0 += Sample.c” the source file is being compiled.

 Could you please let me know what other changes to be made to get the sources compiled for SRCS_a15_0 ?

 

  • Hi Ramesh,

    Are you building OpenCV? What is the MAKECONFIG you are using?

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    Hi Rishabh,

    I am not building an OpenCV.
    To be more precise, I am trying to build an sample application under module section which will be using POSIX related headers and features.
    In turn I will be making a call to module layer from Usecase section.

    To make it simple I created a module by name Sample under module section and tried to compile the source file with below tag. "SRCS_a15_0 += Sample.c"

    Made sure to include SRC_FILES.MK file under "source/vision/platform/ti/tda2/apps/Makefile".

    Coming to MAKEConfig we have created a new configuration by referring to "tda2px_evm_bios_all" and cfg.mk file varies by minute difference(like change in VSDK_BOARD_TYPE ) and uc_cfg.mk has got all the required usecase are set to Yes as per need(per configuration selection)
  • In reply to Ramesh Pradeep Kundati:

    Hi Ramesh,

    tda2px_evm_bios_all is already defined as MAKECONFIG. Can you use a new name?
    I would suggest you to talk with Abhay Sorte/Amol Kulkarni from your company who have been working on VSDK for more than an year now.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    HI Rishabh,

    I meant cfg.mk files are been copied/updated by referring to "tda2px_evm_bios_all" directory under config folder.
    The MAKECONFIG in my case is "harman_proto_A_bios" which uses VISION SDK BOARD TYPE to "HARMAN_TDA2PX_PROTO_A".

    I got to know that Amol is no more working for Harman.
    Please let me know if you need more details about the query.
  • In reply to Ramesh Pradeep Kundati:

    Hi Ramesh,

    Can you provide full path to "source/vision/platform/ti/tda2/apps/configs/MakeConfig" directory you have referred to in your question.
    Also Abhay is still working with your company so you might want to check with him on this.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    Hi Rishabh,

    This is the complete directory path were MakeConfig(harman_proto_A_bios) refers to:

    /opt/V_SDK/FFC/FFC_WORKSPACE/source/vision/platform/ti/tda2/apps/configs/harman_proto_A_bios

    FFC_WORKSPACE is the directory were in we have synced code.

  • In reply to Ramesh Pradeep Kundati:

    Hi Ramesh,

    It seems that you have a different build system.
    I am not aware of Harman's project and directory structure.
    Please ask TI FAEs for further help on this.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    Hi Rishabh,

    On the other hand I have got couple of question regarding porting Linux Application on to Vision SDK framework for which I request you to provide your inputs on it.

    1. We have got an Linux application say Sample(which is designed and working for Linux platform) which is not complete POSIX compliant but has got support for most of the POSIX features in it. Namely
    • Pthread,
    • Semphores,
    • Sockets,
    • FileSystem calls
      • File(OPEN …), Directory(MKDIR…) and Link(UNLINK..) operations
      • Basic(CHMOD,UMASK…) file attributes
      • File descriptor(FCNTL..) manipulations
      • Read/Write(READ,WIRTE..) operations
      • Synchronized(SYNC,FSYNC..), Asynchronous(IO_SETUP,IO_DESTROY..) and Multiplexed(SELECT,EPOLL…) I/O
      • Monitoring(INOTIFY_INIT) file events and
      • FIFO(mkfifo..) operations
    • IPC communications(Shared memory).

     

    As SYBIOS provides pthread support for A15 core and also NDK(Yet to explore) is built for A15 we were trying to compile/build our Linux application(Sample) for A15 core alone on Vision SDK framework.

    Are we on the right direction? Do you foresee any issues with it?

    Recent conversation with TI Engineer states we need to Port Linux on to A15 core? Does it mean porting complete Linux platform on to A15 core and post to which we should start porting our Sample on to A15?

           As mentioned Linux application Sample has got FileSystem calls in place. Do we have support for FileSystem on SYSBIOS? If So, how could we make use of it or do we need to look for corresponding alternatives in it?

    1. And Sample being the server component, there are the other application which communicates to Sample via Sockets or through PIPES or any file based operations. Being Sample built for A15 core, does the other applications which has to communicate to Sample should also be built for A15?

    Request you to pour in your inputs/thoughts on it.

  • In reply to Ramesh Pradeep Kundati:

    Hi Ramesh,

    This thread is regarding the Vision SDK build issue.
    TI engineer will get in touch with you early next week to help you on the same.
    Kindly post questions on any other topic in a new thread.

    Regards,
    Rishabh
  • In reply to Ramesh Pradeep Kundati:

    Hi Ramesh,

    Please find your answer below

    We have got an Linux application say Sample(which is designed and working for Linux platform) which is not complete POSIX compliant but has got support for most of the POSIX features in it. Namely
    ------> If whatever is Supported by POSIX and FATFS filesystem with linux is Supported for VSDK running linux on A15 also.

    Are we on the right direction? Do you foresee any issues with it?
    -----> As of now i can not see any issue.

    Recent conversation with TI Engineer states we need to Port Linux on to A15 core? Does it mean porting complete Linux platform on to A15 core and post to which we should start porting our Sample on to A15?
    ------->Please refer to the linux userguide available with VSDK.

    As mentioned Linux application Sample has got FileSystem calls in place. Do we have support for FileSystem on SYSBIOS? If So, how could we make use of it or do we need to look for corresponding alternatives in it?
    ------->If A15 runs linux then all the control will be provided to linux only so sysbios will not be controlling filesystem.

    And Sample being the server component, there are the other application which communicates to Sample via Sockets or through PIPES or any file based operations. Being Sample built for A15 core, does the other applications which has to communicate to Sample should also be built for A15?
    ----> If the other compnonent uses filesystem calls or socket or anything related to linix then it should be running on A15 only.
    If you want to run it on other cores then you can use IPC communication but you will not be able to use socket.

    Regards,
    Anuj

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.