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.

HELP: DM3730 ProcMgr_attach failed

Other Parts Discussed in Thread: OMAP3530

Hi e2e.ti users,

I have a problem with SysLink. I am using Mistral DM3730 EVM which similar OMAP3530. I need to use SysLink in our project so downloaded the latest version of SysLink (2_00_03_82) and installed as described in install guide. After compile SysLink i loaded the binaries to target.And reboot the EVM, then run the messageq sample as below,

OMAP3# setenv bootargs 'console=ttyS2,115200n8 root=/dev/nfs nfsroot=HOST:nfs_root,nolock rw mem=248M ip=dhcp'                                                                                OMAP3# boot

root@dm3730-am3715-evm:~# insmod /lib/modules/2.6.32/kernel/drivers/dsp/syslink.ko  
root@dm3730-am3715-evm:~# export TRACE=1                                            
root@dm3730-am3715-evm:~# export TRACEFAILURE=1                                     
root@dm3730-am3715-evm:~# export TRACEENTER=1                                       
root@dm3730-am3715-evm:~# export TRACECLASS=3                                    
root@dm3730-am3715-evm:~# cd /ti/syslink-examples/OMAP3530/messageq/             
root@dm3730-am3715-evm:/ti/syslink-examples/OMAP3530/messageq# ./run_messageqapp_debug.sh

After, run the sample it fails on "ProcMgr_attach", what is the problem in my instructions? All the traces below, Waiting your replys, please inform me what's wrong i made?

======== Running app using slaveloader ========
Trace enabled
Trace entry/leave prints enabled
Trace SetFailureReason enabled
Trace class 3
Leaving TraceDrv_ioctl
Entered MultiProc_getId
        name    [0xbef93e3c]
Leaving MultiProc_getId
        id      [0x0]
Entered ProcMgr_open
        handlePtr       [0xbef93b98]
        procId  [0x0]
Entered ProcMgrDrvUsr_ioctl
        cmd     [0xc614e09d]
        args    [0xbef93538]
    ProcMgrDrvUsr_ioctl: API Status [0x0]
Leaving ProcMgrDrvUsr_ioctl
        status  [0x0]
Entered Memory_calloc
        heap    [0x0]
        size    [0x610]
        align   [0x0]
        eb      [0x0]
Entered MemoryOS_calloc
        size    [0x610]
        align   [0x0]
        flags   [0x0]
Entered MemoryOS_alloc
        size    [0x610]
        align   [0x0]
        flags   [0x0]
Leaving MemoryOS_alloc
        ptr     [0x95248]
Leaving MemoryOS_calloc
        ptr     [0x95248]
Leaving Memory_calloc
Leaving ProcMgr_open
        status  [0x0]
Entered ProcMgr_getAttachParams
        handle  [0x0]
        params  [0xbef93b90]
Entered ProcMgrDrvUsr_ioctl
        cmd     [0xc00ce09f]
        args    [0xbef93b4c]
    ProcMgrDrvUsr_ioctl: API Status [0x0]
Leaving ProcMgrDrvUsr_ioctl
        status  [0x0]
Leaving ProcMgr_getAttachParams
Entered ProcMgr_attach
        handle  [0x95248]
        params  [0xbef93b90]
Entered ProcMgrDrvUsr_ioctl
        cmd     [0xc614e0a0]
        args    [0xbef93538]
    ProcMgrDrvUsr_ioctl: API Status [0x86a85003]
Leaving ProcMgrDrvUsr_ioctl
        status  [0x86a85003]
*** ProcMgr_attach: API (through IOCTL) failed on kernel-side!
        Error [0x86a85003] at Line no: 1093 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c

Leaving ProcMgr_attach
        status  [0x86a85003]
ProcMgr_attach failed [0x86a85003]
Entered ProcMgr_close
        handlePtr       [0xbef93b98]
Entered ProcMgrDrvUsr_ioctl
        cmd     [0xc008e09e]
        args    [0xbef93b44]
    ProcMgrDrvUsr_ioctl: API Status [0x0]
Leaving ProcMgrDrvUsr_ioctl
        status  [0x0]
Entered Memory_free
        heap    [0x0]
        block   [0x95248]
        size    [0x610]
Entered MemoryOS_free
        ptr     [0x95248]
        flags   [0x0]
Leaving MemoryOS_free
Leaving Memory_free
Leaving ProcMgr_close
        status  [0x0]
Entered _NotifyDrvUsr_eventWorker
        arg     [0x0]
Setting Trace to: [0x0]