Problems with MontaVista Linux on a Memec Virtex-II pro ff672 board

[S. van Beek]

Hi,

Yes this is the case too on this board, they are multiplexed. But we don't
have a SystemAce adapter and the SystemAce IP is also not included in our
design.

----- Original Message ----- 
From: "Andrei Konovalov" <akonovalov at ru.mvista.com>
To: "S. van Beek" <nlv11891 at prle>
Cc: <Linuxppc-embedded at ozlabs.org>
Sent: Thursday 17 March 2005 14:17
Subject: Re: Problems with MontaVista Linux on a Memec Virtex-II pro ff672
board


> > 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 at ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
>
>