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.

OMAP 3530 SYSLink ProcMgr_attach failed

Other Parts Discussed in Thread: OMAP3530

I compiled syslink with these settings, after load the binaries to target when i run the "./run_messageqapp_release.sh" i get 

ProcMgr_attach failed error. Before syslink i was working on dsplink, To run dsp link examples we need to LPM modules, in 

syslink i didnt use module like lpm? Is there anyone to help me???

 

ubuntults@ubuntults-desktop:~/syslink_2_00_03_82$ make .show-products
DEPOT                    = /home/ubuntults
DEVICE                   = OMAP3530
GPPOS                    = Linux
SDK                      = NONE
SYSLINK_BUILD_DEBUG      = 1
SYSLINK_BUILD_OPTIMIZE   = 0
SYSLINK_TRACE_ENABLE     = 1
LOADER                   = COFF
SYSLINK_INSTALL_DIR      = /home/ubuntults/syslink_2_00_03_82
IPC_INSTALL_DIR               = /home/ubuntults/ti-sdk-AM3715-evm-4.0.0.0/CCSv5.1/ipc_1_23_03_31
BIOS_INSTALL_DIR             = /home/ubuntults/ti-sdk-AM3715-evm-4.0.0.0/CCSv5.1/bios_6_32_03_43
XDC_INSTALL_DIR              = /home/ubuntults/ti-sdk-AM3715-evm-4.0.0.0/CCSv5.1/xdctools_3_22_02_27
LINUXKERNEL                     = /home/ubuntults/ti-sdk-AM3715-evm-4.0.0.0/AM37x-PSP/src/kernel/linux
CGT_ARM_PREFIX              = /home/ubuntults/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-
CGT_C64P_INSTALL_DIR     = /home/ubuntults/ti-sdk-AM3715-evm-4.0.0.0/CCSv5.1/ccsv5/tools/compiler/c6000
CGT_C674_ELF_INSTALL_DIR =
CGT_M3_ELF_INSTALL_DIR   =
CGT_A8_ELF_INSTALL_DIR   =
EXEC_DIR                            = /home/ubuntults/ti-sdk-AM3715-evm-4.0.0.0/filesystem

 

