De-interlacing on OMAP3530

Deinterlacer working:-

It will take current and previous frame for processing and gave deinterlaced frame as output.

This is motion compensated algorithm.

Supporting image resolutions are PAL and NTSC.

Tested application:- Capturing the frame from DVD player/ camera, deinterlacing, writing H.264BP encoded data into a file and displying the deinterlacer content on to LCD.

1. Its working fine at ARM frequency 720MHz and DSP @ 520MHz. We are getting 25fps for PAL input and DSP load is 90%

2.  Its working fine at ARM frequency 720MHz and DSP @ 520MHz. We are getting 29fps for NTSC input and DSP load is 95%

Hi Anil,

I am trying to do the same thing you have mentioned in the post. The processor I am using is OMAP 3530.

"Capturing the frame from camera, deinterlacing, encoded data into a file and displaying the deinterlacer content on to LCD"

For this I need the latest source code and corresponding documents.  

I am  having DVSDK version 3.01.00.10 and 4.01.00.09 installed. There is no change in documents, and also the deinterlacer code looks similar except a minor changes.

 In both the versions the documents are for CCS 3.x, but I am having CCS4.0. Could you please help me in executing the sample deinterlacer application using CCS4.0

Thanks,

HMT

Hi Thalib,

I had executed the code on CCS 3.x not on 4.0 version, mostly the same code will execute on CCS4.0 as well with out any issues.

Please try to build and execute the code/application from CCS 4.0 and tell me if you are facing any problems. Mostly we have to update the versions of different packages (DSP/BIOS, framework components, etc) on .pjt file

Regards

AnilKumar

Hi Anil,

Thanks for your reply. I have imported deinterlace test application into  CCS4.0. After resolving some build dependency I am able to pass the build stage but it fails in linking stage with following error messages.

 'Finished building: D:/CCS/DSP/deinterlacer/app/Client/Test/Src/tsc_h.asm'
' '
'Building target: ../Out/i2p_test.out'
'Invoking: Linker'
"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 6.1.19/bin/cl6x" -@ccsLinker.opt -o "../Out/i2p_test.out"
<Linking>
"../link.i2p.cmd", line 75: error: conflicting placement methods specified for
".text_rts"
"../link.i2p.cmd", line 79: error: conflicting placement methods specified for
".bss_rts"
"../link.i2p.cmd", line 78: warning: no matching section

undefined first referenced
symbol in file
--------- ----------------
_I2P_TI_IDMA3 D:/CCS/DSP/deinterlacer/app/Build/Obj/test_main.obj
_I2P_TI_II2P D:/CCS/DSP/deinterlacer/app/Build/Obj/test_main.obj
_I2P_TI_exit D:/CCS/DSP/deinterlacer/app/Build/Obj/test_main.obj
_I2P_TI_init D:/CCS/DSP/deinterlacer/app/Build/Obj/test_main.obj
_II2P_PARAMS D:/CCS/DSP/deinterlacer/app/Build/Obj/test_main.obj

error: unresolved symbols remain
"../link.i2p.cmd", line 29: error: undefined symbol "_I2P_TI_II2P" used in
expression
error: errors encountered during linking; "../Out/i2p_test.out" not built

