<?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: Sabresd board and WDOG_B</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526944#M84471</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you use WDOG1, you can use below cfg.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;gpc {&lt;/P&gt;&lt;P&gt;&amp;nbsp; fsl,wdog-reset = &amp;lt;1&amp;gt;;&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;wdog2 {&lt;/P&gt;&lt;P&gt;&amp;nbsp;status = "disabled";&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;wdog1 {&lt;/P&gt;&lt;P&gt;&amp;nbsp;status = "ok";&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It should can reboot through WDOG1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to use WDOG2, you need to check your HW design carefully. Once WDOG2&amp;nbsp; enable WCR signal, WDOG_B should be triggered to notify CPU.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 03 Jan 2018 01:19:41 GMT</pubDate>
    <dc:creator>jiujinhong</dc:creator>
    <dc:date>2018-01-03T01:19:41Z</dc:date>
    <item>
      <title>Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526936#M84463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&amp;nbsp; Support,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recently we discovered a strange issue with our own i.MX6 quad board which is similar to sabresd.&amp;nbsp; The OS we ported is Linux 3.14.28 and everything looks fine except we could not successfully reboot the board when we issued the reboot command on console.&amp;nbsp; In our design, we skip WDOG_B circuitry and let it float on GPIO_1 (WDOG_B).&amp;nbsp; However, we have to define &lt;/P&gt;&lt;P&gt;&amp;amp;gpc {&lt;/P&gt;&lt;P&gt;&amp;nbsp; /* use ldo-bypass, u-boot will check it and configure */&lt;/P&gt;&lt;P&gt;// fsl,ldo-bypass = &amp;lt;1&amp;gt;;&lt;/P&gt;&lt;P&gt;// fsl,wdog-reset = &amp;lt;2&amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp; fsl,wdog-reset = &amp;lt;1&amp;gt;;&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;and &lt;/P&gt;&lt;P&gt;&amp;amp;wdog2 {&lt;/P&gt;&lt;P&gt;&amp;nbsp; status = "okay";&lt;/P&gt;&lt;P&gt;// status = "disabled";&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;in our device tree to make this board successfully booted.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we issue "reboot" on console, then the board would be started and hangs at starting kernel.&amp;nbsp; Also, the board is restarted after running up to the following section in mxc_restart in system.c without going through the whole part.&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;__raw_writew(wcr_enable, wdog_base);&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;pr_err("mxc_restart step 3\n");&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;/*&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt; * Due to imx6q errata ERR004346 (WDOG: WDOG SRS bit requires to be&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt; * written twice), we add another two writes to ensure there must be at&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt; * least two writes happen in the same one 32kHz clock period.&amp;nbsp; We save&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt; * the target check here, since the writes shouldn't be a huge burden&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt; * for other platforms.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt; */&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;__raw_writew(wcr_enable, wdog_base);&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;/TD&gt;&lt;TD&gt;__raw_writew(wcr_enable, wdog_base);&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DO you have any suggestion we could eliminate this soft reboot issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vincent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2016 10:01:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526936#M84463</guid>
      <dc:creator>vincentchou</dc:creator>
      <dc:date>2016-08-15T10:01:07Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526937#M84464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vincent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for reliable board reset wdog should reset also pmic (using pwron), as it is done&lt;/P&gt;&lt;P&gt;on sabre schematic spf-27392 p.21 U507 buffer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Aug 2016 10:54:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526937#M84464</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-08-15T10:54:23Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526938#M84465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&amp;nbsp; Igor,&lt;/P&gt;&lt;P&gt;Assuming we could not make another batch of new boards to fix this issue, is there anyway we could skip this problem or lessen the impact?&amp;nbsp; &lt;/P&gt;&lt;P&gt;Vincent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 01:12:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526938#M84465</guid>
      <dc:creator>vincentchou</dc:creator>
      <dc:date>2016-08-16T01:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526939#M84466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vincent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one can try to use ldo on (disable ldo-bypass) configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 01:35:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526939#M84466</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-08-16T01:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526940#M84467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&amp;nbsp; Igor,&lt;/P&gt;&lt;P&gt;Yes, that is exactly we did in the device tree to disable ldo-bypass.&amp;nbsp; When we did that, the board could boot.&amp;nbsp; The problem is that it hangs when we issue "reboot" command on console.&amp;nbsp; Any suggestion?&lt;/P&gt;&lt;P&gt;Vincent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 01:56:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526940#M84467</guid>
      <dc:creator>vincentchou</dc:creator>
      <dc:date>2016-08-16T01:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526941#M84468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&amp;nbsp; Igor,&lt;/P&gt;&lt;P&gt;In addition to the following modification I made in imx6qdl-sabresd.dtsi&lt;/P&gt;&lt;P&gt;----&lt;/P&gt;&lt;P&gt;&amp;amp;gpc {&lt;/P&gt;&lt;P&gt;&amp;nbsp; /* use ldo-bypass, u-boot will check it and configure */&lt;/P&gt;&lt;P&gt;// fsl,ldo-bypass = &amp;lt;1&amp;gt;;&lt;/P&gt;&lt;P&gt;// fsl,wdog-reset = &amp;lt;2&amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp; fsl,wdog-reset = &amp;lt;1&amp;gt;;&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Is there any other steps I should do to disable ldo-bypass?&lt;/P&gt;&lt;P&gt;Vincent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 02:15:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526941#M84468</guid>
      <dc:creator>vincentchou</dc:creator>
      <dc:date>2016-08-16T02:15:58Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526942#M84469</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have you fixed your issu, Vincent?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Dec 2017 08:18:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526942#M84469</guid>
      <dc:creator>jiujinhong</dc:creator>
      <dc:date>2017-12-08T08:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526943#M84470</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&amp;nbsp; Mr. Hong,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No, we still have issues about setting WDOG_B.&amp;nbsp; Is it related to the extra LDO on Sabresd Board?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vincent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2018 10:21:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526943#M84470</guid>
      <dc:creator>vincentchou</dc:creator>
      <dc:date>2018-01-02T10:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Sabresd board and WDOG_B</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526944#M84471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you use WDOG1, you can use below cfg.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;gpc {&lt;/P&gt;&lt;P&gt;&amp;nbsp; fsl,wdog-reset = &amp;lt;1&amp;gt;;&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;wdog2 {&lt;/P&gt;&lt;P&gt;&amp;nbsp;status = "disabled";&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;amp;wdog1 {&lt;/P&gt;&lt;P&gt;&amp;nbsp;status = "ok";&lt;/P&gt;&lt;P&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It should can reboot through WDOG1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to use WDOG2, you need to check your HW design carefully. Once WDOG2&amp;nbsp; enable WCR signal, WDOG_B should be triggered to notify CPU.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Jan 2018 01:19:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Sabresd-board-and-WDOG-B/m-p/526944#M84471</guid>
      <dc:creator>jiujinhong</dc:creator>
      <dc:date>2018-01-03T01:19:41Z</dc:date>
    </item>
  </channel>
</rss>

