Creating my OMX example capture-VPLB-display (OMX_05_02_00_15)

Gabi Gvili

Hi,

I am tiring to create my OMX example that will include capture-VPLB-Display where VPLB is video loop, for this purpose i have done the following:

1. Copied the directory capture-encode to a new directory and renamed it to capture-vplb-display
in ~/ti-ezsdk_dm816x-evm_5_02_02_60/component-sources/omx_05_02_00_15/packages/ti/omx/demos.

2. Changed the makfile in the ~/ti-ezsdk_dm816x-evm_5_02_02_60/component-sources/omx_05_02_00_15/packages/ti/omx/demos/capture-vplb-display directory to compile capture-vplb-display example.

3. Changed the ilclient.c in the directory ~/ti-ezsdk_dm816x-evm_5_02_02_60/component-sources/omx_05_02_00_15/packages/ti/omx/demos/capture-vplb-display to support capture-vplb-display scheme using TI examples capture-encode and c6xtest examples.

4. added in the makefile in ~/ti-ezsdk_dm816x-evm_5_02_02_60/component-sources/omx_05_02_00_15/packages the following lines (similar to capture-encode example):

capture_vlpb_display: capture_vlpb_displayhost

capture_vlpb_displayhost:

ifeq ($(findstring make,$(BUILD_OPTIONS)),make)

$(ECHO) \# Building $(subst host,,$@) executable for core: a8host

$(MAKE) -C $($(subst host,,$@)_EXAMPLES_PATH) CORE=a8host

endif

when i am compiling the example from ~/ti-ezsdk_dm816x-evm_5_02_02_60/component-sources/omx_05_02_00_15/packages, using the command <make capture_vlpb_display> the compilation is endded successfully for the A8 host and an executable for the A8 is created, however i don't see the DSP executable compiled or created anywhere, what, where and how should i do to create the DSP executable?

Thanks,

Gabi

over 14 years ago

0 Archith John Bency over 14 years ago

TI__Intellectual 2910 points

Since you haven't changed any DSP side code, you shouldn't have to recompile the DSP binary. The DSP binary gets generated when you do make omx from the EZSDK top level directory. You can find it in the location:

<OMX_ROOT>/bin/dm81xx/bin/ti816x-evm/dm81xx_c6xdsp_debug.xe674 .

The EZSDK file system by default doesnt load the DSP executable. To add this feature, modify the filesystem's file /etc/init.d/load-hdvicp2-firmware.sh by adding the line in bold:

case "$1" in

start)

echo "Loading HDVICP2 Firmware"

prcm_config_app s

sleep 1

modprobe syslink

sleep 1

firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm816x_hdvicp.xem3 start

echo "Loading DSP Firmware"

firmware_loader 0 /usr/share/ti/ti-media-controller-utils/dm81xx_c6xdsp_debug.xe674 start

This is assuming ofcourse that you have copied the DSP binary above to the location as in the location in the filesystem.

Also, another issue that you will hit when running the use case is that the OMX components on the DSP are instructed to allocate data memory from Share Region #0 which is about 1 MB in size and it will be inadequate for allocating frame sized buffers.

Archith

0 Gabi Gvili over 14 years ago in reply to Archith John Bency

Genius 4120 points

Hi Archith,

Now i think i am hitting the issue of insufficient DSP buffer size, after changing the DSP buffers to 1920x1080x3 i recieve the following error message:

VLPB: Error in OMX_AllocateBuffer() : OMX_ErrorInsufficientResources

How can this problem be overcome?

Can i instruct the OMX DSP component to allocate buffers in another region?

Thanks,

Gabi

0 Gabi Gvili over 14 years ago in reply to Gabi Gvili

Genius 4120 points

Hi Archith,

Regarding my previous question above, of changing the size of DSP OMX component, after looking at the EZSDK memory map in http://processors.wiki.ti.com/index.php/EZSDK_Memory_Map
I see that there is a shared memory region for Host and MC-HDVPSS of 188MB which callled IPC_SR_FRAME_BUFFERS which uses to allocate all video buffers
I have two questions:

Q1. Is it possible to add DSP to share this region as well?

Q2. If the answer to Q1 is positive how can i use this region for DSP OMX buffer allocation?

Thanks,
Gabi

0 Archith John Bency over 14 years ago in reply to Gabi Gvili

TI__Intellectual 2910 points

Gabi,

Can you please re-post the above questions on a separate thread in this forum? This will help in classifying information in the forum better and will help others as well. We will continue this conversation once we have the new thread.

Archith

0 Gabi Gvili over 14 years ago in reply to Archith John Bency

Genius 4120 points

No problem

0 Archith John Bency over 14 years ago in reply to Gabi Gvili

TI__Intellectual 2910 points

Thanks.

Archith

0 Hannes N over 13 years ago

Prodigy 120 points

Hello Gabi,

i already red all corresponding posts of you. i followed strict your way of creating capture_vlpb_display. works. Thanks.

But point 3 (integration of vlpb/modifiy omx chain) has not be done, because it is not clear to me how to get vlpb into chain and check.

