[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] uclinux memory exhausted, unable to allocate RAM



Hi Victor,

victor-sv_yeo@xxxxxxxxxxx wrote:

John wrote:

Can you please add the line

FLTFLAGS += -v

to your user app Makefile, then clean it and rebuild?

Part of of the output from make when building your app will be the verbose (-v) data from elf2flt. Please extract that from the log and post it to the list.


I did not use mb-elf2flt in my compilation. After compilation, I get this microblaze-target which gives:

You did use elf2flt in your compilation, you just don't realise it because the tools hide it from you :)

[root@patricios nodefw]# mb-flthdr microblaze-target
microblaze-target
    Magic:        bFLT
    Rev:          4
    Build Date:   Fri Jun 22 19:05:14 2007
    Entry:        0x44
    Data Start:   0x143260
    Data End:     0x1a4570
    BSS End:      0x269d20
    Stack Size:   0x1000
    Reloc Start:  0x1a4570
    Reloc Count:  0x4761
    Flags:        0x1 ( Load-to-Ram )

As you see, microblaze-target is not an elf file.

Indeed.

Do i generate elf file and then use mb-elf2flt?

The tools do this for you. Thus my request for you to add -v (verbose) to the FLTFLAGS variable. This tells elf2flt to spit out a bunch of useful information when it does its magic. That useful information will help me to help you figure out why you got an invalid reloc in your flat binary.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/