<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Okay, two more things you could try:<br>
    <br>
    <span class="backtick">1) sccBmc&nbsp;-i&nbsp;Tile533_Mesh800_DDR800<br>
      which should re-train the SCC board<br>
      <br>
      2) Exchange </span>in bootscc.sh:<br>
    sccMerge -m 8 -n 12 -noimage -lut_default -force <a
      moz-do-not-send="true" href="http://barrelfish02.mt">barrelfish02.mt</a>&nbsp;
    with<br>
    sccMerge -m 8 -n 12 -noimage -lut_default -force <a
      moz-do-not-send="true" href="http://barrelfish48.mt">barrelfish48.mt</a><br>
    <br>
    Which rev of Barrelfish are you using - the tip? We did a release
    some days ago. I don't think anything SCC related changed. However,
    I you should give the latest version a try anyway.<br>
    <br>
    As I don't see any error message, I assume Barrelfish THINKS&nbsp; it is
    properly initiating the core [1], but it never comes up. <br>
    Can you put a printf in rck_start_core(..) in kernel/arch/scc/rck.c
    to make sure that code is executed? (which I assume it is .. )<br>
    <br>
    [1] By setting the configuration registers in
<a class="moz-txt-link-rfc2396E" href="http://hg.barrelfish.org/file/f86bee507614/kernel/arch/scc/rck.c#l920">&lt;http://hg.barrelfish.org/file/f86bee507614/kernel/arch/scc/rck.c#l920&gt;</a><br>
    <br>
    On 01/31/2012 03:37 PM, Nil Karavadara wrote:
    <blockquote
