public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Nathaniel Mercure <nmercure@electroline.com>
To: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: remote target debug problem running
Date: Wed, 11 May 2005 20:03:00 -0000	[thread overview]
Message-ID: <73EE0374460DD311A89E00609779266801B0996D@excserveur.electrolinequip.com> (raw)

***********************
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


             reply	other threads:[~2005-05-11 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 20:03 Nathaniel Mercure [this message]
2005-05-11 20:13 ` Keith Seitz
2005-08-12 14:42 Thomas Motz
2005-08-12 14:56 ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=73EE0374460DD311A89E00609779266801B0996D@excserveur.electrolinequip.com \
    --to=nmercure@electroline.com \
    --cc=insight@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).