Forums - GStreamer plugin qtimletflite (GBM Support issue)

1 post / 0 new
GStreamer plugin qtimletflite (GBM Support issue)
Join Date: 21 Sep 23
Posts: 1
Posted: Tue, 2023-11-21 02:27
hi there,
I'm trying to do object detection using usb camera via v4l2src on QCS2210.  
The problem I am encountering is  qtimletflite requires GBM memory support.
This is the command.

/ # export XDG_RUNTIME_DIR=/run/user/root && gst-launch-1.0 v4l2src device=/dev/
video0 ! video/x-raw,format=YUY2,width=1280,height=720 ! videoconvert ! qtimletf
lite config=/data/misc/camera/mle_tflite_config.json model=/data/misc/camera/det
ect.tflite labels=/data/misc/camera/labelmap.txt postprocessing=detection ! qtio
verlay bbox-color=0x0000FFFF ! waylandsink x=960 y=0 width=960 height=540 async=
true sync=false enable-last-sample=false


This is the log of what I'm getting.

Setting pipeline to PAUSED ...
GBM_INFO::msmgbm_mapper(160)::gbm mapper instantiated
gbm_create_device(225): Info: backend name is: msm_drm
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
(gst-launch-1.0:2107): GStreamer-CRITICAL **: 06:06:49.438: gst_structure_new_empty: assertion 'gst_structure_validate_name (name)' failed
INFO: Created TensorFlow Lite delegate for NNAPI.
gbm_create_device(225): Info: backend name is: msm_drm
GBM_ERR::msmgbm_bo_create(766)::DRM_IOCTL_PRIME_FD_TO_HANDLE failed =22
Inappropriate ioctl for device
** (gst-launch-1.0:2107): CRITICAL **: 06:06:50.642: create_surface: assertion 'gpuaddress != NULL' failed
** (gst-launch-1.0:2107): CRITICAL **: 06:06:50.777: create_surface: assertion 'gpuaddress != NULL' failed
** (gst-launch-1.0:2107): CRITICAL **: 06:06:50.898: create_surface: assertion 'gpuaddress != NULL' failed

Any suggestions on this?


  • Up0
  • Down0

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.