<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [iMX8MP] How to debug VPU_EncEncodeFrame() = 2 : INVALID_PARAM in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1922710#M226867</link>
    <description>&lt;P&gt;Hi, thanks for replying!&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&lt;SPAN&gt;what's your use case?&lt;BR /&gt;&lt;/SPAN&gt;I am trying to make an application that would run on imx8mp evk, which encodes a single image file (believed to be of YUV420 format) into H264 format.&amp;nbsp;&lt;BR /&gt;Basically, I just want to see first how encoding works as I have no background on this.&lt;/P&gt;&lt;P&gt;This input image file is created via the following command:&lt;BR /&gt;gst-launch-1.0 filesrc location="raw.jpg"&amp;nbsp; ! jpegdec ! filesink location="image_file.yuv"&lt;BR /&gt;&lt;BR /&gt;raw.jpg: JPEG file created on Paint (1920x1080)&lt;BR /&gt;image_file.yuv: my application's input file which I believe/hope is of YUV420 format&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&lt;SPAN&gt;&amp;nbsp;did you download nxp yocto bsp?&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;Yes, I am using yocto-real-time-edge bsp.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&lt;SPAN&gt;what source code do you refer to?&lt;/SPAN&gt;&lt;BR /&gt;None, I am only referring to the VPU reference manual, that's why I included that same question in my original post.&lt;BR /&gt;&lt;BR /&gt;Parameters passed to&amp;nbsp;VPU_EncOpenSimp and VPU_EncEncodeFrame are mostly set to automatic values (0 or -1), according to the manual.&lt;BR /&gt;&lt;BR /&gt;Other parameters are based on the input image file, such as size.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Aug 2024 07:52:03 GMT</pubDate>
    <dc:creator>b_m</dc:creator>
    <dc:date>2024-08-01T07:52:03Z</dc:date>
    <item>
      <title>[iMX8MP] How to debug VPU_EncEncodeFrame() = 2 : INVALID_PARAM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1919984#M226730</link>
      <description>&lt;P&gt;I am trying to encode via VPU wrapper as written in &lt;A href="https://www.nxp.com/docs/en/reference-manual/IMX_VPU_APPLICATION_PROGRAMMING_INTERFACE_LINUX_REFERENCE_MANUAL.pdf" target="_self"&gt;this&lt;/A&gt; manual, however VPU_EncEncodeFrame() is returning 2 : INVALID_PARAM, without any other error logs showing on the console.&lt;BR /&gt;&lt;BR /&gt;1. Can anyone tell me how to debug this to know which parameter is causing this error?&lt;BR /&gt;2. Is&amp;nbsp;VPU_EncEncodeFrame() 's parameter the only parameter that is faulty here, so I don't need to check parameters passed to previously called API's such as VPU_EncOpenSimp()?&lt;BR /&gt;3. Checking vpu_wrapper.c, I see that some logs are output via&amp;nbsp;VPU_LOG() or&amp;nbsp;VPU_ENC_LOG(), can this be enabled from the application side? And is it correct to assume that if it is enabled, the log is directed to the console?&lt;BR /&gt;4. Any sample codes that implements encoding via VPU wrapper, specifically for imx8mp?&lt;BR /&gt;&lt;BR /&gt;Any replies would be highly appreciated!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2024 05:08:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1919984#M226730</guid>
      <dc:creator>b_m</dc:creator>
      <dc:date>2024-07-30T05:08:20Z</dc:date>
    </item>
    <item>
      <title>Re: [iMX8MP] How to debug VPU_EncEncodeFrame() = 2 : INVALID_PARAM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1922648#M226863</link>
      <description>&lt;P&gt;what's your use case? did you download nxp yocto bsp? what source code do you refer to?&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2024 07:18:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1922648#M226863</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2024-08-01T07:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: [iMX8MP] How to debug VPU_EncEncodeFrame() = 2 : INVALID_PARAM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1922710#M226867</link>
      <description>&lt;P&gt;Hi, thanks for replying!&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&lt;SPAN&gt;what's your use case?&lt;BR /&gt;&lt;/SPAN&gt;I am trying to make an application that would run on imx8mp evk, which encodes a single image file (believed to be of YUV420 format) into H264 format.&amp;nbsp;&lt;BR /&gt;Basically, I just want to see first how encoding works as I have no background on this.&lt;/P&gt;&lt;P&gt;This input image file is created via the following command:&lt;BR /&gt;gst-launch-1.0 filesrc location="raw.jpg"&amp;nbsp; ! jpegdec ! filesink location="image_file.yuv"&lt;BR /&gt;&lt;BR /&gt;raw.jpg: JPEG file created on Paint (1920x1080)&lt;BR /&gt;image_file.yuv: my application's input file which I believe/hope is of YUV420 format&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&lt;SPAN&gt;&amp;nbsp;did you download nxp yocto bsp?&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;Yes, I am using yocto-real-time-edge bsp.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&lt;SPAN&gt;what source code do you refer to?&lt;/SPAN&gt;&lt;BR /&gt;None, I am only referring to the VPU reference manual, that's why I included that same question in my original post.&lt;BR /&gt;&lt;BR /&gt;Parameters passed to&amp;nbsp;VPU_EncOpenSimp and VPU_EncEncodeFrame are mostly set to automatic values (0 or -1), according to the manual.&lt;BR /&gt;&lt;BR /&gt;Other parameters are based on the input image file, such as size.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2024 07:52:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1922710#M226867</guid>
      <dc:creator>b_m</dc:creator>
      <dc:date>2024-08-01T07:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: [iMX8MP] How to debug VPU_EncEncodeFrame() = 2 : INVALID_PARAM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1931100#M227265</link>
      <description>&lt;P&gt;sorry I missed this update somehow, I think you need add some extra plugins to support jpeg to yuv, you can try this command to display jpeg firstly, we tested this before&lt;/P&gt;
&lt;P&gt;gst-launch-1.0 -v filesrc location=&amp;lt;output_image&amp;gt;.jpeg ! jpegdec ! imagefreeze ! videoconvert ! autovideosink&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 11:45:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1931100#M227265</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2024-08-13T11:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: [iMX8MP] How to debug VPU_EncEncodeFrame() = 2 : INVALID_PARAM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1931552#M227281</link>
      <description>&lt;P&gt;Hi joanxie, thanks for the follow-up.&lt;/P&gt;&lt;P&gt;Turned out the problem was the 1st argument VpuEncHandle, created from VPU_EncOpenSimp(), was not passed properly to&amp;nbsp;VPU_EncEncodeFrame().&lt;BR /&gt;&lt;BR /&gt;We got too focused on the term "PARAM" of the error code, thought it pertained to VpuEncOpen&lt;STRONG&gt;Param&lt;/STRONG&gt;Simp, and assumed a separate error code (3 : INVALID_HANDLE) would be set with regards to VpuEncHandle.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2024 00:58:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX8MP-How-to-debug-VPU-EncEncodeFrame-2-INVALID-PARAM/m-p/1931552#M227281</guid>
      <dc:creator>b_m</dc:creator>
      <dc:date>2024-08-14T00:58:08Z</dc:date>
    </item>
  </channel>
</rss>

