• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 390 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.

PROCESSOR-SDK-TDAX: [TDA4M] What need files for running apps?

Heechang Kim1
Prodigy 230 points
Part Number: PROCESSOR-SDK-TDAX
Other Parts Discussed in Thread: TDA2, SYSBIOS

Hi,

In TDA2, in order to run the apps, apps.out and firmware files(dra7-dsp1-fw, dsp-f2, ipu2-fw) are needed in Linux.

And, in RTOS, the appimage and MLO files are needed.

In TDA4M, if I build the PSDK, the out files are generated.

If I'd like to run the app, just out file is needed?

BR,

Heechang

  • 0
    Prodigy 230 points

    In targetfs/lib/firmware, there are many files.

    What need the file for running the apps in "firmware" directory?

  • 0 in reply to Heechang Kim1
    TI__Genius 9101 points

    hi Mr Kim,

    After doing "make vision_apps" the .out files to load on R5F, C6x, C7x and A72 are stored here,

    vision_apps/out/J7/A72/LINUX/$PROFILE
    vision_apps/out/J7/R5F/SYSBIOS/$PROFILE
    vision_apps/out/J7/C66/SYSBIOS/$PROFILE
    vision_apps/out/J7/C71/SYSBIOS/$PROFILE
    The *.out files get loaded on respective CPUs.
    See vision_apps/docs/user_guide/BUILD_INSTRUCTIONS.html
    To copy to SD card do below
    make linux_fs_install_sd
    This copies the R5F, C6x, C7x .out from /lib/firmware folder in the SD card.
    Before copying they are renamed as shown below,
    ifeq ($(BUILD_CPU_MCU2_1),yes)
        # copy remote firmware files for mcu2_1
        cp $(VISION_APPS_PATH)/out/J7/R5F/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_mcu2_1.out $(LINUX_FS_PATH)/lib/firmware/j7-main-r5f0_1-fw
    endif
    ifeq ($(BUILD_CPU_C6x_1),yes)
        # copy remote firmware files for c6x_1
        cp $(VISION_APPS_PATH)/out/J7/C66/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_c6x_1.out $(LINUX_FS_PATH)/lib/firmware/j7-c66_0-fw
    endif
    ifeq ($(BUILD_CPU_C6x_2),yes)
        # copy remote firmware files for c6x_2
        cp $(VISION_APPS_PATH)/out/J7/C66/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_c6x_2.out $(LINUX_FS_PATH)/lib/firmware/j7-c66_1-fw
    endif
    ifeq ($(BUILD_CPU_C7x_1),yes)
        # copy remote firmware files for c7x_1
        cp $(VISION_APPS_PATH)/out/J7/C71/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_c7x_1.out $(LINUX_FS_PATH)/lib/firmware/j7-c71_0-fw
    endif

    The also copies A72 .out files to /opt/vision_apps.
        cp $(VISION_APPS_PATH)/out/J7/A72/LINUX/$(LINUX_APP_PROFILE)/*.out $(LINUX_FS_PATH)/opt/vision_apps
        cp $(VISION_APPS_PATH)/apps/basic_demos/app_linux_fs_files/* $(LINUX_FS_PATH)/opt/vision_apps
    In general see vision_apps/makerules/makefile_linux_arm.mak for more details on how things are copied from local folder/files to linux filesystem.
    To boot EVM additional bootloader files are needed these need to be  copied as shown in below file
    vision_apps/docs/user_guide/RUN_INSTRUCTIONS.html
    During boot, uboot loads these binaries to respective CPUs. This is different from TDA2x where the linux kernel would load the binaries.
    Let me know if you need further information
    regards
    Kedar