>> Compilation failure
C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** [../Out/i2p_test.out] Error 1
C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: Target `all' not remade because of errors.
Build complete for project i2p_test

Could you please help me in resolving this issue.

Thanks,

HM Thalib

Hi Thalib,

I moved the deinterlacer project from CCS3.3 to CCSV4 (version 4.2) and I am seeing these errors only

"../link.i2p.cmd", line 75: error: conflicting placement methods specified for
".text_rts"
"../link.i2p.cmd", line 79: error: conflicting placement methods specified for
".bss_rts"
"../link.i2p.cmd", line 78: warning: no matching section

Work around:- (Above errors can be removed by below modification)

Before

.text_rts > DDR2

{..} > DDR2

.bss_rts  > DDR2

{..} > DDR2

 After

.text_rts

{..} > DDR2

.bss_rts

{..} > DDR2

 Remaining errors I am not seeing

Regards

AnilKumar

Hi Anil,

Thanks for the reply,

I have already compiled the code, but commenting out the entire .text_rts and .bss_rts section.   After the above post I have made the modification and it compiles neatly but with the below warning.

"../link.i2p.cmd", line 78: warning: no matching section

Is there will be any issue because of the above warning. is that OK.

The remaining errors were due to missing library. After adding the library, they disappeared.

Once again thanks  for your reply. It solved my problem.

Regards,

Mohamed Thalib H.

Hi Mohamed,

With the above warning, it won't be any problem.

Please go through this link for details (similar to our case)

http://e2e.ti.com/support/development_tools/f/81/t/32531.aspx

Regards

AnilKumar

Hi Anil,

Thanks for the clarification.

I have one more doubt. I want to execute this test app for OMAP3530,  I have configured the target configuration file for OMAP 3530 EVM and compilation is also over.

But in "link.i2p.cmd" file, in comments section it is given as below.

* @file lnk.i2p.cmd
* @brief Linker command file for deinterlacer algorithm.
* This is for use with the C64xx Device Simulator.
*
* If this tutorial is run on a different execution platform, this file
* may need changes to account for differences in the memory map

From the comment we can see this linker map file is for C64xx device, for OMAP3530 do I need to do any modification.

Thanks,

Mohamed Thalib H.

Hi Mohamed,

Initially the file is created for C64XX platform, so the comment is like that. OMAP3530 is comes under the same category (C64XX DSP + Cortex A8) so no need to modify the file.

Regards

AnilKumar

Hi Anil,

In second post in this thread, you have mention that this de-interlace is testing by capturing frame from camera and processing. Is there a source of demo application that is capable of directly running on top of a OS (Linux) without the need of a debugger. If so then, could you please provide the source code of the application.

Regards,

Mohamed Thalib H

Hi Anil,

To explain in more detail, there are 2 requirements from our side.

1. In second post in this thread, you have mentioned that you were able to take the source from the camera and de-interlace and save the h.264 encoded data to a file/display it on LCD. Is the source code of your tests available with the DVSDK? If not, can that be shared ? We are trying to do something very similar here. We want to use an NTSC camera source, deinterlace and display it on the LCD. If we have the source with which you had tested the performance it would be of great help. Please let us know.

2. Also we wanted to know how we can use only the Linux during run time. We want to get away with the CCS for loading the binary in future. Any guidance on this is appreciated.

Regards,

Mohamed Thalib H

Hi Mohamed,

1. For 1st requirement, you can use the dmai applications which meet you requirement

you can find the dmai apps inside DVSDK at dmai_x_xx_xx_xx\packages\ti\sdo\dmai\apps\video_loopback_deinterlacer. 

2. In tis wiki http://processors.wiki.ti.com/index.php/Getting_started_with_IUNIVERSAL you can find the link to

IUNIVERSAL Examples examples contains the linux side test application. Same way we have to convert our deinterlacer algorithm to linux side test applications. (base app is present in the above examples (requirement 1)).

Regards

AnilKumar

Hi Anil,

Thanks for your help in pointing out the source code.  I will look into it.

Meanwhile I have compiled the deinterlace test app using CCS4.2 and having the following configuration of tool and target

1. XDS510USB Plus JATG Emulator

2. OMAP3530 EVM by Mistral.

I would like to execute the test app in above target. While trying to execute the test app in target using CCS4 I am getting a Message that "You are not licensed to use the currently configured connect -type". I am currently using free license. Based on this my questions are below.

1. Do I really need the platinum license to connect using XDS510USB.

2.I have already used XDS510USB and CCS4 to connect with DM355EVM. In the configuration list there is a septate configuration to connect to DM355EVM. Likewise is there any such target configuration to connect with OMAP3530 EVM using XDS510USB Plus.

Regards,

Mohamed Thalib H.

Hi Mohamed,

I am not sure about the license issue.

Regarding to the CCS configuration file you have to use OMAP3530 related configuration file. While doing the configuration select "connection" as Spectrun Digital XDS510USB Emulator and under "Board or Device"  type omap then you can find the configuration.

Regards

AnilKumar

Hi Anil,

I am trying to testing the video_loopback_deinterlacer application. When running the application I got below error.

./video_loopback_deinterlacer_omap3530.x470MV -c deinterlacer -o auto
Starting application...
Failed to open codec engine: encode

By searching the TI forum I found this is due to missing codec engine. [http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/t/6216.aspx]. This thread suggest to build the dvsdk and install the codes/libraries.

While building the dvsdk I got following error.

======== Building decode ========
Configuring application using decode.cfg

configuring decode.xv5T from package/cfg/decode_xv5T.cfg ...
Info: Configuring engine named 'decode' from the info file for DSP server './bin/cs.x64P',
located in package 'ti.sdo.server.cs':
Target app will look for the DSP server image 'cs.x64P' in its current directory.
Adding codec 'aachedec' (ti.sdo.codecs.aachedec.ce.AACHEDEC), scratch groupId=1
Adding codec 'g711dec' (ti.sdo.codecs.g711dec.ce.G711DEC), scratch groupId=1
Adding codec 'g711enc' (ti.sdo.codecs.g711enc.ce.G711ENC), scratch groupId=1
Adding codec 'h264dec' (ti.sdo.codecs.h264dec.ce.H264DEC), scratch groupId=0
Adding codec 'h264enc' (ti.sdo.codecs.h264enc.ce.H264ENC), scratch groupId=0
Adding codec 'jpegdec' (ti.sdo.codecs.jpegdec.ce.JPEGDEC), scratch groupId=0
Adding codec 'jpegenc' (ti.sdo.codecs.jpegenc.ce.JPEGENC), scratch groupId=0
Adding codec 'mpeg2dec' (ti.sdo.codecs.mpeg2dec.ce.MPEG2DEC), scratch groupId=0
Adding codec 'mpeg4dec' (ti.sdo.codecs.mpeg4dec.ce.MPEG4DEC), scratch groupId=0
Adding codec 'mpeg4enc' (ti.sdo.codecs.mpeg4enc.ce.MPEG4ENC), scratch groupId=0
Adding codec 'deinterlacer' (ti.sdo.codecs.deinterlacer.ce.I2P), scratch groupId=0
Info: Reading DSP memory map from the info file for DSP server './bin/cs.x64P',
located in package 'ti.sdo.server.cs':
js: "/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530/decode/decode.cfg", line 33: XDCException: xdc.PACKAGE_NOT_FOUND: /home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/packages/ti/sdo/simplewidget/package.xdc found along the package path, but no schema file was found. Ensure that the package 'ti.sdo.simplewidget' is completely built.
"./package/cfg/decode_xv5T.cfg", line 474
"./package/cfg/decode_xv5T.cfg", line 429
gmake: *** [package/cfg/decode_xv5T.c] Error 1
js: "/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/xdctools_3_16_01_27/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
make[3]: *** [decode_config/linker.cmd] Error 1
make[3]: Leaving directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530/decode'
make[2]: *** [decode] Error 2
make[2]: Leaving directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530'
make[1]: *** [omap3530] Error 2
make[1]: Leaving directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13'
make: *** [demos] Error 2


Again by searching the TI forum I found a solution as said by many in this link [ http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/p/6000/314960.aspx]

I tired the solution give the above link. But I got the following error. 

thalib@SilentStorm:$cd packages/ti/sdo/simplewidget/
thalib@SilentStorm:$make

Building package interface for simplewidget..
making package.mak (because of package.bld) ...
js: "/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/xdctools_3_16_01_27/packages/xdc/xdc.tci", line 546: XDCException: xdc.bld.ROOTDIR_NOT_SET: 'rootDir' has not been set for the target gnu.targets.arm.GCArmv5T; define 'rootDir' in /home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dmai_2_05_00_12/packages/config.bld
all files complete.
thalib@SilentStorm:$



From the error message I tried to change the rootDir variable. but didn't work. And no clue why this happens. Could you please help

Regards,

HM Thalib.

Hi Thalib,

From the top level DVSDK directory do make clean then check for all the package name in Rules.make file is replicating your dvsdk installed packages.

If every package name is pointing properly then do "make".

After building the entire DVSDK try to build the dmai applications.

Make sure that dmai_2_05_00_12/Rules.make variables are pointing to correct DVSDK package are not?

Then move to dmai folder and do "make"

Steps to follow:

1. dvsdk_3_01_00_10$ make clean

2. dvsdk_3_01_00_10$ vi Rules.make (make sure that all package names are proper)

3. dvsdk_3_01_00_10$ make

4. dvsdk_3_01_00_10$ make install

5. dvsdk_3_01_00_10$ cd dmai_2_05_00_12

6. dmai_2_05_00_12$ vi Rules.make (make sure that all package names are proper)

7. dmai_2_05_00_12$ make clean

8. dmai_2_05_00_12$ make

9. dmai_2_05_00_12$ make install

Then run the demo from target.

Regards

AnilKumar

Hi Anil,

I freshing installed the dvsdk 3.01.00.10 and verified the package names in main Rules.make, also verified the Rules.make file in dami package.

I have did make clean. and make check to verify the Rules.make file is ok.

When I did executed make in the dvsdk top directory, I got the bellow error.

DMAI applications can be found under /home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dmai_2_05_00_12/packages/ti/sdo/dmai/apps
To install them to /home/thalib/project/dsp_proj/targetfs
Execute 'make dmai_install'
make -C /home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13 omap3530 DVSDK_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10 XDC_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/xdctools_3_16_01_27 CE_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/codec_engine_2_25_02_11 FC_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/framework_components_2_25_01_05 CMEM_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/linuxutils_2_25_02_08 CODEC_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/cs1omap3530_1_01_00 XDAIS_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/xdais_6_25_02_11 LINK_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dsplink_linux_1_65_00_02 DMAI_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dmai_2_05_00_12 MVTOOL_DIR=/opt/codesourcery/arm_g++_lite_2009q1-203/ CC=/opt/codesourcery/arm_g++_lite_2009q1-203//bin/arm-none-linux-gnueabi-gcc AR=/opt/codesourcery/arm_g++_lite_2009q1-203//bin/arm-none-linux-gnueabi-ar CROSS_COMPILE=/opt/codesourcery/arm_g++_lite_2009q1-203//bin/arm-none-linux-gnueabi- LINUXLIBS_INSTALL_DIR=/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/linuxlibs_3_01 PLATFORM=omap3530
make[1]: Entering directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13'
make -C packages/ti/sdo/simplewidget
make[2]: Entering directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/packages/ti/sdo/simplewidget'
Compiling Button_omap3530.o470MV from Button.c..
Compiling Convert_omap3530.o470MV from Convert.c..
Compiling Font_omap3530.o470MV from Font.c..
Compiling Jpeg_omap3530.o470MV from Jpeg.c..
Compiling Png_omap3530.o470MV from Png.c..
Compiling Screen_omap3530.o470MV from Screen.c..
Compiling Text_omap3530.o470MV from Text.c..

Archiving lib/simplewidget_omap3530.a470MV from Button_omap3530.o470MV Convert_omap3530.o470MV Font_omap3530.o470MV Jpeg_omap3530.o470MV Png_omap3530.o470MV Screen_omap3530.o470MV Text_omap3530.o470MV..

Building package interface for simplewidget..
making package.mak (because of package.bld) ...
js: "/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/xdctools_3_16_01_27/packages/xdc/xdc.tci", line 546: XDCException: xdc.bld.ROOTDIR_NOT_SET: 'rootDir' has not been set for the target gnu.targets.arm.GCArmv5T; define 'rootDir' in /home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dmai_2_05_00_12/packages/config.bld
making package.mak (because of package.bld) ...
js: "/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/xdctools_3_16_01_27/packages/xdc/xdc.tci", line 546: XDCException: xdc.bld.ROOTDIR_NOT_SET: 'rootDir' has not been set for the target gnu.targets.arm.GCArmv5T; define 'rootDir' in /home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dmai_2_05_00_12/packages/config.bld
all files complete.
make[2]: Leaving directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/packages/ti/sdo/simplewidget'

Making all in subdirectory omap3530...
make -C omap3530
make[2]: Entering directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530'

Making all in subdirectory decode...
make[3]: Entering directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530/decode'

======== Building decode ========
Configuring application using decode.cfg

making package.mak (because of package.bld) ...
generating interfaces for package decode_config (because package/package.xdc.inc is older than package.xdc) ...
configuring decode.xv5T from package/cfg/decode_xv5T.cfg ...
Info: Configuring engine named 'decode' from the info file for DSP server './bin/cs.x64P',
located in package 'ti.sdo.server.cs':
Target app will look for the DSP server image 'cs.x64P' in its current directory.
Adding codec 'aachedec' (ti.sdo.codecs.aachedec.ce.AACHEDEC), scratch groupId=1
js: "/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/codec_engine_2_25_02_11/packages/ti/sdo/ce/Engine.xs", line 351: ti.sdo.codecs.aachedec.ce: can't resolve name ti.sdo.ce.ICodec.useCache
"/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530/decode/decode.cfg", line 23
"./package/cfg/decode_xv5T.cfg", line 474
"./package/cfg/decode_xv5T.cfg", line 429
gmake: *** [package/cfg/decode_xv5T.c] Error 1
js: "/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/xdctools_3_16_01_27/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
make[3]: *** [decode_config/compiler.opt] Error 1
make[3]: Leaving directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530/decode'
make[2]: *** [decode] Error 2
make[2]: Leaving directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13/omap3530'
make[1]: *** [omap3530] Error 2
make[1]: Leaving directory `/home/thalib/project/dsp_proj/dvsdk_3_01_00_10/dvsdk_demos_3_01_00_13'
make: *** [demos] Error 2
thalib@Silent

