• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 635 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.

Syslink errors during code load in ProcMgr_map in ti816x

Sivagamy Govindasamy
Expert 6950 points

Hello,

Placing some code section in OCMC0  RAM are in our 816x based Application give these erros during load / attach.

            Loaded file ../f*** _ProcMgr_map: All memEntries slots are in use!

        Error [0x6a85000] at Line no: 2559 in file /datalocal/ti_tools/syslink/syslink_2_00_00_78/packages/ti/syslink/utils/hlos/knl/Linux/../../../../.

./../ti/syslink/procMgr/common/ProcMgr.c

irmware/dvr_rdk_fw_m3video.xem3 *** _ProcMgr_map: All memEntries slots are in use!

        Error [0x6a85000] at Line no: 2559 in file /datalocal/ti_tools/syslink/syslink_2_00_00_78/packages/ti/syslink/utils/hlos/knl/Linux/../../../../.

./../ti/syslink/procMgr/common/ProcMgr.c

on slave procId 1.

Started slave procId 1.

Still code loading is successful and our app works ok functionally. What could be the issue here? Is there a fix available?

Unloading doesnt work due to these errors.

Thanks,

Sivagamy

 

  • 0
    TI__Mastermind 18260 points

    Sivagamy Govindasamy said:
    Loaded file ../f*** _ProcMgr_map: All memEntries slots are in use!
            Error [0x6a85000] at Line no: 2559 in file /datalocal/ti_tools/syslink/syslink_2_00_00_78/packages/ti/syslink/utils/hlos/knl/Linux/../../../../.
    ./../ti/syslink/procMgr/common/ProcMgr.c

    Today's ELF files have lots and lots of sections, and each section needs a separate mapping (which is an issue in itself that will be addressed in upcoming SysLink releases).  The SysLink kernel module (syslink.ko) has a fixed-sized table for these mappings, of which you're running out.

    This table size is dimensioned by the constant ProcMgr_MAX_MEMORY_REGIONS, defined in <syslink>/packages/ti/syslink/ProcMgr.h.  Can you rebuild SysLink after changing the following to something bigger?:
        #define ProcMgr_MAX_MEMORY_REGIONS 32u

    Regards,

    - Rob

     

  • 0 in reply to Robert Tivy
    TI__Mastermind 18260 points

    Forgot to mention one thing about increasing ProcMgr_MAX_MEMORY_REGIONS...

    We fixed an issue in SysLink that prevented ProcMgr_MAX_MEMORY_REGIONS from being increased > 45 or so.  This fix is in the latest release, SysLink 2.00.03.82.  Before the fix, the kernel would crash when ProcMgr_MAX_MEMORY_REGIONS was increased to 64.

    You can get SysLink 2.00.03.82 here: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/syslink/index.html

    Regards,

    - Rob

  • 0 in reply to Robert Tivy
    TI__Expert 6950 points

    Increasing ProcMgr_MAX_MEMORY_REGIONS to 38 resolved the error. Thanks for your help.

    - Sivagamy