All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Michael E Crowe <mike@timesys.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: EST SBC8260
Date: Thu, 22 Mar 2001 12:18:50 -0500	[thread overview]
Message-ID: <3ABA33FA.4FD3B2B0@mvista.com> (raw)
In-Reply-To: 3ABA21C9.4090003@timesys.com


Michael E Crowe wrote:

> .... In order to put a linux kernel
> onto this board, do I have to also purchase a JTAG from WindRiver like
> the VisionProbe or is the monitor that resides on the board enough to
> get PPCBoot working on it?

The early boards I used didn't have much of a monitor, so I always
used JTAG.

The main problem is the Wind tools assume the monitor is in the on-board
flash, and the SIMM is a flash disk.  If you power up the board, the
monitor will re-write the SIMM into something it understands, so you
can't put code out there and expect it to survive (at least with the
recent versions I have seen).  If you can convince the on-board monitor
the flash the local part, well, you get one chance at PPCBoot :-).

Buy an Abatron BDI2000.  You can use it for lots of things, including
programming/debugging PPCBoot and the Linux kernel once you get to
that point.  It's worth every penny if you place any value on your
time.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-03-22 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 16:01 EST SBC8260 Michael E Crowe
2001-03-22 17:18 ` Dan Malek [this message]
2001-03-22 20:32   ` Scott Howard
2001-03-22 21:38     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2001-11-30 20:45 EST sbc8260 Andrew Dixon
2001-11-30 19:11 EST SBC8260 Andrew Dixon
2000-12-14 18:36 Louis Krigovski
2000-12-08 15:17 Louis Krigovski

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=3ABA33FA.4FD3B2B0@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mike@timesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.