From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] having trouble booting a simple kernel on a TQM860 board
Date: Mon, 5 Dec 2011 07:05:54 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1112050701340.21244@oneiric> (raw)
In-Reply-To: <20111205100903.2E06413BE0E6@gemini.denx.de>
On Mon, 5 Dec 2011, Wolfgang Denk wrote:
> Dear Robert,
>
> In message <alpine.DEB.2.02.1112042100270.15118@oneiric> you wrote:
> >
> > i believe i've solved this issue, at least. i downloaded ELDK 4.2
> > and installed the ppc_8xx- toolchain. with that, i managed to
> > compile u-boot 2010.12 and flashed it to my TQM860, reset and, lo
> > and behold, i have a 2010.12 u-boot. so my u-boot issue seems to
> > be resolved.
>
> You update U-Boot, but to a version 4 releases old. Why not to
> current code?
>
> > which generated a uImage file. but as i understand it, i want a
> > cuImage-format file as i used with my lite5200, so i edited the file
>
> No. Now you don't need a cuImage nay more. Just use the DT as I
> showed you in the builkd and boot log I sent before.
for the sake of clarification, you write that i don't *need*
cuImages anymore, but that's not the same as saying that i *must* move
to using device trees. in fact, a cuImage file still works just fine
for my lite5200 boards, so obviously the version of u-boot that i've
flashed to my TQM boards can still handle that format.
so while it's probably a good idea to move to the device tree
recipe, that still doesn't explain why i can't use a cuImage file for
my tqm boards. so i'll test the device tree process later today, but
i'm still curious as to why a cuImage format file still fails in this
case when it works just fine for the other boards.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2011-12-05 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 23:19 [U-Boot] having trouble booting a simple kernel on a TQM860 board Robert P. J. Day
2011-12-02 23:29 ` Scott Wood
2011-12-02 23:41 ` Robert P. J. Day
2011-12-02 23:49 ` Scott Wood
2011-12-03 0:03 ` Robert P. J. Day
2011-12-03 0:17 ` Wolfgang Denk
2011-12-05 2:14 ` Robert P. J. Day
2011-12-05 10:09 ` Wolfgang Denk
2011-12-05 10:37 ` Robert P. J. Day
2011-12-05 12:05 ` Robert P. J. Day [this message]
2011-12-05 12:58 ` Wolfgang Denk
2011-12-05 17:48 ` Robert P. J. Day
2011-12-05 20:02 ` Wolfgang Denk
2011-12-03 0:16 ` Wolfgang Denk
2011-12-03 0:23 ` Robert P. J. Day
2011-12-03 0:26 ` Wolfgang Denk
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.1112050701340.21244@oneiric \
--to=rpjday@crashcourse.ca \
--cc=u-boot@lists.denx.de \
/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.