<?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: decode jpeg images. in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/decode-jpeg-images/m-p/331708#M44835</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found the issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; From the above mentioned documentation ("i.MX 6Dual/6Quad VPU Application Programming Interface Linux Reference Manual", last revision I've found is L3.0.35_4.1.0, 09/2013), 3.2.3 - DecOpenParam, for jpgLineBufferMode description it says:&lt;/P&gt;&lt;P&gt; "jpgLineBufferMode where 0 is a LineBuffer mode and 1 is a streaming mode."&lt;/P&gt;&lt;P&gt; But actually it's the opposite.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 0 is a streaming mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 1 is a LineBuffer mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I've tested it and seems to be working well. I will happy if someone from freescale will confirm and update the manual.&lt;/P&gt;&lt;P&gt; thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Feb 2015 09:24:23 GMT</pubDate>
    <dc:creator>omerlevin</dc:creator>
    <dc:date>2015-02-02T09:24:23Z</dc:date>
    <item>
      <title>decode jpeg images.</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/decode-jpeg-images/m-p/331707#M44834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;Hello, I am trying to decode JPEG images using "Line buffer Mode". Reviewing the documentation in "i.MX 6Dual/6Quad VPU Application Programming Interface Linux Reference Manual" Rev L3.0.35_4.1.0, 09/2013, and the mxc_vpu_test (from LTIB) I have a few questions.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt; - It seems there are quite a few differences in the flow: The test is not setting DecOpenParam.jpgLineBufferMode, thus using a default value of 0, meaning (according to the documentation) 'Line-Buffer Mode". In this mode, according to the flowchart in &amp;lt;3.3.1.1&amp;gt;, functions vpu_DecUpdateBitstreamBuffer()/vpu_DecGetBitstreamBuffer() should only be called once at the start of decoding, and not per frame as done in the test code. Similar call is done to Vpu_DecStartOneFrame().&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt; - According to the documentation, in line buffer mode (DecOpenParam.jpgLineBufferMode =0) There's a need to "set bitstream to bitstreambuffer start address" (p.43). How should that be done?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;When trying to do it by transferring the decoder input stream to bitstreambuffer start address using vpu_DecUpdateBitstreamBuffer() or vpu_DecBitBufferFlush(), vpu_DecGetOutputInfo() returns with decodingSuccess=17 (vpu needs more bitstream in rollback mode).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;My version info below. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt; Thanks in advance. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;Omer&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;my version info&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;Product Info: i.MX6Q&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;VPU firmware version: 2.1.5_r32515&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 12pt;"&gt;VPU library version: 5.4.6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333330154419px;"&gt;&lt;BIG&gt;&lt;BIG&gt;&lt;SPAN style="font-size: 8pt;"&gt;&lt;/SPAN&gt;&lt;/BIG&gt;&lt;/BIG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jan 2015 15:41:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/decode-jpeg-images/m-p/331707#M44834</guid>
      <dc:creator>omerlevin</dc:creator>
      <dc:date>2015-01-29T15:41:47Z</dc:date>
    </item>
    <item>
      <title>Re: decode jpeg images.</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/decode-jpeg-images/m-p/331708#M44835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found the issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; From the above mentioned documentation ("i.MX 6Dual/6Quad VPU Application Programming Interface Linux Reference Manual", last revision I've found is L3.0.35_4.1.0, 09/2013), 3.2.3 - DecOpenParam, for jpgLineBufferMode description it says:&lt;/P&gt;&lt;P&gt; "jpgLineBufferMode where 0 is a LineBuffer mode and 1 is a streaming mode."&lt;/P&gt;&lt;P&gt; But actually it's the opposite.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 0 is a streaming mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; 1 is a LineBuffer mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I've tested it and seems to be working well. I will happy if someone from freescale will confirm and update the manual.&lt;/P&gt;&lt;P&gt; thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Feb 2015 09:24:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/decode-jpeg-images/m-p/331708#M44835</guid>
      <dc:creator>omerlevin</dc:creator>
      <dc:date>2015-02-02T09:24:23Z</dc:date>
    </item>
  </channel>
</rss>

