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.

Setting up SharedRegions using Syslink

Other Parts Discussed in Thread: OMAPL138, SYSBIOS

This is a newb question, but I'm using an OMAPL138 and I've implemented a shared memory interface between the DSP and the ARM cores where both are using SharedRegion under Sysbios. Now I want to move the ARM impl to Syslink and Linux...

The question is how do I carve out/reserve the memory regions in Linux  that I used to do using the "static configuration" javascript stuff under sysbios?

I see where I can config a region at runtime using SharedRegion_setEntry but dont I have to reserve these regions beforehand so that Linux doesnt already occupy it?

  • Hi Kent,

    You can carve out memory to reserve for SysLink from the Linux kernel memory, using the "mem=" command in your
    bootargs.  Here is an example taken from  http://processors.wiki.ti.com/index.php/SysLink_Install_Guide

    SysLink requires a few specific arguments to be passed to the Linux kernel during boot up. To run the examples, 3MB of memory is needed by SysLink for communication between GPP and slave(s), and for slave(s) external memory usage to place its code/data sections. This must be reserved by specifying 3MB less of available memory for Linux kernel usage.

    • For example, with available memory of 256M, memory required for shared regions/other utils is 5M and SysLink is 3M leaving only 248M for the Linux kernel.
    bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=HOST:nfs_root,nolock rw mem=248M ip=dhcp
    

    This is just an example, bootargs may vary depending on available setup

    Best regards,

        Janet