From: Wolfgang Denk <wd@denx.de>
To: James Don <JDon@spacebridge.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kernel 2.4 smc1 problems ... advice please ...
Date: Sat, 14 Dec 2002 22:13:32 +0100 [thread overview]
Message-ID: <20021214211337.0CF9FC6139@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 14 Dec 2002 14:37:06 EST." <DB0585C9F6F9D411BE8F00D0B7896A4CC05F11@SNCMAIL>
In message <DB0585C9F6F9D411BE8F00D0B7896A4CC05F11@SNCMAIL> you wrote:
>
> I am cuurently trying to boot up the linux kernel using ppcboot 1.16 and the
> 2.4 kernel with only smc1 uart support as a start on an MPC860 FADS derived
> board.
Which 2.4 kernel? Please be precise.
> So far I have:
> - ppcboot running great
> - tftpboot graps my kernel puts in RAM
> - bootm starts my kernel ... BUT no serial activity ...
This is a FAQ. See the Q&A section in http://www.denx.de/re/DPLG.html
Either you're passing a wrong bd_info structure, or a wrong clock
frequency (see also the PPCBoot README about the "clocks_in_mhz"
stuff.)
> I am using the vision ICE currently to debug the kernel start up but it has
> a problem stepping through the 'rfi' etc when memory protection is running.
You cannot step through rfi, not with any BDM debugger.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
I paid too much for it, but its worth it.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-14 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 19:37 kernel 2.4 smc1 problems ... advice please James Don
2002-12-14 21:13 ` Wolfgang Denk [this message]
2002-12-16 12:28 ` Leonardo Pereira Santos
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 21:08 James Don
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=20021214211337.0CF9FC6139@atlas.denx.de \
--to=wd@denx.de \
--cc=JDon@spacebridge.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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.