Problems running C6xtest

Hi Vimal,

I assume you meant the firmware file "./component-sources/omx_05_02_00_30/bin/dm81xx/bin/ti816x-evm/dm81xx_c6xdsp_debug.xe674" as it will be running on the DSP, not the media controllers?

The program runs a bit further now but I get this error repeatedly now:

# insmod /syslink.ko
SysLink version : 2.00.05.85
SysLink module created on Date:Feb 24 2012 Time:10:34:20
mdev used greatest stack depth: 5176 bytes left
# firmware_loader 0 dm81xx_c6xdsp_debug.xe674 start
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 0 start Successful
# /c6xtest_a8host_debug.xv5T
 Vlpb-Copy example
===============================

Starting threads
Assertion at Line no: 430 in /home/ralphc/ezsdk/ti-ezsdk_dm816x-evm_5_03_01_15/component-sources/syslink_2_00_05_85/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../.
./ti/syslink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (status >= 0) : failed
Assertion at Line no: 430 in /home/ralphc/ezsdk/ti-ezsdk_dm816x-evm_5_03_01_15/component-sources/syslink_2_00_05_85/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../.
./ti/syslink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (status >= 0) : failed
Assertion at Line no: 430 in /home/ralphc/ezsdk/ti-ezsdk_dm816x-evm_5_03_01_15/component-sources/syslink_2_00_05_85/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../.
./ti/syslink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (status >= 0) : failed
Assertion at Line no: 430 in /home/ralphc/ezsdk/ti-ezsdk_dm816x-evm_5_03_01_15/component-sources/syslink_2_00_05_85/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../.
./ti/syslink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (status >= 0) : failed
Assertion at Line no: 430 in /home/ralphc/ezsdk/ti-ezsdk_dm816x-evm_5_03_01_15/component-sources/syslink_2_00_05_85/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../.
./ti/syslink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (status >= 0) : failed

My boot arguments include "notifyk.vpssm3_sva=0xBF900000" so I'm not sure what this means.

Ralph

Okay, it's working now. I think my syslink.ko was out of sync with my kernel configuration.

Ralph

Dear Ralph,

I am using the latest EZSDK, 5.03.01.15 for TI816x/ AM389x board and trying to run the Gstreamer application.

I am getting exactly the same error as you from syslink while running the gstreamer app.

Here is what it happens

root@dm816x-evm:~# gst-launch-0.10 -v filesrc location=seas.mov ! qtdemux name=
demux demux.audio_00 ! queue ! faad ! alsasink demux.video_00 ! queue ! nal2byte
stream_h264 ! omx_h264dec ! omx_scaler ! omx_ctrl display-mode=OMX_DC_MODE_108
0P_60 ! gstperf ! omx_videosink
Assertion at Line no: 445 in /home/PRDVF/syslink_85/syslink_2_00_05_85/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Linux/SharedRegionDrv.c: (heapHandle != NULL) : failed
Assertion at Line no: 1344 in /swcoe/sdk/cm/netra/arago-tmp/work/dm816x-evm-none-linux-gnueabi/ti-syslink-2_00_05_85-r4i/syslink_2_00_05_85/packages/ti/syslink/ipc/hlos/usr/HeapMemMP.c: (hpHandle != NULL) : failed
gst-launch-0.10: DmmDelegateHeap.c:193: DmmDelegate_createIpcHeap: Assertion `(heapHandle != 0)' failed.
Aborted
root@dm816x-evm:~#

Please let me know how you solved this.

Thanks in Advance.

Regards,

Salih

All I can suggest is that you run "make clean" in the root of EZSDK followed by "make" in order to rebuild all components of the EZSDK. It is possible some elements of your system are built against different versions or configurations of one another.

Ralph

Hi,  Ralph

How did you solve the problem. Now I have the same problem with you,  please give me some suggestions how I can go about it. Thanks in advance.

Thanks

zhong

Hi, I recommend rebuilding your syslink module against the correct kernel headers for your current kernel.

Ralph

Hi Ralph

Thanks for your recommendation. I do the jobs according to your suggsition, but the question is still  unsolved, at least in one point, I can sure that drivers and kernel are not matched is the key to the question.

zhong