From: s.s-c-h-m-i-t-t@web.de
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Problem booting Linux with Redboot v1.94 on IXP425
Date: Tue, 24 May 2005 09:32:00 -0000 [thread overview]
Message-ID: <42926CAC.10903@web.de> (raw)
Hi there,
After updating to Redboot´s v1.94 I can´t boot the 2.4.19-rmk6 kernel
any more. I adapted Redboot successfully (I guess) for my IXP425-Target
which has no PCI NIC, 128MB SDRAM and the second UART only usable.
After initializing Redboot (fis init) I load the zImage and start it:
> load -r -v -b 0x01600000 zImage
> go 0x01600000
After this there is no message any more. The kernel seems to stick -
BID2000, however, says the target is running. The same with prebuilt
uClinux Images for the ixdp425.
When doing this with the old v2.00 (v1.5) Redboot with the kernel
everything works fine.
Any comments or hints???
Regards,
Stefan.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-05-23 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-24 9:32 s.s-c-h-m-i-t-t [this message]
2005-05-26 8:47 ` Mark Salter
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=42926CAC.10903@web.de \
--to=s.s-c-h-m-i-t-t@web.de \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).