RE: [microblaze-uclinux] problem booting U-boot

["LEROY Jean-Loup" <jean-loup.leroy@xxxxxx>]

Thanks a lot.

In fact I had a hardware problem according to the DDR memory interface. I then succeed to boot U-Boot.

Regards,

Jean-Loup

> -----Message d'origine-----
> De : owner-microblaze-uclinux@xxxxxxxxxxxxxx [mailto:owner-microblaze-
> uclinux@xxxxxxxxxxxxxx] De la part de John Williams
> Envoyé : mercredi 18 avril 2007 01:36
> À : microblaze-uclinux@xxxxxxxxxxxxxx
> Objet : Re: [microblaze-uclinux] problem booting U-boot
> 
> Hi Jen-Loup,
> 
> LEROY Jean-Loup wrote:
> 
> > I successfully run Petalinux on my Xilinx ML402 board.
> 
> That's good to hear
> 
> > Then I changed my hardware design in order to allow dynamic partial
> > reconfiguration. My XPS project is now a submodule.
> 
> I'm assuming your kernel still boots nad runs on this new configuration?
> 
> > Then, I boot FS-Boot, I download u-boot.srec file (with FS-BOOT)
> > successfully. After the download, the "GO(image_start)" instruction (the
> > last one in FS-BOOT) must run the U-BOOT, but nothing happened, the
> > microblaze seems to freeze.
> 
> You shuld try downloading u-boot directly into memory, and running it
> "by itself".  To do this you can use the petalinux-jtag-boot command:
> 
> Assuming you have completed the SW build, and elected to copy the
> resulting images into /tftpboot, you shuold be able to do something like
> this (from the HW project directory)
> 
> petalinux-jtag-boot -i /tftpboot/u-boot-s.bin -a <start address>
> 
> the <start address> parameter can just be the start of physical DDR
> memory - u-boot is packaged up inside an auto-relocation header so it
> should relocate itself to the correct address in memory.
> 
> A few other things to check - look at the u-boot/System.map file to make
> sure that u-boot is being linked to run near the *top* of the ML402
> system memory.
> 
> Also, the ML40X reference designs from Xilinx often were creted so that
> the bus address window of the DDR was tweice the size of the actual
> physical memory.  This allows tricks like unchcached memory shadowing,
> but it means that you'ev got to suppply an "parameter main_memory_size="
> override in your EDK project MSS file.  You should have a look at the
> ML401 design distributed with PetaLinux, and make sure you've got
> something similar in your design.
> 
> I hope this helps,
> 
> 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/


___________________________
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/