Linux/AM5728: Memory allocation error in VIP capture

Marka Reddy

Part Number: AM5728

Tool/software: Linux

Hi,

we are developing a custom board based AM5728 GP EVM. in our board we are tying to capture video on VIN5A and VIN6A simultaneously. The g-streamer pipeline is not working. Below is the pipeline

root@am57xx-evm:~# gst-launch-1.0 -e v4l2src device="/dev/video3" io-mode=4 ! 'video/x-raw,width=1024,height=768,framerate=30
/1' ! vpe num-input-buffers=8 ! 'video/x-raw,height=768,width=1024,framerate=30/1' ! queue ! ducatih264enc ! h264parse ! que
ue ! mp4mux ! filesink location=/home/root/19_01.mp4 v4l2src device="/dev/video2" io-mode=4 ! 'video/x-raw,width=1024,height
=768,framerate=30/1'! vpe num-input-buffers=8 ! 'video/x-raw,height=768,width=1024,framerate=30/1' ! queue ! ducatih264enc !
h264parse ! queue ! mp4mux ! filesink location=/home/root/19_02.mp4
Setting pipeline to PAUSED ...
[ 231.985071] omap-iommu 55082000.mmu: 55082000.mmu: version 2.1
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
[ 232.052567] vip 489b0000.vip: dma_alloc_coherent of size 1572864 failed
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed to allocate required memory.
Additional debug info:
../../../gst-plugins-good-1.6.3/sys/v4l2/gstv4l2src.c(511): gst_v4l2src_decide_allocation (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
Buffer pool activation failed
EOS on shutdown enabled -- waiting for EOS after Error
Waiting for EOS...
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data flow error.
Additional debug info:
../../../../gstreamer-1.6.3/libs/gst/base/gstbasesrc.c(2943): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming task paused, reason not-negotiated (-4)
[ 233.438273] vip 489b0000.vip: dma_alloc_coherent of size 1572864 failed

** (gst-launch-1.0:1165): CRITICAL **: gst_fd_memory_get_fd: assertion 'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:1165): CRITICAL **: gst_fd_memory_get_fd: assertion 'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:1165): CRITICAL **: gst_fd_memory_get_fd: assertion 'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

** (gst-launch-1.0:1165): CRITICAL **: gst_fd_memory_get_fd: assertion 'GST_IS_FD_ALLOCATOR (mem->allocator)' failed

Please help us to resolve the issue

Marka reddy

over 6 years ago

0 Margarita Gashova over 6 years ago

TI__Guru* 80190 points

Hello Marka Reddy,

Please increase cma to 128 and give a try.
You could do this in uboot.

=> setenv optargs cma=128MiB
=> saveenv

In booting prints you must see cma: Reserved 128 MiB at 0x00000000f7c00000
or
root@am57xx-evm:~# cat /proc/cmdline
console=ttyO2,115200n8 cma=128MiB root=PARTUUID=00095f8c-02 rw rootfstype=ext4 rootwait

BR
Margarita

0 Margarita Gashova over 6 years ago

TI__Guru* 80190 points

Marka,

There is one more error "streaming task paused, reason not-negotiated (-4)" not only vip 489b0000.vip: dma_alloc_coherent of size 1572864 failed.
You must add format in the capsfilter as below:

'video/x-raw, format=(string)YUY2, width=(int)xxx, height=(int)xxx...'
Change the format depending of what your video source provides.

BR
Margarita

0 Marka Reddy over 6 years ago in reply to Margarita Gashova

Expert 1260 points

Hi,
Thank you
The memory error and streaming task paused error are disappeared. but the system is getting reboot upon entering the pipeline
BR
Marka Reddy

0 Margarita Gashova over 6 years ago in reply to Marka Reddy

TI__Guru* 80190 points

Hello,

Please make sure that you could capture from the both before to merge them into one pipeline.
Please try to set cma to 64 and check do you observe the error or restart.
I would recommend you to enable the vip debug and gstreamer debug and dmesg to check what is going on.

BR
Margarita

0 Marka Reddy over 6 years ago in reply to Margarita Gashova

Expert 1260 points

Hi,
@ 400 MHz ==> 1024x76 30fps raw capture working
@400 Mhz ==> 1024x768 30fps 2 channels not able to capture
@600 Mhz ==> system is getting reset while trying to capture 2 channels simultaneously

cma = 64 in all these iterations
Is there any way to know exact reason for reset(any log or debug ??)

BR
Marka Reddy

0 Marka Reddy over 6 years ago in reply to Marka Reddy

Expert 1260 points

We are awaiting your reply.

Regards,
MR

0 Margarita Gashova over 6 years ago in reply to Marka Reddy

TI__Guru* 80190 points

Hello Marka Reddy,

Please refer the below thread about multichannel capture:
e2e.ti.com/.../640197
On second page you will find a patch. There you, could find and suggestions how you could debug this if there is a need.

Hope this helps.

BR
Margarita

Processors

Processors forum

Linux/AM5728: Memory allocation error in VIP capture