Some thing is failing which I have highlighted in red. could this be the reason.

Not sure what goes wrong.

Regards,

Mohamed Thalib H

Hi Anil,

Based on the recommendation form TI side we have brought  the XDS100v2 USB Emulator. I would like to try execute the previously compiled de-interlace application with your help.

But I am not sure how to setup the XDS100v2 with OMAP3530 EVM Rev D board to exectue the de-interlace app.

Could you please help me in choosing the correct settings for CCS4.2.

Regards,

Mohamed Thalib H.

Anil said:

1. Its working fine at ARM frequency 720MHz and DSP @ 520MHz. We are getting 25fps for PAL input and DSP load is 90%

2.  Its working fine at ARM frequency 720MHz and DSP @ 520MHz. We are getting 29fps for NTSC input and DSP load is 95%

 

Hi Anil.

In your post, you are talking about the C64x+ frequency and its value 520 MHz. What did you do to modify the frequency of the C64x+? In my case, I am working with the omap3530 too, in particular for video decoding tasks and the C64x+ is not able to perform to higher frequencies than 360 MHz. Theoretically, the user's guide of omap3530 makes sure the next frequencies :

ARM/DSP:

720 MHz/520 MHz @1.35V

600 MHz/430 MHz @1.35V

550 MHz/400 MHz @1.27V

