[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] U-boot in Bram
Hi,
A. Bose wrote:
I am aware of what you are saying.
I have 192 Kbytes of useable BRAM available (each BRAM can use 32Kbits) in
my V5LX50 (48 BRAMs) and the max size that a block ram instance can be is:
131072 bytes (128 Kbytes) according to the BRAM pcore doc.
I found that my u-boot image was about 121 Kbytes. Therefore it should fit.
I just can't figure out the how to change the start address as mentioned:
U-boot also requires space for brk and malloc sections, so things might
get a bit tight.
Anyway, a way to do this might be to configure u-boot to link the
application to zero-based address space (probably offset to about 0x70
hex to avoid the exception and IRQ vectors etc).
Then, I believe XPS allows you to add an elf-only SW project, basically
it will just run init_bram on whatever elf file you point it at. So,
you would point this at u-boot's elf output file - typically u-boot/u-boot.
WARNING:MDT - None of the ELF files for MICROBLAZE instance microblaze_0
start
at address 0x00000000
If memory at start address is not initialized properly, the processor
after
startup will run arbitrarily
So, this warning is just the Xilinx tools telling you to be careful -
normally when you build an app inside EDK it automatically link's
Xilinx's crt0 runtime, and places null interrupt/exception vectors etc.
You might need to do something ismilar with u-boot to remove this warning.
Unless you configure the MicroBlaze 0x0_invalid_opcode parameter, the
CPU will quietly chomp through any 0x0 NOP opcodes in memory until it
reaches u-boot, so if you know what you are doing you can probably
ignore this one.
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/