🚀 go-pugleaf

>In article <BzF1nI.z0@world.std.com> gkulosa@world.std.com (Greg A
>Kulosa) writes: 
>>Interactive-C (IC) works by first downloading a 'pseudo-code'
>>interpreter to the 6.270 board.  I believe that this interpreter
>>(which is written in 68HC11 assembler) is about 10K.  This is
>>obviously way too big for the internal memory of the 68HC11 used in
>>the Miniboard design.  Then, you would also download your code
>>produced by IC.  Since the Miniboard has no capability to add external
>>memory, you can't use IC with it.
>
In article <lj4lnkINN2dh@exodus.Eng.Sun.COM>
cmcmanis@pepper.Eng.Sun.COM (Chuck McManis) asks:

>Ok, would it be possible to load the interpreter into EPROM (the
>miniboard does take a variant with 12K eprom. And then run your
>programs out of the EEPROM ? 

There are a couple reasons why this would be hard.  First is that the
pcode program uses some self-modifying code, which would be
problematic for obvious reasons if running out of any type of ROM.
These sections could be recoded either to not use self-modifying
techniques, or to copy themselves into a known RAM area.  (It would be
nice for this to be done anyway so that IC could be used to develop
real ROM-based applications.)

The second thing is that the 12K EPROM version of the 6811 has only
512 bytes of EEPROM.  This isn't really enough to do much of anything
in terms of being a main code space area.

Perhaps if someone wrote a sub-set of the pcode program, say about
500 to 700 bytes long, and then modified the host side of IC to
compile for this subset, the approach would be workable.  


	- Fred