That was what I thought (sram or fram) so I used parallel connected sram. I
want to hook up a 4 meg flash rom for storage of source code screens for
application storage. The system is configured with three eight bit latches
for the address so it can access 16777216 bytes of whatever. You're exactly
right about forth not caring about where its getting its data from though;
its all in the inner interpreter. I think that I'm porting all of this for
the 100 mhz scenix part next though. That's what they need at work. I'm
really stoked to see what this already spunky os looks like going 20 times
faster!

-----Original Message-----
From: Andy Kunz <montana@FAST.NET>
To: PICLIST@MITVMA.MIT.EDU <PICLIST@MITVMA.MIT.EDU>
Date: Saturday, February 06, 1999 3:59 PM
Subject: Re: Forth for the PIC


>At 07:24 PM 2/4/99 -0700, you wrote:
>>I abandoned that idea immediately because of speed constraints. You could
do
>>that; you just wouldnt like it too much. It would just be no faster than a
>>basic stamp. Thanks for the whacking attempt though.
>
>You could go pretty quick if you used FRAM or SRAM instead of EEPROM, or if
>you used the PIC at high speed (20MHz).
>
>All depends on what you're after.  The nice part about Forth is that you
>can make the memory access mechanism totally invisible - the program would
>never have to know it's running on a serial/external vs. a internal memory.
>
>Andy
>
>   \-----------------/
>    \     /---\     /
>     \    |   |    /          Andy Kunz
>      \   /---\   /           Montana Design
>/---------+   +---------\     http://www.montanadesign.com
>| /  |----|___|----|  \ |
>\/___|      *      |___\/     Go fast, turn right,
>                               and keep the wet side down!
>