• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 236 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.

TDA4VM: How to get started developing R5F?

Cherry Zhou
Mastermind 22235 points
Part Number: TDA4VM
Other Parts Discussed in Thread: SYSCONFIG, SYSBIOS

Hi team,

SDK: Processor SDK RTOS J721E 08_06_01

There is no problem with build and Run to flash to the micro SD card using Video Apps previously.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/vision_apps/docs/user_guide/BUILD_AND_RUN.html

1) Does the current SDK RTOS primarily want to use make to build bin files for co-processes development? If the customer want to develop Main Domain - R5F, just to modify the demo code directly to speed up the development process? As shown below "platform/${SOC}/rtos", or which path needs to be developed first? 

2) Should Video Apps be the primary development principal architecture location? To develop MCUSW, is it required to port relevant information to Video Apps? Or use the bin developed by MCUSW to put in Video Apps? 

3) CCS is primarily used as a debug tool? Each coprocessor can be created in CCS and the entire chip can be configured in sysconfig. But the RTOS is not available since it required to import other SDK? 

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j721e.html#debugging-without-hlos-running-on-a72-rtos-only-baremetal

4) Is it recommended to review the documentation for the MCU side development process first? 

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Mastermind 38525 points

    Hello,

    Vision Apps is a frame work developed which integrates different components within Processor SDK RTOS (PSDK RTOS) like SysBIOS, PDK, OpenVX, Algorithms to realize system applications for vision processing like surround view, auto park assist.

    Customer can develop their own frame work if required and use accordingly. MCUSW is not integrated as part of vision apps. If customer want to use Vision Apps and require MCUSW , he has to integrate it.

    Yes CCS is a debug tool. Only resources like DMA,Interrupts etc..can be configured in sysconfig. Please look into section 

    6.3.2. Step 3: Load RTOS/baremetal application binaries thru CCS .

    What exactly is the requirement of customer here I couldn't understand. Please mention it clearly.

    Thanks

    Tarun Mukesh

     

  • 0 in reply to Tarun Mukesh Puvvada
    TI__Mastermind 22235 points

    Hi Tarun,

    Thank you for the support.

    Is the general development process including the following 3 steps? 

    1) Develop coprocesses directly at /ti-processor-SDK-RTOS-j721e-EVM-08_06_01_03/vision_apps/platform/j721e/RTOS/ to develop the corresponding process (modify or add new code).

    2) After modification or addition, you need to execute ./make_SDK.sh under /ti-processor-SDK-RTOS-j721e-EVM-08_06_01_03/vision_apps/.

    3) Finally make Linux_FS_install_SD flash into USD card. 

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 38525 points

    Yes all the steps mentioned are correct for other cores.

    If you are doing for MCU1_0 , you have enable Macros at  below paths

    1)  ti-processor-sdk-rtos-j721e-evm-08_06_01_03/vision_apps/vision_apps_build_flags.mak

          BUILD_CPU_MCU1_0?=yes

    2)ti-processor-sdk-rtos-j721e-evm-08_06_01_03/vision_apps/platform/j721e/rtos/common/app_cfg.h

       #define ENABLE_IPC_MCU1_0

    Regards

    Tarun Mukesh