• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 549 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:

Compiler/TDA2SG: TDA4 UBOOT is compatibility the TDA2S UBOOT

Compiler/TDA4VMXEVM: TDA4 fireware

reset_zhang
Intellectual 850 points

Part Number: TDA4VMXEVM

Tool/software: TI C/C++ Compiler

Hi.

I  See the log:

Remoteproc 2 started successfully
** File not found /lib/firmware/j7-mcu-r5f0_0-fw **

   how can I get   j7-mcu-r5f0_0-fw

1,It is the mcu fireware?  how can I load the mcu fireware support the cpsw9 to test the eth?

2,   Will    j7-mcu-r5f0_0-fw  j7-mcu-r5f0_1-fw   j7-mcu-r5f1_0-fw    j7-mcu-r5f1_1-fw  default   generate?I find the rootfs only   j7-mcu-r5f0_0-fw  j7-mcu-r5f0_1-fw .

  • 0
    TI__Guru** 120931 points

    Hi,

    Please ensure the j7-mcu-r5f0_0-fw, is present in the /rootfs/lib/firmware, on the SD card under test.

    If it is present, the please ensure Uboot is a known state, by running the below:

    - Power on the EVM.

    - Hit Any Key in terminal window to stop the autoboot sequence and enter uboot prompt.

    - In uboot prompt, run the below commands.

    => env default -a

    => saveenv

    - Reboot the board.

    In regards to generating firmware binaries and creating an SD card, include CPSW9, please reference the online PSDKRA documentation.   

    The firmware images which will be built and installed to SD card are controlled by build flags listed here, where vision_apps/vision_apps_build_flags.mak, can be modified as needed.

    Install and run out of box SDK demos from prebuilt binaries [LINK] by referring to instructions on this page [LINK].  

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 850 points

    thanks。

    as we know,tda4  has 2*r5 in the main domain,1*r5 in the mcu domain.

    in the sdk, there is Mcu1_0  ,Mcu1_1,Mcu2_0,Mcu2_1,Mcu3_0,Mcu1_1,  which prensent   r5  in   the main domain   ,which in the mcu domain.   

  • 0 in reply to reset_zhang
    TI__Guru** 120931 points

    Hi,

    One way to check naming convention, and how the generated files, are mapped to the files which Uboot is loading,  is to look at the ./vision_apps/makerules/make_linux_arm.mak, where images are being copied:

    $(VISION_APPS_PATH)/out/J7/R5F/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_mcu1_0.out $(LINUX_FS_PATH)/lib/firmware/j7-mcu-r5f0_0-fw
    $(VISION_APPS_PATH)/out/J7/R5F/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_mcu1_1.out $(LINUX_FS_PATH)/lib/firmware/j7-mcu-r5f0_1-fw
    $(VISION_APPS_PATH)/out/J7/R5F/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_mcu2_0.out $(LINUX_FS_PATH)/lib/firmware/j7-main-r5f0_0-fw
    $(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
    $(VISION_APPS_PATH)/out/J7/R5F/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_mcu3_0.out $(LINUX_FS_PATH)/lib/firmware/j7-main-r5f1_0-fw
    $(VISION_APPS_PATH)/out/J7/R5F/SYSBIOS/$(LINUX_APP_PROFILE)/vx_app_tirtos_linux_mcu3_1.out $(LINUX_FS_PATH)/lib/firmware/j7-main-r5f1_1-fw

    The hi-hited images are the R5's which are present in the MCU domain. 

    Regards,

    kb