From: Ruedi Hofer <ruedi.hofer@ascom.ch>
To: raphael.bossek@solutions4linux.de, linuxppc-embedded@lists.linuxppc.org
Subject: Loading the Kernel on a FADS
Date: Thu, 23 Dec 1999 09:42:30 +0100 [thread overview]
Message-ID: <3861E076.9BFCA5E8@ascom.ch> (raw)
Hi Raphael,
I'm still in a much earlier stage than you are. I just managed to get the
fadsrom working. Now I try to load the kernel (2.3.18) which I've compiled
for the FADS.
My next steps are now:
1. make zImage of the Kernel
2. mkrombin of the kernel
3. convert to s records
4. load the code with mpc8bug
Problem:
Unfortunately when I try to do a 'mkrombin' of the Kernel the mkrombin exits
with a message like this:
nscns:1
ehp:0x804aee0
epp:0x804af14
something wrong with file (1) zImage
Question:
Is my procedure correct?
How do you download the kernelcode to the board?
--
Best regards
Ruedi Hofer
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-12-23 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 8:42 Ruedi Hofer [this message]
1999-12-23 23:12 ` Loading the Kernel on a FADS Raphael Bossek
2000-01-03 11:40 ` Mika Kuoppala
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=3861E076.9BFCA5E8@ascom.ch \
--to=ruedi.hofer@ascom.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=raphael.bossek@solutions4linux.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 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).