linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Müller" <jamuelle@ee.ethz.ch>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: XUPV2P update to kernel 2.6 fails
Date: Sat, 06 Dec 2008 21:10:35 +0100	[thread overview]
Message-ID: <493ADC3B.2040505@ee.ethz.ch> (raw)

Hi all,

I was wondering if anyone got the XUPV2P board successfully up and
running with a recent 2.6 kernel?

I didn't succeed. I tried the newest kernel from xilinx git (2.6.27) and
also an older one, 2.6.22 (also from xilinx git). For the newer I used
the "device-tree" as bsp. For the 2.6.22 I just copied over the
xparameters_ml300.h file.

In both cases no output at all was observable at the uart. Not even a
single sign from the uart at any time...

Strange is, the same download.bit file is working with a 2.4 kernel.
Could it be a kernel .config issue?

But can this really be a software/kernel issue? For the 2.4 kernel there
was an output from the "bootloader"  (some addresses and the
"Loading..." information) even for wrong configured kernels...

On this list I was reading something about setting the uart clockfreq
correctly in the .dts (it was not set at all, I have to stick with EDK
9.1). But this didn't help for me.

To boot the FPGA I have to use an ace file on a cf-disc. For this I use
the download.bit file together with the simpleImage.virtex405-XUPV2P.elf
(on 2.6.27) or zImage (on 2.6.22)...

Any suggestions on this? Thanks a lot!

Regards,
Jan

             reply	other threads:[~2008-12-06 20:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06 20:10 Jan Müller [this message]
2008-12-09 23:09 ` XUPV2P update to kernel 2.6 fails John Linn
2008-12-10 10:05 ` Joachim Meyer
2008-12-10 19:41   ` Alan Casey
2008-12-10 23:13   ` Jan Mueller
2008-12-11 15:41     ` saadia dhouib
2008-12-11 15:44   ` saadia dhouib

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=493ADC3B.2040505@ee.ethz.ch \
    --to=jamuelle@ee.ethz.ch \
    --cc=linuxppc-embedded@ozlabs.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 NNTP newsgroup(s).