Re: some questions about XUP and the generation of ace file

[greenlean <jmgomez@atc.ugr.es>]

Hi,=20

I'm responding myself and windstorm. First of all, I'm Spanish and I suppos=
e
you too...

Xilinx has translate the compiler tools to spanish, and if you have a look
to the line 430 of the file /opt/Xilinx91i/EDK91i/data/xmd/genace.tcl you
can see

if { [catch {set saddr [exec powerpc-eabi-objdump -x $elffile | grep -w
"start address"]} err] } {

this line pruduces the error. If we do an obj-dump of this file, one using
the ELDK compiler and other one using the EDK cross compiler tool, we see:

$ppc_4xx-objdump -x zImage.elf | less --> Compilador ELDK 4.1
****************************************************************
architecture: powerpc:common, flags 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
start address0x00400000

Program Header:
****************************************************************

$powerpc-eabi-objdump -x zImage.elf  --> Xilinx PowerPC compiler
****************************************************************
arquitectura: powerpc:common, opciones 0x00000112:
EXEC_P, HAS_SYMS, D_PAGED
direcci=C3=B3n de inicio 0x00400000

Encabezado del Programa:
****************************************************************

That's the error, you must translate the start address tag in the opt file
to your language.... In my case this is

if { [catch {set saddr [exec powerpc-eabi-objdump -x $elffile | grep -w
"direcci=C3=B3n de inicio"]} err] } {

By...

PD: I still have a problem with the zImage.elf file  generated by the
compiler, xmd told me that the file is corrupted that this is not an valid
elf file, I posted it some time ago, and I've  no response if someone knows
why it's happening please contact me.



greenlean wrote:
>=20
> Hi windstorm,
>=20
> Have you correct the error, you get when generating the ace file?? I'm
> trying to build the linux system for the XUPV2P board, and I have the sam=
e
> error:
>=20
> Using GenACE option file : xupGenace.opt
> Error: Executable zImage.elf does not contain start address..
>=20
> As you and Xilinx said in the answer
> (http://www.xilinx.com/support/answers/23192.htm) my genace.tcl file is
> patched, and it uses de powerPC objdump.
>=20
> I have tryed to use the ppc_4xx-objdump cross tool of ELDK instead of the
> powerpc-eabi-objdump that is used in the genace.tcl file, and the result
> was an error:
>=20
> ***********
> Executing xmd script : /opt/Xilinx91i/EDK91i/data/xmd/genace.tcl
>=20
> #######################################################################
> XMD GenACE utility. Generate SystemACE File from bit/elf/data Files
> #######################################################################
> Using GenACE option file : xupGenace.opt
> GenACE Options:
>         Board      : user
>         Jtag Devs  : xc2vp30
>         FPGA pos   : 1
>         JPROG      : true
>         HW File    : implementation/download.bit
>         ACE File   : system.ace
>         nCPUs      : 1
>=20
>         Processor ppc_hw_1 Information
>                 Debug opt : -debugdevice devicenr 1 cpunr 1
>                 ELF files : zImage.elf
>                 Start PC Address : 0x00400000
>=20
> ############################################################
> Converting Bitstream 'implementation/download.bit' to SVF file
> 'implementation/download.svf'
> Executing 'impact -batch bit2svf.scr'
>=20
> Copying implementation/download.svf File to  system.svf File
>=20
>=20
> ############################################################
> Converting ELF file 'zImage.elf' to SVF file 'zImage.svf'
> Error: E02 Failed to download ELF file
>=20
> ERROR(1053): UNABLE to Read Elf File. The Elf File Maybe Corrupted
>         : zImage.elf
>=20
>=20
> *********
>=20
>=20
>=20
> but the Error:executable zImage.elf does not contain start address..
> didn't appear. And the compiler assign the address  0x00400000...
>=20
> This error is the same, that xmd told me if I try to download directly th=
e
> linux kernel to the board, maybe there is any relation...
>=20
> I don't know what is happening...
>=20
> Any info or help???
>=20
>=20
>=20
> windstorm wrote:
>>=20
>> 1 it's strange. the ns16550.c do exist in the arch/ppc/boot/
>> directory, not arch/ppc/boot/common. I just download the source
>> yesterday.
>>=20
>> 2 Can you show me some reference about the "small bootloader"? Or any
>> web material about it?
>>=20
>> 2007/8/10, Grant Likely <grant.likely@secretlab.ca>:
>>> On 8/10/07, windstorm <likunarmstrong@gmail.com> wrote:
>>> > Hello all:
>>> >
>>> > I am trying to transfer the Linux onto XUP board. The kernel source I
>>> > used is from the git trees from andrei konovalov or grant likely. But
>>> > I encounter two questions now.
>>> >
>>> > 1 Generally, I should correct the kernel source file
>>> > arch/ppc/boot/common/ns16550.c, In that file, changing SERIAL_BAUD
>>> > from 9600 to 38400  makes the bootloader talk at 38400. I always do i=
t
>>> > when I use standard kernel source. But this time I found out that the
>>> > ns16550.c's path is arch/ppc/boot/, not arch/ppc/boot/common/, and
>>> > there was no "SERIAL_BAUD" string any more. So, how can I control the
>>> > baud rate?
>>>
>>> ???
>>>
>>> I don't know what you're referring to.  ns16550.c is in
>>> arch/ppc/boot/common on my tree, and it still contains the SERIAL_BAUD
>>> #define.
>>>
>>> >
>>> > 2 I have compiled the kernel and obtained a Image.elf whose size is
>>> > 1.7MB, and then it's time for creating a system.ace file which I can
>>> > put onto a compact flash card.  I Changed the file xupGenace.opt like
>>> > the follow:
>>>
>>> You can do this, but I don't think it's a particularly good idea.
>>> Binding the kernel image into an ACE file results in a *very* large
>>> ace file, and it's slow.  Consider the fact that doing it that way
>>> means that you're transferring the entire 1.7MB image via JTAG.
>>>
>>> I've also seem problems where DDR isn't fully initialized before the
>>> SystemACE tries to transfer the image which results in a non-booting
>>> system.
>>>
>>> What I do, is I've got a small bootloader that lives in BRAM and is
>>> just smart enough to load an elf file off of the CF card.  If I can
>>> get permission to do so, I'll publish the source for my utility.
>>>
>>> >
>>> > -jprog
>>> > -board user
>>> > -target ppc_hw
>>> > -hw ./implementation/download.bit
>>> > -elf zImage.elf
>>> > -configdevice devicenr 1 idcode 0x1127e093 irlength 14 partname
>>> xc2vp30
>>> > -debugdevice devicenr 1 cpunr 1
>>> > -ace system.ace
>>> >
>>> > and executed the command: xmd -tcl genace.tcl -opt genace.opt
>>> >
>>> > and the result I saw is:  Using GenACE option file : genace.opt
>>> > Error: Executable zImage.elf does not contain start address..
>>> >
>>> > I examine the information by google, some said that it's the bug of
>>> > development tools without sp, but both my ISE and EDK was patched.
>>> > Others said that it's because of the "mb-objdump", we should chage it
>>> > into "powerpc-eaci-objdump", and actually I had done this correction.
>>> > BUT, the error still here.
>>> >
>>> > Could anyone please to help me about this question? I will be very
>>> grateful.
>>>
>>> Very odd.  I haven't seen this problem myself so I can't be much help.
>>> sorry.
>>>
>>> >
>>> > BTW, could any kind person send any basic config file, which had been
>>> > proved that the kernel compiled based on it could work good on XUP
>>> > board?
>>>
>>> I don't have that board, sorry
>>>
>>> g.
>>>
>>> --
>>> Grant Likely, B.Sc., P.Eng.
>>> Secret Lab Technologies Ltd.
>>> grant.likely@secretlab.ca
>>> (403) 399-0195
>>>
>>=20
>>=20
>> --=20
>> web: http://www.forwind.cn
>> msn: likunarmstrong at hotmail.com
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>=20
>>=20
>=20
>=20

--=20
View this message in context: http://www.nabble.com/some-questions-about-XU=
P-and-the-generation-of-ace-file-tp12090990p14433748.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.