linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Bergandi <mbergandi@gmail.com>
To: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
Cc: linuxppc-dev@ozlabs.org, Eric Cottrell <wb1hbu@runbox.com>
Subject: Re: Can not get "new" MPC8313e-RDB to boot "as-shipped" flash image
Date: Tue, 24 Feb 2009 13:55:53 -0500	[thread overview]
Message-ID: <1c641bc80902241055j33984de6re0f9a887494fa93a@mail.gmail.com> (raw)
In-Reply-To: <49A3EBFF.4030906@aimvalley.nl>

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

Hi guys,

I have the Rev B board and I have it working quite well. I'll share what I
have
discovered so far.

In Eric's case, the board seems suspect. There is already a Rev C of this
board, but
I am not sure if it is actually available yet. You may want to check on
that.

Regarding U-Boot, mine shipped with v. 1.3.0. The LTIB provided dts files
follow
the original dts format. There is a new dts spec and if you ever intend to
use
a mainline kernel, you will need to use the newer dts provided in the kernel
source. Did I mention this board has at least basic support in 2.6.28 :). I
have
not determined the extent of the support though.

I have successfully used the provided U-Boot v1.3.0 to boot a 2.6.28 kernel
with
the dts-v1 device tree. Hence, I hope that will clear your speculation about
the
device tree being the problem.

I have seen the same problem that you guys have seen where U-Boot gets to
the "Uncompressing kernel ..." then reboots. This happened to me when I
passed the wrong device tree .dtb. I have also had this happen if I made
a change to the kernel config. I haven't been able to determine what exactly

that I changed that caused the problem though.

Also, if you are feeling adventurous, you can also get the latest U-Boot.
There
is a specifc branch for this board:

$ git clone git://git.denx.de/u-boot-mpc83xx.git

I haven't attempted this since I don't currently have a probe to recovery a
bad boot loader flash.

Hope this helps,

Mike

[-- Attachment #2: Type: text/html, Size: 1680 bytes --]

  parent reply	other threads:[~2009-02-24 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 23:23 Can not get "new" MPC8313e-RDB to boot "as-shipped" flash image Eric Cottrell
2009-02-24 12:45 ` Norbert van Bolhuis
2009-02-24 14:36   ` Eric Cottrell
2009-02-24 16:29     ` Norbert van Bolhuis
2009-02-24 16:56       ` Eric Cottrell
2009-02-24 18:55   ` Michael Bergandi [this message]
2009-03-02  0:58     ` Eric Cottrell

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=1c641bc80902241055j33984de6re0f9a887494fa93a@mail.gmail.com \
    --to=mbergandi@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nvbolhuis@aimvalley.nl \
    --cc=wb1hbu@runbox.com \
    /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;
as well as URLs for NNTP newsgroup(s).