6502
/
PLASMA
mirror of https://github.com/dschmenk/PLASMA.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
PLASMA/doc/Version 2.1.md

17 KiB
Raw Permalink Blame History

PLASMA Version 2.11

Welcome to PLASMA: the Grand Unifying Platform for the Apple 1, ][, and ///.

Version 2.11 is a minor update to address the relocating loader for EDASM generated modules with 8 bit fixups. All modules up to now have been generated by PLASM and only use 16 bit fixups. Mostly usefull for future modules built with EDASM. Check out the Assembly Language Toolkit below.

If you already have 2.1 installed, here are the updated files:

PLASMA 2.11 Update

Download the full 2.11 disk image set:

PLASMA 2.11 HD Full System

PLASMA 2.11 800K Full System

PLASMA 2.11 ProDOS Boot & Install

PLASMA 2.1 System Libraries

PLASMA 2.11 Build Tools

PLASMA 2.1 Demos

PLASMA 2.1 TCP/IP network modules

PLASMA 2.11 Apple /// SOS and SANE floating point modules

PLASMA 2.11 Apple /// SOS Mame Boot

PLASMA 2.11 Apple /// Mame hard disk image

PLASMA 2.11 PLFORTH stand-alone boot

PLASMA 2.11 Assembly Language Toolkit

PLASMA now has a ProDOS hard disk install script. Mass storage is the recommended installation that looks like (replacing HARDISK with your volume name of choice) if you want to copy files yourself:

Boot & System Files => /HARDISK/PLASMA/

Build Files => /HARDISK/PLASMA/BLD/

Demo Files => /HARDISK/PLASMA/DEMOS/

Floating Point SANE Files => /HARDISK/PLASMA/SYS

INET Files => /HARDDISK/PLASMA/SYS

Use the System Utilities to copy the floppy images into the above mentioned directories.

Apple 1

The Apple 1 is a very constrained system compared to the ][ and ///. It is required to have the CFFA1 disk adapter installed to provide file storage and a full 32K od RAM. To get the files onto the CF card required the use of CiderPress and they must be placed in one directory. Most PLASMA programs won't work on the Apple 1 due to limited filesystem support, video/graphics capabilities, and lack of audio output. It does, however, make a good place to start when porting PLASMA to a new platform.

Apple ][

To boot directly into PLASMA, you will need to put the system files in the root prefix of the boot device and make sure PLASMA.SYSTEM is the first SYSTEM file in the directory. Otherwise, start PLASMA.SYSTEM from your program launcher of choice. All Apple ][ models with 64K and two floppy drives are supported up to a maxed out IIGS with accelerator and hard drive.

65802/65816 Support

PLASMA can utilize the 16 bit features of the 65802 and 65816 processors to improve performance of the PLASMA VM operation. This is transparent to the programmer/user and doesn't make any additional memory or capabilities available to PLASMA. PLASMA will automatically run the most optimal VM for your configuration.

Apple ///

The Apple /// gets the environment it always wanted: The ability to navigate the filesystem with a command line interface. The Apple /// always boots from the floppy drive, even if a hard disk is installed. PLASMA2-A3MAME.PO is an Apple 3 bootable disk containing the SOS.DRIVER configured for the Apple 3 Ready-To-Run Mame environment. apple3.hd is the pre-installed PLASMA hard disk image set up for Apple 3 Ready-to-Run. For a physical Apple 3, the PLASMA2-FPSOS.PO floppy should be updated with the SOS.DRIVER configured for the machine. Once booted, type S /HARDISK/PLASMA (or your install directory of choice) to change to, and set, the system directory. This can be automated by creating an AUTORUN file on the boot floppy with the above command in it.

PLASMA Command Line Shell

PLASMA incorporates a very basic command line shell to facilitate navigating the filesystem and executing both SYSTEM/SOS programs and PLASMA modules. It has a few built-in commands:

Command Operation
C [PREFIX] Catalog prefix
P <PREFIX> change to Prefix
/ change to parent prefix
V show online Volumes
S <PREFIX> set System prefix*
+SOS <SOS.INTERP> [PREFIX] launch SOS interpreter*
-<SYSTEM PROGRAM> [PARAMS] launch SYSTEM program**
+<PLASMA MODULE> [PARAMS] exec PLASMA module 
[Optional parameters]
<Required parameters>
* Apple /// only
** Apple ][ only

The shell is very brief with error messages. It is meant solely as a way to run programs that accept command line parameters and take up as little memory as possible. It does, however, provide a rich runtime for PLASMA modules.

Included Modules

PLASMA comes with many library modules used by the tools, demos and sample code. The PLASMA system volume must remain in place for the duration of PLASMAs run otherwise it won't be able to find CMD or the system libraries. Probably the most useful included module is the editor. It is used for editing PLASMA source file, assembly source files, or any text file. Execute it with:

+ED [TEXT FILE] [GOTO LINE NUMBER]

The file manipulation utilities to copy, delete, rename, create directories, and change file type and aux type remove the need for external programs to do the same. PLASMA can now be installed with the tools included on the PLASMA2-SYS boot floppy. They are:

+COPY [-R] <SRCPATH>+ <DSTPATH>
+DEL [-R] <FILEPATH>
+REN <FILENAME> <NEWNAME>
+NEWDIR <NEWDIRECTORY>
+TYPE <FILENAME> [NEWTYPE [NEWAUX]]
+CAT [-R] <FILEPATH]