root@dm3730-am3715-evm:/ti/syslink-examples/OMAP3530/messageq# ./run_messageqapp_release.sh
======== Running app using slaveloader ========
ProcMgr_attach failed [0x86a85003]
MessageQApp sample application
Run for all supported proc IDs
Entered MessageQApp_startup
[1] + Stopped                    ./run_messageqapp_release.sh

 

 

  • I see a critical thing while i compiling syslink, i see "because package/package.xdc.inc is older than package.xdc" note while compiling. This is

    can be the reason of ProcMgr fails??

     

    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/ipc/rtos/syslinkMemMgr] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.ipc.rtos.syslinkMemMgr (because package/package.xdc.inc is older than package.xdc) ...
        translating SyslinkMemMgr
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/ipc/rtos/syslinkMemMgr/nullMemMgr] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.ipc.rtos.syslinkMemMgr.nullMemMgr (because package/package.xdc.inc is older than package.xdc) ...
        translating MemMgrSupportNull
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/ipc/rtos/syslinkMemMgr/shMemMgr] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.ipc.rtos.syslinkMemMgr.shMemMgr (because package/package.xdc.inc is older than package.xdc) ...
        translating SharedMemoryMgr
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/ipc/rtos/syslinkMemMgr/tilerMemMgr] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.ipc.rtos.syslinkMemMgr.tilerMemMgr (because package/package.xdc.inc is older than package.xdc) ...
        translating TilerMemoryMgr
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/rtos/bios6] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.procMgr.rtos.bios6 (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/hlos/tilerDaemon] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.hlos.tilerDaemon (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/frameq] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.frameq (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/gateMP] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.gateMP (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/heapBufMP] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.heapBufMP (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/heapMemMP] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.heapMemMP (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/knlNotify] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.knlNotify (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/listMP] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.listMP (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/messageQ] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.messageQ (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/notify] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.notify (because package/package.xdc.inc is older than package.xdc) ...
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/platforms/evm6472/core0] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.platforms.evm6472.core0 (because package/package.xdc.inc is older than package.xdc) ...
        translating Platform
    ======== .interfaces [/home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/samples/rtos/platforms/evm6472/core1] ========
    making package.mak (because of package.bld) ...
    generating interfaces for package ti.syslink.samples.rtos.platforms.evm6472.core1 (because package/package.xdc.inc is older than package.xdc) ...
        translating Platform

  • No one to help?? I didn't change any configuration and compile the syslink again and after insmod syslink.ko  set TRACEFAILURE=1 ; TRACE=1  , i run 

    the ./run_messageqapp_debug.sh  script  extended failure message i get. ProcMgr_attach: API (through IOCTL) failed on kernel-side!

    The failure message say for the error at line     "Error [0x86a85003] at Line no: 1093 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c"

    but when i check the line 1093 in ProcMgr.c file i didnt see anything can be cause to an error... What is the problem with syslink???


    root@dm3730-am3715-evm:/ti/syslink-examples/OMAP3530/messageq# ./run_messageqapp_debug.sh

    ======== Running app using slaveloader ========
    Trace enabled
    Trace SetFailureReason enabled
    *** 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
    ProcMgr_attach failed [0x86a85003]
    MessageQApp sample application
    Trace enabled
    Trace SetFailureReason enabled
    Run for all supported proc IDs
    Entered MessageQApp_startup
    *** Ipc_control: API (through IOCTL) failed on kernel-side!
            Error [0xffffffff] at Line no: 1077 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/ipc/hlos/usr/Ipc.c
    Error in Ipc_control Ipc_CONTROLCMD_LOADCALLBACK [0xffffffff]
    Leaving MessageQApp_startup ffffffff
    Trace enabled
    Trace SetFailureReason enabled
    Stopped slave procId 0.
    *** ProcMgr_unload: API (through IOCTL) failed on kernel-side!
            Error [0x8485f003] at Line no: 1357 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c
    Unloaded slave procId 0.
    Unmapping SV: 0x87d00000, SP: 0x87d00000, MP: 0x87d00000,
      size 0xfdb00, mask 0x5, cached 0
    *** ProcMgr_unmap: Info provided does not match with any mapped entry
            Error [0xfffffffb] at Line no: 2265 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c
    ProcMgr_unmap failed [0xfffffffb]
    Unmapping SV: 0x87dfdb00, SP: 0x87dfdb00, MP: 0x87dfdb00,
      size 0x2500, mask 0x5, cached 0
    *** ProcMgr_unmap: Info provided does not match with any mapped entry
            Error [0xfffffffb] at Line no: 2265 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c
    ProcMgr_unmap failed [0xfffffffb]
    Unmapping SV: 0x87e00000, SP: 0x87e00000, MP: 0x87e00000,
      size 0x100000, mask 0x5, cached 0
    *** ProcMgr_unmap: Info provided does not match with any mapped entry
            Error [0xfffffffb] at Line no: 2265 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c
    ProcMgr_unmap failed [0xfffffffb]
    Unmapping SV: 0x87f00000, SP: 0x87f00000, MP: 0x87f00000,
      size 0x100000, mask 0x5, cached 0
    *** ProcMgr_unmap: Info provided does not match with any mapped entry
            Error [0xfffffffb] at Line no: 2265 in file /home/ubuntults/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c
    ProcMgr_unmap failed [0xfffffffb]
    Mapped entries in ./omap3530_memmap.txt to slave procId 0.
    ======== Running app using agruments ========

  • I'm having exactly the same problem, running the syslink examples on an omap3570.   I see the exact same failure...

    Entered ProcMgrDrvUsr_ioctl
            cmd     [0xc614e0a0]
            args    [0xbe932550]
        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/jimk/syslink_2_00_03_82/packages/ti/syslink/procMgr/hlos/usr/ProcMgr.c
    Leaving ProcMgr_attach

    I suspect that the DSP application is not starting up.  I added a System_printf statement at the start of main() in the DSP application, and it never seems to print.   Can someone suggest how to proceed??

     

    Thanks

     

     

     

  • I've gotten a bit farther by enabling kernel level tracing.

    insmod syslink.ko TRACE=1 TRACEFAILURE=1

    Now dmesg shows that ProcMgr_attach fails because of a failure to configure the DSP memory management unit.

     

    [22121.579681] Trace enabled
    [22121.579681] Trace SetFailureReason enabled
    [22146.920959] *** _OMAP3530_halMmuEnable: iommu_get failed!
    [22146.920959]  Error [0x86a85003] at Line no: 375 in file /home/jimk/syslink_2_00_03_82/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omap3530/omap3530dsp/Linux/omap3530_hal_mmu.c
    [22146.920989] *** OMAP3530_halMmuCtrl: Failed to configure DSP MMUat _OMAP3530_halMmuEnable
    [22146.920989]  Error [0x86a85003] at Line no: 184 in file /home/jimk/syslink_2_00_03_82/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omap3530/omap3530dsp/Linux/omap3530_hal_mmu.c
    [22146.921020] *** OMAP3530PROC_attach: Failed to enable the slave MMU
    [22146.921020]  Error [0x86a85003] at Line no: 1091 in file /home/jimk/syslink_2_00_03_82/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omap3530/omap3530dsp/omap3530proc.c
    [22146.921051] *** Processor_attach: Failed to attach to the specific Processor!
    [22146.921051]  Error [0x86a85003] at Line no: 121 in file /home/jimk/syslink_2_00_03_82/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/common/Processor.c
    [22146.921081] *** ProcMgr_attach: Processor_attach failed!
    [22146.921081]  Error [0x86a85003] at Line no: 986 in file /home/jimk/syslink_2_00_03_82/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/common/ProcMgr.c
    [22146.921112] *** ProcMgrDrv_ioctl: Kernel-side ProcMgr_attach failed
    [22146.921112]  Error [0x86a85003] at Line no: 895 in file /home/jimk/syslink_2_00_03_82/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/Linux/ProcMgrDrv.c

  • Hi,

    From the kernel trace that you have got, it seems that you may have missed the iommu patch for the kernel. Excerpt from the Install Guide for a previous SysLink release (2.00.00.73):

    Patching the kernel

     

    Download a kernel patch required (see Dependencies) to enable iommu for iva2 subsystem and apply it on the kernel

    as shown below:

    #Copy the patch to kernel source directory

    $ cp enable-iommu-for-iva2.patch

    AM35x-OMAP35x-PSP-SDK-03.00.00.03/src/kernel/linux-03.00.00.03

    $ cd AM35x-OMAP35x-PSP-SDK-03.00.00.03/src/kernel/linux-03.00.00.03

    $ patch -p0 < enable-iommu-for-iva2.patch

    Ensure that this patch is applied before creating uImage. Since syslink uses iommu internally, it is mandatory to

    have this patch applied.

    This patch is available in the buildutils/hlos/knl folder in the SysLink release package.

    I didn't find this step in the new Install Guide, so it may have been inadvertently missed.

    Can you try patching the kernel, rebuilding and trying again with the new uImage?

    Regards,
    Mugdha

  • Hi,

    Ahmet Caliskan said:

    Before syslink i was working on dsplink, To run dsp link examples we need to LPM modules, in 

    syslink i didnt use module like lpm? Is there anyone to help me???

    SysLink does not require LPM module because it internally includes the power management code. The DSP is powered up when ProcMgr_attach is called.

    Regards,
    Mugdha

  • Thanks Mudgha!   The mmu patch worked. 

    I'm using the Angstrom kernel (2.6.32).  I applied the edit to arch/arm/mach-omap2/omap3-iommu.c, recompiled, and redeployed the kernel.  Now the messageQ example application is working.

    Best regards,

    Jim

     

     

  • Hi Jim,

    I couldnt find enable-iommu-for-iva2.patch  can you send me the patch or your  omap3-iommu.c file?

    Best regards,

    Ahmet

  • Ahmet,

    The MMU enable patch for the kernel is available in the buildutils/hlos/knl folder in the SysLink release package.

    Regards,
    Mugdha

  • Hi ,

    i'm using AM35x-OMAP35x-LINUX-PSP-04.02.00.07 with Beagle board REVC5. i used kernel from the PSP. then i built syslink with the following tools.

    bios_6_33_00_19

    ipc_1_23_05_40

    codec_engine_3_21_02_25

    TI_CGT_C6000_7.3.1

    xdctools_3_23_00_32

    syslink_2_10_01_15

    after built i'm running with the following bootargs

    console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext2 rw rootwait mem=250M

    after booting into file system when i'm trying to load syslink.ko i'm getting following messages.

    /]#insmod /lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko TRACE=1 TRACEFAILURE=1
    [   38.611999] SysLink version : 2.10.01.15
    [   38.611999] SysLink module created on Date:Jan  6 2012 Time:14:13:04
    [   38.622894] Trace enabled
    [   38.625701] Trace SetFailureReason enabled
    [   38.907684] ------------[ cut here ]------------
    [   38.912567] WARNING: at /home/eswar/vtobbc/script-build/kernel/kernel/lockdep.c:2481 lockdep_trace_alloc+0xac/0xec()
    [   38.923583] Modules linked in: syslink(+)
    [   38.927825] [<c004a348>] (unwind_backtrace+0x0/0xec) from [<c00721d0>] (warn_slowpath_common+0x4c/0x64)
    [   38.937683] [<c00721d0>] (warn_slowpath_common+0x4c/0x64) from [<c0072200>] (warn_slowpath_null+0x18/0x1c)
    [   38.947784] [<c0072200>] (warn_slowpath_null+0x18/0x1c) from [<c009e870>] (lockdep_trace_alloc+0xac/0xec)
    [   38.957824] [<c009e870>] (lockdep_trace_alloc+0xac/0xec) from [<c00fa000>] (kmem_cache_alloc_notrace+0x1c/0xd0)
    [   38.968383] [<c00fa000>] (kmem_cache_alloc_notrace+0x1c/0xd0) from [<c00f1d5c>] (__get_vm_area_node+0xac/0x1f8)
    [   38.978942] [<c00f1d5c>] (__get_vm_area_node+0xac/0x1f8) from [<c00f276c>] (__vmalloc_node+0x70/0xa8)
    [   38.988586] [<c00f276c>] (__vmalloc_node+0x70/0xa8) from [<c00f28c0>] (vmalloc+0x24/0x2c)
    [   38.997802] [<c00f28c0>] (vmalloc+0x24/0x2c) from [<bf02aa8c>] (MemoryOS_alloc+0xc0/0x1a4 [syslink])
    [   39.008117] [<bf02aa8c>] (MemoryOS_alloc+0xc0/0x1a4 [syslink]) from [<bf01f970>] (Memory_alloc+0x68/0x154 [syslink])
    [   39.019805] [<bf01f970>] (Memory_alloc+0x68/0x154 [syslink]) from [<bf020408>] (GateMutex_create+0x1c/0x90 [syslink])
    [   39.031616] [<bf020408>] (GateMutex_create+0x1c/0x90 [syslink]) from [<bf043268>] (GateMP_setup+0xd8/0x3b4 [syslink])
    [   39.043457] [<bf043268>] (GateMP_setup+0xd8/0x3b4 [syslink]) from [<bf018118>] (Platform_setup+0x188/0x5b8 [syslink])
    [   39.055267] [<bf018118>] (Platform_setup+0x188/0x5b8 [syslink]) from [<bf043898>] (Ipc_setup+0xa0/0x158 [syslink])
    [   39.066772] [<bf043898>] (Ipc_setup+0xa0/0x158 [syslink]) from [<bf1134d8>] (KnlUtilsDrv_initializeModule+0x4d8/0x568 [syslink])
    [   39.079193] [<bf1134d8>] (KnlUtilsDrv_initializeModule+0x4d8/0x568 [syslink]) from [<c003a3b8>] (do_one_initcall+0xc8/0x1a0)
    [   39.090942] [<c003a3b8>] (do_one_initcall+0xc8/0x1a0) from [<c00ab434>] (sys_init_module+0x90/0x1b0)
    [   39.100494] [<c00ab434>] (sys_init_module+0x90/0x1b0) from [<c0044540>] (ret_fast_syscall+0x0/0x3c)
    [   39.109954] ---[ end trace eda13c4b30a0aa20 ]---
    [   39.114776] BUG: sleeping function called from invalid context at /home/eswar/vtobbc/script-build/kernel/mm/slab.c:3101
    [   39.126068] in_atomic(): 0, irqs_disabled(): 128, pid: 635, name: insmod
    [   39.133056] INFO: lockdep is turned off.
    [   39.137176] irq event stamp: 30895
    [   39.140716] hardirqs last  enabled at (30894): [<c00d53d8>] get_page_from_freelist+0x304/0x490
    [   39.149749] hardirqs last disabled at (30895): [<bf02633c>] Gate_enterSystem+0x10/0x18 [syslink]
    [   39.159271] softirqs last  enabled at (29553): [<c007837c>] irq_exit+0x50/0x9c
    [   39.166839] softirqs last disabled at (29546): [<c007837c>] irq_exit+0x50/0x9c
    [   39.174438] [<c004a348>] (unwind_backtrace+0x0/0xec) from [<c00fa018>] (kmem_cache_alloc_notrace+0x34/0xd0)
    [   39.184631] [<c00fa018>] (kmem_cache_alloc_notrace+0x34/0xd0) from [<c00f1d5c>] (__get_vm_area_node+0xac/0x1f8)
    [   39.195220] [<c00f1d5c>] (__get_vm_area_node+0xac/0x1f8) from [<c00f276c>] (__vmalloc_node+0x70/0xa8)
    [   39.204864] [<c00f276c>] (__vmalloc_node+0x70/0xa8) from [<c00f28c0>] (vmalloc+0x24/0x2c)
    [   39.213775] [<c00f28c0>] (vmalloc+0x24/0x2c) from [<bf02aa8c>] (MemoryOS_alloc+0xc0/0x1a4 [syslink])
    [   39.224060] [<bf02aa8c>] (MemoryOS_alloc+0xc0/0x1a4 [syslink]) from [<bf01f970>] (Memory_alloc+0x68/0x154 [syslink])
    [   39.235717] [<bf01f970>] (Memory_alloc+0x68/0x154 [syslink]) from [<bf020408>] (GateMutex_create+0x1c/0x90 [syslink])
    [   39.247528] [<bf020408>] (GateMutex_create+0x1c/0x90 [syslink]) from [<bf043268>] (GateMP_setup+0xd8/0x3b4 [syslink])
    [   39.259368] [<bf043268>] (GateMP_setup+0xd8/0x3b4 [syslink]) from [<bf018118>] (Platform_setup+0x188/0x5b8 [syslink])
    [   39.271179] [<bf018118>] (Platform_setup+0x188/0x5b8 [syslink]) from [<bf043898>] (Ipc_setup+0xa0/0x158 [syslink])
    [   39.282684] [<bf043898>] (Ipc_setup+0xa0/0x158 [syslink]) from [<bf1134d8>] (KnlUtilsDrv_initializeModule+0x4d8/0x568 [syslink])
    [   39.295074] [<bf1134d8>] (KnlUtilsDrv_initializeModule+0x4d8/0x568 [syslink]) from [<c003a3b8>] (do_one_initcall+0xc8/0x1a0)
    [   39.306823] [<c003a3b8>] (do_one_initcall+0xc8/0x1a0) from [<c00ab434>] (sys_init_module+0x90/0x1b0)
    [   39.316406] [<c00ab434>] (sys_init_module+0x90/0x1b0) from [<c0044540>] (ret_fast_syscall+0x0/0x3c)

    when i tried to run samples i'm getting following message.

    [root@VRINDA-OBBC messageq]# ./messageqapp_release 1 DSP ./messageq_omap3530_dsp.x64P

    MessageQApp sample application
    Entered MessageQApp_startup
    Loa[  120.398803] *** _OMAP3530_halMmuEnable: iommu_get failed!
    [  120.398803]  Error [0x86a85003] at Line no: 375 in file /home/eswar/vtobbc/syslink/ti/syslink_2_10_01_15/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omc
    ding and startin[  120.426666] *** OMAP3530_halMmuCtrl: Failed to configure DSP MMUat _OMAP3530_halMmuEnable
    [  120.426666]  Error [0x86a85003] at Line no: 184 in file /home/eswar/vtobbc/syslink/ti/syslink_2_10_01_15/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/omc
    g procId [0] wit[  120.458496] *** OMAP3530PROC_attach: Failed to enable the slave MMU
    [  120.458496]  Error [0x86a85003] at Line no: 1091 in file /home/eswar/vtobbc/syslink/ti/syslink_2_10_01_15/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/family/hlos/knl/oc
    h [./messageq_om[  120.487518] *** Processor_attach: Failed to attach to the specific Processor!
    [  120.487548]  Error [0x86a85003] at Line no: 121 in file /home/eswar/vtobbc/syslink/ti/syslink_2_10_01_15/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/common/Proc
    ap3530_dsp.x64P][  120.515075] *** ProcMgr_attach: Processor_attach failed!
    [  120.515075]  Error [0x86a85003] at Line no: 986 in file /home/eswar/vtobbc/syslink/ti/syslink_2_10_01_15/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/common/Proc

    [  120.540557] *** ProcMgrDrv_ioctl: Kernel-side ProcMgr_attach failed
    [  120.540588]  Error [0x86a85003] at Line no: 925 in file /home/eswar/vtobbc/syslink/ti/syslink_2_10_01_15/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/procMgr/hlos/knl/Lc
    ProcMgr_attach failed [0x86a85003]
    SlaveLoader_startup status [-2035789821]
    Leaving MessageQApp_startup 86a85003



    after searched i found this thread. i'm using 2.6.37 kernel. so i think iva2 patch is already applied.
    So, can anyone please help to solve .

  • Hi Eswar,


    I upgrated kernel release to 2.6.37 to and saw thet iva2 patch is not applied.You must activate IVA2.2 subsystem before using SysLink.

    Ahmet


  • Hi Ahmet,

    Thanks for reply. i verified omap-iommu.c

    in patch file it says

    --- arch/arm/mach-omap2/omap3-iommu.c   2009-11-27 15:47:53.000000000 +0530
    +++ arch/arm/mach-omap2/omap3-iommu-new.c       2009-11-27 15:44:35.000000000 +0530
    @@ -36,13 +36,13 @@
                    .nr_tlb_entries = 8,
                    .clk_name = "cam_ick",
            },
    -#if defined(CONFIG_MPU_BRIDGE_IOMMU)
    +/*#if defined(CONFIG_MPU_BRIDGE_IOMMU)*/
            {
                    .name = "iva2",
                    .nr_tlb_entries = 32,
                    .clk_name = "iva2_ck",
            },
    -#endif
    +/*#endif*/
     };
     #define NR_IOMMU_DEVICES ARRAY_SIZE(omap3_iommu_pdata)


    and in2.6.37 kernel,  omap-iommu.c the patch is already there.

    #ifdef CONFIG_ARCH_OMAP3
    static struct iommu_device omap3_devices[] = {
            {
                    .base = 0x480bd400,
                    .irq = 24,
                    .pdata = {
                            .name = "isp",
                            .nr_tlb_entries = 8,
                            .clk_name = "cam_ick",
                            .da_start = 0x0,
                            .da_end = 0xFFFFF000,
                    },
            },
    #if defined(CONFIG_OMAP_IOMMU_IVA2)
            {
                    .base = 0x5d000000,
                    .irq = 28,
                    .pdata = {
                            .name = "iva2",
                            .nr_tlb_entries = 32,
                            .clk_name = "iva2_ck",
                            .da_start = 0x11000000,
                            .da_end = 0xFFFFF000,
                    },
            },
    #endif
    };
    #define NR_OMAP3_IOMMU_DEVICES ARRAY_SIZE(omap3_devices)
    static struct platform_device *omap3_iommu_pdev[NR_OMAP3_IOMMU_DEVICES];

    i tried by rebuild kernel and syslink by enable CONFIG_OMAP_IOMMU_IVA2=y in config file.

    my bootargs are

    console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext2 rw rootwait mem=250M omapfb.video_mode=320x240-24@60

    my products.mk configuration from syslink directory  is and i'm using 2009 toolchain for arm.

    DEPOT                    = /home/eswar/vtobbc/syslink/ti
    DEVICE                   = OMAP3530
    GPPOS                    = Linux
    SDK                      = NONE
    TI81XXDSP_DMTIMER_FREQ   =
    SYSLINK_BUILD_DEBUG      = 1
    SYSLINK_BUILD_OPTIMIZE   = 0
    SYSLINK_TRACE_ENABLE     = 1
    LOADER                   = COFF
    SYSLINK_INSTALL_DIR      = /home/eswar/vtobbc/syslink/ti/syslink_2_10_01_15
    IPC_INSTALL_DIR          = /home/eswar/vtobbc/syslink/ti/ipc_1_23_05_40
    BIOS_INSTALL_DIR         = /home/eswar/vtobbc/syslink/ti/bios_6_33_00_19
    XDC_INSTALL_DIR          = /home/eswar/vtobbc/syslink/ti/xdctools_3_23_00_32
    LINUXKERNEL              = /home/eswar/vtobbc/syslink/ti/kernel
    QNX_INSTALL_DIR          =
    CGT_ARM_PREFIX           = /home/eswar/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-
    CGT_C64P_INSTALL_DIR     = /home/eswar/vtobbc/syslink/ti/TI_CGT_C6000_7.3.1
    CGT_C674_INSTALL_DIR     =
    CGT_C674_ELF_INSTALL_DIR =
    CGT_M3_ELF_INSTALL_DIR   =
    CGT_A8_ELF_INSTALL_DIR   =
    EXEC_DIR                 = /home/eswar/vtobbc/syslink/ti/target_fs

    But still i'm getting same error. and at the end end trace message coming.

    What i can do now to resolve error?