All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Konovalov <akonovalov@ru.mvista.com>
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 16:17:30 +0300	[thread overview]
Message-ID: <4239836A.5010200@ru.mvista.com> (raw)
In-Reply-To: <002001c52aef$d29dbb70$9c9c9182@ddns.htc.nl.philips.com>

 > We added the IP to the hardware and loaded the new bitstream in the FPGA.

- isn't this the root of the problem? Any hardware conflict?

Not sure about the ff672 board and the Comm2 module, but in case of fg456 board and P160 COMM module
rev 2 SystemACE and the parallel flash sit on the same data bus. And in the design generated by default
the chip selects are always enabled for both. Maybe you have something similar.
Just a pure guess.

Thanks,
Andrei

S. van Beek wrote:
> Hello there,
> 
> This is our first post on this list, hi all! We're two Dutch students working with a Virtex-II pro ff672 board from Memec
> with the Communications 2 module. We've compiled a simple kernel wich comes with MontaVista Linux 3.1 (2.4.20) with ethernet
> and a serial port. It mounts its root filesystem over NFS and everything seems to work nicely. The next step we wanted to
> make was adding support for the Flash on the com board. We added the IP to the hardware and loaded the new bitstream in the
> FPGA. Next thing, we enabled support for MTD devices in the kernel. After that, the kernel did not seem to boot anymore. It
> stopped at the message 'Now booting the kernel'. So we read some documentation about debugging. We recompiled this kernel
> with the -g -ggdb options and removed the -O (optimalization) flag. Then we did not even see the ppc boot loader messages
> anymore when trying to boot. So we tried to compile the first kernel (with only serial and ethernet support) -wich worked
> fine before- with debugging and it gave us the same result.. no output at all. Can anyone give us some hints on what we can
> try more to find out what is going wrong?
> 
> Regards, Sander van Beek Daniel van Os
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org 
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  parent reply	other threads:[~2005-03-17 13:17 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
2005-03-17 13:17 ` Andrei Konovalov [this message]
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=4239836A.5010200@ru.mvista.com \
    --to=akonovalov@ru.mvista.com \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=nlv11891@natlab.research.philips.com \
    /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.