cite="mid:CAG6dnr9fZuvaPXTvA-Ytw1eMg5386TGNH1Vg8+csbz2VAfDM8Q@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      HI,<br>
      <br>
      Thank for quick reply.<br>
      <br>
      I am using sccboot.sh to boot barrelfish on to cores<br>
      <br>
      <b>bootscc.sh</b><br>
      #!/bin/bash<br>
      #<br>
      # Starts Barrelfish on SCC<br>
      <br>
      # Reset CRBs and everything else<br>
      sccReset -g<br>
      <br>
      # Create an SCC memory image &amp; LUT mapping<br>
      sccMerge -m 8 -n 12 -noimage -lut_default -force <a
        moz-do-not-send="true" href="http://barrelfish02.mt">barrelfish02.mt</a><br>
      #sccMerge -m 8 -n 12 -noimage -lut_default -force <a
        moz-do-not-send="true" href="http://barrelfish12.mt">barrelfish12.mt</a><br>
      #sccMerge -m 8 -n 12 -noimage -lut_default -force <a
        moz-do-not-send="true" href="http://barrelfish48.mt">barrelfish48.mt</a><br>
      #sccMerge -m 8 -n 12 -noimage -lut_default -force <a
        moz-do-not-send="true" href="http://barrelfish24.mt">barrelfish24.mt</a><br>
      <br>
      # Preload memory with image<br>
      sccBoot -g obj<br>
      <br>
      # Release reset of core #0<br>
      sccReset -r 0<br>
      <br>
      # Watch the output of all cores as it goes...<br>
      ./watchall.sh<b><br>
        <br>
        watchall.sh</b><br>
      #!/bin/bash -i<br>
      #<br>
      # Shows output of all Barrelfish SCC cores simultaneously, as it
      arrives.<br>
      <br>
      trap "pkill -P $$" SIGINT<br>
      <br>
      for i in `seq 0 1`; do<br>
      # XXX: We use grep here to enforce line-buffered output, so
      concurrent<br>
      # input from UARTs isn't garbled.<br>
      &nbsp;&nbsp; # cat /dev/crbif0rb0c${i}ttyS0 | grep . --line-buffered &amp;<br>
      &nbsp;&nbsp;&nbsp; cat /dev/crbif0rb0c${i}ttyS0 &amp;&gt; $HOME/core${i}.log<br>
      done<br>
      <br>
      wait<br>
      <br>
      <br>
      <div class="gmail_quote">On Tue, Jan 31, 2012 at 1:12 PM, Stefan
        K&auml;stle <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:stefan.kaestle@inf.ethz.ch">stefan.kaestle@inf.ethz.ch</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div bgcolor="#FFFFFF" text="#000000"> Hi,<br>
            <br>
            the output should be something like:
            <div class="im"><br>
              <br>
              My APIC ID: 0<br>
              Barrelfish CPU driver starting on scc core 0<br>
              init: invoked as: init 2097152<br>
              Spawning memory server (scc/sbin/mem_serv)...<br>
              Spawning monitor (scc/sbin/monitor)...<br>
              starting monitor as 'scc/sbin/monitor 327680 '<br>
              monitor: invoked as: scc/sbin/monitor 327680<br>
            </div>
            RAM allocator initialised, 1611 MB (of 1627 MB) available
            <div class="im"><br>
              Spawning chips on core 0<br>
              Spawning /scc/sbin/ramfsd on core 0<br>
              Spawning /scc/sbin/spawnd on core 0<br>
              Spawning /scc/sbin/startd on core 0<br>
              chips: client waiting for ramfs<br>
              ramfsd.0: pre-populating from boot image...<br>
              chips: client waiting for ramfs<br>
              ramfsd.0: /scc/sbin/examples/xmpl-hello already exists,
              skipping it<br>
              ramfsd.0: ready<br>
              chips: notifying client about ramfs<br>
              chips: notifying client about ramfs<br>
              kernel 0: Allocating RAM at 0x80000000 uninitialized<br>
              kernel 0: Allocating RAM at 0x80010000 uninitialized<br>
              spawnd.0: coreid 1 is arch id 1<br>
              chips: client waiting for all_spawnds_up<br>
              Monitor 0: booting scc core 1 as '/scc/sbin/cpu'<br>
              kernel 0: Allocating RAM at 0x80020000 uninitialized<br>
            </div>
            Kernel starting at address 0x80100000
            <div class="im"><br>
              My APIC ID: 1<br>
              Barrelfish CPU driver starting on scc core 1<br>
            </div>
            init: invoked as: init 2097152 0 chanid=0 frame=<a
              moz-do-not-send="true" href="tel:2147614720"
              value="+12147614720" target="_blank">2147614720</a>
            <div class="im"><br>
              Spawning memory server (scc/sbin/mem_serv)...<br>
              Spawning monitor (scc/sbin/monitor)...<br>
            </div>
            starting monitor as 'scc/sbin/monitor 327680 0 chanid=0
            frame=<a moz-do-not-send="true" href="tel:2147614720"
              value="+12147614720" target="_blank">2147614720</a> '<br>
            monitor: invoked as: scc/sbin/monitor 327680 0 chanid=0
            frame=<a moz-do-not-send="true" href="tel:2147614720"
              value="+12147614720" target="_blank">2147614720</a><br>
            RAM allocator initialised, 1611 MB (of 1627 MB) available<br>
            frame base at 0x80020000 -- 0x80021000
            <div class="im"><br>
              kernel 1: Allocating RAM at 0x80020000 uninitialized<br>
            </div>
            URPC physical frame at 0x80020000<br>
            Spawning spawnd on core 1
            <div class="im"><br>
              all 2 monitors up<br>
              chips: client waiting for spawn.1.ready<br>
            </div>
            kernel 1: Allocating RAM at 0x81000000 uninitialized<br>
            kernel 1: Allocating RAM at 0x81001000 uninitialized<br>
            kernel 1: Allocating RAM at 0x81040000 uninitialized
            <div class="im"><br>
              chips: notifying client about spawn.1.ready<br>
              chips: client waiting for all_spawnds_up<br>
              chips: notifying client about all_spawnds_up<br>
              chips: notifying client about all_spawnds_up<br>
              startd.0: starting app /scc/sbin/examples/xmpl-hello on
              core 0<br>
              spawnd.0: spawning /scc/sbin/examples/xmpl-hello on core 0<br>
              startd.0: starting app /scc/sbin/examples/xmpl-hello on
              core 1<br>
              kernel 0: Allocating RAM at 0x80021000 uninitialized<br>
              Hello World<br>
            </div>
            spawnd.1: spawning /scc/sbin/examples/xmpl-hello on core 1<br>
            No bootscript<br>
            kernel 1: Allocating RAM at 0x81002000 uninitialized<br>
            Hello World<br>
            <br>
            It seems the second core (id=1) is not started. Did you
            configure the SCC properly? <br>
            What arguments did you give to sccMerge? [1]<br>
            <br>
            Hope this helps<br>
            &nbsp;Stefan<br>
            <br>
            [1] <a moz-do-not-send="true"
              href="http://www.barrelfish.org/TN-005-SCC.pdf"
              target="_blank">&lt;http://www.barrelfish.org/TN-005-SCC.pdf&gt;</a>,
            chapter 2.4 Boot process: first (bootstrap) core)
            <div>
              <div class="h5"><br>
                <br>
                <br>
                On 01/31/2012 12:01 PM, Nil Karavadara wrote:
                <blockquote type="cite"> HI,<br>
                  <br>
                  I have made changes (only menu.lst needed changes) but
                  the out put is still the same.<br>
                  <br>
                  <b>Output log:</b><br>
                  <br>
                  My APIC ID: 0<br>
                  Barrelfish CPU driver starting on scc core 0<br>
                  init: invoked as: init 2097152<br>
                  Spawning memory server (scc/sbin/mem_serv)...<br>
                  Spawning monitor (scc/sbin/monitor)...<br>
                  starting monitor as 'scc/sbin/monitor 327680 '<br>
                  monitor: invoked as: scc/sbin/monitor 327680<br>
                  RAM allocator initialised, 1608 MB (of 1624 MB)
                  available<br>
                  Spawning chips on core 0<br>
                  Spawning /scc/sbin/ramfsd on core 0<br>
                  Spawning /scc/sbin/spawnd on core 0<br>
                  Spawning /scc/sbin/startd on core 0<br>
                  chips: client waiting for ramfs<br>
                  ramfsd.0: pre-populating from boot image...<br>
                  chips: client waiting for ramfs<br>
                  ramfsd.0: /scc/sbin/examples/xmpl-hello already
                  exists, skipping it<br>
                  ramfsd.0: ready<br>
                  chips: notifying client about ramfs<br>
                  chips: notifying client about ramfs<br>
                  kernel 0: Allocating RAM at 0x80000000 uninitialized<br>
                  kernel 0: Allocating RAM at 0x80010000 uninitialized<br>
                  spawnd.0: coreid 1 is arch id 1<br>
                  chips: client waiting for all_spawnds_up<br>
                  Monitor 0: booting scc core 1 as '/scc/sbin/cpu'<br>
                  kernel 0: Allocating RAM at 0x80020000 uninitialized<br>
                  all 2 monitors up<br>
                  chips: client waiting for spawn.1.ready<br>
                  chips: notifying client about spawn.1.ready<br>
                  chips: client waiting for all_spawnds_up<br>
                  chips: notifying client about all_spawnds_up<br>
                  chips: notifying client about all_spawnds_up<br>
                  startd.0: starting app /scc/sbin/examples/xmpl-hello
                  on core 0<br>
                  spawnd.0: spawning /scc/sbin/examples/xmpl-hello on
                  core 0<br>
                  startd.0: starting app /scc/sbin/examples/xmpl-hello
                  on core 1<br>
                  kernel 0: Allocating RAM at 0x80021000 uninitialized<br>
                  Hello World<br>
                  No bootscript<br>
                  <br>
                  <b>Menu.lst</b><br>
                  timeout 0<br>
                  <br>
                  # spawnd is used to control which cpus are booted<br>
                  #<br>
                  # "spawnd boot" will use the skb and pci to figure out
                  and<br>
                  #&nbsp; boot all cores in the machine<br>
                  #<br>
                  # "spawnd boot bootscc=1-6" will not use the skb and<br>
                  # boot the list of cores passed as argument.<br>
                  # The hardware id of the cores to boot should be
                  specified.<br>
                  # This list may not include the bsp core id.<br>
                  <br>
                  title&nbsp;&nbsp;&nbsp; Barrelfish<br>
                  root&nbsp;&nbsp;&nbsp; (nd)<br>
                  kernel&nbsp;&nbsp;&nbsp; /scc/sbin/cpu loglevel=4<br>
                  module&nbsp;&nbsp;&nbsp; /scc/sbin/cpu<br>
                  module&nbsp;&nbsp;&nbsp; /scc/sbin/init<br>
                  <br>
                  # Domains spawned by init<br>
                  module&nbsp;&nbsp;&nbsp; /scc/sbin/mem_serv<br>
                  module&nbsp;&nbsp;&nbsp; /scc/sbin/monitor<br>
                  <br>
                  module&nbsp;&nbsp;&nbsp; /scc/sbin/chips boot<br>
                  module&nbsp;&nbsp;&nbsp; /scc/sbin/ramfsd boot<br>
                  module&nbsp; /scc/sbin/spawnd boot bootscc=1<br>
                  module&nbsp; /scc/sbin/startd boot<br>
                  # modules needed to start the networking<br>
                  # module&nbsp; /scc/sbin/eMAC core=0<br>
                  # module&nbsp; /scc/sbin/netd core=0 cardname=eMAC2_0<br>
                  # module&nbsp; /scc/sbin/eMAC core=1<br>
                  # module&nbsp; /scc/sbin/netd core=1 cardname=eMAC2_1<br>
                  <br>
                  # RCK memory map<br>
                  # Everything up til VGA is private RAM (maybe we want
                  to throw it away)<br>
                  mmap&nbsp;&nbsp;&nbsp; map&nbsp;&nbsp;&nbsp; 0x0&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 0xa000&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 2<br>
                  # Everything after VGA is private RAM (we also live in
                  this area)<br>
                  mmap&nbsp;&nbsp;&nbsp; map&nbsp;&nbsp;&nbsp; 0xe800&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 0x26ff1800&nbsp;&nbsp;&nbsp; 1<br>
                  # Shared RAM (over all MCs) in the middle of address
                  space<br>
                  #mmap&nbsp;&nbsp;&nbsp; map&nbsp;&nbsp;&nbsp; 0x80000000&nbsp;&nbsp;&nbsp; 0x4000000&nbsp;&nbsp;&nbsp; 1<br>
                  mmap&nbsp;&nbsp;&nbsp; map&nbsp;&nbsp;&nbsp;&nbsp; 0x80000000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x40000000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<br>
                  # At the very end we have some platform memory (bootup
                  EEPROM)<br>
                  mmap&nbsp;&nbsp;&nbsp; map&nbsp;&nbsp;&nbsp; 0xfffc0000&nbsp;&nbsp;&nbsp; 0x40000&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 2<br>
                  <br>
                  <br>
                  module /scc/sbin/examples/xmpl-hello core=0<br>
                  module /scc/sbin/examples/xmpl-hello core=1<br>
                  <br>
                  Is there anything ma i missing?<br>
                  <br>
                  Thank you,<br>
                  <br>
                  <br>
                  <div class="gmail_quote">On Wed, Jan 25, 2012 at 2:28
                    PM, Stefan K&auml;stle <span dir="ltr">&lt;<a
                        moz-do-not-send="true"
                        href="mailto:stefan.kaestle@inf.ethz.ch"
                        target="_blank">stefan.kaestle@inf.ethz.ch</a>&gt;</span>
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      <div bgcolor="#FFFFFF" text="#000000"> Hi Nil,<br>
                        <br>
                        I assume you modified your menu.lst to start the
                        hello program. The menu.lst [1] for the SCC
                        provided in the tip version of the Barrelfish
                        tree should not start the hello world program
                        automatically.<br>
                        <br>
                        Adding the following entry to the menu.lst would
                        start the hello program on core 0 (assuming you
                        compiled it).<br>
                        <tt>module&nbsp; /scc/sbin/examples/xmpl-hello core=0</tt><br>
                        <br>
                        If you wanted it to start on more cores, you
                        could add several lines, such as:<br>
                        <tt>module&nbsp; /scc/sbin/examples/xmpl-hello core=0<br>
                          module&nbsp; /scc/sbin/examples/xmpl-hello core=1<br>
                          module&nbsp; /scc/sbin/examples/xmpl-hello core=2</tt><br>
                        <br>
                        If you omit the paramter <tt>core=</tt>, the
                        program is started on the core 0.<br>
                        <br>
                        Hope this helps,<br>
                        &nbsp;Stefan<br>
                        <br>
                        [1] see <a moz-do-not-send="true"
                          href="http://hg.barrelfish.org/file/8c906f8f22fb/hake/menu.lst.scc"
                          target="_blank">http://hg.barrelfish.org/file/8c906f8f22fb/hake/menu.lst.scc</a>
                        <div>
                          <div><br>
                            <br>
                            <br>
                            On 01/24/2012 05:46 PM, Nil Karavadara
                            wrote: </div>
                        </div>
                        <blockquote type="cite">
                          <div>
                            <div> Hi,<br>
                              <br>
                              I have manged to boot barrelfish on SCC.
                              My question is i have booted barrelfish on
                              two cores of SCC and i can see "Hello
                              world" printed once is this correct? (i
                              think that core0 and core1 both will
                              output "Hello world" and i should see it
                              twice on screen)<br clear="all">
                              <br>
                              Thank you.<br>
                              <br>
                              -- <br>
                              Kind Regards,<br>
                              Nil Karavadara<font color="#888888"><br>
                                <br>
                              </font><font color="#888888">Centre for
                                Computer Science and Informatics
                                Research<br>
                                Science &amp; Technology Research
                                Institute<br>
                                University of Hertfordshire</font><br>
                              <br>
                              <br>
                              <fieldset></fieldset>
                              <br>
                            </div>
                          </div>
                          <pre>_______________________________________________
