MIPS (purple) compilation problems.

Hi

I'm trying to port the U-Boot to Marvell board with MIPS (rm7000) I am using a cross compiler mips64-elf.
I'm trying to compile the purpule_config and I have some compilation problems,
when I'm using the cpu/mips/config flag -mabicalls I get a lot of warnings:
c1: warning: -G is incompatible with PIC code which is the default
.........
and an LD error:
mips64-elf-ld: common/main.o: linking PIC files with non-PIC files Bad value: failed to merge target specific data of file
common/main.o

When I remove the -mabicalls flag, the compilation pass, and the LD fail again on different error:
mips64-elf-ld: target elf32-tradbigmips not found

The LD is looking for elf32-tradbigmips because in the LD script we define the output file to be: elf32-tradbigmips

why do we use this definition and not elf32-bigmips?? and what is the difference between these two??
and why when I install my cross compiler I don't have support for this output format??

so I changed it the output format to elf32-bigmips then I'm getting this LD error:
: undefined reference to `_GLOBAL_OFFSET_TABLE_'

I know it is because I don't have this define in the linker script, and I guess the elf32-tradbigmips has this definition. What should I do??

Thanks

I'm trying to port the U-Boot to Marvell board with MIPS (rm7000)

I see that after relocating to the DRAM the disassembly of the u-boot shows me
that we jump back to the flash:

start.S: dis:
la t9,board_init_r lui t9,0xbfc1

                                                  addiu     t9,20140

j t9 jr t9

I see that I get the same problem when I jump to printf etc. maybe it is because I don't compile the code as PIC? Is there any

special compilation flag I should use?

Can someone please send me a disassembly of the U-Boot for any of the MIPS board (purple, incaip or dbaux100).

Is there any special handle for relocating of the MIPS that is different from the PPC, that I should take under consideration???

Quoted 4 lines

c1: warning: -G is incompatible with PIC code which is the default
.........
and an LD error:
mips64-elf-ld: common/main.o: linking PIC files with non-PIC files

Quoted 3 lines · In message <[email protected]> you wrote:

I'm trying to port the U-Boot to Marvell board with MIPS (rm7000)

In your Subject: you write: MIPS (purple) compilation problems. I cannot see any relation to the Infineon Purple board here??

Quoted 5 lines

I see that after relocating to the DRAM the disassembly of the u-boot shows me
that we jump back to the flash:

What did you disassemble? The code in RAM?

Quoted 6 lines

start.S: dis:
la t9,board_init_r lui t9,0xbfc1

                                                 addiu     t9,20140

j t9 jr t9

This cannot work. This is what I see for the "purple" board:

...
move a0, a1
564: 00a02021 move a0,a1
la t9, board_init_r
568: 8f990000 lw t9,0(gp)
j t9

56c:   03200008        jr      t9
       move    a1, a2          /* delay slot                   */
570:   00c02821        move    a1,a2

Quoted 4 lines

I see that I get the same problem when I jump to printf etc. maybe it is because I don't compile the code as PIC? Is there any

If you meddle with the compiler options you better know EXACTLY what you are doing.

Quoted 3 lines

special compilation flag I should use?

Use the flags as they are defined in U-Boot. This is what works for me.

Quoted 4 lines

Can someone please send me a disassembly of the U-Boot for any of the MIPS board (purple, incaip or dbaux100).

See above.

Quoted 4 lines

Is there any special handle for relocating of the MIPS that is different from the PPC, that I should take under consideration???

There are differences, but your problem is not caused by any of these. You use bad compiler options and/or misconfigured tools.

Quoted 6 lines

Quoted 6 lines

c1: warning: -G is incompatible with PIC code which is the default
.........
and an LD error:
mips64-elf-ld: common/main.o: linking PIC files with non-PIC files

I don't understand why you don't follow the clear hints the compiler is giving: "incompatible with PIC code which is the default". If your compiler is configured such that PIC is the default, and this default is causing incompatibilities, I would try to find out which compiler option can be used NOT to generate PIC. ["-fno-pic" comes to mind.]

Wolfgang Denk

The code I disassemble below is the u-boot image.

As I understand the code must be PIC, other wise when we will relocate

to the DRAM in the next function
call we will jump back to the Flash, cause the compiler might use

absolute jump and not a relative branch/jump.

Can you please send me a short description how did you built your cross compiler.