Re: [microblaze-uclinux] Booting the petalinux kernel with FS-boot

["Stephane Rousseau" <stephaner@xxxxxxxxx>]

Hi,

If your board has ethernet, you can start with FS-boot, then transfer
u-boot.srec via serial line. And the use a tftp server to send your
image.ub with Ethernet to your board.

Regards,

Stephane

On 10/5/07, Theidel Gerd <gerd.theidel@xxxxxx> wrote:
> It is possible to start the image.srec directly with FS-boot,
> I just triued it to be sure (but takes about 10 min over serial line).
> Make sure that your configured Kernel Image does not need any components
> like Flash, etc... that you don't have in your design.
>
> Regards,
> Gerd
>
>
>
> -----Original Message-----
> From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Cor Venner
> Sent: Mittwoch, 3. Oktober 2007 18:09
> To: microblaze-uclinux@xxxxxxxxxxxxxx
> Subject: [microblaze-uclinux] Booting the petalinux kernel with FS-boot
>
> Is there someone who can help me with this:
>
> I'm trying to run Petalinux on a very basic system with only external
> SDRAM and a serial port. First I tried to download U-boot with FS-boot.
> U-boot displays its position into memory, then it falls back to the
> FS-Boot loader (it's like the board is reset).  So I tried downloading
> the kernel image directly with FS-boot.
>
> Is it possible to boot the kernel with FS-boot?
>
> I have tried this (image.srec) and got the following result:
>
> =================================================
> 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....
> FS-BOOT: Image download successful.
> FS-BOOT: Warning image location differ from default boot location. Image
> will no t boot automatically after POR.
> FS-BOOT: Press 'n' to boot old image.
> FS-BOOT: Use new image.
> FS-BOOT: Booting image...
> Found romfs @ 0x200e408c (0x00000000)
> #### klimit 200f6000 ####
> Moving 0x00000000 bytes from 0x200e408c to 0x200f523c New klimit:
> 0x200f6000
>
>
> Notice that romfs size is 0. I assume the the romfs is a part of
> "image.srec". According to the documentation it is described as "The
> Linux
> kernel and root filesystem image in SREC format". So how can the size be
> 0.
>
> Is there someone who can help me.
>
> Best regards, Cor Venner
>
> ___________________________
> 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/
>
>
___________________________
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/