Barrelfish-users mailing list
<a moz-do-not-send="true" href="mailto:Barrelfish-users@lists.inf.ethz.ch" target="_blank">Barrelfish-users@lists.inf.ethz.ch</a>
<a moz-do-not-send="true" href="https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users" target="_blank">https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users</a>
</pre>
                        </blockquote>
                        <font color="#888888"> <br>
                          <pre cols="72">-- 
Stefan K&auml;stle
ETH Z&uuml;rich
CAB E 69
Universit&auml;tstrasse 6
CH-8092 Z&uuml;rich
Switzerland
Email: <a moz-do-not-send="true" href="mailto:stefan.kaestle@inf.ethz.ch" target="_blank">stefan.kaestle@inf.ethz.ch</a>
Phone: <a moz-do-not-send="true" href="tel:%2B41%2044%20632%208289" value="+41446328289" target="_blank">+41 44 632 8289</a></pre>
                        </font></div>
                      <br>
                      _______________________________________________<br>
                      Barrelfish-users mailing list<br>
                      <a moz-do-not-send="true"
                        href="mailto:Barrelfish-users@lists.inf.ethz.ch"
                        target="_blank">Barrelfish-users@lists.inf.ethz.ch</a><br>
                      <a moz-do-not-send="true"
                        href="https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users"
                        target="_blank">https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users</a><br>
                      <br>
                    </blockquote>
                  </div>
                  <br>
                  <br clear="all">
                  <br>
                  -- <br>
                  Kind Regards,<br>
                  Nil Karavadara<font color="#888888"><br>
                    <br>
                  </font><font color="#888888">Centre for Computer
                    Science and Informatics Research<br>
                    Science &amp; Technology Research Institute<br>
                    University of Hertfordshire</font><br>
                  <br>
                </blockquote>
                <br>
              </div>
            </div>
            <font color="#888888">
              <pre cols="72">-- 
Stefan</pre>
            </font></div>
        </blockquote>
      </div>
      <br>
      <br clear="all">
      <br>
      -- <br>
      Kind Regards,<br>
      Nil Karavadara<font color="#888888"><br>
        <br>
      </font><font color="#888888">Centre for Computer Science and
        Informatics Research<br>
        Science &amp; Technology Research Institute<br>
        University of Hertfordshire</font><br>
      <br>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Stefan</pre>
  </body>
</html>