From: Andreas Schweigstill <andreas@schweigstill.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] single step flash w/ gdb ocdremote ??
Date: Mon, 08 Aug 2005 15:00:20 +0200 [thread overview]
Message-ID: <42F75764.4040409@schweigstill.de> (raw)
In-Reply-To: <BAY107-F201E5BD32DC0129F222B71C7B90@phx.gbl>
Dear Chuck!
Chuck T. schrieb:
> Remote DDD works fine except for one fatal flaw ... I can't single step
> flash. It single steps code loaded into RAM. Since both insight and
> DDD are really just shells talking to gdb talking to ocdremote
> (gdbserver workalike) it seems clear that my problem is I haven't
> configured gdb to use hardware breakpoints while single stepping, but
> I've searched and searched and googled and googled and can't find
> anything other than hbreak. What am I missing?
Unfortunately I don't work with GDB related debuggers but on the
Lauterbach TRACE32 ICD there are two possibilities for setting hardware
breakpoints; first you can specify it by an additional parameter called
/onchip. Second you you define a memory map with the attributes
map.readonly or map.bonchip (which are internally the same). I expect
that similar attributes exist for GDB. Unfortunately not all ARM related
debugging features are implemented properly on GDB; that's why I prefer
Lauterbach debuggers. IIRC they allow also to set software breakpoints
in certain Flash memory devices.
With best regards
Andreas Schweigstill
--
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstra?e 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/
prev parent reply other threads:[~2005-08-08 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 15:23 [U-Boot-Users] single step flash w/ gdb ocdremote ?? Chuck T.
2005-08-08 13:00 ` Andreas Schweigstill [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=42F75764.4040409@schweigstill.de \
--to=andreas@schweigstill.de \
--cc=u-boot@lists.denx.de \
/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