From: Steve Rossi <srossi@ccrl.mot.com>
To: clark@esteem.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Do I shoot myself in the foot first or HEAD.S?
Date: Wed, 19 Jul 2000 09:09:27 -0500 [thread overview]
Message-ID: <3975B697.63313411@ccrl.mot.com> (raw)
In-Reply-To: 1.5.4.32.20000719011945.006845c0@pop.esteem.com
clark@esteem.com wrote:
>
> 4. Has any one managed to get an EST VisionICE in circuit emulator to work
> with linuxPPc? If so How? Would I be better off using the GNU Debuger?
>
We did use EST's VisionICE box to download linux kernel images to our target
hardware before we had a rom monitor with network loading. It was also helpful
to debug the early boot stuff when we were porting to custom hardware - before
the memory management is enabled. Once the memory manager is enabled, the
VisionICE becomes mostly useless, because as has been said many times on this
list - most BDM debuggers don't understand virtual addresses. Nevertheless the
VisionICE did offer some utility to us.
I wrote a little app that slaps an EST .bin file header on a linux image
(zvmlinux or zvmlinux.inird). I can send that to you if you want it. Then I use
Download to Target from VisionClick and that sticks the whole image in RAM. You
do need to disable VisionICE's interception of software breakpoint emulation
interrupts - do 'cf sbe special'. That should be it.
--
-------------------------------------------------------
Steven K. Rossi srossi@ccrl.mot.com
Staff Engineer
Multimedia Communications Research Laboratory
Motorola Labs
-------------------------------------------------------
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-19 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 1:19 Do I shoot myself in the foot first or HEAD.S? clark
2000-07-19 1:30 ` Graham Stoney
2000-07-19 8:03 ` Wolfgang Denk
2000-07-19 8:13 ` Wolfgang Denk
2000-07-19 14:09 ` Steve Rossi [this message]
2000-07-19 15:13 ` Wolfgang Denk
2000-07-19 15:19 ` Tom Roberts
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=3975B697.63313411@ccrl.mot.com \
--to=srossi@ccrl.mot.com \
--cc=clark@esteem.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).