From: "Cliff" <gdbinsight@citiz.net>
To: <insight@sources.redhat.com>
Subject: How to use "Command to issue after attaching"
Date: Wed, 22 Oct 2003 12:30:00 -0000 [thread overview]
Message-ID: <007f01c39898$5c39d210$0100a8c0@tamahome> (raw)
Hi, all:
I'm using arm-elf-insight with ocdlibremote, and I want to send some commands to ocdlibremote after attaching it.
I put them in .gdbinit file and it really executes, but when I push the "run" button, insight try to detach and re-attach the target, so my settings are all lost.
I want to write some registers into the target CPU(S3C44BOX) so that I can use it's SDRAM without initialize by the user program.
It is a serial of commands like
monitor long 0x01c80000 = 0x11111002
monitor long 0x01c80004 = 0x0600
monitor long 0x01c80008 = 0x7ffc
.....
Then I try the "Command to issue after attaching" in the Target Selection dialog, but it seems only one command to issue. How can I run more than one command after attaching the target?
next reply other threads:[~2003-10-22 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 12:30 Cliff [this message]
2003-10-22 13:05 ` Peter Reilley
2003-10-22 16:19 ` Keith Seitz
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='007f01c39898$5c39d210$0100a8c0@tamahome' \
--to=gdbinsight@citiz.net \
--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).