From: Jaap-Jan Boor <jjboor@aimsys•nl>
To: "S. van Beek" <nlv11891@natlab•research.philips.com>
Cc: Linuxppc-embedded@ozlabs•org
Subject: Re: Problems with MontaVista Linux on a Memec Virtex-II pro ff672 board
Date: Thu, 17 Mar 2005 13:57:56 +0100 [thread overview]
Message-ID: <77bd0d4ff58c05c9207a1e401ccd13d5@aimsys.nl> (raw)
In-Reply-To: <002001c52aef$d29dbb70$9c9c9182@ddns.htc.nl.philips.com>
is there something printed before 'Now booting the kernel'?
If so, do the memory ranges not overlap or something?
Jaap-Jan
On 17-mrt-05, at 13:49, S. van Beek wrote:
> Hello there,
> =A0
> This is our first post on this list, hi all!
> We're two Dutch students working with a Virtex-II pro ff672 board from=20=
> Memec with the Communications 2 module. We've compiled a simple kernel=20=
> wich comes with MontaVista Linux=A03.1 (2.4.20) with ethernet and a=20
> serial port. It mounts its root filesystem over NFS and everything=20
> seems to work nicely. The next step we wanted to make was=20
> adding=A0support for the Flash=A0on the com board. We added the IP to =
the=20
> hardware and loaded the new bitstream in the FPGA. Next thing, we=20
> enabled support for MTD devices in the kernel. After that, the kernel=20=
> did not seem to boot anymore. It stopped at the message 'Now booting=20=
> the kernel'. So we read some documentation about debugging. We=20
> recompiled this kernel with the -g -ggdb options and removed the -O=20
> (optimalization) flag. Then we did not even see the ppc boot loader=20
> messages anymore when trying to boot. So we tried to compile the first=20=
> kernel (with only serial and ethernet support) -wich worked fine=20
> before-=A0with debugging and it gave us the same result.. no output at=20=
> all.
> Can anyone give us some hints on what we can try more to find out=20
> what is going wrong?
> =A0
> Regards,
> Sander van Beek
> Daniel van Os
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
J.G.J. Boor Anton Philipsweg 1
Software Engineer 1223 KZ Hilversum
AimSys bv tel. +31 35 689 1941
Postbus 2194, 1200 CD Hilversum mailto:jjboor@aimsys•nl
next prev parent reply other threads:[~2005-03-17 12:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 12:49 Problems with MontaVista Linux on a Memec Virtex-II pro ff672 board S. van Beek
2005-03-17 12:57 ` Jaap-Jan Boor [this message]
2005-03-17 13:17 ` Andrei Konovalov
2005-03-17 13:24 ` S. van Beek
2005-03-17 15:37 ` Peter Ryser
2005-03-17 15:57 ` S. van Beek
2005-03-17 18:04 ` Peter Ryser
2005-03-18 10:55 ` S. van Beek
2005-04-18 16:52 ` Tony Lee
2005-03-17 17:14 ` Mark A. Greer
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=77bd0d4ff58c05c9207a1e401ccd13d5@aimsys.nl \
--to=jjboor@aimsys$(echo .)nl \
--cc=Linuxppc-embedded@ozlabs$(echo .)org \
--cc=nlv11891@natlab$(echo .)research.philips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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