hantro h264 broken in kernel 6.6.52

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

hantro h264 broken in kernel 6.6.52

Jump to solution
4,050 Views
ihermida
Contributor II

Hi all,

 

There is a regresion on a kernel v6.6 due to commit https://github.com/nxp-imx/linux-imx/commit/4ca7e59f00e03acb01476e106de3870214efc682

You can try the next command to test the h264 codec, or well reproduce a video containing it.

 

gst-launch-1.0 videotestsrc ! video/x-raw, format=I420, width=640, height=480 ! vpuenc_h264 ! h264parse ! v4l2h264dec ! fakesink

 

Reverting that commit solves the problem, but the real problem is in the file drivers/mxc/hantro_v4l2/vsi-v4l2.h, where adding a new field in the "struct v4l2_daemon_dec_buffers " causes a missaligment (in the specific commit it is the field "u64 process_time")

 

Can you point to a proper fix for having h264 working?

 

BR / Isaac

 

0 Kudos
Reply
1 Solution
3,873 Views
ihermida
Contributor II


I found where the problem comes...

We were using the meta-freescale layer, which is using the imx-vpu-hantro version 1.32.

This recent commit in the layer solved the problem

https://github.com/Freescale/meta-freescale/commit/a63a107a3681d4a6342145290f62e98d8607ec0f

 

It might be a missaligment between the kernel (that introduced the u64 process_time value) and the imx vpu code.

Using the kernel 6.6.52 with the imx vpu hantro 1.35 works.

 

 

View solution in original post

4 Replies
4,041 Views
joanxie
NXP TechSupport
NXP TechSupport

do you use imx8mm? what kind of issue do you find when you use this command? I haven't got imx8mm now, pls share the detailed issue or logfile with me

0 Kudos
Reply
4,037 Views
ihermida
Contributor II

Yes, I reproduce it in the i.mx8m mini. We have seen it using default NXP images for Android, and I narrow it down till linux and the mentioned commit.

You can monitor the "hantrodec" interrupts and see how they are not generated. and the video is not reproduced. Try the command 

gst-launch-1.0 videotestsrc ! video/x-raw, format=I420, width=640, height=480 ! vpuenc_h264 ! h264parse  ! v4l2h264dec ! fakesink

(or fpsdisplaysink).

 

The error is that the command just get locked (no video, no interrupts, nothing in dmesg).

"""

root@ccimx8mm-dvk:~# gst-launch-1.0 videotestsrc ! video/x-raw, format=I420, width=640
, height=480 ! vpuenc_h264 ! h264parse  ! v4l2h264dec ! fakesink
Setting pipeline to PAUSED ...

====== V4L2DEC: 1.24.0 build on Jul 24 2024 02:25:45. ======
====== VPUENC: 4.9.1 build on Aug  8 2024 05:28:21. ======
       wrapper: 3.0.0 (VPUWRAPPER_ARM64_LINUX Build on Jul 24 2024 01:56:50)
       vpulib: 1.1.1
       firmware: 1.1.1.65535
Pipeline is PREROLLING ...
Redistribute latency..
""

 

You can use gplay and a video with h264 codec. Gplay just fails as it cannot reproduce the video. Use whatever command to reproduce the problem. And check the interrupts.

root@ccimx8mm-dvk:~# grep hantro /proc/interrupts
29:          0          0          0          0     GICv3  39 Level     hantrodec
30:          0          0          0          0     GICv3  40 Level     hantrodec
root@ccimx8mm-dvk:~#

 

In case of internal vpu error, it fails "silently" so there is not any relevant information in the dmesg output.

 

The error using a h264 video with gplay is "a general stream error"

"""

