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

Original question:

PROCESSOR-SDK-J721S2: [j721s2] How to enable MCU R5F cores running in split mode in SPL boot flow

PROCESSOR-SDK-J721S2: [j721s2] How to fix load /lib/firmware/j721s2-mcu-r5f0_1-fw fail

jiahao chang
Prodigy 150 points
Part Number: PROCESSOR-SDK-J721S2
Other Parts Discussed in Thread: TDA4VM

Tool/software:

Dear TI

After patched the
[FAQ] TDA4VM: How to enable MCU R5F cores running in split mode in SPL boot flow.
u-boot_patches_to_enable_MCU_R5F_SplitMode.zip
Linux_patches_to_enable_MCU_R5F_SplitMode.zip

u-boot load /lib/firmware/j721s2-mcu-r5f0_1-fw fail
It cause by the size of vx_app_rtos_linux_mcu1_1.out is 0 , right ?

Is there any suggestion for this, thanks

a) u-boot command
=> load mmc 0:5 0x82000000 /lib/firmware/j721s2-mcu-r5f0_1-fw
Failed to load '/lib/firmware/j721s2-mcu-r5f0_1-fw'

=> load mmc 0:5 0x82000000 /lib/firmware/j721s2-main-r5f0_1-fw
335028 bytes read in 120 ms (2.7 MiB/s)

b)root@j721s2-evm:/lib/firmware# ls -la
lrwxrwxrwx 1 root root 62 Mar 9 2018 j721s2-mcu-r5f0_1-fw -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out
lrwxrwxrwx 1 root root 79 Mar 9 2018 j721s2-mcu-r5f0_1-fw-sec -> /usr/lib/firmware/ti-ipc/j721s2/ipc_echo_test_mcu1_1_release_strip.xer5f.signed

lrwxrwxrwx 1 root root 62 Mar 9 2018 j721s2-main-r5f0_1-fw -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_1.out
lrwxrwxrwx 1 root root 69 Mar 9 2018 j721s2-main-r5f0_1-fw-sec -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_1.out.signed

c)
root@j721s2-evm:~# ls -la /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out
-rw-r--r-- 1 root root 0 Mar 9 2018 /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out
root@j721s2-evm:~#
root@j721s2-evm:~# ls -la /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_0.out
-rw-r--r-- 1 root root 1203596 Mar 9 2018 /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu2_0.out
root@j721s2-evm:~#

d) uart log

6518.putty_2.log

Best Regards
Jiahao

  • 0
    TI__Guru 64610 points

    Hi,

    Are you rebuilding Linux image and u-boot post integration of patches.

    You need to copy the updated Linux image, u-boot image, tiboo3.bin, tispl.bin to boot media.

    jiahao chang said:

    a) u-boot command
    => load mmc 0:5 0x82000000 /lib/firmware/j721s2-mcu-r5f0_1-fw
    Failed to load '/lib/firmware/j721s2-mcu-r5f0_1-fw'

    => load mmc 0:5 0x82000000 /lib/firmware/j721s2-main-r5f0_1-fw
    335028 bytes read in 120 ms (2.7 MiB/s)

    You no need to run above explicitly, default u-boot will load the firmware to remote cores.
    If u-boot not loaded, then Linux will load the firmware to remote cores. 

    Best Regards,
    Sudheer

  • 0 in reply to Doredla Sudheer Kumar
    Prodigy 150 points

    Hi Sudheer

    1)
    Are you rebuilding Linux image and u-boot post integration of patches.
    You need to copy the updated Linux image, u-boot image, tiboo3.bin, tispl.bin to boot media.
    >>
    Yes, I have re-build all image, and flashed all image (tiboot3.bin , tispl.bin , u-boot.img , rootfs.ext )

    2)
    You no need to run above explicitly, default u-boot will load the firmware to remote cores.
    If u-boot not loaded, then Linux will load the firmware to remote cores.
    >>
    Because I see this error log in booting log (6518.putty_2.log)
    Failed to load '/lib/firmware/j721s2-mcu-r5f0_1-fw'
    then I do this test to double check this error

    3)
    I find the cause of load '/lib/firmware/j721s2-mcu-r5f0_1-fw' fail

    by the vx_app_rtos_linux_mcu1_1.out is zero size

    root@j721s2-evm:/lib/firmware# ls -la
    lrwxrwxrwx 1 root root 62 Mar 9 2018 j721s2-mcu-r5f0_1-fw -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out

    root@j721s2-evm:~# ls -la /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out
    -rw-r--r-- 1 root root 0 Mar 9 2018 /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out

    How to setup build for vx_app_rtos_linux_mcu1_1.out ?


    Thanks
    Jiahao

  • 0 in reply to jiahao chang
    TI__Guru 64610 points

    Hi,

    jiahao chang said:

    I find the cause of load '/lib/firmware/j721s2-mcu-r5f0_1-fw' fail

    by the vx_app_rtos_linux_mcu1_1.out is zero size

    root@j721s2-evm:/lib/firmware# ls -la
    lrwxrwxrwx 1 root root 62 Mar 9 2018 j721s2-mcu-r5f0_1-fw -> /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out

    root@j721s2-evm:~# ls -la /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out
    -rw-r--r-- 1 root root 0 Mar 9 2018 /usr/lib/firmware/vision_apps_evm/vx_app_rtos_linux_mcu1_1.out

    Yes, you can rebuild vision apps and copy the MCU1_1 image from vison to  /usr/lib/firmware/vision_apps_evm/

    If you wish to have any other image, please soft link the required image using "ln" command.

    Best Regards,
    Sudheer