• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 100 subscribers
  • Views 353 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.

TDA4VM: Do I need to add these ipc xer5f after BootApp?

Ni Hua
Prodigy 235 points
Part Number: TDA4VM

Will the SBL-->BootApp process continue to load rpmsg*.ko modules related services after atf_opte. appimage, tidtb_linux.appimage, and tikernelimage_linux.appimage are started? I have tested the program of the inter-core communication ipc section you mentioned before, but it failed in this process. Do I need to load other modules later? Or if ipc_echo_test_mcu1_0_release_strip.xer5f is placed into BootApp, can it communicate normally? What should I do?In a word? Do I need to add these ipc images after BootApp? I saw the path is in packages\ti\boot\sbl\example\boot_app\multicore_images\j721e_evm\* ,  have the ipc images.

and the A72 cores log when i insmod the raleted module, seems remoteproc not running:

  • 0
    Prodigy 235 points

    The bootapp seems to run away after loading the kernel? The terminal output is a bunch of error garbled code.

  • 0
    Prodigy 235 points

    My SD card currently has these images in the boot path:

  • 0 in reply to Ni Hua
    TI__Mastermind 49866 points

    Hello,

    Let me be clear here, You are using Boot App in PDK and also you are using HLOS as linux on A72.

    If you are expecting ipc echo test on Main domain cores then you need to built lateapp1,latepapp2,lateapp3 with ipc echo test binaries from the script and also in the log i observed that it didn't show 

    MCU2_0 booted

    MCU2_1 booted

    .

    .

    as such to know whether the remaining cores are booted or not.

    Please mention step by step changes whatever you did and help me understand you expectation of IPC on which core.

    Regards

    Tarun Mukesh

  • 0 in reply to Tarun Mukesh Puvvada
    Prodigy 235 points

    I just used the official TI downloaded program and did not make other program changes.

    I've seen how the lateapp1, lateapp2, lateapp3 makes in this script:

    C:\ti-processor-sdk-rtos-j721e-evm-08_06_00_12\pdk_jacinto_08_06_00_31\packages\ti\boot\sbl\example\boot_app\scripts\constructappimage_multistage_j721e.sh

    Can I add my MCU1_0 file: ipc_echo_test_mcu1_0_release_strip.xer5f  ? Will this allow my IPC test demo to start after BootApp?

  • 0 in reply to Ni Hua
    TI__Mastermind 49866 points

    Hello,

    No.This is for lateapp Main domain cores .If you see "app" in the sd card that has to be mcu1_0 related executable.

    May i know you are testing IPC between which cores ?

    Regards

    Tarun Mukesh

  • 0 in reply to Tarun Mukesh Puvvada
    Prodigy 235 points

    Hi Tarun, I'm testing the IPC communication between A72 Core and the MCU R5 Core. So do I need to use app(BootApp), as an IPC communication way? However, I have checked that there is no IPC related source code for rpmsg in BootApp, only some sciserver setup part. Is this the reason why I did not start remoteproc related drivers on Linux with A72 core? If this is the reason, how can I modify BootApp so that it has IPC-related capabilities?

  • 0 in reply to Ni Hua
    TI__Mastermind 49866 points

    Hello,

    yes in App(Boot APP) you have to include IPC to start IPC communication.

    Is IPC working between A72 and remaining cores  now apart from MCU1_0?

    Regards

    Tarun Mukesh

  • 0 in reply to Tarun Mukesh Puvvada
    Prodigy 235 points

    Hello Tarun, 

    Yes, there may be future needs to communicate between other cores, but for now we only want to communicate between A72 and MCU1_0. So do you have a full-featured BootApp, including IPC communication. Inter-nuclear communication can also use the TISCI mechanism based on sciserver/sciclient in a way, right? If rpmsg and TISCI can be developed in both ways, which development way is less difficult? Looking forward to your reply. Sincere thanks！

  • 0 in reply to Ni Hua
    TI__Mastermind 49866 points

    Hello, 

    Please expect a bit of delay in response as I am on urgent leave. 

    Regards 

    Tarun Mukesh 

  • 0 in reply to Tarun Mukesh Puvvada
    Prodigy 235 points

    Hi, Tarun,

    Can you help me with this problem sometime? It's urgent. Thank you so much.

    Regards

    Ni Hua

  • 0 in reply to Ni Hua
    TI__Mastermind 49866 points

    Hello Ni Hua,

    Sorry for the delay.

    Ni Hua said:
    there may be future needs to communicate between other cores, but for now we only want to communicate between A72 and MCU1_0

    The Boot APP you are trying should contain IPC in it then only it can be used as per your expectation.

    If you use Ipc echo test on MCU1_0 then remaining boot app functionality won't work and linux will also not be booted up.

    Regards

    Tarun Mukesh