The -R option will operate on the directories recursively. Wildcard filenames can be specified with '*' matching zero or more characters, and '?' matching any character. When copying files to the current directory, = can be used as a shortcut.

Compiler Modules

The build disk includes sample source, include files for the system modules, and the PLASMA compiler+optimizer modules. The compiler is invoked with:

+PLASM [-[W][O[2]] <SOURCE FILE> [OUTPUT FILE]

Compiler warnings are enabled with -W. The optional optimizer is enabled with -O and extra optimizations are enabled with -O2. The source code for a few sample programs are included. The big one, RPNCALC.PLA, is the sample RPN calculator that uses many of PLASMA's advanced features. The self-hosted compiler is the same compiler as the cross-compiler, just transcribed from C to PLASMA (yes, the self-hosted PLASMA compiler is written in PLASMA). It requires patience when compiling: it is a fairly large and extensive program.

Assembly Toolkit

New for 2.11 is the assembly language toolkit. The PLASMA module was originally architected around the REL file generated by the ProDOS toolkit assembler, EDASM. This minor update fixes the PLASMA relocating loader to handle 8 bit fixups. PLASM generated modules only use 16 bit fixups, so not an issue for existing modules. Download the toolkit that includes the ProDOS EDASM assembler and sample code. Also the 2.11 updates (if you have 2.1 already installed) here:

PLASMA 2.11 Assembly Language Toolkit

PLASMA 2.11 Update

FORTH Module

New for version 2.1 is a FORTH language module capable of interpreting script files and interactive programming. Further documentation here: https://github.com/dschmenk/PLASMA/blob/master/doc/PLFORTH.md. Samples scripts are in /HARDISK/BLD/SCRIPTS

Demos

There are some demo programs included for your perusal. Check out ROGUE for some diversion. You can find the documentation here: https://github.com/dschmenk/PLASMA/blob/master/doc/Rogue%20Instructions.md. A music sequencer to play through a MockingBoard if it is detected, or the built-in speaker if not. A minimal Web server if you have an Uthernet2 card (required). Try SPIDERSfor some hires shoot'em-up action. Bug reports appreciated.

Source Code

Most sample source code is included from the project. They build without alteration and should be a good starting point for further explorations. The header files for the included library modules are in the INC directory.

Video Playlist

There is a YouTube playlist created for learning PLASMA.

Issues

  • All the modules and runtime are written mostly in PLASMA; the compiler and editor as well. This means that there may be some startup delay as the PLASMA module loader reads in the module dependencies and performs dynamic linking. But a 1 MHz, 8 bit CPU interpreting bytecodes is never going to match a modern computer. As noted earlier, an accelerator and mass storage are your (and PLASMA's) friend.

  • All the project modules are included. They have been lightly tested.

  • The Apple /// may not always report errors properly or at all.

  • The documentation is sparse and incomplete. Yep, could use your help...

Changes in PLASMA for 2.11 Release

  1. Minor update to load modules generated by EDASM with 8 bit fixups

Changes in PLASMA for 2.1 Release

  1. Lots of small bug fixes in floating point, file copy and graphics libraries

  2. MULT opcode speedup improvements

  3. Overhaul 65802/65814 VM for better speed and compatibility with PLFORTH compilation

  4. Many Apple /// improvements and bug fixes

  5. Low memory fixes and tests

  6. FORTH language support as a PLASMA module. Full accessabilit to PLASMA modules and libraries

  7. Install script for ProDOS mass storage

Changes in PLASMA for 2.0 Release

  1. Fix command line buffer overflow

  2. Use VBlank to blink editor cursor so not CPU speed dependent

  3. Add = for +COPY current destination

  4. Add //c support for DGRLIB and GRLIB wait-for-VBlank routines

Changes in PLASMA for 2.0 Beta

  1. Compilers allows for including self imported defines

  2. Compilers fixed for local constants

  3. Floating point string formatting fixes and improvements

  4. Fiber library exports number of active fibers

Changes in PLASMA for 2.0 Alpha 2

  1. Self hosted compiler fixes for invalid array size constants

  2. Ensure IDs in self hosted compiler are 31 characters significant

  3. Fix bug COPY file parsing and move common routine into MATCHFILES

Changes in PLASMA for 2.0 Alpha 1

  1. Improved entry/exit for 128K Apple IIe //c

  2. Improved entry for Apple ///

  3. Improved entry and function calls for 16 bit VM

Changes in PLASMA for 2.0 DP 4

  1. Improved editor auto-indenting

  2. Compiler fix for terneray operator precedence

  3. Machine check for HGR library

Changes in PLASMA for 2.0 DP 3

  1. File manipulation utilities fixed for Apple /// SOS vs ProDOS differences

  2. More optimizations for HiRes graphics libraries

  3. Spiders From Mars hires demo game

Changes in PLASMA for 2.0 DP 2

  1. Many file manipulaition utilities (COPY, REName, NEWDIRectory, DELete, CATalog, TYPE)

  2. New and updated libraries for lo-res. double lo-res and hi-res graphics w/ sprites

  3. 32 bit integer library for those times when 16 bits just isn't enough

  4. Apple /// improvements to other SOS.INTERP launching with SOS utility

  5. Apple /// JIT VM for speed and non JIT version to free up global memory

  6. Editor improvements

  7. A couple small compiler optimizations

  8. Needed to break out TCP/IP modules into seperate floppy image

  9. Library changes require full install

Changes in PLASMA for 2.0 DP 1z

  1. Many fixes for the value zero - especially in 65802/65816 divide routine

Changes in PLASMA for 2.0 DP 1 E+C

  1. Greatly improved code editor and additional compiler stats

Changes in PLASMA for 2.0 DP 1a

  1. Fix interaction with JIT compiler and module load/unload

Changes in PLASMA for 2.0 DP 1

  1. Expanded bytecode for more efficient size/performance of programs

  2. Just-In-Time Compiler for native code performance (6502 and 65816) for frequently called routines

  3. Automatically identify and run most optimal VM for configuration

Changes in PLASMA for 1.2

  1. Add TFTPD TFTP server

  2. Fix Uthernet 1 driver

  3. Add mouse module

  4. Fix IRQ issues for interrupt driven mouse driver

Changes in PLASMA for 1.1

  1. All known bugs are fixed

  2. PLASM compiler received a little performance boost with an assembly language helper for ID/keyword lexical scanner

Changes in PLASMA for 1.0

If you have been programming in PLASMA before, the 1.0 version has some major and minor changes that you should be aware of:

  1. Case is no longer significant. Imported symbols were always upper case. Now, all symbols are treated as if they were upper case. You may find that some symbols clash with previously defined symbols of different case. Hey, we didn't need lower case in 1977 and we don't need it now. You kids, get off my lawn!

  2. Modules are now first class citizens. Translation: importing a module adds a symbol with the module name. You can simply refer to a module's address with it's name. This is how a module's API table is accessed (instead of adding a variable of the same name in the IMPORT section).

  3. Bytecode changes means previously compiled modules will crash. Rebuild.

  4. BYTE and WORD have aliases that may improve readability of the code. CHAR (character) and RES (reserve) are synonyms for BYTE. VAR (variable) is a synonym for WORD. These aliases add no functionality. They are simply syntactic sugar to add context to the source code, but may cause problems if you've previously used the same names for identifiers.

  5. When declaring variables, a base size can come after the type, and an array size can folllow the identifier. For instance:

res[10] a, b, c

will reserve three variables of 10 bytes each. Additionally:

res[10] v[5], w[3]

will reserve a total of 80 bytes (10 * 5 + 10 * 3). This would be useful when combined with a structure definition. One could:

res[t_record] patients[20]

to reserve an array of 20 patient records.

  1. Ternary operator. Just like C and descendants, ?? and :: allow for an if-then-else inside an expression:
puts(truth == TRUE ?? "TRUE" :: "FALSE")
  1. Multiple value assignements. Multiple values can be returned from functions and listed on variable assignments:
def func#3 // Return 3 values
  return 10, 20, 30
end

a, b, c = 1, 2, 3
c, d, f = func()
x, y = y, x // Swap x and y
  1. DROP allows for explicit dropping of values. In the above func() example, if the middle value was the only one desired, the others can be ignored with:
drop, h, drop = func()
  1. The compiler tracks parameter and return counts for functions. If the above func() were used without assigning all the return values, they would be dropped:
a = func() // Two values silently dropped

To generate compiler warning for this issue, and a few others, use the -W option when compiling.

  1. Lambda (Anonymous) Functions. The ability to code a quick function in-line can be very powerful when used properly. Look here, https://en.wikipedia.org/wiki/Anonymous_function, for more information.

  2. SANE (Standard Apple Numerics Environment) Floating Point Library. An extensive library (two, actually) of extended floating point (80 bit IEEE precision) functionality is suported. A wrapper library has been written to greatly simplify the interface to SANE. Look at the RPNCALC.PLA source code as an example.

  3. Library Documentation. Preliminary documentation is available on the Wiki: https://github.com/dschmenk/PLASMA/wiki

  4. Significant effort has gone into VM tuning and speeding up module loading/dynamic linking.

  5. The VM zero page usage has changed. If you write assembly language routines, you will need to rebuild.

Thanks

I wish to thank the people who have contributed the the PLASMA project. They have greatly improved the development of the language and documentation:

  • Martin Haye: PLASMA programmer extraordinaire. Mr. Lawless Legends has requested many of the crucial features that set PLASMA apart.
  • Steve F (ZornsLemma): Has taken the optimizer to new levels and his work on porting PLASMA to the Beeb are amazing: http://stardot.org.uk/forums/viewtopic.php?f=55&t=12306&sid=5a503c593f0698ebc31e590ac61b09fc
  • Peter Ferrie: Assembly optimizer extraordinaire. He has made significant improvements into the code footprint in PLASMA so all the functionality can exist in just a few bytes.
  • David Schmidt (DaveX): His help in documentation have made it much more accessible and professional. Of course any errors are all his. Just kidding, they're mine ;-)
  • Andy Werner (6502.org): Catching the grammatical errors that I ain't no good at.
  • John Brooks: Apple II Guru par excellence. His insights got 10% performance increase out of the VM.

Dave Schmenk http://schmenk.is-a-geek.com