home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
rtsi.com
/
2014.01.www.rtsi.com.tar
/
www.rtsi.com
/
UNIFLEX
/
UNIFLEX
/
UniFLEX_Common.tar.Z
/
UniFLEX_Common.tar
/
config.notes
next >
Wrap
Text File
|
1982-10-10
|
3KB
|
52 lines
These notes describe the major changes for the new configurable
(Version X.08 and greater) version on UniFLEX. These changes
affect:
1. The UniBUG ROM
2. The disk format programs
3. The limits and restrictions on UniFLEX itself.
UniBUG ROM.
Version X.08 requires a new UniBUG ROM. This ROM must provide
at least the following facilities, in addition to any existing
facilities provided by the ROM.
1. A set of vectors, starting at $F800, which allow the system
access to the ROM low-level terminal I/O routines. These
vectors should be structured as follows:
org $F800
fdb pdata Print a null terminated string pointed to by (X)
fdb hexbyt Print a single hex digit in (A)
fdb outsp Print a single space character
fdb inch Read a single character (& echo) from terminal in (A)
2. The UniBUG banner (printed when the ROM is entered) now has the
following (informal) convention:
UniBUG BOOT ROM (cpu/disk/term)
Where "cpu", "disk" and "term" describe the hardware supported by
the ROM. For example:
UniBUG BOOT ROM (MPU/DMF3/S4)
would describe a ROM for the SWTPc (S+) MPU system with a DMF3
disk controller and MP-S4 I/O cards.
Disk format programs and bootstrap loaders.
Along with version X.08 of UniFLEX, a new set of disk formatting
programs have been developed. These programs take the form of a
common core which drives the entire formatting process, specific code
to perform the "format drive" function which differs for each device
type being formatted, the bootstrap loader for the device and
the identification (info field) for the format program.
The bootstrap loader now has some special constraints:
1. The loader must be self relocating to an address which is
normally mapped in by the ROM but which is not used directly
by UniFLEX. The ROM will normally load the bootstrap at
logical address $B000. Currently, all bootstrap loaders
will relocate to $B800.
2. The bootstrap must ensure that any memory addresses used in
the file loading process are actually mapped in. Currently
this means that the bootstrap in most cases must map in
the page at $A000. UniFLEX is allowed to load in the
memory between $5000 and $B7FF.
3. The bootstrap must use the vectors provided by the UniFLEX
file for setting the "boot time" in UniFLEX. This is done
by setting the time [$5002]. Other vectors exist at
$5000-$5006 which are used by UniFLEX and "install".