<?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>i.MX ProcessorsのトピックRe: Understanding booting issues</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725654#M112852</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think my question wasn't clear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I'm implementing the system as a product, there will not be any access to target console. Then, if the system fails to boot up or continuously restarting, I would like to indicate the user "system failed in Linux boot". So how I can understand the system failure without any access to kernel log.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Mar 2018 10:58:43 GMT</pubDate>
    <dc:creator>mathew_k_t</dc:creator>
    <dc:date>2018-03-05T10:58:43Z</dc:date>
    <item>
      <title>Understanding booting issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725652#M112850</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know, how to understand system hang during booting? When I search about it, I found NMI watchdog.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is NMI watchdog is the solution to understand system hang during booting? Please confirm it?&lt;/LI&gt;&lt;LI&gt;How to enable NMI watchdog in imx6ull evk?&lt;/LI&gt;&lt;LI&gt;Is there any other way to understand system error during booting?&lt;/LI&gt;&lt;LI&gt;Once understand the error, I would like to indicate the same&lt;SPAN class=""&gt;. &lt;/SPAN&gt;How &lt;SPAN class=""&gt;doing&lt;/SPAN&gt; it?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Mar 2018 04:57:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725652#M112850</guid>
      <dc:creator>mathew_k_t</dc:creator>
      <dc:date>2018-03-05T04:57:17Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding booting issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725653#M112851</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi mathew_k_t&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for boot understanding one can follow Boot Chapter of Reference Manual,&lt;/P&gt;&lt;P&gt;check with jtag SRC_SBMR1,2 registers, test signals with oscilloscope and&lt;/P&gt;&lt;P&gt;use guidelines from link&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/307723"&gt;i.MX6Q NAND boot issues&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do not think that NMI watchdog can shed more light on problem.&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>Mon, 05 Mar 2018 06:25:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725653#M112851</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-03-05T06:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding booting issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725654#M112852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think my question wasn't clear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I'm implementing the system as a product, there will not be any access to target console. Then, if the system fails to boot up or continuously restarting, I would like to indicate the user "system failed in Linux boot". So how I can understand the system failure without any access to kernel log.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Mar 2018 10:58:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725654#M112852</guid>
      <dc:creator>mathew_k_t</dc:creator>
      <dc:date>2018-03-05T10:58:43Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding booting issues</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725655#M112853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi mathew_k_t&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in application, when it successfully boot, you can add led as indicator.&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>Mon, 05 Mar 2018 11:20:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Understanding-booting-issues/m-p/725655#M112853</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-03-05T11:20:40Z</dc:date>
    </item>
  </channel>
</rss>

