Re: ARM Simulator Bug?

Re: ARM Simulator Bug?

[David Mc Kenna]

Hi Richard,

I think I have gotten closer to solving my problem. It relates to the linker
script I use with compilation of gcc. 

If I take the standard armelf.x from the ldscripts directory and link against
it my problem disappears. My problem is that I wish to place my reset vectors
at 0x00 not the standard 0x8000. So I change the line:

  /* Read-only sections, merged into text segment: */
  . = 0x8000;

to

  /* Read-only sections, merged into text segment: */
  . = 0x00;

and my problem resurfaces. At a quick check of my memory contents from gdb at
0x00 I get 0x01 as opposed to what I get when I "download" the program using
Run->Download of 0xEA000015.

Any ideas?

Thanks,
Dave


--
http://www.iol.ie

Re: ARM Simulator Bug?

[Richard Earnshaw]

> Hi Richard,
> 
> I think I have gotten closer to solving my problem. It relates to the linker
> script I use with compilation of gcc. 
> 
> If I take the standard armelf.x from the ldscripts directory and link against
> it my problem disappears. My problem is that I wish to place my reset vectors
> at 0x00 not the standard 0x8000. So I change the line:
> 
>   /* Read-only sections, merged into text segment: */
>   . = 0x8000;
> 
> to
> 
>   /* Read-only sections, merged into text segment: */
>   . = 0x00;
> 
> and my problem resurfaces. At a quick check of my memory contents from gdb at
> 0x00 I get 0x01 as opposed to what I get when I "download" the program using
> Run->Download of 0xEA000015.
> 
> Any ideas?

Not really.   Does "arm-elf-objdump -xd exe-file" display something 
sensible?

R.

gdb run command

[Raja Saleru]

Hello, I am asking very poor question.

The gdb "run" command does it ment only for debugging the application on
stand alone machine or can be used while remote debugging ?

while remote debugging, by using the "run" command I observer the following
message, even I didnot started running.

 The program being debugged has been started already.
 Start it from the beginning? (y or n)

- regards
raja

Re: gdb run command

[Tim Combs]

Typically with remote debugging, use the "continue" command.


Tim

On Wed, Sep 03, 2003 at 10:59:32PM +0900, Raja Saleru wrote:
> Hello, I am asking very poor question.
> 
> The gdb "run" command does it ment only for debugging the application on
> stand alone machine or can be used while remote debugging ?
> 
> while remote debugging, by using the "run" command I observer the following
> message, even I didnot started running.
> 
>  The program being debugged has been started already.
>  Start it from the beginning? (y or n)
> 
> - regards
> raja
>