From: Wolfgang Denk <wd@denx.de>
To: Dustin Byford <dustin@firein.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: custom mpc8240 student project (long)
Date: Mon, 18 Feb 2002 23:32:56 +0100 [thread overview]
Message-ID: <20020218223301.57292109E2@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 18 Feb 2002 15:32:14 MST." <auto-000008693306@zipmail.com>
In message <auto-000008693306@zipmail.com> you wrote:
> I understand what you're saying about the COP so I need to evaluate my
> options. We are all students working on this so I don't think my coleauges
> will spring for the BDI since we don't have one available to us at the
> University. Is the BDI1000/2000 the least expensive way to use the JTAG/COP?
In terms of time AND money AND power: definitely.
> An alternate idea: What if I jumper in a 32 pin PDIP 8-bit EEPROM somewhere
> that I can boot from (RCS0/8-bit). I can pull this part off of the board and
> throw it in a programmer we have at the university. Hopefully I'll be able
> to program it with something that will "simply" program itself onto the TSOP
> AMD flash (which would then be jumpered to (32-bit/RCS1). Remove the jumpers
> and reset the board and maybe I would have a ROM that can downlaod stuff
> through the UART. Not the quickest of development cycles but it is a no-cost
> solution.
OK, now you can program your boot device. You plug it in, power on,
and you are lucky: no magic smoke to be seen.
But your code doesn't run (and I guarantee you that it will not run
on first attempt).
I bet you'd like to have a debugger then...
> Or: Leave the EEPROM on RCS0 all the time. The AMD Flash on RCS1 all the
> time and find another place to put the UART. Suggestions?
Yes, two: find some working hardware which already has the firmware
running, or get yourself the neccesary tools.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
See us @ Embedded Systems Nuremberg, Feb 19-21, Hall 12 K01 (with TQ)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-18 22:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7E8519F1A7C0D211B0D200A0C93AA60F08447D20@ntmail.iskratel.si>
2002-02-18 21:17 ` custom mpc8240 student project (long) Dustin Byford
2002-02-18 21:44 ` Wolfgang Denk
[not found] ` <auto-000008693306@zipmail.com>
2002-02-18 22:32 ` Wolfgang Denk [this message]
2002-02-19 11:40 ` Jerry Van Baren
2002-02-19 16:53 ` Bob Piatek
2002-02-20 2:32 ` Greg Griffes
2002-02-22 18:33 Kerl, John
2002-02-22 20:51 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 1:11 Dustin Byford
2002-02-22 1:07 Dustin Byford
2002-02-21 20:12 Kerl, John
2002-02-21 20:32 ` Jim Thompson
2002-02-21 22:40 ` Ron Bianco
2002-02-22 9:32 ` Geir Frode Raanes
2002-02-22 13:09 ` Jerry Van Baren
2002-02-23 19:16 ` Dan Malek
2002-02-25 12:18 ` Geir Frode Raanes
2002-02-27 11:46 ` Christian Pellegrin
2002-02-18 10:33 Dustin Byford
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=20020218223301.57292109E2@denx.denx.de \
--to=wd@denx.de \
--cc=dustin@firein.net \
--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).