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.

C6Accel Application on EZSDK 5.04.00.11 Kernel and File System

Other Parts Discussed in Thread: TVP7002

Hey guys.

A few months ago I was developing on EZSDK 5.01.01.80 with C6Accel and the app ran on DM816x EVM. Recently I need video capture feature which was not implemented on that version. When I migrated to EZSDK 5.04.00.11 and suddenly found C6Accel obsolete. How do I make my old app run on the new kernel and file system?

I once copied the old c6accel_app and ran it but got something like this:

root@dm816x-evm:~/dm816x-evm/c6accel_applications# ./c6accel_app
****************************************************************Unable to handle kernel NULL pointer dereference at
virtual address 00000010
**************
pgd = cdd50000
Sample applicati[00000010] *pgd=8e782031on for testing k, *pte=00000000ernels in C6Acce, *ppte=00000000l started.
****
****************Internal error: Oops: 17 [#1]
last sysfs file: /sys/module/pvrsrvkm/initstate
Modules linked in: cmemk bufferclass_ti omaplfb pvrsrvkm ipv6 ti81xxhdmi ti81xxvin tvp7002 ti81xxvo ti81xxfb vpss sy
slink
CPU: 0 Not tainted (2.6.37 #1)
PC is at DLOAD_query_symbol+0x1c/0x90 [syslink]
LR is at ElfLoader_getSymbolAddress+0xa8/0x104 [syslink]
pc : [<bf013844>] lr : [<bf010588>] psr: a0000013
sp : cdd59d48 ip : cdd59d80 fp : cdd59d7c
r10: bf0957e9 r9 : 00000000 r8 : cdd59e70
r7 : 00000000 r6 : bf0957e9 r5 : db5d4000 r4 : db5da000
r3 : cdd59e70 r2 : bf0957e9 r1 : 00000000 r0 : 00000000
Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: 8dd50019 DAC: 00000015
Process c6accel_app (pid: 1440, stack limit = 0xcdd582e8)
Stack: (0xcdd59d48 to 0xcdd5a000)
9d40: cdd59ddc cdd59e70 e300152d db5da000 db5d4000 bf0957e9
9d60: 00000000 cdd59e70 cdd58000 00000000 cdd59db4 cdd59d80 bf010588 bf013834
9d80: 00000000 bf0957e9 cdd59e70 cdd59d98 c01b5bd8 db5d4000 cdd59e70 bf0957e9
9da0: 00000000 00000000 cdd59de4 cdd59db8 bf001c0c bf0104ec 00000000 bf0957e9
9dc0: cdd59e70 bf029a08 d72bc000 db5e6000 bf0957e9 cdd59e70 cdd59e1c cdd59de8
9de0: bf0053d4 bf001b48 00000000 bf0957e9 cdd59e70 c0084c8c 00000000 bf0fb684
9e00: bf0fb684 bf0fb8c0 00000000 00000000 cdd59ea4 cdd59e20 bf018fb0 bf005230
9e20: 00000000 cdd59e30 c01f6000 c01f5fa4 00000000 d3518d08 cdd59e74 cdd59e48
9e40: c01f74a4 c01f5ff4 c03ba940 00000002 0000000a d23b8b88 00000001 a0000013
9e60: d23b8800 d23b90a7 cdd59e84 cdd59e78 c01f5fe4 c01febf8 cdd59e9c babe0002
9e80: 00000000 00000000 bf0fb8c0 40f10c6c cdd58000 00000000 cdd59ecc cdd59ea8
9ea0: bf04d574 bf018f34 babe0002 00000000 40f10c6c c014f497 bf0fb8c0 00000005
9ec0: cdd59ef4 cdd59ed0 bf086540 bf04d4b8 c014f497 40f10c6c d2c14e88 00000000
9ee0: d2016280 00000005 cdd59f04 cdd59ef8 c00d305c bf0864e4 cdd59f74 cdd59f08
9f00: c00d376c c00d3040 40303000 d23be800 c01dfe20 d23b76c0 4f9dc5ca 09896800
9f20: 000dd128 d23be800 40303000 cdd59f70 000000a7 40303000 cdd58000 00000000
9f40: 00000001 000000a7 00000000 00000000 40f10c6c c014f497 00000005 d2016280
9f60: cdd58000 00000000 cdd59fa4 cdd59f78 c00d3804 c00d3278 e1a02001 00000001
9f80: 000dd128 40f10c6c c014f497 000dc204 00000036 c0045fa8 00000000 cdd59fa8
9fa0: c0045e00 c00d37b8 40f10c6c c014f497 00000005 c014f497 40f10c6c 00000001
9fc0: 40f10c6c c014f497 000dc204 00000036 00000100 0000ff9f 0000033c 00000000
9fe0: 000dc248 40f10c40 0006a1f4 40294aec 20000010 00000005 000149b8 000153a5
Backtrace:
[<bf013828>] (DLOAD_query_symbol+0x0/0x90 [syslink]) from [<bf010588>] (ElfLoader_getSymbolAddress+0xa8/0x104 [sysli
nk])
[<bf0104e0>] (ElfLoader_getSymbolAddress+0x0/0x104 [syslink]) from [<bf001c0c>] (Loader_getSymbolAddress+0xd0/0x160
[syslink])
r8:00000000 r7:00000000 r6:bf0957e9 r5:cdd59e70 r4:db5d4000
[<bf001b3c>] (Loader_getSymbolAddress+0x0/0x160 [syslink]) from [<bf0053d4>] (ProcMgr_getSymbolAddress+0x1b0/0x280 [
syslink])
r7:cdd59e70 r6:bf0957e9 r5:db5e6000 r4:d72bc000
[<bf005224>] (ProcMgr_getSymbolAddress+0x0/0x280 [syslink]) from [<bf018fb0>] (Platform_stopCallback+0x88/0x490 [sys
link])
[<bf018f28>] (Platform_stopCallback+0x0/0x490 [syslink]) from [<bf04d574>] (Ipc_control+0xc8/0x14c [syslink])
[<bf04d4ac>] (Ipc_control+0x0/0x14c [syslink]) from [<bf086540>] (IpcDrv_drvioctl+0x68/0x298 [syslink])
r7:00000005 r6:bf0fb8c0 r5:c014f497 r4:40f10c6c
[<bf0864d8>] (IpcDrv_drvioctl+0x0/0x298 [syslink]) from [<c00d305c>] (vfs_ioctl+0x28/0x44)
r6:00000005 r5:d2016280 r4:00000000
[<c00d3034>] (vfs_ioctl+0x0/0x44) from [<c00d376c>] (do_vfs_ioctl+0x500/0x540)
[<c00d326c>] (do_vfs_ioctl+0x0/0x540) from [<c00d3804>] (sys_ioctl+0x58/0x7c)
[<c00d37ac>] (sys_ioctl+0x0/0x7c) from [<c0045e00>] (ret_fast_syscall+0x0/0x30)
r8:c0045fa8 r7:00000036 r6:000dc204 r5:c014f497 r4:40f10c6c
Code: e24dd00c e50b3030 e1a09001 e1a0a002 (e5906010)
****************---[ end trace 8e61016b822e760d ]---
******************************************

  • Hi,

        The C6accel is diccontinued from EZSDK 05.03 release onwards.

        Latest release 05.05.00.04 available. You can download this from http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/latest/index_FDS.html

       There are couple of things you need to ensure for running C6accel on latest EZSDK,

       - EZSDK follows the memory map defined in http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map, Ensure to change the C6accel as per this.

       - Do a incremental integration.

         - Initially include only C6accel app, Not loading media controller (Video-M3, VPSS-M3) application, for which you need to ensure the resources (Shared region, etc...) are aligned.

    Thanks & Regards,

    Velan

  • Hi

       Also, Please refer to link http://processors.wiki.ti.com/index.php/EZSDK_Feature_List which details about the features supported in each of the releases.

    Thanks & Regards,
    Velan

  • Hey Velan,

    I checked out the memory mapping document and tried quite a number of combinations. But actually when I tried to run c6accel_app example it crashes at Engine_open() function within C6accel_create(). It seems to be somewhat related to codec_engine. Does codec_engine need to be modified also?

    Regards,
    Hongdong 

  • Hongdong,

             This could be due to two reason.

             - Other cores are loaded (Ensure that Video-M3 and VPSS-M3 are not loaded)

             - DSP codec server still not in the expected configuration, First run the Codec engine examples.

             you can also enable CE traces by running export CE_DEBUG=[1,2,3]

    Thanks & Regards,

    Velan