From: Dustin Byford <dustin@firein.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: custom mpc8240 student project (long)
Date: Mon, 18 Feb 2002 03:33:48 -0700 [thread overview]
Message-ID: <auto-000008646423@zipmail.com> (raw)
Hi,
For purely academic purposes I am building an IP router based on an mpc8240
in my "capstone" EE class at NMSU. I was wondering if someone who may have
done something similar could tell me if I'm working in the right direction.
I've done some research with the list archives and I think I have decided on
a basic hardware layout. I'm just wondering if my ideas are sane and I have
a couple of questions.
I will be wire-wrapping the entire design (sockets have been acquired) and
and plan to use:
MPC8240 (At ~30MHz bus)
National 16550 UART connected to RCS1, etc...
2 16-bit flash ROMs (8MByte total) (Am29LV320D x2) connected toRCS0, etc...
128MB SDRAM in 1 DIMM
PCI (wire wrap board attached to a backplane) with 2 FA310TX netgear cards
There is also a reset circuit, a power supply, and I'm guessing I need a
buffer between the UART and the CPU and a MAX232 for serial line driving.
I also planned to start out by programming the ROMs through the BDM/JTAG port
on the CPU. I'll start with the GDB target for MPCs and attempt to load a
program into RAM to program the 2 flashes, with--ppcboot. Hopefully this
will allow me to run the 2.4_devel version of the ppc kernel, busybox/uclibc
as a distro and iptables as the "router".
I'm expecting many frustrations (I mean learning experiences) along the way
and I suppose I'll begin with sandpoint code for ppcboot and the kernel.
So, what do you think. Will it work? Also, is there maybe a different
kernel I should start out with. Anybody see any major pitfalls?
Also, in the chance that this works I would love to PCB it and fire it up at
200 MHz/100MHz Memory/66MHz PCI and then hang it on my wall because I have to
give the 8240 back to my professor. I can design the PCB but what is the
cheapest way to get a 4-6 layer board done.
Thanks for any and all advice!
--Dustin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-02-18 10:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 10:33 Dustin Byford [this message]
[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
2002-02-19 11:40 ` Jerry Van Baren
2002-02-19 16:53 ` Bob Piatek
2002-02-20 2:32 ` Greg Griffes
-- strict thread matches above, loose matches on Subject: below --
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-22 1:07 Dustin Byford
2002-02-22 1:11 Dustin Byford
2002-02-22 18:33 Kerl, John
2002-02-22 20:51 ` Wolfgang Denk
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=auto-000008646423@zipmail.com \
--to=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 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.