Syslink Problem: ProcMgr_load hangs

Lee Holeva

Whenever I attempt to load any DSP code with IPC functions ProcMgr_load hangs. It returns whenever I attempt to load non-IPC code. I see:

ProcMgr Attach status = 0x97d2000

ProcMgr state after attach = 1

I'm using procId=0 for the DSP of the c6a816x EVM. The ARM side code is copied from the ProcmgrApp example that came with EZSDK. Syslink is version 02_00_00_56.

Am I missing something or do I simply need to wait for the beta release?

Update:

I rebuilt my ARM-side code with ProcMgr.c as part of my project and put a couple of Osal_printfs in to see what is happening. The process is getting stuck after the call to ProcMgrDrvUsr_ioctl in the syslink.ko module. The ioctl never returns. I'm using the pre-built syslink.ko as it came with EZSDK.

Lee Holeva

over 14 years ago

0 Lee Holeva over 14 years ago

Genius 4615 points

^{Not sure why this is, but the app is no longer hanging, but now I'm getting an error code after load:}

^{root@c6a816x-evm:~/c6a816x-evm/r1397# ./runDSP_debug.xv5T DSPtasks.out
ProcMgr_attach status: 0x97d2000
After attach: ProcMgr_getState
state [0x1]
Error in ProcMgr_load: status = 0x8485f003
Registered remote event number 10 with Notify module for processor 0
Registered remote event number 11 with Notify module for processor 0
Registered remote event number 12 with Notify module for processor 0
Registered remote event number 13 with Notify module for processor 0
Error in Notify_sendEvent for processor 0Status = -7
Press Return to cleanup and exit}

^{Error in Notify_sendEvent for processor 0Status = -7
Unregistered remote event number 10 with Notify module. Status [0x0]
Unregistered remote event number 11 with Notify module. Status [0x0]
Unregistered remote event number 12 with Notify module. Status [0x0]
Unregistered remote event number 13 with Notify module. Status [0x0]
Ipc_control Ipc_CONTROLCMD_STOPCALLBACK status = -1
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]}

^{The promgrapp that came with the EZSDK also gives an error code:}

^{oot@c6a816x-evm:~/c6a816x-evm/r1397# ./procmgrapp.exe 0 DSPtasks.out
ProcMgrApp sample application
Entered ProcMgrApp_startup
ProcMgr_attach status: [0x97d2000]
After attach: ProcMgr_getState
state [0x1]
ProcMgr_load status: [0x3046000]
After load: Error in Ipc_control Ipc_CONTROLCMD_LOADCALLBACK: -1
Leaving ProcMgrApp_startup
Press enter to continue and perform shutdown ...}

^{Entered ProcMgrApp_shutdown
Ipc_control Ipc_CONTROLCMD_STOPCALLBACK status: [0xffffffff]
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}

^{I've also tried the NotifyApp example and this works only locally, the message passing fails going between the ARM and DSP.}

^{Lee Holeva}

0 Ben Clarke over 14 years ago in reply to Lee Holeva

Prodigy 40 points

Lee

I am getting this same error:

root@c6a816x-evm:~/c6a816x-evm/r1397# ./runDSP_debug.xv5T DSPtasks.out
ProcMgr_attach status: 0x97d2000
After attach: ProcMgr_getState
state [0x1]
Error in ProcMgr_load: status = 0x8485f003

Did you find a solution to the problem with procMgr_load()?

Thanks.

0 Lee Holeva over 14 years ago in reply to Ben Clarke

Genius 4615 points

Ben Clarke said:

Did you find a solution to the problem with procMgr_load()?

Origially I could not get the DSP-side code to build in EZSDK so went to CCS, but at the time I did not know about the missing Syslink rtos library, without which the code builds, but will not run. When I figured-out how to build the DSP-side code using xdc in the SDK, with the Syslink rtos library, the problem of procMgr hanging went away.

Lee Holeva

Processors

Processors forum

Syslink Problem: ProcMgr_load hangs