Hello,
We are trying to run the demo application included in the DM8168 DVR RDK. When running the load script (./load.sh) we get the following errors:
root@dvr:/opt/dvr_rdk/ti816x# ./load.shAttached to slave procId 2.Loaded file ../firmware/dvr_rdk_fw_m3vpss.xem3 on slave procId 2.Started slave procId 2.After Ipc_loadcallback status [0x00000000]After Ipc_startcallback status [0x00000000]Attached to slave procId 1.*** _ProcMgr_map: All memEntries slots are in use! Error [0x6a85000] at Line no: 2561 in file /home/min/DVR_RDK_BASE/DVRRDK_01_09_00_19/ti_tools/syslink/syslink_2_00_04_83/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/common/ProcMgr.c
repeats the same error (0x6a85000) ~ 20 times, then it hangs with:
Loaded file ../firmware/dvr_rdk_fw_m3video.xem3 on slave procId 1.Started slave procId 1.*** _ProcMgr_map: All memEntries slots are in use! Error [0x6a85000] at Line no: 2561 in file /home/min/DVR_RDK_BASE/DVRRDK_01_09_00_19/ti_tools/syslink/syslink_2_00_04_83/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/common/ProcMgr.c*** _ProcMgr_map: All memEntries slots are in use! Error [0x6a85000] at Line no: 2561 in file /home/min/DVR_RDK_BASE/DVRRDK_01_09_00_19/ti_tools/syslink/syslink_2_00_04_83/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/common/ProcMgr.cAfter Ipc_loadcallback status [0x00000000]
We have tried increasing the ProcMgr_MAX_MEMORY_REGIONS as described here:
http://e2e.ti.com/support/embedded/bios/f/355/t/136229.aspx
but we still get the same errors. Any advice or direction would be appreciated.
Thanks!
Aaron
Aaron Ridinger We have tried increasing the ProcMgr_MAX_MEMORY_REGIONS as described here: http://e2e.ti.com/support/embedded/bios/f/355/t/136229.aspx but we still get the same errors.
but we still get the same errors.
Did you rebuild the whole of SysLink, including the syslink.ko kernel module?
The whole of SysLink and the application should be rebuilt after changing ProcMgr_MAX_MEMORY_REGIONS (this is true for 2.00.04.83, later SysLink releases require just the kernel module rebuild). You don't need to rebuild the remote core executable, just the host side of things.
Also, make sure you're actually using the newly build syslink.ko instead of some older one - the syslink.ko banner should specify when it was built.
Regards,
- Rob
Hi Rob,
Thanks for the advice. When we rebuild all of SysLink and the application we now do see a change, however when increasing the ProcMgr_MAX_MEMORY_REGIONS at ~42 or above (we were using 38 before), we now get the following error:
*** ProcMgrDrv_ioctl: Unsupported ioctl command specified
Error [0xfffffffe] at Line no: 2129 in file /home/min/DVR_RDK_BASE/DVRRDK_01_09_00_19/ti_tools/syslink/syslink_2_00_04_83/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/Linux/ProcMgrDrv.c
DMA: Module install successful, device major num = 251
DRV: Module install successful
DRV: Module built on Apr 27 2012 17:36:00
[c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
[m3video] Remote Debug Shared Memory @ 0xbff05020
[m3vpss ] Remote Debug Shared Memory @ 0xbff0a040
Any further things we can try?
Is it advisable to use a later release of SysLink?
Thanks,Aaron
Please sanity check that you re-linked your user-mode app with SysLink after you modify ProcMgr_MAX_MEMORY_REGIONS and rebuild. At least in the 2.00.* releases, that #define is built into both the usermode lib and the kernel driver, so you must relink your app, too.
Also note that the release notes for SysLink 2.00.05.85 mention a fix for a blown stack if ProcMgr_MAX_MEMORY_REGIONS is "too big". You should be able to update to 2.00.05.85 (or 2.00.06.87) without much pain. I'd stay away from the 2.10.* stream until the RDK updates.
Finally, for the archives, the ugly sordid history of this ProcMgr_MAX_MEMORY_REGIONS chaos is somewhat captured here. Unfortunately a bit nasty.
Chris
Thanks for that info Chris. Today we were trying to ensure that the user-mode app was re-linked, however, since we haven't written any apps yet and are just trying to run the DVR RDK demo, I'm unsure if this is actually taking place.
So to be safe, we rebuilt the entire DVR RDK package, but still get the same ProcMgr_MAX_MEMORY_REGIONS errors.
We also tried using the prebuilt binaries of u-boot, kernel and jffs2 file system, included with the DVR RDK and flashed them to NAND. When trying to run the demo applications included with the RDK, we still get the same ProcMgr_MAX_MEMORY_REGIONS error. I expected that using the prebuilt demo files included that everything would work, but it didn't. Maybe there is something wrong with our setup...
I might try updating to SysLink 2.00.05.85 to see if that makes any difference.
Any other thoughts or insight in the meantime would be appreciated.
I'm going to move this post to the Linux forum as this seems more like a Linux-side discussion. And there's a better chance of RDK knowledgeable folks (of which I'm not) seeing it. Please keep us posted.
We upgraded to Syslink 2.00.06.87 and increased the ProcMgr_MAX_MEMORY_REGIONS to 64, and ensured that we rebuilt both syslink and the applications. The result was that there were no more ProcMgr_map memory slot errors and the demo application would run.
Thanks for your help.