<?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: P1022:kernel hangs after loading device tree print in P-Series</title>
    <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508177#M3151</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Santosh, I think there is some problem with your DRAM. Could you print memory contents @ address 0x0 in u-boot? Also, try to write some dummy data to it. 0x0 is usually the address of mapped DRAM. You can look for the mapped DRAM address in board config file in u-boot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 May 2016 09:13:32 GMT</pubDate>
    <dc:creator>adeel</dc:creator>
    <dc:date>2016-05-10T09:13:32Z</dc:date>
    <item>
      <title>P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508165#M3139</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are using P1022 processor based custom board.&lt;/P&gt;&lt;P&gt;SDKv1.9 is used to bring up Linux on this board.Using SD card interface we are able to run the U-boot.&lt;/P&gt;&lt;P&gt;While running kernel image(uImage) through uboot from SD card,We are getting console prints up to "&lt;STRONG&gt;Loading&lt;/STRONG&gt; &lt;STRONG&gt;Device Tree to 004e5000, end 004ebc27 ... OK" &lt;/STRONG&gt;and hangs.After enabling DEBUG macro in u-boot,prints are coming up to "&lt;STRONG&gt;## Transferring control to Linux (at address 20000000) ..." &lt;/STRONG&gt;and hangs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;LOG:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;## Booting kernel from Legacy Image at 01000000 ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Image Name:&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Image Type:&amp;nbsp;&amp;nbsp; PowerPC Linux Kernel Image (gzip compressed)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Data Size:&amp;nbsp;&amp;nbsp;&amp;nbsp; 4256593 Bytes = 4.1 MiB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Load Address: 20000000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Entry Point:&amp;nbsp; 20000000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Verifying Checksum ... OK&lt;/P&gt;&lt;P&gt;## Flattened Device Tree blob at 00c00000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Booting using the fdt blob at 0xc00000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Uncompressing Kernel Image ... OK&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Loading Device Tree to 004e5000, end 004ebc27 ... OK&lt;/P&gt;&lt;P&gt;## Transferring control to Linux (at address 20000000) ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;hangs......&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By running codewarrior in attach mode,we are getting PC value as &lt;STRONG&gt;0xe00.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Can any one please help me in this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Santosh Kumar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 12:11:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508165#M3139</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-09T12:11:54Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508166#M3140</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try enabling early console.&amp;nbsp; You might get more output.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 12:25:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508166#M3140</guid>
      <dc:creator>timur_tabi</dc:creator>
      <dc:date>2016-05-09T12:25:38Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508167#M3141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/timurtabi"&gt;timurtabi&lt;/A&gt;​,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your replay...&lt;/P&gt;&lt;P&gt;I am not able to find any early printk/console option in kernel hacking in menuconfig..&lt;/P&gt;&lt;P&gt;kernel debugging options are not enabled in menuconfig.&lt;/P&gt;&lt;P&gt;But if we see .config file &lt;STRONG&gt;CONFIG_PPC_EARLY_DEBUG&lt;/STRONG&gt; and &lt;STRONG&gt;CONFIG_EARLY_PRINTK &lt;/STRONG&gt;are enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Santosh Kumar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 13:49:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508167#M3141</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-09T13:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508168#M3142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You want the 'earlycon' command line parameter.&amp;nbsp; See &lt;A href="https://www.kernel.org/doc/Documentation/kernel-parameters.txt" title="https://www.kernel.org/doc/Documentation/kernel-parameters.txt"&gt;https://www.kernel.org/doc/Documentation/kernel-parameters.txt&lt;/A&gt;.&amp;nbsp; I don't remember what the exact parameters would be.&amp;nbsp; You would need to figure out the physical address of the serial port you're using.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 13:57:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508168#M3142</guid>
      <dc:creator>timur_tabi</dc:creator>
      <dc:date>2016-05-09T13:57:30Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508169#M3143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, What is the full address 0xe00?????? and what is mapped at 0xe00? Is it PCI?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 14:31:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508169#M3143</guid>
      <dc:creator>adeel</dc:creator>
      <dc:date>2016-05-09T14:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508170#M3144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Adeel,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your replay...&lt;/P&gt;&lt;P&gt;Full address is 0x00000E00.&lt;/P&gt;&lt;P&gt;It is mapped to &lt;STRONG&gt;IVOR14 - instruction TLB error &lt;/STRONG&gt;interrupt vector.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Santosh Kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 14:48:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508170#M3144</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-09T14:48:41Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508171#M3145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, you're going to have to figure that out.&amp;nbsp; It's the base address of the serial port you're using.&amp;nbsp; This is basic kernel debugging.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 14:49:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508171#M3145</guid>
      <dc:creator>timur_tabi</dc:creator>
      <dc:date>2016-05-09T14:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508172#M3146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are unable to load u-boot elf to &lt;STRONG&gt;core-1 &lt;/STRONG&gt;through debugger due to some issue. On core-0 u-boot is running successfully.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;For linux porting whether both the cores should be enabled or not??&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Whether this may cause any issue on linux porting???&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 15:17:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508172#M3146</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-09T15:17:22Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508173#M3147</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Santosh, I think there is no instruction at address 0x20000000. Why your Kernel Load address is 0x20000000:&lt;/P&gt;&lt;P&gt;Load Address: 20000000&lt;/P&gt;&lt;P&gt;Entry Point:&amp;nbsp; 20000000&lt;/P&gt;&lt;P&gt;Usually they are 0x00000000.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 15:26:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508173#M3147</guid>
      <dc:creator>adeel</dc:creator>
      <dc:date>2016-05-09T15:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508174#M3148</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have tried with default 0x0 address and observed prints are coming up to "&lt;STRONG style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;Uncompressing Kernel Image ..."(OK print is not coming) &lt;/STRONG&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt; getting hanged.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;After changing load address and entry point to 0x20000000 using mkimage,uncompressing is working fine.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 15:41:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508174#M3148</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-09T15:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508175#M3149</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;0 is the correct address to uncompress the kernel to.&amp;nbsp; 0xc00000 is a bad place to load the fdt, as it can get overwritten by a large kernel.&amp;nbsp; Move it higher.&amp;nbsp; Likewise, I would load the uImage higher than 0x01000000.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 May 2016 21:37:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508175#M3149</guid>
      <dc:creator>scottwood</dc:creator>
      <dc:date>2016-05-09T21:37:48Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508176#M3150</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks for your replay...&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;We have tried with default uImage with load address as 0x0 and observed prints are coming up to "&lt;/SPAN&gt;&lt;SPAN style="font-weight: bold; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;Uncompressing Kernel Image ..."(OK print is not coming) &lt;/SPAN&gt;&lt;SPAN style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;and &lt;/SPAN&gt;&lt;SPAN style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;getting hanged.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;We have observed u-boot is writing some interrupt vectors from 0x100 to 0xf00 locations.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;After changing load address to 0x20000000 using mkimage uncompressing is working fine.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;We are not sure whether this vectors causing issue or not...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;Please find the screenshot for the interrupt vector address(&lt;STRONG&gt;IVOR&lt;/STRONG&gt;) in codewarrior register list..&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="error.jpg"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/57041iBAA2D2091645ACE6/image-size/large?v=v2&amp;amp;px=999" role="button" title="error.jpg" alt="error.jpg" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 05:15:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508176#M3150</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-10T05:15:08Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508177#M3151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Santosh, I think there is some problem with your DRAM. Could you print memory contents @ address 0x0 in u-boot? Also, try to write some dummy data to it. 0x0 is usually the address of mapped DRAM. You can look for the mapped DRAM address in board config file in u-boot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 09:13:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508177#M3151</guid>
      <dc:creator>adeel</dc:creator>
      <dc:date>2016-05-10T09:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508178#M3152</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am able to print memory content of DRAM(0x0) using u-boot.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;U-boot is getting stuck after performing write operation from 0x0 to 0xff0.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif;"&gt;We have observed u-boot is writing some interrupt vectors from 0x100 to 0xf00 locations.If we are doing write operations to these vector addresses u-boot is getting stuck.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Please find the attached memory dump in log file.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 09:56:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508178#M3152</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-10T09:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508179#M3153</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Scott is also right. Probably your device tree is overwritten by uImage. Download your uImage at 0x08000000.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 09:57:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508179#M3153</guid>
      <dc:creator>adeel</dc:creator>
      <dc:date>2016-05-10T09:57:47Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508180#M3154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;we are running uImage at 0x20000000(Load Address) and changed device tree load address to 0x08000000 and observed console prints are coming up to "&lt;STRONG&gt;Loading Device Tree to 004e5000, end 004ebc27 ... OK" &lt;/STRONG&gt;​and hangs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 10:33:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508180#M3154</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-10T10:33:48Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508181#M3155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Santosh, it is not overwritten problem. Your DRAM doesn't look good. I think you should check with your hardware guys. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 11:48:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508181#M3155</guid>
      <dc:creator>adeel</dc:creator>
      <dc:date>2016-05-10T11:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508182#M3156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ours is&lt;STRONG&gt; 2GB DDR&lt;/STRONG&gt;, we performed &lt;STRONG&gt;mtest&lt;/STRONG&gt; and observed,except for the memory range&amp;nbsp; 0x100 to 0x1000 (where IVOR 0 to 15) mtest is passed for other memory regions of DDR. &lt;/P&gt;&lt;P&gt;Still it can be a DDR hardware error or we are missing something in configuration or it is expected behavior for IVOR mapped region. &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;And whether we need to relocate IVOR to some other region?&lt;/STRONG&gt;&amp;nbsp; .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 12:53:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508182#M3156</guid>
      <dc:creator>santoshkumaraki</dc:creator>
      <dc:date>2016-05-10T12:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508183#M3157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, you don't need to relocate IVORs.&amp;nbsp; You should not be taking an exception during the handoff.&amp;nbsp; That said, if you run a recent upstream U-Boot, IVORs are elsewhere which makes it easier to diagnose crashes during boot handoff.&amp;nbsp; Otherwise, you need to debug it the hard way to find out why an exception is happening.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 May 2016 18:43:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508183#M3157</guid>
      <dc:creator>scottwood</dc:creator>
      <dc:date>2016-05-10T18:43:47Z</dc:date>
    </item>
    <item>
      <title>Re: P1022:kernel hangs after loading device tree print</title>
      <link>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508184#M3158</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Santosh, If you load uncompressed image at 0x20000000 and the crashed happened then can you print memory content from debugger?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 May 2016 08:46:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/P-Series/P1022-kernel-hangs-after-loading-device-tree-print/m-p/508184#M3158</guid>
      <dc:creator>adeel</dc:creator>
      <dc:date>2016-05-11T08:46:25Z</dc:date>
    </item>
  </channel>
</rss>

