gdb off by 4 bytes

I'm having a problem with gdb lying to me.  If I have this:

> #include <stdio.h>
>
> static char *MyStrings[] = {"string1", "string2", "string3"};
>
> char *Strings2[] = {"string2_1", "string2_2"};
>
> int
> main ()
> {
>     printf ("MyStrings = %x\n", MyStrings);
>     printf ("MyStrings[0] = %s\n", MyStrings[0]);
>
>     printf ("Strings2 = %x\n", Strings2);
>     printf ("Strings2[0] = %s\n", Strings2[0]);
>     getchar ();
>     return 0;
> }
It prints:
> MyStrings = 459ee170
> MyStrings[0] = string1
> Strings2 = 459ee168
> Strings2[0] = string2_1
But gdb reports:
> (gdb) p &MyStrings
> $1 = (char *(*)[3]) 0x459ee16c
> (gdb) p &Strings2
> $2 = (char *(*)[2]) 0x459ee168

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  <at>  0x200e408c (0x00000000)
#### klimit 200f6000 ####
Moving 0x00000000 bytes from 0x200e408c to 0x200f523c
New klimit: 0x200f6000

adding shared libraries to petalinux

sorry,

Using NFS with uClinux kernel

I need the Kernel 2.6 like RTOS

Re: Booting the petalinux kernel with FS-boot

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@...>
To: <microblaze-uclinux@...>
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  <at>  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@...
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
> 

Request for Petalinux Quotation

Dear John, 
We would like to purchase your PetaLinux to use in our boards, 
Could you please provide the quotation of your software? 
The required details are as follows. 
PetaLinux for PPC and Microblaze for ML410 board. 
Do you provide any assistance if we need? 
How is different yours from free distribution?
If we order, how much time you required to deliver the software CDs and related material?

looking forward to hear from you.

with regards,
Solomon Raju

******************************************** 
K. Solomon Raju 
Scientist, 
Room No: E-107 
Digital Systems Group, * 
Central Electronics Engineering Research Institute, * 
Pilani-333031, Rajasthan, India 
* 
Voice: +91 1596 252271 (O): Mobile: +91 9460842188 
e-mail: solomon@... 
kota_solomonraju@... 
----------- and ---------------------------------------* 

Ph.D. Scholar, Dept. Electronics & Comp. Engg. * 
Indian Institute of Technology Roorkee (IITR) * 
Roorkee 247 667, India 
e-mail: rajukdec@... 
**********************************************

      ___________________________________________________________ 
Want ideas for reducing your carbon footprint? Visit Yahoo! For Good  http://uk.promotions.yahoo.com/forgood/environment.html

RE: Booting the petalinux kernel with FS-boot

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@...
[mailto:owner-microblaze-uclinux@...] On Behalf Of Cor Venner
Sent: Mittwoch, 3. Oktober 2007 18:09
To: microblaze-uclinux@...
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  <at>  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@...
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/

Re: Booting the petalinux kernel with FS-boot

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@...> 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@...
> [mailto:owner-microblaze-uclinux@...] On Behalf Of Cor Venner
> Sent: Mittwoch, 3. Oktober 2007 18:09
> To: microblaze-uclinux@...
> 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  <at>  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@...
> 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@...
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>