🚀 go-pugleaf

In <1992Nov6.114542.2744@reed.edu> reeder@reed.edu (P. Douglas Reeder) writes:

>In article <Bx9JGp.464@jabba.ess.harris.com> dwilliam@jabba.ess.harris.com (Dave Williams) writes:
>:In article<???> reeder@reed.edu (Doug Reeder) writes:
>:>Functionally, the HC11 is always in single-chip operating mode, so
>:>hardware not part of the EVB cannot be in the memory map.  This means 
>:>you are forever limited to the two 8K blocks of RAM (though you could
>:>replace the 8K ROM with one of your own).
>:
>:   Hummm.  I wouldn't say that - There's quite a few holes in the
>:EVB memory map where you could put all sorts of nifty stuff.

>How? There are no connectors to the address and data busses on the board.
>The B and C ports ara available at connector P1, but only as general I/O
>ports, since connector P1 looks like an HC11 in single-chip mode.

   Uhhhh,  errrr, ummm.  "Whoops."  (Maybe my .sig is appropriate
here, huh?)

   Sorry about that.  I've been switching back and forth between the 
EVBU and the EVB so much that I've gotten them confused.  The EVBU 
has a very similar P1 connector, which *can* be used to add in more
memory-mapped hardware.  Most of the stuff I've added to the EVB 
board has been driven off of I/O signals from the various single-
chip ports.  Oh well.

   Not to mention the fact that I keep hacking on the buffalo ROM
to add in my own custom routines.  I keep thinking it's something
*I* added in.  :-)

-- 
  Dave Williams                                     | I'm lucky if I can
    dwilliam@jabba.ess.harris.com                   | even spell opinion,
      "Huh?  What?  Could you repeat the question?" | much less have them.