cedar_ve driver not able to allocate memory
#11
If you want you can play with my build, maybe it fit you kernel too.

(12-21-2021, 11:57 AM)tvall Wrote: yeah i had ve_size set to 16mb most tests. but ive tried several values between 12mb and 32mb and they all give the same result.

I tried range 12 to 16M and it worked for me. For now I use 12M.


Attached Files
.zip   cedar_driver.zip (Size: 14.58 KB / Downloads: 18)
  Reply
#12
Code:
reg = <0x01c00000 0xd0>;

thats what i needed under syscon, now it loads just fine and might be working. now i need to figure out how to use it. but thatll be tomorrow
  Reply
#13
(12-21-2021, 01:31 PM)tvall Wrote:
Code:
reg = <0x01c00000 0xd0>;

thats what i needed under syscon, now it loads just fine and might be working. now i need to figure out how to use it. but thatll be tomorrow

Good news. If needed, I'll provide tomorrow a simple gstreamer command line to test camera capture (has left it at office). To use gstreamer, you also need to build cedar plugin (I haven't troubles with that) https://github.com/gtalusan/gst-plugin-cedar
  Reply
#14
Setup camera:
Code:
media-ctl --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1280x720@1/15]'

Start gstreamer:


Code:
GST_PLUGIN_PATH=/usr/local/lib/gstreamer-1.0 GST_DEBUG=3 gst-launch-1.0   \
    v4l2src device=/dev/video0 ! video/x-raw,format=UYVY,framerate=15/1,width=1280,height=720      \
    ! videoconvert ! video/x-raw,format=NV12       \
    ! clockoverlay time-format="%Y-%m-%d %H:%M:%S"    \
              ! cedar_h264enc ! h264parse     \
              ! splitmuxsink send-keyframe-requests=true max-size-time=30000000000 muxer=matroskamux max-files=32     \
                    location=/root/recordings/chunk_%06d.mkv                                                                           
  Reply
#15
(12-20-2021, 02:22 PM)cooler Wrote: So far I've utilized hardware cedar encoder having ~8fps at 1280x720 and 2-3-4fps at 1920x1080 via gstreamer.

Congratulations!

Do you have a sense how close you are to the limits of the hardware? I wonder if it can support 1920x1080 at higher frame rates (say, 10 or 15 fps) after optimization or not, and if the fundamental bottleneck is the general CPU or the H.264 encoder.
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)