public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Richard Danter <richard.danter@ntlworld.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] BDI2000 vs Vision-ICE
Date: Fri, 09 Jan 2004 09:58:17 +0000	[thread overview]
Message-ID: <3FFE7B39.3060300@ntlworld.com> (raw)
In-Reply-To: 3FFDC547.3010302@lucent.com

Mike Wellington wrote:
> People at my place of work are telling me that the
> Vision-Ice supports "backtrace" and the BDI2000 does
> not.   I looked on the Abatron website and it doesn't
> say.  Can anyone confirm or deny this?

I can't talk about the Abatron, but for vICE there are a couple of 
options which are/were available.

 >
 > By "backtrace", I mean the ability to set a breakpoint,
 > hit that breakpoint, and be able to see the last N
 > instructions executed.

In the old days there was vEVENT. It was a bus trace system which 
captured all accesses from the CPU to any/all peripherals. It was 
available for most of the architectures WR/EST supported. This was EOL'd 
in favour of the LA-Trace.

LA-Trace is a combination of a vPROBE or vICE with a full logic 
analyser. The reason for switching to this was that the old vEVENT could 
not keep up with the newer CPU's running at high (>50MHz) bus speeds.

The problem with both of these options, and any other system using bus 
capture, is that they don't see everything. When the CPU is executing 
code from cache there is nothing visible outside so all you see are the 
code and data read/writes associated with a cache miss. Worse still is 
that when a read occurs the cache will usually get a complete cache 
line, not just the word required. Somtimes the whole line will be used 
(as in sequential code) but not always. It's tricky working out what is 
relevant and what is not. As caches get bigger so this problem gets worse.

The best option is vTRACE, but it is available only on a limited number 
of CPU's. This is beacuse vTrace uses the trace capability built in to 
some CPU's. The best trace capabilities are in the ColdFIRE range - they 
all support data tracing as well as code, but on PowerPC you can get 
code trace on the 405x, 440GP and 56x (NEXUS). There are also some MIPS 
processors which have this capability.

Whilst we are talking about vICE, thought I would just mention that it 
now supports Linux debugging too on some CPUs. That is, it has MMU 
awareness for the 82xx and 405x CPUs so you can debug the kernel and 
loadable modules with full source code. More than that though, they now 
also support some user-land debugging. I spose this is more relevant to 
the linux mailing list though...

Rich

  parent reply	other threads:[~2004-01-09  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 18:58 [U-Boot-Users] U-Boot on MPC8280 Rod Boyce
2004-01-08 12:36 ` John W. Linville
2004-01-08 21:01   ` [U-Boot-Users] BDI2000 vs Vision-ICE Mike Wellington
2004-01-08 23:04     ` Wolfgang Denk
2004-01-09  9:58     ` Richard Danter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-08 22:56 Wells, Charles
2004-01-09 13:29 VanBaren, Gerald
2004-01-09 15:50 ` Mike Wellington

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=3FFE7B39.3060300@ntlworld.com \
    --to=richard.danter@ntlworld.com \
    --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