Would it be possible to get your iclient.* and iclient_utils.* ? or your capture-encode-example ?

Would be nice. Thanks

Hannes (hema@luisenhain.de)

0 Gabi Gvili over 13 years ago in reply to Hannes N

Genius 4120 points

Hello Hannes,

I am glad to hear that my posts have helped you, i didn't understand exactly what have you succeed to do and what haven't you succeed to do. Meanwhile can you please tell me which TI SOC are you working with? what EZSDK version are you using? what OMX chain are you trying to build?
The most important post for using VLPB is this: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/144078.aspx
Please read it carefully. I have some more interesting posts:

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/154259.aspx

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/155547.aspx

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/207595/748381.aspx#748381

0 Hannes N over 13 years ago in reply to Gabi Gvili

Prodigy 120 points

Hello Gabi,

thank you very much for your answer. I have a DM8148EVM ezsdk 5.4.0.11, omx 5.2.0.38.

At this point I still try to recreate your example to get a first step towards a chain like ISS->CAP->VLPB (DSP image processing)->DEI->ENC->STREAM. It seems that today i just arrived the "VLPB: Error in OMX_AllocateBuffer()" described in this example. Tomorrow I try to understand howto modify these memory definitions/files... to get the current chain running. I still have no idea if my implementation of the chain does work:

VFCC->DEI->VLPB->VFDC
\_>VIDENC

Do you know where to get a link/description how to remote debug the vlpb_component code (running on dsp). because i did not really succeed in modifying src/ti/omx/comp/vlpb/omx_vlpb.c component of c6xtest itself. Changing & compiling ok - but changes it did not write a file (enable VLPB_RECORD_BITSREAM) or TIMM_OSAL_Memcpy (buttom) did not modify frame buffer and printf cannot be seen... for me it is still not clear how this componentcode is transported to the dsp.

Thanks

Hannes

0 Gabi Gvili over 13 years ago in reply to Hannes N

Genius 4120 points

Hi Hannes,

I am sorry but at the moment what you want to do is not possible in EZSDK ver 5.04, i did that with the help of TI employee Archith John Bency in EZSDK ver 5.02 and it also worked on EZSDK ver. 5.03, but it is no longer working with EZSDK ver 5.04.

Please see also the following:

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/179107.aspx

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/210846/748062.aspx#748062

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/210109/756425.aspx#756425

The DSP executable is in <OMX_ROOT>/bin/dm814x/debug/dm814x_xxxxx.xe674 and there is also a map file that you can see all the symbols(function, variables) used by the DSP.

Remote debugging of the DSP is done with code composer and JTAG HW emulator (blackhawk http://www.blackhawk-dsp.com/products/ or spectrum digital http://www.spectrumdigital.com/index_orig.php?cPath=22), code composer can be downloaded for a 90 days trial here:

http://processors.wiki.ti.com/index.php/Download_CCS?DCMP=dsp-mc-opemmp-120828&HQS=dsp-mc-opemmp-pr-sw3

Gabi

0 Thomas Lo over 13 years ago in reply to Gabi Gvili

Expert 1560 points

Hi,

after reading the post, does it mean it is not possible to pass a video frame to DSP for processing through VLPB omx component because buffer can't be allocated due to insufficient memory size,

which require change the configuration for DSP to use the shared region, but it is not possible because the value DioFQCFG_module->fqBufInfoCtx.curSrRegionBuf can't be changed?

does i understand it correctly?

Thanks

0 Gabi Gvili over 13 years ago in reply to Thomas Lo

Genius 4120 points

Yes, You understood it correctly, the geniuses from TI didn't think anyone would need to process video frames using the VLPB on the DSP. Can you imagine that?
The solution they gave me was for EZSDK 5.02 and they didn't make it the default use case even now in EZSDK 5.04.

0 Thomas Lo over 13 years ago in reply to Gabi Gvili

Expert 1560 points

Hi Gabi,

Then what is the way you are using now in order to use DSP for frame processing?

Thanks

0 Gabi Gvili over 13 years ago in reply to Thomas Lo

Genius 4120 points

I am using the vlpb, as i said TI gave me a solution for EZSDK 5.02 that was valid also for EZSDK 5.03, so i am still working with EZSDK 5.03.
They are working now for a solution for EZSDK 5.04, please see this:

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/210109/762367.aspx#762367

0 Roberto Borja over 13 years ago in reply to Hannes N

Intellectual 300 points

Johannes N said:
Changing & compiling ok - but changes it did not write a file (enable VLPB_RECORD_BITSREAM) or TIMM_OSAL_Memcpy (buttom) did not modify frame buffer and printf cannot be seen... for me it is still not clear how this componentcode is transported to the dsp.

I too was wondering if Gabi or a TI engineer could clarify why printf nor the vlpb record Bitstream modify the component to print to the console or make a file. From what I gather, Gabi has connected the vlpb to the rest of the omx chain and has modified the component to do processing. As far as I can tell, I have been unable to modify the component, or connect it but that is another question for Gabi on another thread.

Processors

Processors forum

Creating my OMX example capture-VPLB-display (OMX_05_02_00_15)