From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Jon Loeliger" <jdl@jdl.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: StorCenter Help?
Date: Fri, 11 Jan 2008 16:20:12 -0700 [thread overview]
Message-ID: <fa686aa40801111520m3b9c3ea6rc7ee38519dcc9a4b@mail.gmail.com> (raw)
In-Reply-To: <E1JDT1Q-0007Bj-1Q@jdl.com>
On 1/11/08, Jon Loeliger <jdl@jdl.com> wrote:
> Folks,
>
> Anyone out there with an 8241 board such as
> the IoMega StorCenter who would be willing to
> help me debug my arch/powerpc cuImage problems?
>
> I feel like I am missing something very basic in
> my port... like, "Did you map this memory right?"
> or "Did you set _this_ magic bit?"
>
> I have posted the 3 patches that provide the basic
> port and cuImage support as well. The U-Boot that
> I have is still legacy, so I'd like to get linux
> working first via the cuImage, and then work on U-Boot.
>
> The problem is that as soon as U-Boot uncompresses the
> cuImage and loads it, I get no further console output.
>
> The failing log follows.
>
> And I don't have a BDI-2000 or JTAG thing I can use here.
> Which is sort of why I'm tossing this out for general help.
Since you're getting absolutely no output after uncompression it
probably means that you're failing in the boot wrapper... which means
mmu is off, and the serial port is already set up by u-boot.
You should be able to add direct writes to the uart fifo register from
within the bootwrapper code to see how far you get in the progress.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-01-11 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 23:10 StorCenter Help? Jon Loeliger
2008-01-11 23:20 ` Grant Likely [this message]
2008-01-11 23:25 ` Jon Loeliger
2008-01-11 23:30 ` Grant Likely
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=fa686aa40801111520m3b9c3ea6rc7ee38519dcc9a4b@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).