Re: remote target debug problem running

Re: remote target debug problem running

[Thomas Motz]

I had the same problem, when I try to start insight over .gdbinit the
"File->Target Settings" target entry is blank.

Which command for .gdbinit does the equivalent of the Target-Settings Menue
in Insight?

I can set the Baudrate and the ComPort but not the target.

A workaround might be the settings in the preference or the history from
Insight.
But every time when  I start insight the target field is empty.

>It prints the error for one of two reasons: you haven't selected a
>target to debug (File->Target Settings..." or it isn't setting the
>target based on the last run (which is a bug).
>

Does anybody know a reason why insight looses the history?

(Insight 6.3, cygwin, Win2K)

Regards
Thomas








>On Wed, 2005-05-11 at 16:02 -0400, Nathaniel Mercure wrote:
>
>> .../gdb/insight --command=~/bin/mips-gdb.ini
>>     cat ~/bin/mips-gdb.ini
>>         set remoteti 10
>>         set heur 0
>>         set remote memory-write-packet-size fixed
>>         set remote memory-write-packet-size 4200
>>         set download-write-size 3584
>>
>>         target remote localhost:2345
>>         load eCos.elf
>>
>> The problem here is that I CAN'T browses any source file.
>
>That's because you've only downloaded the code to your target board. You
>haven't given GDB/Insight an executable to work on. I presume that
>"eCos.elf" was generated by a compiler. I suggest you change your
>startup script to do:
>
>file eCos.elf
>target remote localhost:2345
>load
>
>instead of the last two lines you have. The "file" command is the
>equivalent of Insight's "open": it causes GDB to read in debugging
>information for your executable.
>
>> When I use open/run to select the elf file and run it.  The board
connects
>> to the
>> remote server but doesn't download the code and gives the following
message.
>>
>>     "You cannot do that without a process to debug"
>>     ...
>>
>> In this case I CAN browses the source code ?!
>
>That's because the "open" command does the equivalent of GDB's "file"
>command (the step you were missing before).
>
>It prints the error for one of two reasons: you haven't selected a
>target to debug (File->Target Settings..." or it isn't setting the
>target based on the last run (which is a bug).
>
>Keith

RE: remote target debug problem running

[Dave Korn]

----Original Message----
>From: Thomas Motz
>Sent: 12 August 2005 15:41

> I had the same problem, when I try to start insight over .gdbinit the
> "File->Target Settings" target entry is blank.
> 
> Which command for .gdbinit does the equivalent of the Target-Settings
> Menue in Insight?
> 
> I can set the Baudrate and the ComPort but not the target.

  IIUYC, you want to use the "target remote <device>" command, e.g. "target
remote /dev/ttyS0"

  I don't know why the settings are getting lost.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

Re: remote target debug problem running

[Keith Seitz]

On Wed, 2005-05-11 at 16:02 -0400, Nathaniel Mercure wrote:

> .../gdb/insight --command=~/bin/mips-gdb.ini
>     cat ~/bin/mips-gdb.ini
>         set remoteti 10
>         set heur 0
>         set remote memory-write-packet-size fixed
>         set remote memory-write-packet-size 4200
>         set download-write-size 3584
> 
>         target remote localhost:2345
>         load eCos.elf
> 
> The problem here is that I CAN'T browses any source file.

That's because you've only downloaded the code to your target board. You
haven't given GDB/Insight an executable to work on. I presume that
"eCos.elf" was generated by a compiler. I suggest you change your
startup script to do:

file eCos.elf
target remote localhost:2345
load

instead of the last two lines you have. The "file" command is the
equivalent of Insight's "open": it causes GDB to read in debugging
information for your executable.

> When I use open/run to select the elf file and run it.  The board connects
> to the 
> remote server but doesn't download the code and gives the following message.
> 
>     "You cannot do that without a process to debug"
>     ...
> 
> In this case I CAN browses the source code ?!

That's because the "open" command does the equivalent of GDB's "file"
command (the step you were missing before).

It prints the error for one of two reasons: you haven't selected a
target to debug (File->Target Settings..." or it isn't setting the
target based on the last run (which is a bug).

Keith

remote target debug problem running

[Nathaniel Mercure]

***********************
Your mail has been scanned by InterScan VirusWall.
***********-***********


Hello 

I'm new to Insight and I'm trying to use it to debug a remote Mips core. 
Using an EPI JTAG probe.

When I use the following command to start Insight the code is downloaded to
the target board no problem and I can use the continue/stop icons to start
and stop the board.

.../gdb/insight --command=~/bin/mips-gdb.ini
    cat ~/bin/mips-gdb.ini
        set remoteti 10
        set heur 0
        set remote memory-write-packet-size fixed
        set remote memory-write-packet-size 4200
        set download-write-size 3584

        target remote localhost:2345
        load eCos.elf

The problem here is that I CAN'T browses any source file.


When I use open/run to select the elf file and run it.  The board connects
to the 
remote server but doesn't download the code and gives the following message.

    "You cannot do that without a process to debug"
    ...

In this case I CAN browses the source code ?!

Any Body as an Idea on how I could browse the code and set break points at
the same time :|

Nathaniel Mercure
Electroline Equipment
Embedded Software guy