From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound9-blu-R.bigfish.com (outbound-blu.frontbridge.com [65.55.251.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTP id 1D662DDF10 for ; Thu, 13 Dec 2007 04:21:03 +1100 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Linux 2.6 from git.xilinx and XUPV2P Date: Wed, 12 Dec 2007 09:19:38 -0800 In-Reply-To: <14299307.post@talk.nabble.com> References: <14274035.post@talk.nabble.com> <14299307.post@talk.nabble.com> From: "Stephen Neuendorffer" To: "greenlean" , Message-Id: <20071212171940.8D86B17B0067@mail230-blu.bigfish.com> List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , The xparameters file is specific to your hardware design. You should change the name of the generated xparameters file to match xparameters_xupv2p.h=20 Unfortunately, it's sort of an historical artifact that it was done this way... In reality, all the different xparameters files should really just be one, since only one can be active at a time. The last error sounds like you haven't actually generated an elf file? have you tried running objdump on it? Steve > -----Original Message----- > From:=20 > linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs.org > =20 > [mailto:linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@oz > labs.org] On Behalf Of greenlean > Sent: Wednesday, December 12, 2007 9:05 AM > To: linuxppc-embedded@ozlabs.org > Subject: Re: Linux 2.6 from git.xilinx and XUPV2P >=20 >=20 >=20 >=20 > greenlean wrote: > >=20 > > Thanks both for the response, I've allready visited some of=20 > the links.=20 > >=20 > > Yes, you was right it's easear than I think, my problem was=20 > the .config > > file. Now, I have generated it from ml300_defconfig and=20 > after some changes > > it compiles, but I've two question: > >=20 > > * I've chosen as platform the XUPV2P in Machine Type,=20 > instead of ML300, > > so the xparameters file that I'm using is the=20 > xparameters_xupv2p.h, but > > the xparameters file generated by the EDK is=20 > xparameters_ml300 despite I > > told it to use XUPV2P, so I can't overwrite it...=20 > >=20 > > Should I use the xparameters_ml300 generated by EDK or the > > xparameters_xupv2p included in the git kernel tree?. I=20 > can't compile with > > the edk's xparameters_ml300 file because there's some=20 > definition that the > > compiler can't find, so I'm using the xparameters_xupv2p. > >=20 > > * Second, if I compile using the xparameters_xupv2p, when=20 > I do the dow > > command to download the image to the board, the xmd shell tell me: > > =20 > > XMD% dow zImage.elf > > Failed to download ELF file > >=20 > > ERROR(1053): UNABLE to Read Elf File. The Elf File=20 > Maybe Corrupted > > : zImage.elf > > Maybe this error is due to the above asumption??. I'll post=20 > this second > > one on xilinx-support maybe it's realted with my system..... > >=20 > >=20 > >=20 >=20 > --=20 > View this message in context:=20 > http://www.nabble.com/Linux-2.6-from-git.xilinx-and-XUPV2P-tp1 > 4274035p14299307.html > Sent from the linuxppc-embedded mailing list archive at Nabble.com. >=20 > _______________________________________________ > Linuxppc-embedded mailing list > Linuxppc-embedded@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded >=20 >=20