Hi A, A. Bose wrote:
I am trying to port the Avnet LX50 eval board. I can get a basic kernel to boot by modifying the auto-config.in file for microblaze-auto etc.. , but I having problems building u-boot.
If there is no support for my board in the u-boot directory does that mean I cannot build u-boot as per the README in the u-boot directory?
No. petalinux contains a generic microblaze-auto u-boot target, which is sufficient for almost every standard board. The u-boot config system is automatically updated according to the system parmaters, in the auto-config.in file.
microblaze-uclinux-gcc -g -Os -D__KERNEL__ -DTEXT_BASE=0x8ffc0000
-I/home/devel/petalinux-v0.30-rc1DEV/software/petalinux-dist/u-boot/include
-fno-builtin -ffreestanding -nostdinc -isystem
/home/devel/petalinux-v0.30-rc1DEV/tools/linux-i386/microblaze-uclinux-tools/bin/../lib/gcc/microblaze-uclinux/3.4.1/include
-pipe -ffixed-r31 -D__microblaze__ -mno-xl-soft-mul -mcpu=v7.00.a
-Wall -Wstrict-prototypes -I ../board/petalogix/microblaze-auto/ -c -o
cache.o cache.c
{standard input}: Assembler messages:
{standard input}:185: Error: unknown opcode "nopnop"
this is a known bug in our u-boot distro - simply edit to add semicolons after each "nop" instruction in the code fragment that you quoted. This is fixed internally, and will be updated in the next release.
It is triggered only when a system is built without caches (which is pretty rare, since performance is poor).
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/