<?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: NPU Support in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/NPU-Support/m-p/1493406#M192829</link>
    <description>&lt;P&gt;I don't totally understand what you mean by check the log about the NPU in the kernel, however we did realize that we had a mixture of SOM's with and without NPU and that was the main issue.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 21 Jul 2022 14:42:44 GMT</pubDate>
    <dc:creator>_Alex_</dc:creator>
    <dc:date>2022-07-21T14:42:44Z</dc:date>
    <item>
      <title>NPU Support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NPU-Support/m-p/1490508#M192611</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are trying to get NPU running on a IMX8Plus, and are often ending up with warnings about unsupported evis version. We were starting with an "imx-image-multimedia" build and adding the packagegroup-imx-ml on top of that and not having much luck.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We ended up putting on a an imx-image-full build onto a couple systems and two of the three SOM's we had worked, but one still reported unsupported evis version when running samples. Looking into the differences we noticed the not working system had some things like "vipsi" and "dsp" in /sys/devices/platform/, but the SOM that didn't work doesn't have these.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Any ideas as to what the minimum set of features required to get ML examples working on NPU is?&lt;BR /&gt;Any idea why some boards would have VIPSI/DSP and others wouldn't?&lt;/P&gt;&lt;PRE&gt;38500000.vipsi&lt;/PRE&gt;&lt;PRE&gt;3b6e8000.dsp &lt;/PRE&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 20:28:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NPU-Support/m-p/1490508#M192611</guid>
      <dc:creator>_Alex_</dc:creator>
      <dc:date>2022-07-15T20:28:46Z</dc:date>
    </item>
    <item>
      <title>Re: NPU Support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NPU-Support/m-p/1493142#M192808</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/200827"&gt;@_Alex_&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please check the log about npu in kernel&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2022 07:43:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NPU-Support/m-p/1493142#M192808</guid>
      <dc:creator>Zhiming_Liu</dc:creator>
      <dc:date>2022-07-21T07:43:17Z</dc:date>
    </item>
    <item>
      <title>Re: NPU Support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/NPU-Support/m-p/1493406#M192829</link>
      <description>&lt;P&gt;I don't totally understand what you mean by check the log about the NPU in the kernel, however we did realize that we had a mixture of SOM's with and without NPU and that was the main issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2022 14:42:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/NPU-Support/m-p/1493406#M192829</guid>
      <dc:creator>_Alex_</dc:creator>
      <dc:date>2022-07-21T14:42:44Z</dc:date>
    </item>
  </channel>
</rss>

