linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: somshekar c kadam <schandra@in.mvista.com>
To: John Linn <John.Linn@xilinx.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: ML507 EDK 10.1
Date: Tue, 03 Jun 2008 08:16:22 +0530	[thread overview]
Message-ID: <1212461182.25185.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20080602143551.54964C80052@mail135-wa4.bigfish.com>

Hi John Linn,

Yes I have dowloaded the linux_support.tar.gz.
So if I get you correct I will use the bit stream provided by
linux_support.tar.gz clubbed with the zImage to create Ace file, I hope
that should work Ace file should boot the kernel. correct me if I am
wrong. Let create it and test it

As for ML403 we created zImage.dts and clubbed it with bit stream and
created ace file it botts up fine.

Thanks in Advance
Neelu

On Mon, 2008-06-02 at 08:35 -0600, John Linn wrote:
> Hi Neelu,
> 
> The easiest way to get a good baseline with the board and the kernel is
> to use the bitstream for the board that we provide in the file,
> linux_support.tar.gz, on http://git.xilinx.com.
> 
> In the PPC440 directory of the support file, there's a bit stream for
> the board. If you don't use a Xilinx probe to download to the board, you
> will need to create an ACE file from that bit stream, but it sounds like
> you know how to do that.
> 
> I know the state of the Xilinx Git tree, but I don't know the state of
> Grant's for sure. We have baselined our Git tree such that you should be
> able to make it work quick and easy (that's our goal).
> 
> To build arch/powerpc, the following commands should create zImage in
> the arch/powerpc/boot directory that can be used with the bitstream from
> the linux_support.tar.gz file.  I am currently using the ELDK 4.1 tools
> to build the kernel.
> 
> > make ARCH=powerpc ml507_defconfig
> > make ARCH=powerpc zImage
> 
> We also provide a ramdisk image in the support file, you can build it
> also after copying the ramdisk images into the arch/powerpc/boot
> directory.  The default command line of the kernel, in the ml507.dts
> file in the arch/powerpc/boot/dts directory, is setup to use the
> ramdisk.
> 
> > make ARCH=powerpc zImage.initrd
> 
> Hope that helps,
> John Linn
> 
> -----Original Message-----
> From: linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org
> [mailto:linuxppc-embedded-bounces+john.linn=xilinx.com@ozlabs.org] On
> Behalf Of somshekar c kadam
> Sent: Monday, June 02, 2008 4:19 PM
> To: linuxppc-embedded@ozlabs.org
> Subject: ML507 EDK 10.1
> 
> Hi All,
> 
> Currently I am working with ML507 Base Reference design. I  have
> installed Eval 10.1 edk I am bale to create ace file using xmd with base
> download.bit. and able to boot the board. Now I want to boot the board
> with Xilinx Linux kernel from Xilinx git tree. I am facing compilation
> problem with zImage.dts for ml507_defconfig.
> 
>   
> 
> 
> now I need to create ace file for Linux for ML507.
> I tried creating zImage.dts its failing. Kernel error see below
> 
> Please help or give some pointers wherein I can compile zImge.dts. this
> is from latest git tree. Seems for me arch/powerpc wrapper code is
> broken. Please suggest.
> currently I have no bdi I need to stick to Ace compact Flash booting.
> Also bit confused where we have two git tree one is Xilinx git tree one
> more from Grant Likely which should I use ?
> 
> Thanks In Advance
> 
> Neelu
> 
> ---------------------------------------------------
> WRAP    arch/powerpc/boot/zImage.dts
> DTC: dts->dtb  on file
> "/home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc/bo
> ot/dts/ml507.dts"
> objcopy: Unable to recognise the format of the input file `vmlinux'
> make[1]: *** [arch/powerpc/boot/zImage.dts] Error 1
> make: *** [zImage.dts] Error 2
> 
> 
> 
> 
> WIth Verbose =1 
> 
> 
>  /bin/sh
> /home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc/boo
> t/wrapper -c -o arch/powerpc/boot/zImage.dts -p dts   -s
> /home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc/boo
> t/dts/ml507.dts vmlinux
> + kernel=
> + ofile=zImage
> + platform=of
> + initrd=
> + dtb=
> + dts=
> + cacheit=
> + binary=
> + gzip=.gz
> + CROSS=
> + object=arch/powerpc/boot
> + objbin=arch/powerpc/boot
> + tmpdir=.
> + '[' 8 -gt 0 ']'
> + case "$1" in
> + cacheit=y
> + shift
> + '[' 7 -gt 0 ']'
> + case "$1" in
> + shift
> + '[' 6 -gt 0 ']'
> + ofile=arch/powerpc/boot/zImage.dts
> + shift
> + '[' 5 -gt 0 ']'
> + case "$1" in
> + shift
> + '[' 4 -gt 0 ']'
> + platform=dts
> + shift
> + '[' 3 -gt 0 ']'
> + case "$1" in
> + shift
> + '[' 2 -gt 0 ']'
> +
> dts=/home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc
> /boot/dts/ml507.dts
> + shift
> + '[' 1 -gt 0 ']'
> + case "$1" in
> + '[' -z '' ']'
> + kernel=vmlinux
> + shift
> + '[' 0 -gt 0 ']'
> + '['
> -n
> /home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc/boo
> t/dts/ml507.dts ']'
> + '[' '!'
> -r
> /home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc/boo
> t/dts/ml507.dts -a -r
> arch/powerpc/boot/dts//home/neelu/xilinx/xilinx_gittree/test44/linux-2.6
> -xlnx/arch/powerpc/boot/dts/ml507.dts ']'
> + '[' -z '' ']'
> + dtb=dts.dtb
> + arch/powerpc/boot/dtc -O dtb -o dts.dtb -b
> 0
> /home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc/boo
> t/dts/ml507.dts
> DTC: dts->dtb  on file
> "/home/neelu/xilinx/xilinx_gittree/test44/linux-2.6-xlnx/arch/powerpc/bo
> ot/dts/ml507.dts"
> + '[' -z vmlinux ']'
> + platformo=arch/powerpc/boot/dts.o
> + lds=arch/powerpc/boot/zImage.lds
> + ext=strip
> + objflags=-S
> + tmp=./zImage.24209.o
> + ksection=.kernel:vmlinux.strip
> + isection=.kernel:initrd
> + case "$platform" in
> ++ basename vmlinux
> + vmz=./vmlinux.strip
> + '[' -z y -o '!' -f ./vmlinux.strip.gz -o ./vmlinux.strip.gz -ot
> vmlinux ']'
> + objcopy -S vmlinux ./vmlinux.strip.24209
> objcopy: Unable to recognise the format of the input file `vmlinux'
> make[1]: *** [arch/powerpc/boot/zImage.dts] Error 1
> make: *** [zImage.dts] Error 2
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> ------------------
> 
> 
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  reply	other threads:[~2008-06-02 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 22:18 ML507 EDK 10.1 somshekar c kadam
2008-06-02 14:35 ` John Linn
2008-06-03  2:46   ` somshekar c kadam [this message]
2008-06-03 21:08   ` somshekar c kadam
2008-06-03 22:08   ` somshekar c kadam
2008-07-30  2:26   ` ML507 EDK 10.1 SP2 somshekar c kadam

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=1212461182.25185.3.camel@localhost.localdomain \
    --to=schandra@in.mvista.com \
    --cc=John.Linn@xilinx.com \
    --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).