• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 116 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.

DRA829J: SDK Setup for MCUs

Jose Daniel Ambrocio
Prodigy 30 points

Part Number: DRA829J

Hello TI team,

We are working on a device using the DRA829J SoC mainly in the R5 cores. In our software development environment, we created a common setup of the SDK, that is, we use the same RTOS SDK setup for MCU1_0 and MAIN domain cores. We basically downloaded the SDK from TI website and configured with the following script and options:

./setup_psdk_rtos.sh --firmware_only --skip_pc_emulation --skip_atf_optee 

and edited the Rules.make file to update TOOLS_INSTALL_PATH.

Then whenever we need to compile the dependencies, we do it per core:

make -j$(nproc) -C $SDK_RTOS_J721E_PATH/ti-processor-sdk-rtos-j721e-evm-10_01_00_04/pdk_jacinto_10_01_00_25/packages/ti/build -s pdk_libs BOARD=j721e_evm CORE=$CORE_NAME

where CORE_NAME can be mcu1_0, mcu2_0, mcu2_1, mcu3_0, mcu3_1

Once dependencies are generated we can compile our applications and link them with the SDK libraries. This process has worked good. However, we started to include the vision apps but the instructions mention to use the sdk builder script. In the official TI documentation, every time I click on sdk builder guideline it always send me to the vision apps page. I assume that this script is needed only for vision apps compilation. The build_flags and other makes in the sdk_builder folder seems to be specific for vision apps.

My point is that using sdk_builder the other cores are impacted because seems that the folders and other SDK variables are modified and compilation does not work. It's mandatory to use the sdk builder to build vision apps? or can we just go directly to the vision apps to compile as standalone library? 

  • 0
    Prodigy 30 points

    I forgot to mention that we are including vision apps in the MCU2_0 core

  • 0 in reply to Jose Daniel Ambrocio
    TI__Mastermind 20410 points

    Hi Jose,

    It is recommended to build vision_apps using sdk_builder as it builds all the necessary libraries and the entire vision_apps libraries and remote core firmwares.

    you can also build specific application or firmwares/libraries by going inside vision_apps. which part you want to build specifically in vision_apps ?

    And can you describe more about your application ? Refer to this docs for more details.

    FYI, DRA829J does not have VPAC (ISP) so some features will not be supported from vision_apps.

    Regards,
    Gokul

  • 0
    Prodigy 30 points

    Thanks for the reply Gokul. The main goal is to use our application to capture images using two cameras. We are using the app_multi_cam demo as base. When doing the setup for vision apps compilation I observed that Linux toolchain is downloaded, I assume this is done in order to compile a demo app to be executed in Linux, correct? just for the demo app. For our application I assume we dont need the Linux toolchain as we are compiling only for MCU2_0.

    Can you provide the procedure to compile the vision apps as standalone library and point which dependencies should be compiled first (such as ethernet, pdk, etc)?

    My point here is to avoid any unnecessary setup dont needed to build our R5 application and just take what we need.

    Regards,

    Jose Ambrocio

  • 0 in reply to Jose Daniel Ambrocio
    TI__Mastermind 20410 points

    Hi Jose,

    Jose Daniel Ambrocio said:
    I assume this is done in order to compile a demo app to be executed in Linux, correct?

    It is needed for demos and if you are planning to use tiovx in your application then it is required. Because tiovx uses a72 as host and you will be needing linux toolchains to build your application.

    Jose Daniel Ambrocio said:
    I assume we dont need the Linux toolchain as we are compiling only for MCU2_0.

    It depends on what type of application are you building. As i mentioned if you building application from vision_apps as example then you will need those toolchains.

    Regards,
    Gokul