• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 455 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.

Linux/AM5726: example on modifying MLO to get DSP up and running

Colombo Carlo
Mastermind 24070 points
Part Number: AM5726

Tool/software: Linux

Hi everybody, 

I would like to enable onboard DSP , please  coudl you redirect me to a proper example and info on :

  1. How can I modify the MLO or the A15’s code to “wake up” the DSP ?
  2. How do I compile both A15 and C66xx projects into one APP file ?

thank you 

best regards

Carlo

  • 0
    TI__Guru 50170 points
    Hi, Carlo,

    Is the device running Linux or RTOS on A15? Why do you need to wake up DSP in MLO while the system is coming up and DSP is not usable before system is ready? What's the application?
    If device is running Linux, do you mean to have linux kernel and C66 executable into one image?
    If this is what you are looking for, the answer is no. Even in RTOS case, it can't be in one image.
    The way it is done (in Linux case) is the DSP/IPU binaries are in Linux filesystem. During kernel boot up, remoteproc will download the DSP/IPU binaries to the DSP/IPU.

    Rex
  • 0 in reply to Rex Chang
    TI__Mastermind 24070 points
    Hi Rex ,
    considering A15 running Linux , do you have an example I can refer to to see a basic example ( like an "hello world " ) loaded and running on DSP ?
    my goal is to load the DSP and start it , being able to have a single binary to be loaded in the flash ( so to flash a single SD card for example )
    thank you
    best regards
    Carlo
  • 0 in reply to Colombo Carlo
    TI__Guru 50170 points
    Hi, Carlo,

    We have prebuilt DSP/IPU example binaries in the Linux filesystem. There is one in /usr/bin/ipc/examples/ex02_messageq/debug/Server_dspX.xe66 for C66 and corresponding Linux executable app_host.
    The other one is in /lib/firmware/ipc/ti_platforms_evmDRA7XX_dspX/messageq_single.xe66 for DSP and corresponding Linux app is /usr/bin/MessageQBench.

    You can follow the section of "Running the Bundled IPC Examples" in
    software-dl.ti.com/.../How_to_Guides.html

    Modify the link of /lib/firmware/dra7-dspX-fw.xe66 to corresponding DSPX binaries. Then, either reboot the system or unbind/bind the DSP to reload the new DSP binaries.

    Each DSP binary has its own configuration. So, you will need different DSP binaries for different DSP cores. You can see that in the folder structure or the binary file names.

    Rex
  • 0 in reply to Rex Chang
    TI__Mastermind 24070 points
    Hi Rex
    thank you very much
    best regards
    Carlo
  • 0 in reply to Colombo Carlo
    TI__Guru** 116170 points

    Carlo,

    Steps provided by Rex Applies to users who are using ARM Linux and RTOS On the DSP. BAsed on previous interaction with you and your customer, it appears that they are using TI RTOS on both  ARM and DSP and using SBL and not  uboot/Linux. Please confirm.

    If this is RTOS -RTOS , then we have  covered this topic in the Software Developers guide as part of secondary bootloader  documentation.  There is no modification required to RTOS SBL to wake up DSP as it has mechanism to detect DSP image and wake up the core based on application binary.

    The ARM, DSP and M4 images can be merged into a single image using tool called MulticoreImageGen that we provide as part of the boot package. This topic was covered in detail in the AM57x boot slides that I had provided to you and your customer last year. I am providing a screenshot  for reference: