[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] fs-boot/u-boot trouble on ml403
> Causes can be multiple, but I also got a similar problem so in case it
> may help, I will describe it.
> First correct me if I am wrong but the fs-boot srec downloading does not
> deal with the flash memory but with the ram.
Yes. FS-BOOT just look at specific sector in FLASH and check u-boot (kernel) image if is there.
If yes, load it and run. If not, just wait for srec via serial.
You may check inside the
> fs_memcpy function and put some printf debug.
> For my case as soon as I was reading into the ddr, the system hung. I
> did put this to check: xil_printf("dst: %x, src: %x\n\r", *dst, *src);
> For my case it was obviously a ddr mistake, I was not routing correctly
> the DDR_CE signal of my mpmc module.
You have to run memory test on every new design first - this give you quick result
without spend time on debugging.
> You may try to directly boot Petalinux from ram, by typing this in xmd:
> % dow -data image.bin 0xADDR_OF_RAM
> % con 0xADDR_OF_RAM
> It will remove the possibilities of tftp boot or serial download errors.
Yes. Your 0xADDR_OF_RAM should be memory start.
> Hope it will help,
> abelshaw@xxxxxxxxxx wrote:
>> Hello all,
>> I am trying to put a linux-2.6 kernel onto a ML403 board.
>> The step I'm stuck on is the FS-BOOT just hangs up while downloading
>> the U-boot
>> FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
>> FS-BOOT: System initialisation completed.
>> FS-BOOT: No existing image in FLASH. Starting image download.
>> FS-BOOT: Waiting for SREC image....
>> The spin wheel goes for a split second, then nothing happens even
>> after the cat
>> command finishes.
>> I've checked the u-boot image and the file endings only have just LF
>> endings I
>> believe (0A endings), so I don't think I have the problem described in
>> the uart
>> issue in fs-boot thread. (I also checked my serial cable just to be
>> sure and it
>> Two things that I think could possibly be fouling it up, but I don't
>> know enough
>> about this kind of project yet to know how to check:
>> 1) To get the kernel to actually build Vendor settings of Xilinx/ML401
>> had to be
>> used, as it wouldn't build when we changed it to ML403. Perhaps the
>> image is wrong?
>> 2) What I think might be messing this up is I had to manually edit the
>> auto-config.h file because the edk-9.1 I'm using didn't recognize the
>> memory (of any type) so it didn't create a FLASH_MEMORY_START so the
>> program wouldn't build. I added in manually the START and SIZE of my
>> Memory peripheral, could there be memory address issues from changing
>> it that way?
>> The only two lines I added to the auto-config.h file the edk created were
>> #define CONFIG_XILINX_FLASH_START (0x41800000)
>> #define CONFIG_XILINX_FLASH_SIZE (0x00010000)
>> Let me know if there is also a much easier way that I've missed.
>> microblaze-uclinux mailing list
>> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
>> Mailing List Archive :
> microblaze-uclinux mailing list
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/