Article View: sci.electronics
Article #4097Re: Dual-port memory access?
From: Mike McManus
Date: Sat, 13 Jan 1990 00:01
Date: Sat, 13 Jan 1990 00:01
42 lines
2990 bytes
2990 bytes
In article <3310@uceng.UC.EDU> schriste@uceng.UC.EDU (Steven V. Christensen) writes:
> Let's say I want to build come computer-based device, OK, and let's
> say I want to interface this to an IBM-PC, OK. I want that the
> PC could be able to download into the memory of this project,
> and then kick the processor to start executing.
> Holding and starting the processor via PC control is no problem.
> My question is, what is the best way to facilitate the PC-downloading
> of the other CPU's memory?
I'm not sure what you want to do exactly, but is sounds like you don't need
2-way communication between your PC (host) and the CPU device. If this is the
case, dual-port is not the way to go. My suggestion, if you not concerned
about speed or real-time transfer between the host and CPU is to use an RS-232
link. The serial port already exists on the PC. Adding a serial port to your
CPU board is not terribly complicated. Having done it before, I don't remember
all the details, but you only need a serial chip (National 8250 or Intel 8251;
your PC uses one of these, can't remember which...), line drivers (1488/1489),
and interface the puppy right to the CPU. You then need to write a small
"monitor" routine that can be blown into PROM and be bootstrapped at start-up
time of the CPU. All it needs to do is a few simple commands: read the serial
port for incoming data, put the data into selected memory locations, and run
from selected locations. Of course you can get fancier, this is just bare
bone. Hope this helps, Steven.
BTW, I did something similar to this using a home-built 80186 CPU board and PC
as my senior project in 88 (it's still sitting in my closet :-). Used the PC
for software developement, downloaded via RS-232, and ran out of RAM. I think
that Dr. Sarma at U.C. has a copy of my report, if it would help you.
Otherwise, e-mail me with questions!
--
Disclaimer: All spelling and/or grammer in this document are guaranteed to be
correct; any exseptions is the is wurk uv intter-net deemuns.
Mike McManus (mikemc@ncr-fc.FtCollins.ncr.com)
NCR Microelectronics
2001 Danfield Ct. mikemc@ncr-fc@ncr-sd.sandiego.ncr.com, or
Ft. Collins, Colorado mikemc@ncr-fc@ccncsu.colostate.edu
(303) 223-5100 Ext. 360 (they're ugly, but they work!)
Technical Details
Message-ID:
<MIKEMC.90Jan12170158@mustang.ncr-fc.FtCollins.NCR.com>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!ncar!boulder!ccncsu!ncr-fc!mikemcReferences:
<3310@uceng.UC.EDU>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!ncar!boulder!ccncsu!ncr-fc!mikemc From: mikemc@mustang.ncr-fc.FtCollins.NCR.com (Mike McManus) Newsgroups: sci.electronics Subject: Re: Dual-port memory access? Message-ID: <MIKEMC.90Jan12170158@mustang.ncr-fc.FtCollins.NCR.com> Date: 13 Jan 90 00:01:58 GMT References: <3310@uceng.UC.EDU> Sender: news@ncr-fc.FtCollins.NCR.COM Organization: NCR Microelectronic Products, Ft. Collins, CO Lines: 42 In-reply-to: schriste@uceng.UC.EDU's message of 12 Jan 90 02:48:01 GMT