mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: a question about adding panda ES support before i get rolling
Date: Thu, 9 Feb 2012 15:45:44 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1202091539470.7618@oneiric> (raw)


  a preliminary question to make sure i'm on the right track in terms
of adding panda ES support.  i have a couple panda boards -- an
earlier EA3 revision (OMAP 4430), and a panda ES (OMAP 4460).

  using a regular panda config and build, i can boot the earlier
board:

barebox 2012.02.0-00090-g675502d-dirty (Feb  8 2012 - 17:03:18)

Board: Texas Instrument's Panda
PandaBoard Revision: 003
ehci@ehci0: USB EHCI 1.00
Malloc space: 0x8d000000 -> 0x8effffff (size 32 MB)
Stack space : 0x8cff8000 -> 0x8d000000 (size 32 kB)
Open /boot/bareboxenv No such file or directory
no valid environment found on /boot/bareboxenv. Using default
environment
running /env/bin/init...

so that's a good sign.  and the Revision number of 3 matches what i
see here:

http://omappedia.org/wiki/PandaBoard_Revisions#PandaBoard_Revision_History

so far, so good.

  now if i use precisely the same files for my ES, i get absolutely no
output.  none.  but that's not surprising since in the omap4_generic.c
file, i read:

unsigned int omap4_revision(void)
{
        unsigned int chip_rev = 0;
        unsigned int rev = cortex_a9_rev();

        switch(rev) {
        case 0x410FC091:
                return OMAP4430_ES1_0;
        case 0x411FC092:
                chip_rev = (readl(OMAP44XX_CTRL_BASE + 0x204)  >> 28) & 0xF;
                if (chip_rev == 3)
                        return OMAP4430_ES2_1;
                else if (chip_rev >= 4)
                        return OMAP4430_ES2_2;
                else
                        return OMAP4430_ES2_0;
        }
        return OMAP4430_SILICON_ID_INVALID;
}

i'm assuming the fact there is *no* checking for an OMAP4460 is the
reason i get nothing, is that a reasonable assumption?  i'll post more
detail later about what i'm going to try but given that the above
function does not take into account the OMAP4460-based ES boards,
would that cause a complete lack of output at boot time?  thanks.

rday


-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-02-09 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 20:45 Robert P. J. Day [this message]
2012-02-10 11:41 ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1202091539470.7618@oneiric \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox