From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: mrchaoxiang@hotmail.com
Cc: gdb@sources.redhat.com
Subject: Re: ColdFire registers
Date: Fri, 22 Jul 2005 18:21:00 -0000 [thread overview]
Message-ID: <200507221820.j6MIKxEC014714@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <BAY12-F84C4F5D685FC99D8A8281ACC90@phx.gbl> (message from =?gb2312?B?z/Igs6w=?= on Fri, 22 Jul 2005 13:29:35 +0000)
From: =?gb2312?B?z/Igs6w=?= <mrchaoxiang@hotmail.com>
Date: Fri, 22 Jul 2005 13:29:35 +0000
I am using m68k-bdm-elf-gdb 6.0 for my MCF5249EVB.I built the toolchain
myself.
The gdb debugger can connect to the target with command 'target bdm
/dev/bdmcf0'.
my problem is the debugger can display only basic CPU registers, the eMAC
registers such as
MACSR, ACC0, ACC1 can't be accessed. The 'info reg' command also results
the basic registers.
How can I tell the gdb to read and modify eMAC registers?
Not unless you contribute the code for gdb to do that ;-).
Mark
prev parent reply other threads:[~2005-07-22 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 13:29 向 超
2005-07-22 13:34 ` Daniel Jacobowitz
2005-07-22 18:21 ` Mark Kettenis [this message]
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=200507221820.j6MIKxEC014714@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sources.redhat.com \
--cc=mrchaoxiang@hotmail.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).