ERROR Error from element /GstPlayBin3:playbin3/GstURIDecodeBin3:uridecodebin3/GstURISo
urceBin:urisourcebin0/GstParseBin:parsebin0/GstAiurDemux:aiurdemux0: GStreamer encount
ered a general stream error.
GStreamer encountered a general stream error.
/usr/src/debug/imx-gst1.0-plugin/4.9.1+git/plugins/aiurdemux/aiurdemux.c(1229): aiurde
mux_pull_task (): /GstPlayBin3:playbin3/GstURIDecodeBin3:uridecodebin3/GstURISourceBin
:urisourcebin0/GstParseBin:parsebin0/GstAiurDemux:aiurdemux0:
streaming stopped, reason not-negotiated, state 3 for /mnt/data/3DMark_1280x720_h264_a
ac_44100
"""

0 Kudos
Reply
3,874 Views
ihermida
Contributor II


I found where the problem comes...

We were using the meta-freescale layer, which is using the imx-vpu-hantro version 1.32.

This recent commit in the layer solved the problem

https://github.com/Freescale/meta-freescale/commit/a63a107a3681d4a6342145290f62e98d8607ec0f

 

It might be a missaligment between the kernel (that introduced the u64 process_time value) and the imx vpu code.

Using the kernel 6.6.52 with the imx vpu hantro 1.35 works.

 

 

3,404 Views
marcocavallini
Contributor V

I have basically the same issue using the kernel 6.6.52 (Yocto 5.x Scarthgap) then I applied the patch you suggested and with the imx vpu hantro 1.35 I get the same error.
What am I missing ?

# uname -a
Linux mx8mm 6.6.52-ucm-imx8m-mini-4.0-g1be724da3a09 #1 SMP PREEMPT Tue Jul 29 17:42:41 UTC 2025 aarch64 GNU/Linux


# gst-launch-1.0 videotestsrc ! video/x-raw, format=I420, width=640, height=480 ! vpuenc_h264 ! h264parse  ! v4l2h264dec ! fakesink

Setting pipeline to PAUSED ...

====== V4L2DEC: 1.24.0 build on May  6 2024 08:51:28. ======
====== VPUENC: 4.9.0 build on May  8 2024 06:06:55. ======
	wrapper: 3.0.0 (VPUWRAPPER_ARM64_LINUX Build on Apr 24 2024 06:33:53)
	vpulib: 1.1.1
	firmware: 1.1.1.127
ERROR: from element /GstPipeline:pipeline0/vpuenc_h264:vpuenc_h264-0: Could not initialize supporting library.
Additional debug info:
/usr/src/debug/gstreamer1.0-plugins-base/1.24.0.imx/gst-libs/gst/video/gstvideoencoder.c(1799): gst_video_encoder_change_state (): /GstPipeline:pipeline0/vpuenc_h264:vpuenc_h264-0:
Failed to start encoder
ERROR: pipeline doesn't want to preroll.
Failed to set pipeline to PAUSED.
Setting pipeline to NULL ...
Freeing pipeline ...


# grep hantro /proc/interrupts
 32:          0          0          0          0     GICv3  39 Level     hantrodec
 33:          0          0          0          0     GICv3  40 Level     hantrodec


I added to the image the following packages

# Core VPU packages
IMAGE_INSTALL:append = " \
    imx-gst1.0-plugin \
    linux-firmware \
    imx-vpu-hantro \
    imx-vpu-hantro-daemon \
    imx-vpu-hantro-vc \
    libimxvpuapi2 \
"


Thanks

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2074983%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3Ehantro%20h264%20broken%20in%20kernel%206.6.52%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2074983%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EThere%20is%20a%20regresion%20on%20a%20kernel%20v6.6%20due%20to%20commit%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fnxp-imx%2Flinux-imx%2Fcommit%2F4ca7e59f00e03acb01476e106de3870214efc682%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fnxp-imx%2Flinux-imx%2Fcommit%2F4ca7e59f00e03acb01476e106de3870214efc682%3C%2FA%3E%3C%2FP%3E%3CP%3EYou%20can%20try%20the%20next%20command%20to%20test%20the%20h264%20codec%2C%20or%20well%20reproduce%20a%20video%20containing%20it.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3Egst-launch-1.0%20videotestsrc%20!%20video%2Fx-raw%2C%20format%3DI420%2C%20width%3D640%2C%20height%3D480%20!%20vpuenc_h264%20!%20h264parse%20!%20v4l2h264dec%20!%20fakesink%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EReverting%20that%20commit%20solves%20the%20problem%2C%20but%20the%20real%20problem%20is%20in%20the%20file%26nbsp%3Bdrivers%2Fmxc%2Fhantro_v4l2%2Fvsi-v4l2.h%2C%20where%20adding%20a%20new%20field%20in%20the%20%22struct%20v4l2_daemon_dec_buffers%20%22%20causes%20a%20missaligment%20(in%20the%20specific%20commit%20it%20is%20the%20field%20%22u64%20process_time%22)%3C%2FP%3E%3CBR%20%2F%3E%3CP%3ECan%20you%20point%20to%20a%20proper%20fix%20for%20having%20h264%20working%3F%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EBR%20%2F%20Isaac%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2074983%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3Ei.MX%208M%20%7C%20i.MX%208M%20Mini%20%7C%20i.MX%208M%20Nano%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMultimedia%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2091298%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20hantro%20h264%20broken%20in%20kernel%206.6.52%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2091298%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CBR%20%2F%3EI%20found%20where%20the%20problem%20comes...%3C%2FP%3E%3CP%3EWe%20were%20using%20the%20meta-freescale%20layer%2C%20which%20is%20using%20the%20imx-vpu-hantro%20version%201.32.%3C%2FP%3E%3CP%3EThis%20recent%20commit%20in%20the%20layer%20solved%20the%20problem%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FFreescale%2Fmeta-freescale%2Fcommit%2Fa63a107a3681d4a6342145290f62e98d8607ec0f%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FFreescale%2Fmeta-freescale%2Fcommit%2Fa63a107a3681d4a6342145290f62e98d8607ec0f%3C%2FA%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EIt%20might%20be%20a%20missaligment%20between%20the%20kernel%20(that%20introduced%20the%20u64%26nbsp%3Bprocess_time%20value)%20and%20the%20imx%20vpu%20code.%3C%2FP%3E%3CP%3EUsing%20the%20kernel%206.6.52%20with%20the%20imx%20vpu%20hantro%201.35%20works.%3C%2FP%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2075074%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20hantro%20h264%20broken%20in%20kernel%206.6.52%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2075074%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EYes%2C%20I%20reproduce%20it%20in%20the%20i.mx8m%20mini.%20We%20have%20seen%20it%20using%20default%20NXP%20images%20for%20Android%2C%20and%20I%20narrow%20it%20down%20till%20linux%20and%20the%20mentioned%20commit.%3C%2FP%3E%3CP%3EYou%20can%20monitor%20the%20%22hantrodec%22%20interrupts%20and%20see%20how%20they%20are%20not%20generated.%20and%20the%20video%20is%20not%20reproduced.%20Try%20the%20command%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CFONT%20face%3D%22monospace%22%3Egst-launch-1.0%20videotestsrc%20!%20video%2Fx-raw%2C%20format%3DI420%2C%20width%3D640%2C%20height%3D480%20!%20vpuenc_h264%20!%20h264parse%26nbsp%3B%20!%20v4l2h264dec%20!%20fakesink%3C%2FFONT%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3E(or%20fpsdisplaysink).%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSPAN%3EThe%20error%20is%20that%20the%20command%20just%20get%20locked%20(no%20video%2C%20no%20interrupts%2C%20nothing%20in%20dmesg).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%22%22%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eroot%40ccimx8mm-dvk%3A~%23%20gst-launch-1.0%20videotestsrc%20!%20video%2Fx-raw%2C%20format%3DI420%2C%20width%3D640%3CBR%20%2F%3E%2C%20height%3D480%20!%20vpuenc_h264%20!%20h264parse%20%26nbsp%3B!%20v4l2h264dec%20!%20fakesink%3CBR%20%2F%3ESetting%20pipeline%20to%20PAUSED%20...%3CBR%20%2F%3E%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%20V4L2DEC%3A%201.24.0%20build%20on%20Jul%2024%202024%2002%3A25%3A45.%20%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3E%3D%3D%3D%3D%3D%3D%20VPUENC%3A%204.9.1%20build%20on%20Aug%20%26nbsp%3B8%202024%2005%3A28%3A21.%20%3D%3D%3D%3D%3D%3D%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bwrapper%3A%203.0.0%20(VPUWRAPPER_ARM64_LINUX%20Build%20on%20Jul%2024%202024%2001%3A56%3A50)%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bvpulib%3A%201.1.1%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bfirmware%3A%201.1.1.65535%3CBR%20%2F%3EPipeline%20is%20PREROLLING%20...%3CBR%20%2F%3ERedistribute%20latency..%3CBR%20%2F%3E%22%22%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSPAN%3EYou%20can%20use%20gplay%20and%20a%20video%20with%20h264%20codec.%20Gplay%20just%20fails%20as%20it%20cannot%20reproduce%20the%20video.%20Use%20whatever%20command%20to%20reproduce%20the%20problem.%20And%20check%20the%20interrupts.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Eroot%40ccimx8mm-dvk%3A~%23%20grep%20hantro%20%2Fproc%2Finterrupts%3CBR%20%2F%3E29%3A%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BGICv3%20%26nbsp%3B39%20Level%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bhantrodec%3CBR%20%2F%3E30%3A%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B0%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BGICv3%20%26nbsp%3B40%20Level%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3Bhantrodec%3CBR%20%2F%3E%3CA%20href%3D%22mailto%3Aroot%40ccimx8mm-dvk%3A~%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eroot%40ccimx8mm-dvk%3A~%23%3C%2FA%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSPAN%3EIn%20case%20of%20internal%20vpu%20error%2C%20it%20fails%20%22silently%22%20so%20there%20is%20not%20any%20relevant%20information%20in%20the%20dmesg%20output.%3C%2FSPAN%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3CSPAN%3EThe%20error%20using%20a%20h264%20video%20with%20gplay%20is%20%22a%20general%20stream%20error%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%22%22%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EERROR%20Error%20from%20element%20%2FGstPlayBin3%3Aplaybin3%2FGstURIDecodeBin3%3Auridecodebin3%2FGstURISo%3CBR%20%2F%3EurceBin%3Aurisourcebin0%2FGstParseBin%3Aparsebin0%2FGstAiurDemux%3Aaiurdemux0%3A%20GStreamer%20encount%3CBR%20%2F%3Eered%20a%20general%20stream%20error.%3CBR%20%2F%3EGStreamer%20encountered%20a%20general%20stream%20error.%3CBR%20%2F%3E%2Fusr%2Fsrc%2Fdebug%2Fimx-gst1.0-plugin%2F4.9.1%2Bgit%2Fplugins%2Faiurdemux%2Faiurdemux.c(1229)%3A%20aiurde%3CBR%20%2F%3Emux_pull_task%20()%3A%20%2FGstPlayBin3%3Aplaybin3%2FGstURIDecodeBin3%3Auridecodebin3%2FGstURISourceBin%3CBR%20%2F%3E%3Aurisourcebin0%2FGstParseBin%3Aparsebin0%2FGstAiurDemux%3Aaiurdemux0%3A%3CBR%20%2F%3Estreaming%20stopped%2C%20reason%20not-negotiated%2C%20state%203%20for%20%2Fmnt%2Fdata%2F3DMark_1280x720_h264_a%3CBR%20%2F%3Eac_44100%3CBR%20%2F%3E%22%22%22%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2075061%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20hantro%20h264%20broken%20in%20kernel%206.6.52%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2075061%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3Edo%20you%20use%20imx8mm%3F%20what%20kind%20of%20issue%20do%20you%20find%20when%20you%20use%20this%20command%3F%20I%20haven't%20got%20imx8mm%20now%2C%20pls%20share%20the%20detailed%20issue%20or%20logfile%20with%20me%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2143454%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20hantro%20h264%20broken%20in%20kernel%206.6.52%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2143454%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20have%20basically%20the%20same%20issue%20using%20the%20kernel%206.6.52%20(Yocto%205.x%20Scarthgap)%20then%20I%20applied%20the%20patch%20you%20suggested%20and%20with%20the%20imx%20vpu%20hantro%201.35%20I%20get%20the%20same%20error.%3CBR%20%2F%3EWhat%20am%20I%20missing%20%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-c%22%3E%3CCODE%3E%23%20uname%20-a%0ALinux%20mx8mm%206.6.52-ucm-imx8m-mini-4.0-g1be724da3a09%20%231%20SMP%20PREEMPT%20Tue%20Jul%2029%2017%3A42%3A41%20UTC%202025%20aarch64%20GNU%2FLinux%0A%0A%0A%23%20gst-launch-1.0%20videotestsrc%20!%20video%2Fx-raw%2C%20format%3DI420%2C%20width%3D640%2C%20height%3D480%20!%20vpuenc_h264%20!%20h264parse%20%20!%20v4l2h264dec%20!%20fakesink%0A%0ASetting%20pipeline%20to%20PAUSED%20...%0A%0A%3D%3D%3D%3D%3D%3D%20V4L2DEC%3A%201.24.0%20build%20on%20May%20%206%202024%2008%3A51%3A28.%20%3D%3D%3D%3D%3D%3D%0A%3D%3D%3D%3D%3D%3D%20VPUENC%3A%204.9.0%20build%20on%20May%20%208%202024%2006%3A06%3A55.%20%3D%3D%3D%3D%3D%3D%0A%09wrapper%3A%203.0.0%20(VPUWRAPPER_ARM64_LINUX%20Build%20on%20Apr%2024%202024%2006%3A33%3A53)%0A%09vpulib%3A%201.1.1%0A%09firmware%3A%201.1.1.127%0AERROR%3A%20from%20element%20%2FGstPipeline%3Apipeline0%2Fvpuenc_h264%3Avpuenc_h264-0%3A%20Could%20not%20initialize%20supporting%20library.%0AAdditional%20debug%20info%3A%0A%2Fusr%2Fsrc%2Fdebug%2Fgstreamer1.0-plugins-base%2F1.24.0.imx%2Fgst-libs%2Fgst%2Fvideo%2Fgstvideoencoder.c(1799)%3A%20gst_video_encoder_change_state%20()%3A%20%2FGstPipeline%3Apipeline0%2Fvpuenc_h264%3Avpuenc_h264-0%3A%0AFailed%20to%20start%20encoder%0AERROR%3A%20pipeline%20doesn't%20want%20to%20preroll.%0AFailed%20to%20set%20pipeline%20to%20PAUSED.%0ASetting%20pipeline%20to%20NULL%20...%0AFreeing%20pipeline%20...%0A%0A%0A%23%20grep%20hantro%20%2Fproc%2Finterrupts%0A%2032%3A%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20GICv3%20%2039%20Level%20%20%20%20%20hantrodec%0A%2033%3A%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20%20%20%20%20%200%20%20%20%20%20GICv3%20%2040%20Level%20%20%20%20%20hantrodec%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%3CBR%20%2F%3EI%20added%20to%20the%20image%20the%20following%20packages%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-c%22%3E%3CCODE%3E%23%20Core%20VPU%20packages%0AIMAGE_INSTALL%3Aappend%20%3D%20%22%20%5C%0A%20%20%20%20imx-gst1.0-plugin%20%5C%0A%20%20%20%20linux-firmware%20%5C%0A%20%20%20%20imx-vpu-hantro%20%5C%0A%20%20%20%20imx-vpu-hantro-daemon%20%5C%0A%20%20%20%20imx-vpu-hantro-vc%20%5C%0A%20%20%20%20libimxvpuapi2%20%5C%0A%22%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%3CBR%20%2F%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E