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

How to share memory from arm side (HLOS) to RTOS side

kare vaishnavi
Prodigy 10 points


Hi all,

I am trying to run notify sample example of syslink. I want to see the code flow by inserting the logs on both HLOS and RTOS side.

I thought to dump some values as logs to the shared memory area  on RTOS side.

previously I used DSP/Bridge , there I used some API's on ARM side  to reserve,map the DSP memory and send that through DSPNode_PutMessage API.

Now i am trying to do same thing using syslink. How to send shared memory to RTOS side from HLOS side?

Thanks in advance.

  • 0
    TI__Mastermind 18260 points

    SysLink contains a module named SharedRegion that is used to create and manage memory areas that are to be shared between the ARM and DSP-subsystem processors.  SharedRegion memory can be used for allocating MessageQ messages with which you can communicate other SharedRegion information.  The SysLink documentation contains detailed usage help for these and all SysLink modules, and the SysLink product also contains many samples for illustrating such usage.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Prodigy 80 points

    Thank u

    -Vaishnavi

  • 0 in reply to vaishnavi kare
    Guru 10685 points

    Hi Robert,

    I've been following this thread. How does CMEMK work with SharedRegion? I know that CMEMK allocates contiguous blocks of physical memory to the ARM that can then be used with the DSP but I am struggling to understand how the DSP gets information on where that memory is.

    Thanks,
    Ralph

  • 0 in reply to _Ralph_
    TI__Mastermind 18260 points

    CMEMK is not related to SharedRegion.  It predates SharedRegion by many years.

    The DSP gets information about CMEM buffers by way of Codec Engine's VISA APIs.  Since only the host processor can allocate/free from CMEM, the host performs the allocation and fills in a data structure with the physical address of the CMEM buffer(s), then sends this data structure across to the DSP, and the DSP then accesses the CMEM buffers by way of the physical address passed in the message.

    That's how it's done in Codec Engine, but in general the DSP needs to receive the physical address of the buffer through some IPC mechanism.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Guru 10685 points

    Hi Rob, thanks for that useful description. You seem to be quite up on DSP/GPP stuff; would you be able to point me in the direction of any documents regarding the allocation of memory to the HDVICPs via the Media Controller using DOMX? I did a Google search of ti.com and only found 29 web pages, none of them very useful!

    Regards,

    Ralph

  • 0 in reply to _Ralph_
    TI__Mastermind 18260 points

    _Ralph_ said:

    Hi Rob, thanks for that useful description. You seem to be quite up on DSP/GPP stuff; would you be able to point me in the direction of any documents regarding the allocation of memory to the HDVICPs via the Media Controller using DOMX? I did a Google search of ti.com and only found 29 web pages, none of them very useful!

    Ralph,

    I'm not knowledgable on the DOMX/Media Controller/HDVICP, those components are higher-level than what I work on or know about.  My area is the software below/under those components.  I'm sure that one of the other Forums would be better for an answer (but not sure which one).  My apologies.

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    Guru 10685 points

    No problem, I'll have a hunt around the other forums and see what happens.

    Thanks,
    Ralph