• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 467 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 samples runtime error

Ben Clarke
Prodigy 40 points


I am running into an error trying to run the Syslink sample programs provided in the SDK with Syslink v 2_00_00_56. I was able to successfully compile both the HLOS and RTOS side applications but when I try to run procmgr.exe on the notify sample xe674 I get an error on ProcMgr_load() shown below. I tried loading several of the DSP samples and each seem to hit the same error at ProcMgr_load(). I tried disabling all video driver related modules as indicated by the install guide but the error still occurs.

Do I need to do any additional config such as enabling something in the PRCM to get the c674 to run? I am using the syslink.ko module shipped with the sdk, do I need to recompile it?

Thanks in advance.

 

root@c6a816x-evm:/usr/bin# procmgrapp.exe 0 /notify_ti81xx_dsp.xe674
ProcMgrApp sample application
Entered ProcMgrApp_startup
ProcMgr_attach status: [0x97d2000]
After attach: ProcMgr_getState
    state [0x1]
Error in ProcMgr_load [0x83046005]
Leaving ProcMgrApp_startup
Press enter to continue and perform shutdown ...

Entered ProcMgrApp_shutdown
Assertion at Line no: 127 in /Arago/netra/arago-tmp/work/c6a816x-evm-none-linux-gnueabi/ti-syslink-02_00_00_56-r1i/syslink_02_00_00_56_alpha2/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/utils/hlos/Memory.c: (size > 0) : failed
Assertion at Line no: 261 in /Arago/netra/arago-tmp/work/c6a816x-evm-none-linux-gnueabi/ti-syslink-02_00_00_56-r1i/syslink_02_00_00_56_alpha2/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/utils/hlos/knl/osal/Linux/MemoryOS.c: (size > 0) : failed
Assertion at Line no: 304 in /Arago/netra/arago-tmp/work/c6a816x-evm-none-linux-gnueabi/ti-syslink-02_00_00_56-r1i/syslink_02_00_00_56_alpha2/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Linux/IpcDrv.c: (status >= 0) : failed
Ipc_control Ipc_CONTROLCMD_STOPCALLBACK status: [0xffffffff]
ProcMgr_stop status: [0x6a85000]
After stop: ProcMgr_getState
    state [0x2]
ProcMgr_unload status: [0x8485f003]
After unload: ProcMgr_getState
    state [0x2]
ProcMgr_detach status: [0x6a85000]
After detach: ProcMgr_getState
    state [0x0]
ProcMgr_close status: [0x0]
Leaving ProcMgrApp_shutdown
root@c6a816x-evm:/usr/bin#

  • 0
    Guru 10685 points

    Sod it. I now get exactly the same error myself in EZSDK 5.00.00.56!

    root@c6a816x-evm:/usr/bin# procmgrapp.exe 0 /notify_ti81xx_dsp.xe674
    ProcMgrApp sample application
    Entered ProcMgrApp_startup
    ProcMgr_attach status: [0x97d2000]
    After attach: ProcMgr_getState
        state [0x1]
    Error in ProcMgr_load [0x83046005]
    Leaving ProcMgrApp_startup
    Press enter to continue and perform shutdown ...

    Does anyone have any tips on how to fix this? I followed the Syslink Install Guide to the tee in order to build all the apps. Strangely I can run the application fine by itself:

    i.e.

    # /messageqapp.exe 0 messageq_ti81xx_dsp.xe674
    MessageQApp sample application
    MessageQApp_startup entered
    Loading and starting procId [0] with [messageq_ti81xx_dsp.xe674]
    Entered ProcMgrApp_startup
    ProcMgr_attach status: [0x97d2000]
    After attach: ProcMgr_getState
        state [0x1]
    ProcMgr_load status: [0x3046000]
    After load: ProcMgr_getState
        state [0x3]
    ProcMgr_start passed [0x6a85000]
    After start: ProcMgr_getState
        state [0x4]
    Leaving ProcMgrApp_startup
    ProcMgrApp_startup status [0]
    Leaving MessageQApp_startup 0
    Entered MessageQApp_execute
    MessageQApp_threadHandler entered
    Registering heapId 0 with MessageQ for procId: 0
    MessageQ_create name MSGQ_30  status [0x0] : procId [0]
    Sending synchronizaion notification to ProcId: 0
    Sent synchronizaion notification to ProcId: 0
    MessageQ_open Status [0x0] : procId [0]
    MessageQApp_queueId  [0x0] : procId [0]
    Sending a message #100 to 0                                          
    Sending a message #200 to 0                                          
    Sending a message #300 to 0                                          
    Sending a message #400 to 0                                          
    Sending a message #500 to 0
    Sending a message #600 to 0
    Sending a message #700 to 0
    Sending a message #800 to 0
    Sending a message #900 to 0
    Sending a message #1000 to 0
    Leaving MessageQApp_threadHandler 0
    Leaving MessageQApp_execute
    Entered MessageQApp_shutdown()
    Shutting down procId [0]
    Entered ProcMgrApp_shutdown
    Ipc_control Ipc_CONTROLCMD_STOPCALLBACK status: [0x97d2000]
    ProcMgr_stop status: [0x6a85000]
    After stop: ProcMgr_getState
        state [0x2]
    ProcMgr_unload status: [0x0]
    After unload: ProcMgr_getState
        state [0x2]
    ProcMgr_detach status: [0x6a85000]
    After detach: ProcMgr_getState
        state [0x0]
    ProcMgr_close status: [0x0]
    Leaving ProcMgrApp_shutdown
    ProcMgrApp_shutdown status [0]
    Leaving MessageQApp_shutdown()

    Thanks,
    Ralph