From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: Eric Cottrell <wb1hbu@runbox.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Can not get "new" MPC8313e-RDB to boot "as-shipped" flash image
Date: Tue, 24 Feb 2009 17:29:15 +0100 [thread overview]
Message-ID: <49A4205B.30207@aimvalley.nl> (raw)
In-Reply-To: <E1LbyOG-0000uL-Hf@garm.runbox.com>
Hi Eric,
So it never ever booted properly ?
Hmm, it certainly looks like your distributor (or whoever you got the MPC8313E-RDB
from) lend it out and got a messed up board back. Or maybe they messed it up
themselfes.
Go complain and send it back.
indeed, rev 2.x is better (much less TSEC bugs).
---
N. van Bolhuis.
Eric Cottrell wrote:
> Hello,
>
> Thanks for the help. I will look into that. It is confusing as the latest ltib appears not to have the aliases. This is my first venture into Embedded Linux as our existing PowerPC products use PSOS. Most of my Linux experience is on the Intel PC platform.
>
> Yes, the 1.3.3 version was what was shipped with the board. The rootfs and kernel appear to be older. So I suspect someone upgraded the uBoot and ran into trouble.
>
> I am comparing this with the Rev B board we also got. I hope to return the Rev A4 and make the boards all Rev B because it has a later processor. The Rev B boards have 1.3.0 so it should need the aliases as well. Looking in the uBoot changelogs there are some nice additions and fixes for this board so I will look to dig more into uBoot and upgrade it. I hate to stumble out of the box.
>
> 73 Eric
>
next prev parent reply other threads:[~2009-02-24 16:29 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 [this message]
2009-02-24 16:56 ` Eric Cottrell
2009-02-24 18:55 ` Michael Bergandi
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=49A4205B.30207@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=linuxppc-dev@ozlabs.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.