<?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: Kernel logging causes USB instability in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886735#M134295</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;for i.MX7 such detailed NIC-301 description is not available for customers,&lt;/P&gt;&lt;P&gt;suggest to work with nxp local marketing office if you have special need for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Feb 2019 00:39:44 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2019-02-07T00:39:44Z</dc:date>
    <item>
      <title>Kernel logging causes USB instability</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886732#M134292</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have a handful of kernel modules that can log a fair amount of data to the kernel logs. We have noticed that this&amp;nbsp;can cause instability of the USB Camera we have plugged in. So far we have been struggling to come up with ideas on&amp;nbsp;why kernel logging would&amp;nbsp;cause this and&amp;nbsp;possible remedy action besides reducing the&amp;nbsp;amount of kernel logging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some ideas so far (keep in mind these may be very ignorant):&lt;/P&gt;&lt;P&gt;Kernel logging maybe gets written to disk and that freezes the system? Maybe DMA for the SD card takes over the memory bus and causes issues?&lt;/P&gt;&lt;P&gt;Kernel logging is higher priority than USB driver maintenance?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any additional ideas or experiments&amp;nbsp;would be appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jan 2019 23:58:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886732#M134292</guid>
      <dc:creator>dogisfat</dc:creator>
      <dc:date>2019-01-18T23:58:43Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel logging causes USB instability</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886733#M134293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ALLEN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in general logging (seems handled by uart) consumes some processor&lt;/P&gt;&lt;P&gt;time, internal buses and memory bandwidth which may affect usb module&lt;/P&gt;&lt;P&gt;operations. One can try to disable uart dma, use polling option. Another very general&lt;/P&gt;&lt;P&gt;way is to increase usb module priority with NIC-301 settings (sect.4.6 Network&lt;/P&gt;&lt;P&gt;Interconnect Bus System (NIC-301) i.MX7D Reference Manual), similar to&lt;/P&gt;&lt;P&gt;sect.45.3.3.1 QoS registers' address look-up example, sect.45.3.4 NIC-specific parameters&lt;/P&gt;&lt;P&gt;i.MX6DQ Reference Manual.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.nxp.com/docs/en/reference-manual/IMX6DQRM.pdf"&gt;http://www.nxp.com/docs/en/reference-manual/IMX6DQRM.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Unfortunately for i.MX7 such detailed NIC-301 description is not available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2019 00:07:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886733#M134293</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2019-01-22T00:07:44Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel logging causes USB instability</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886734#M134294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;Is it possible to get a description of the NIC parameters and locations as in table 45-5 of the IMX6DQRM? Without that it is impossible to guess at the location and offset of the NIC configuration registers. We are also experiencing some issues with the M4 accessing DDR memory during high USB and Ethernet usage and would like to explore the NIC qos as a potential solution for that as well.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Feb 2019 16:34:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886734#M134294</guid>
      <dc:creator>dogisfat</dc:creator>
      <dc:date>2019-02-06T16:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel logging causes USB instability</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886735#M134295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;for i.MX7 such detailed NIC-301 description is not available for customers,&lt;/P&gt;&lt;P&gt;suggest to work with nxp local marketing office if you have special need for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Feb 2019 00:39:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-logging-causes-USB-instability/m-p/886735#M134295</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2019-02-07T00:39:44Z</dc:date>
    </item>
  </channel>
</rss>