However, I am using a function of the DSP/BIOS's API (clk_countspms) and the results is always the same: 360 MHz..

Any suggestion will be grateful!

Thanks in advance

Óscar

 

 

Hi Oscar,

Make sure that you are running the DSP at 520MHz.

How are you changing the frequency?

If you are using PSP_04.02.00.07 then you can change by this way

http://processors.wiki.ti.com/index.php/UserGuidePowerMgmt_PSP_04.02.00.07#cpufreq_.26_SmartReflex

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!

Thanks for your answer AnilKumar, but your suggestion is for the ARM and I was talking about the DSP frequency.

I dont know if modifying the ARM frequency, the DSP frequency changes automatically. Could you verify me that idea please?

Thanks in advance

Óscar

Hi Oscar,

I think it will change the IVA frequency as well if we set OPP6 (arm 720MHz)

After doing this you can check the IVA clock frequency by this script

http://processors.wiki.ti.com/index.php/TI81XX_PSP_PM_Clock_Framework_User_Guide#Using_Script_to_dump_details

$ ./browser rate dpll2_clk

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!

Thank for your answer AnilKumar, but how can I modify the Operating Performance Point for OMAP3530?? I was looking for but I didn't find anything...I have checked the ARM frequency, and its value is 679.56 MHz by means the command cat /proc/cpuinfo. However, I am not able to obtain the DSP frequency...

Any suggestion guys??

Thanks in advance

Óscar

Hi Tsvetolin Shulev,

         Thanks for your answer, I will contact the FAE then,

Regards,

-David

Hi David,

You stated that RidgeRun has an existing NDA, however I wasn't able to find it in our database.  Could you send me the NDA document?

Marcus