From: "drscott can't tell" <drscott50s@gmail.com>
To: barebox@lists.infradead.org
Subject: booting issues with PandaBoard
Date: Sun, 26 Jun 2011 09:16:24 -0700 [thread overview]
Message-ID: <BANLkTikjQPPzar_CmJsoh9=2BOGOUY83Vg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1437 bytes --]
I have more data to add regarding the PandaBoard boot issue referenced by
Belisko Marek:
1. In our group we have two PandaBoards - both rev A3 but bought 1 1/2
months apart. The latest PandaBoard boots just fine with the stock June
barebox. The earlier board does not.
2. All of the comments below are relative to the earlier A3 board...
3. If I copy MLO from the Angstrom distribution and then compile using
panda_defconfig and copy barebox.bin as u-boot.bin - barebox hangs after
displaying board revision (03).
4. Using panda_defconfig and if I comment out the two lines:
//register_device(&hsmmc_dev);
//panda_ehci_init();
in board.c then barebox boots up properly, obviously without usb and sd card
support:
5. If I rebuild same image using panda_xload_defconfig and copy the
barebox.bin.ift as MLO and the generated barebox.bin to the card, the
booting hangs after following displayed:
barebox 2011.06.0 (Jun 26 2011 - 08:45:43)
Board: Texas Instrument's Panda
PandaBoard Revision: 003
Malloc space: 0x84000000 -> 0x86000000 (size 32 MB)
Stack space : 0x8f000000 -> 0x8f008000 (size 32 kB)
It would appear to me that there is a subtle startup issue between MLO
startup and barebox startup. The fact that one board behaves properly and
the other doesn't at the same rev level indicates some sort of 'on the edge'
in-stability. I will feed back any other findings as I test more...
Scott Tilden, PhD
U of Arizona
[-- Attachment #1.2: Type: text/html, Size: 1543 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2011-06-26 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='BANLkTikjQPPzar_CmJsoh9=2BOGOUY83Vg@mail.gmail.com' \
--to=drscott50s@gmail.com \
--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