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

["Cor Venner" <cor.venner@xxxxxxxxx>]

Hello folks,

Some update:

I've found out by studying the System.map file and the binairy image that 
the romfs is located at __init_end. So romfs is overlapping a bunch of 
symbols with a 'b' or a 'B' flag. I don't know what the meaning is of that 
flag. Can somebody help me?

I assume that these symbols are initialised at runtime, otherwise the 
overlap would make no sense. However there is also a 256 byte space for the 
command line "saved_command_line". Is this also filled in when starting the 
kernel?

At start up of the image the image tries to make space for those overlapped 
variables by moving the compressed romfs behind _ebss. This is were the last 
unused part of the kernel image is located. The question remain why the size 
of the block that has to be moved is zero. Is there someone who can give me 
an answer?

Thx.

Best regards, Cor Venner

----- Original Message ----- 
From: "Cor Venner" <cor.venner@xxxxxxxxx>
To: <microblaze-uclinux@xxxxxxxxxxxxxx>
Sent: Wednesday, October 03, 2007 6:09 PM
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/