Recent changes to feature-requests

Add direct flash memory access opcode(s).

2005-10-13T17:04:09Z

Similar to the internal EEPROM opcodes, we will need
ways to modify at least part of the internal flash
memory, say the top 4 KB of the 16F877(A). Basically
this calls for a read and a write instruction. Apart from
these, the run routine from internal EEPROM call should
be extended to also allow running code from the internal
flash memory in the same way, and extend it in such a
way that assembly level routines can be called as well.
Note that the latter would require storing 14-bit values,
and the former only needs 8-bit values. Basically most
of this could be controlled using the 16-bit mode field,
but this might not be transparant to the user.

Add graphical features to graphical LCD.

2005-10-13T01:43:24Z

Currently the graphical LCD is used in 44780
compatibility mode, which allows only text and user
defined graphics at a 6-point font width. However, the
Drake 3 LCD display has a large number of graphical
capabilities, and can be used as additional memory. A
way needs to be devised that allows easy and fast
access to this memory. There are a number of ways this
can be accomplished:

1) Define loadgfx and storegfx instructions, that load
and store data at a speficied address.
2) Use the local cursor pointer of the LCD display, and
create a way to move this to a different location. The
regular print commands could then be used to write
things to the LCD, though new instructions should be
introduced for reading.
3) Even more advanced would be to place the LCD in a
special writing mode, so that large amounts of data can
be written to it with the least amount of accesses.
4) It could be implemented similarly to the TV and
alphanumeric LCDs, by extending the prc/prd commands.
5) Graphics commands could be written around the
"graphics" bytecode, which allows for drawing
lines/circles et cetera. This would be combined with
implementation of the plot command.
6) A combination of the above.

Write local assembler.

2005-10-13T01:38:28Z

It would be nice if the system had a cartridge that
would contain a text editor that could edit text(s)
stored on that same cartridge, which could then be
assembled to a fixed location which could be executed.
Basically this would involve:

1) creating a text editor (e.g. a line editor, of which
the lines are stored in a linked list)
2) creating a file system to store the text files on
the cartridge (though it can start with allowing only
one text file)
3) creating an assembler that can assemble the text
file into bytecode and store it at a fixed location
4) creating a method to select between the text editor,
the assembler and running the assembled code.