Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 393 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: Prepare SD card with Vision_apps and booting via SBL for EVM

Pablo Varela
Genius 5949 points
Part Number: TDA4VM

Hello.

We are planning to test vision_apps in J721e using SBL and SD card.

After building all vision apps, and following documentation, whole flle system should be updated in SD card using "linux_fs_install_sd" (with at least DTB changes and the binaries to be loaded in cores)

This make option updates rfs partiton, but also boot partition. The file uenv.txt is updated to adapt u-boot execution and  sysfw.itb. The coment in documentation is:

My question is about that the file mentioned sysfw.itb is properly changed. Then, this operation is only available to SD card prepared to be used with R5 SPL?. When SBL is used, SD card needs tiboot3.bin (SBL itself), TIFS.bin and app. 

Thus, sysfw.ib file is not present in SD card. And also, the one used instead (TIFS) is comming from prebuilt binary and TI informs that customer can not change it.

(https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1088104/tda4vm-tifs-loading-question)

Could you clarify this?

Thanks

  • 0
    TI__Guru* 79626 points

    Hi,

    Pablo Varela said:
    My question is about that the file mentioned sysfw.itb is properly changed. Then, this operation is only available to SD card prepared to be used with R5 SPL?

    Yes, sysfw.itb is used only in SPL boot flow when it includes R5 SPL.

    But internally sysfw.itb also uses tifs.bin and some additional configs (like board_cfg etc.)
    Hence, the meaning of "customer can build sysfw.itb" is that the configs can be changed here by the customer and rebuild, but the tifs is prebuilt here too.

    In case of SBL flow, the SBL takes care of the initialization and customer can build this using make sbl_mmcsd_img as mentioned in the screenshot shared by you. Here, the SBL loads the prebuilt TIFS.bin file.

    Let me know if this answers your query.

    Regards,
    Nikhil

  • 0 in reply to Nikhil Dasan
    Genius 5949 points

    Hello Nikhil,

    Your explanation is clear about the relationship between sysfw and TIFS, but the point to be remarked is that SBL loads prebuilt TIFS. Should this prebuilt binary be changed when using SBL created from another SDK (e.g SDK_08_05) or is invariant?

    When using SPL, vision_apps need to be prepared with "make linux_fs_install_sd". TI documentation says that "make linux_fs_install_sd" replaces sysfw.itb in the SD. But in our case it is not present (in our SD) and make command does not fail. Thus, we understand that replacement is not happening. Is this part of the documentation not relevant for SBL HLOS? It sounds a bit confusing to us

    Thanks

  • +1 in reply to Pablo Varela
    TI__Guru* 79626 points

    Hi Pablo,

    Pablo Varela said:
    Should this prebuilt binary be changed when using SBL created from another SDK (e.g SDK_08_05) or is invariant

    The TIFS should correspond to the SDK release. There shouldn't be a mismatch in the SDK version between SBL and TIFS

    Pablo Varela said:
    Thus, we understand that replacement is not happening. Is this part of the documentation not relevant for SBL HLOS? It sounds a bit confusing to us

    Sorry, this looks like an outdated comment. I will have this removed in the upcoming release. 

    If we refer the implementation as shown below, you could see that only uenv.txt would be copied but not sysfw.itb (in any case). Hence you do not see an error here.

    define MODIFY_FS =
	# copy uEnv.txt and sysfw.itb for PSDK RTOS
	cp $(VISION_APPS_PATH)/apps/basic_demos/app_linux_fs_files/uEnv_$(SOC)_vision_apps.txt $(2)/
	cp $(VISION_APPS_PATH)/apps/basic_demos/app_linux_fs_files/uEnv_$(SOC)_edgeai_apps.txt $(2)/
	cp $(2)/$(UENV_NAME) $(2)/uEnv.txt
	# update any additional files specific to PSDK RTOS in the filesystem
	-cp $(VISION_APPS_PATH)/apps/basic_demos/app_linux_fs_files/limits.conf $(1)/etc/security/limits.conf 2> /dev/null
	sync
endef

    Regards,
    Nikhil