<?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: problem with booting linux on MPC8260 in PowerQUICC Processors</title>
    <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254885#M403</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you tell exactly what kind of "tx ring buffer set up by U-Boot"?&lt;/P&gt;&lt;P&gt;I can not understand :smileysad:&lt;/P&gt;&lt;P&gt;Early debug can realy help me&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Sep 2013 13:46:31 GMT</pubDate>
    <dc:creator>eugenetodoruk</dc:creator>
    <dc:date>2013-09-27T13:46:31Z</dc:date>
    <item>
      <title>problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254877#M395</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;UPD:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;My idea to debug kernel with BDI was wrong. BDI not working with memory at the current frequency... And I can't fix this problem.&lt;/P&gt;&lt;P&gt;Now I debug kernel with the GPIO led &lt;SPAN aria-label="Happy" class="emoticon_happy emoticon-inline" style="height:16px;width:16px;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My next problem in caches and MMU. When Linux tryed to setup instruction cache or data cache or both, board going to reset (in u-boot both caches turned off). If I not turned on both caches, then my board hangs after turning on the MMU for real:&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/* Now turn on the MMU for real! */&lt;/P&gt;&lt;P&gt;li&amp;gt;-r4,MSR_KERNEL&lt;/P&gt;&lt;P&gt;FIX_SRR1(r4,r5)&lt;/P&gt;&lt;P&gt;lis&amp;gt;r3,start_kernel@h&lt;/P&gt;&lt;P&gt;ori&amp;gt;r3,r3,start_kernel@l&lt;/P&gt;&lt;P&gt;mtspr&amp;nbsp;&amp;nbsp;&amp;nbsp; SPRN_SRR0,r3&lt;/P&gt;&lt;P&gt;mtspr&amp;nbsp;&amp;nbsp;&amp;nbsp; SPRN_SRR1,r4&lt;/P&gt;&lt;P&gt;SYNC&lt;/P&gt;&lt;P&gt;RFI&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you answer me why caches can not work? This may be due to wrong initialization of memory or local bus?&lt;/P&gt;&lt;P&gt;Where should I look for the MMU problem?&lt;/P&gt;&lt;P&gt;Sorry for my english&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt; previous message:&lt;/P&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have a problem with booting linux on our board with MPC8260 processor.&lt;/P&gt;&lt;P&gt;The thing is we made a custom board for our own needs, and it resets after u-boot transfers control to 0x0 address. I've tried to debug it using BDI2000. What I do is catching the instruction on 0x0 and then going on step by step. Sometimes it resets from a random address, sometimes it jumps to the non-sdram memory address. And it does so almost right after catching the instruction, and I don't advance in debugging very far.&lt;/P&gt;&lt;P&gt;Can you help me?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;U-Boot 2013.07-rc1-00012-g7315cfd-dirty (Aug 07 2013 - 18:39:32)&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;MPC8260 Reset Status: Check Stop, External Soft, External Hard&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;MPC8260 Clock Configuration&lt;/P&gt;&lt;P&gt;- Bus-to-Core Mult 3x, VCO Div 2, 60x Bus Freq&amp;nbsp; 33-100, Core Freq 100-300&lt;/P&gt;&lt;P&gt;- dfbrg 0, corecnf 0x08, busdf 3, cpmdf 1, plldf 0, pllmf 1, pcidf 3&lt;/P&gt;&lt;P&gt;- vco_out&amp;nbsp; 133333332, scc_clk&amp;nbsp;&amp;nbsp; 33333333, brg_clk&amp;nbsp;&amp;nbsp; 33333333&lt;/P&gt;&lt;P&gt;- cpu_clk&amp;nbsp;&amp;nbsp; 99999999, cpm_clk&amp;nbsp;&amp;nbsp; 66666666, bus_clk&amp;nbsp;&amp;nbsp; 33333333&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CPU:&amp;nbsp;&amp;nbsp; MPC8260 (HiP4 Rev 14, Mask B.1 4K25A) at 100 MHz&lt;/P&gt;&lt;P&gt;Board: PR1-2&lt;/P&gt;&lt;P&gt;DRAM:&amp;nbsp; 64 MiB&lt;/P&gt;&lt;P&gt;Flash: 128 MiB&lt;/P&gt;&lt;P&gt;In:&amp;nbsp;&amp;nbsp;&amp;nbsp; serial&lt;/P&gt;&lt;P&gt;Out:&amp;nbsp;&amp;nbsp; serial&lt;/P&gt;&lt;P&gt;Err:&amp;nbsp;&amp;nbsp; serial&lt;/P&gt;&lt;P&gt;Net:&amp;nbsp;&amp;nbsp; FCC1, FCC2&lt;/P&gt;&lt;P&gt;Hit any key to stop autoboot:&amp;nbsp; 0&lt;/P&gt;&lt;P&gt;U-Boot &amp;gt; run nfsboot&lt;/P&gt;&lt;P&gt;Using FCC1 device&lt;/P&gt;&lt;P&gt;TFTP from server 192.168.0.5; our IP address is 192.168.0.23&lt;/P&gt;&lt;P&gt;Filename 'uImage.bin'.&lt;/P&gt;&lt;P&gt;Load address: 0x500000&lt;/P&gt;&lt;P&gt;Loading: #################################################################&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; #################################################################&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; #################################################################&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; #################################################################&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ##################################################&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 587.9 KiB/s&lt;/P&gt;&lt;P&gt;done&lt;/P&gt;&lt;P&gt;Bytes transferred = 1585226 (18304a hex)&lt;/P&gt;&lt;P&gt;Using FCC1 device&lt;/P&gt;&lt;P&gt;TFTP from server 192.168.0.5; our IP address is 192.168.0.23&lt;/P&gt;&lt;P&gt;Filename 'uImage-mpc8260-pr1-2.dtb'.&lt;/P&gt;&lt;P&gt;Load address: 0x400000&lt;/P&gt;&lt;P&gt;Loading: ###&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 479.5 KiB/s&lt;/P&gt;&lt;P&gt;done&lt;/P&gt;&lt;P&gt;Bytes transferred = 12288 (3000 hex)&lt;/P&gt;&lt;P&gt;## Current stack ends at 0x03f87618&lt;/P&gt;&lt;P&gt;*&amp;nbsp; kernel: cmdline image address = 0x00500000&lt;/P&gt;&lt;P&gt;## Booting kernel from Legacy Image at 00500000 ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Image Name:&amp;nbsp;&amp;nbsp; Angstrom/2.6.39/mpc8260-pr1-2&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; 1585162 Bytes = 1.5 MiB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Load Address: 00000000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Entry Point:&amp;nbsp; 00000000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Verifying Checksum ... OK&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; kernel data at 0x00500040, len = 0x0018300a (1585162)&lt;/P&gt;&lt;P&gt;## Flattened Device Tree blob at 00400000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Booting using the fdt blob at 0x400000&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Uncompressing Kernel Image ... OK&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; kernel loaded at 0x00000000, end = 0x00315d20&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Loading Device Tree to 007f9000, end 007fefff ... OK&lt;/P&gt;&lt;P&gt;## Transferring control to Linux (at address 00000000) ...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Booting using OF flat tree...&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337316"&gt;pr1-2.c.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337316"&gt;defconfig.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337316"&gt;pr1-2.dts.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-337316"&gt;pr1-2.h.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2013 13:46:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254877#M395</guid>
      <dc:creator>eugenetodoruk</dc:creator>
      <dc:date>2013-08-14T13:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254878#M396</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Eugene, this sounds like a memory setup problem.&amp;nbsp; Also make sure you are running BDI&amp;nbsp; initially with caches disabled.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Aug 2013 15:40:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254878#M396</guid>
      <dc:creator>sinanakman</dc:creator>
      <dc:date>2013-08-14T15:40:16Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254879#M397</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I do not recommend using JTAG to debug early Linux startup on this chip (at least until you're running in C code).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First, make sure the device tree toplevel compatible ("fsl,PR1-2") is recognized by the platform code you're trying to use.&amp;nbsp; BTW, you shouldn't us "fsl," as the vendor prefix because this isn't a Freescale board.&amp;nbsp; Also make sure that the addresses are correct for how you've got U-Boot configuring things like the IMMR, and that you're describing the right serial port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next, try using CONFIG_PPC_EARLY_DEBUG_CPM.&amp;nbsp; If that doesn't output anything, double check sure that CONFIG_PPC_EARLY_DEBUG_CPM_ADDR is set properly for how U-Boot is initializing the serial port.&amp;nbsp; If that doesn't help, try manually outputting a character immediately after __start in head_32.S.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Aug 2013 17:41:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254879#M397</guid>
      <dc:creator>scottwood</dc:creator>
      <dc:date>2013-08-23T17:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254880#M398</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Scott, what would be your reservation running BDI on 82xx ? It might be a useful info for future. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Aug 2013 04:10:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254880#M398</guid>
      <dc:creator>sinanakman</dc:creator>
      <dc:date>2013-08-24T04:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254881#M399</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the answer.&lt;/P&gt;&lt;P&gt;I agree that it looks like a memory problem. But u-boot working right.&lt;/P&gt;&lt;P&gt;What does it mean "running BDI&amp;nbsp; initially with caches disabled"? I must set "DCACHE FLUSH" in BDI configuration?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Aug 2013 12:19:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254881#M399</guid>
      <dc:creator>eugenetodoruk</dc:creator>
      <dc:date>2013-08-26T12:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254882#M400</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the answer.&lt;/P&gt;&lt;P&gt;I tried to setup CONFIG_PPC_EARLY_DEBUG_CPM, but I don't see the debug information. Do I understand correctly that CONFIG_PPC_EARLY_DEBUG_CPM_ADDR is the registers address of my console? I know that my SMC1 registers live at 0xf0011a82, and I set CONFIG_PPC_EARLY_DEBUG_CPM_ADDR=0xf0011a82.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt;&amp;gt;If that doesn't help, try manually outputting a character immediately after __start in head_32.S.&lt;/P&gt;&lt;P&gt;How can I do it? Can you give me example? Thank you very much&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Aug 2013 12:33:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254882#M400</guid>
      <dc:creator>eugenetodoruk</dc:creator>
      <dc:date>2013-08-26T12:33:22Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254883#M401</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure -- I may have been thinking of 85xx where there are sections of the init that can't be stepped through due to a hardware quirk (needing to have a valid mapping in AS0 for IVOR15 in order for a JTAG device to receive debug events).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Sep 2013 16:21:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254883#M401</guid>
      <dc:creator>scottwood</dc:creator>
      <dc:date>2013-09-12T16:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254884#M402</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, the address is for the tx ring buffer set up by U-Boot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Sep 2013 16:22:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254884#M402</guid>
      <dc:creator>scottwood</dc:creator>
      <dc:date>2013-09-12T16:22:12Z</dc:date>
    </item>
    <item>
      <title>Re: problem with booting linux on MPC8260</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254885#M403</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you tell exactly what kind of "tx ring buffer set up by U-Boot"?&lt;/P&gt;&lt;P&gt;I can not understand :smileysad:&lt;/P&gt;&lt;P&gt;Early debug can realy help me&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Sep 2013 13:46:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/problem-with-booting-linux-on-MPC8260/m-p/254885#M403</guid>
      <dc:creator>eugenetodoruk</dc:creator>
      <dc:date>2013-09-27T13:46:31Z</dc:date>
    </item>
  </channel>
</rss>

