From: "Doug Hubbard" <dhubbard@scires.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: BDM and gdb
Date: Thu, 16 Aug 2001 12:25:04 -0400 [thread overview]
Message-ID: <sb7bbbbe.017@mail.scires.com> (raw)
I am using the Macraigor Systems RAVEN bdm dongle and attempting, initially to just look at the processor registers. I am using the test code and make file supplied by Macraigor.
First, (complaint) the connector on the bdm cable appears to have been installed backwards. Someone noticed because they shaved the key of the connector. When plugged correctly (pin 1 to pin 1) I get jtag/bdm errors, when plugged in backwards I get no download errors.
Once downloaded the program will not execute and when I poke around the processor registers they all show an address AND a value of 0x5015010.
I have tried this on 2 MBX boards and our custom board which uses the same MPC860 processor.
TIA.
― Doug
Doug Hubbard
Software Engineer
Scientific Research Corporation
2300 Windy Ridge Parkway
Suite 400, South
Atlanta, GA 30339
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-08-16 16:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=sb7bbbbe.017@mail.scires.com \
--to=dhubbard@scires.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).