<?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: i.MX28 - Reset problem in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663546#M101882</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an excerpt from our modified mach-mxs.c, based on the 4.4 kernel source. Sounds like you're using Windows CE, so I'm unable to&amp;nbsp;offer any porting advice &lt;IMG alt="Smiley Happy" class="emoticon emoticon-smileyhappy" id="smileyhappy" src="https://community.nxp.com/i/smilies/16x16_smiley-happy.png" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will provide a formal patch soon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that rtc_addr (0x80056000) and dram_addr (0x800e0000) base addresses are obtained&amp;nbsp;from our device tree:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define MXS_CLKCTRL_RESET_CHIP (1 &amp;lt;&amp;lt; 1)&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define MXS_PWRDOWN_DRAM (1 &amp;lt;&amp;lt; 16)&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define MXS_DRAM_CTR16 0x40&lt;/SPAN&gt;

&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_CTRL 0x0&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_WATCHDOG 0x50&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_PERSISTENT1 0x70&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_CTRL_WATCHDOGEN 0x00000010&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_PERSISTENT1_FORCE_UPDATER 0x80000000&lt;/SPAN&gt;

&lt;SPAN style="font-size: 12px; color: #333399;"&gt;static void mxs_restart(enum reboot_mode mode, const char *cmd)&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;{&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; //set HW_RTC_WATCHDOG to 2 seconds:&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; if (rtc_addr) {&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; writel(2000, rtc_addr + STMP3XXX_RTC_WATCHDOG);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; __mxs_setl(STMP3XXX_RTC_CTRL_WATCHDOGEN, rtc_addr + STMP3XXX_RTC_CTRL);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; __mxs_setl(STMP3XXX_RTC_PERSISTENT1_FORCE_UPDATER, rtc_addr + STMP3XXX_RTC_PERSISTENT1);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; }&lt;/SPAN&gt;

&lt;SPAN style="font-size: 12px; color: #333399;"&gt; if (dram_addr) {&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; pr_err("Powering down DRAM...\n");&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; __raw_writel(MXS_PWRDOWN_DRAM, dram_addr + MXS_DRAM_CTR16);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; pr_err("Failed to power down the DRAM\n");&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; }&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; else {&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; pr_err("dram_addr not mapped, bypassing DRAM power-down\n");&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; }&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px;"&gt;//falls through to the original reboot mechanism here&lt;/SPAN&gt;

&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Nov 2020 13:56:46 GMT</pubDate>
    <dc:creator>hungry_horace</dc:creator>
    <dc:date>2020-11-02T13:56:46Z</dc:date>
    <item>
      <title>i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663536#M101872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Whilst torture-testing a design&amp;nbsp;that is largely based on the i.MX28 EVK, we are encountering intermittent soft reboot/reset failures. The behavior is the same as that observed earlier during the design process when we discovered that we were exceeding the 100mA inrush current limitation imposed by the power supply subsystem (i.MX28 Applications Processor Reference Manual, Rev.2 p. 947). This prevents the startup sequence from completing, and leaves the board in a totally locked up state.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The occurrence is very rare, but because of the nature of the product, this type of behavior is simply not&amp;nbsp;something we can ship with.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We believe we have traced&amp;nbsp;the root cause to the DDR2 memory, which is powered from the VDDA rail. We are using a 256MB part:&amp;nbsp;&lt;A class="link-titled" href="https://www.micron.com/parts/dram/ddr2-sdram/mt47h128m16rt-25e?pc=%7B4064C2CD-AB47-4DB0-AB9A-A91579FD303A%7D" title="https://www.micron.com/parts/dram/ddr2-sdram/mt47h128m16rt-25e?pc=%7B4064C2CD-AB47-4DB0-AB9A-A91579FD303A%7D"&gt;Micron Technology, Inc. - MT47H128M16RT-25E&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using a current probe, upon reset we&amp;nbsp;see the inrush hitting a&amp;nbsp;100mA ceiling.&amp;nbsp;Driving the DDR2 from a separate rail lowers that current to around 60mA. This isn't a&amp;nbsp;suitable solution because&amp;nbsp;it prevents us from being able to operate under battery power.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are seeking a recommendation on how to resolve this.&amp;nbsp;For example, any suggestions for alternative 256MB DDR2 parts that operate within the&amp;nbsp;100mA constraints.&amp;nbsp;We are approaching the&amp;nbsp;end of the development cycle, so&amp;nbsp;we really have to implement the least invasive fix possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2016 16:59:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663536#M101872</guid>
      <dc:creator>hungry_horace</dc:creator>
      <dc:date>2016-11-15T16:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663537#M101873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most likely, the issue is caused by some inappropriate design of the power supply section. Is your system powered by 5V only source, or by battery only source, or the power is mixed? Do you use linear regulators or DCDC converter as the main power supply when the system is up and running? Also, please provide your system's schematic to make me able to check it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Artur&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Nov 2016 11:58:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663537#M101873</guid>
      <dc:creator>art</dc:creator>
      <dc:date>2016-11-29T11:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663538#M101874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just want to follow up - after discussing with NXP FAE's,&amp;nbsp;we established that&amp;nbsp;during the reboot, the RAM can occasionally be left in a state where it's drawing over 100mA.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This has been resolved by editing&amp;nbsp;mach-mxs.c's machine_restart function. Instead of asserting the chip reset, we configure the watchdog for a two second timeout, then power down the DRAM by setting the POWER_DOWN bit in HW_DRAM_CTL16.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Nov 2016 15:03:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663538#M101874</guid>
      <dc:creator>hungry_horace</dc:creator>
      <dc:date>2016-11-29T15:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663539#M101875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;Thanks for the reply Artur, my follow-up is below.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Nov 2016 15:06:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663539#M101875</guid>
      <dc:creator>hungry_horace</dc:creator>
      <dc:date>2016-11-29T15:06:52Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663540#M101876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tim,&lt;/P&gt;&lt;P&gt;i'm interested about this issue and need more information. How often does it occured? Do you use a mainline kernel? Is there a specific test scenario?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2016 18:42:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663540#M101876</guid>
      <dc:creator>lategoodbye</dc:creator>
      <dc:date>2016-12-20T18:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663541#M101877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stefan - sorry for the delay. Happens once&amp;nbsp;every few hundred reboots, probably depends on the RAM configuration you're using. We use a 4.4.0 mainline kernel.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a patch I want to submit, but I have no idea who to send it to.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Jan 2017 20:03:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663541#M101877</guid>
      <dc:creator>hungry_horace</dc:creator>
      <dc:date>2017-01-21T20:03:45Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663542#M101878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please run&amp;nbsp;./scripts/get_maintainer.pl -f arch/arm/mach-mxs/mach-mxs.c to know the people and mailing lists you should send this patch to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 22 Jan 2017 00:41:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663542#M101878</guid>
      <dc:creator>fabio_estevam</dc:creator>
      <dc:date>2017-01-22T00:41:32Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663543#M101879</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tim, thank you for your post. I believe we may have a similar issue found during reboot testing of our i.mx28 design. I was running a reboot test overnight testing a fix for the windows ce ethernet driver which would occasionally fail to reconnect after reboot (turns out the PHY reset conditions were not obeyed). Anyway a couple of times in the hundreds of reboots our board failed to restart.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i think this is similar because we do not even see any of the early debug output. I am yet to check the PMU supply rails in this state. It seems to make sense that the reset may occur when the sdram is active doing something and requiring a lot of current. Your reboot seems a good work around to prevent this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you try the alternative reboot that includes the PMU? I believe there are two reset bits one a processor reset and the other includes the PMU. This was my next thing to try.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as for your application, although this seems rare we need to be sure if our systems are remotely rebooted they do come back online.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jan 2017 22:57:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663543#M101879</guid>
      <dc:creator>markwilliams</dc:creator>
      <dc:date>2017-01-25T22:57:12Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663544#M101880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually further to my comment above the&amp;nbsp;HW_CLKCTRL_ENET_RESET_BY_SW_CHIP won't help as it seems the current limit is enabled by default during startup. I will try your suggestion.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jan 2017 12:12:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663544#M101880</guid>
      <dc:creator>markwilliams</dc:creator>
      <dc:date>2017-01-26T12:12:55Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663545#M101881</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark, does your design also have 256 MB RAM?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jan 2017 17:44:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663545#M101881</guid>
      <dc:creator>lategoodbye</dc:creator>
      <dc:date>2017-01-26T17:44:45Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663546#M101882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an excerpt from our modified mach-mxs.c, based on the 4.4 kernel source. Sounds like you're using Windows CE, so I'm unable to&amp;nbsp;offer any porting advice &lt;IMG alt="Smiley Happy" class="emoticon emoticon-smileyhappy" id="smileyhappy" src="https://community.nxp.com/i/smilies/16x16_smiley-happy.png" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will provide a formal patch soon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that rtc_addr (0x80056000) and dram_addr (0x800e0000) base addresses are obtained&amp;nbsp;from our device tree:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define MXS_CLKCTRL_RESET_CHIP (1 &amp;lt;&amp;lt; 1)&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define MXS_PWRDOWN_DRAM (1 &amp;lt;&amp;lt; 16)&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define MXS_DRAM_CTR16 0x40&lt;/SPAN&gt;

&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_CTRL 0x0&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_WATCHDOG 0x50&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_PERSISTENT1 0x70&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_CTRL_WATCHDOGEN 0x00000010&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;#define STMP3XXX_RTC_PERSISTENT1_FORCE_UPDATER 0x80000000&lt;/SPAN&gt;

&lt;SPAN style="font-size: 12px; color: #333399;"&gt;static void mxs_restart(enum reboot_mode mode, const char *cmd)&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt;{&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; //set HW_RTC_WATCHDOG to 2 seconds:&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; if (rtc_addr) {&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; writel(2000, rtc_addr + STMP3XXX_RTC_WATCHDOG);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; __mxs_setl(STMP3XXX_RTC_CTRL_WATCHDOGEN, rtc_addr + STMP3XXX_RTC_CTRL);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; __mxs_setl(STMP3XXX_RTC_PERSISTENT1_FORCE_UPDATER, rtc_addr + STMP3XXX_RTC_PERSISTENT1);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; }&lt;/SPAN&gt;

&lt;SPAN style="font-size: 12px; color: #333399;"&gt; if (dram_addr) {&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; pr_err("Powering down DRAM...\n");&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; __raw_writel(MXS_PWRDOWN_DRAM, dram_addr + MXS_DRAM_CTR16);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; pr_err("Failed to power down the DRAM\n");&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; }&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; else {&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; pr_err("dram_addr not mapped, bypassing DRAM power-down\n");&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; mdelay(50);&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px; color: #333399;"&gt; }&lt;/SPAN&gt;
&lt;SPAN style="font-size: 12px;"&gt;//falls through to the original reboot mechanism here&lt;/SPAN&gt;

&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Nov 2020 13:56:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663546#M101882</guid>
      <dc:creator>hungry_horace</dc:creator>
      <dc:date>2020-11-02T13:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX28 - Reset problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663547#M101883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it does&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jan 2017 22:30:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX28-Reset-problem/m-p/663547#M101883</guid>
      <dc:creator>markwilliams</dc:creator>
      <dc:date>2017-01-26T22:30:24Z</dc:date>
    </item>
  </channel>
</rss>

