diff --git a/Doc/ChangeLog.txt b/Doc/ChangeLog.txt index 040b26c8..7e3f7e77 100644 --- a/Doc/ChangeLog.txt +++ b/Doc/ChangeLog.txt @@ -2,6 +2,9 @@ Version 3.4 ----------- NOTE: Changes require HBIOS/CBIOS/Apps sync, version bump to 3.4 to ensure integrity - WBW: Device type number moved from upper nibble to full byte +- A?C: Support for EP ITX-Mini Z180 Platform +- M?R: Significant improvement in User Guide document + Version 3.3 ----------- diff --git a/Doc/RomWBW Applications.pdf b/Doc/RomWBW Applications.pdf index adc44907..76bc9953 100644 Binary files a/Doc/RomWBW Applications.pdf and b/Doc/RomWBW Applications.pdf differ diff --git a/Doc/RomWBW Disk Catalog.pdf b/Doc/RomWBW Disk Catalog.pdf index 2decaa26..0e1c8ac6 100644 Binary files a/Doc/RomWBW Disk Catalog.pdf and b/Doc/RomWBW Disk Catalog.pdf differ diff --git a/Doc/RomWBW Errata.pdf b/Doc/RomWBW Errata.pdf index 784bb17f..60a3dc49 100644 Binary files a/Doc/RomWBW Errata.pdf and b/Doc/RomWBW Errata.pdf differ diff --git a/Doc/RomWBW ROM Applications.pdf b/Doc/RomWBW ROM Applications.pdf index fa902c90..115d2b47 100644 Binary files a/Doc/RomWBW ROM Applications.pdf and b/Doc/RomWBW ROM Applications.pdf differ diff --git a/Doc/RomWBW System Guide.pdf b/Doc/RomWBW System Guide.pdf index 049484d8..716a6a19 100644 Binary files a/Doc/RomWBW System Guide.pdf and b/Doc/RomWBW System Guide.pdf differ diff --git a/Doc/RomWBW User Guide.pdf b/Doc/RomWBW User Guide.pdf index d79aa0d3..dc5d3ed6 100644 Binary files a/Doc/RomWBW User Guide.pdf and b/Doc/RomWBW User Guide.pdf differ diff --git a/ReadMe.md b/ReadMe.md index 33619747..8d169dc7 100644 --- a/ReadMe.md +++ b/ReadMe.md @@ -3,7 +3,7 @@ **RomWBW ReadMe** \ Version 3.4 \ Wayne Warthen ([wwarthen@gmail.com](mailto:wwarthen@gmail.com)) \ -31 Oct 2023 +27 Nov 2023 # Overview diff --git a/ReadMe.txt b/ReadMe.txt index 9c4daa71..26cb1bba 100644 --- a/ReadMe.txt +++ b/ReadMe.txt @@ -1,6 +1,6 @@ RomWBW ReadMe Wayne Warthen (wwarthen@gmail.com) -31 Oct 2023 +27 Nov 2023 diff --git a/Source/Doc/UserGuide.md b/Source/Doc/UserGuide.md index b863cf57..5715524a 100644 --- a/Source/Doc/UserGuide.md +++ b/Source/Doc/UserGuide.md @@ -11,12 +11,12 @@ companion documents you should refer to as appropriate: of RomWBW. It includes a reference for the RomWBW HBIOS API functions. -* $doc_apps$ is a reference for the OS-hosted proprietary command - line applications that were created to enhance RomWBW. - * $doc_romapps$ is a reference for the ROM-hosted applications provided with RomWBW including the monitor, programming languages, etc. +* $doc_apps$ is a reference for the OS-hosted proprietary command + line applications that were created to enhance RomWBW. + * $doc_catalog$ is a reference for the contents of the disk images provided with RomWBW. It is somewhat out of date at this time. @@ -56,11 +56,14 @@ produced by these developer communities: * [retro-comp](https://groups.google.com/forum/#!forum/retro-comp) * [Small Computer Central](https://smallcomputercentral.com/) +A complete list of the currently supported platforms is found in the +[Installation] section. + General features include: * Z80 Family CPUs including Z80, Z180, and Z280 * Banked memory services for several banking designs -* Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, Zip, Iomega +* Disk drivers for RAM, ROM, Floppy, IDE ATA/ATAPI, CF, SD, USB, Zip, Iomega * Serial drivers including UART (16550-like), ASCI, ACIA, SIO * Video drivers including TMS9918, SY6545, MOS8563, HD6445 * Keyboard (PS/2) drivers via VT8242 or PPI interfaces @@ -77,12 +80,12 @@ ROM firmware itself: * ROM BASIC (Nascom BASIC and Tasty BASIC) * ROM Forth -A dynamic disk drive letter assignment mechanism allows mapping -operating system drive letters to any available disk media. -Additionally, mass storage devices (IDE Disk, CF Card, SD Card) support -the use of multiple slices (up to 256 per device). Each slice contains -a complete CP/M filesystem and can be mapped independently to any -drive letter. This overcomes the inherent size limitations in legacy +A dynamic disk drive letter assignment mechanism allows mapping +operating system drive letters to any available disk media. +Additionally, mass storage devices (IDE Disk, CF Card, SD Card, etc.) +support the use of multiple slices (up to 256 per device). Each slice +contains a complete CP/M filesystem and can be mapped independently to +any drive letter. This overcomes the inherent size limitations in legacy OSes and allows up to 2GB of accessible storage on a single device. The pre-built ROM firmware images are generally suitable for most @@ -104,7 +107,7 @@ By design, RomWBW isolates all of the hardware specific functions in the ROM chip itself. The ROM provides a hardware abstraction layer such that all of the operating systems and applications on a disk will run on any RomWBW-based system. To put it simply, you can take -a disk (or CF/SD Card) and move it between systems transparently. +a disk (or CF/SD/USB Card) and move it between systems transparently. A tool is provided that allows you to access a FAT-12/16/32 filesystem. The FAT filesystem may be coresident on the same disk media as RomWBW @@ -138,12 +141,12 @@ a set of directories. Each of these directories has its own ReadMe.txt file describing the contents in detail. In summary, these directories are: -| **Directory** | **Description** | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| **Binary** | The final output files of the build process are placed here. Most importantly, the ROM images with the file names ending in ".rom" and disk images ending in .img. | -| **Doc** | Contains various detailed documentation, both RomWBW specifically as well as the operating systems and applications. | -| **Source** | Contains the source code files used to build the software and ROM images. | -| **Tools** | Contains the programs that are used by the build process or that may be useful in setting up your system. | +| **Directory** | **Description** | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| **Binary** | The final output files of the build process are placed here. Most importantly, the ROM images with the file names ending in ".rom" and disk images ending in .img. | +| **Doc** | Contains various detailed documentation, both RomWBW specifically as well as the operating systems and applications. | +| **Source** | Contains the source code files used to build the software and ROM images. | +| **Tools** | Contains the programs that are used by the build process or that may be useful in setting up your system. | ## Installation @@ -153,6 +156,12 @@ distribution. Subsequently, you can write disk images on your disk drives (IDE disk, CF Card, SD Card, etc.) which then provides even more functionality. +**NOTE:** The pre-built ROM images distributed with RomWBW are based on +the default system configurations as determined by the hardware +provider/designer. This document does not provide hardware +construction or configuration information. Please contact your hardware +provider/designer as needed. + The pre-built ROM images will automatically detect and support typical devices for their corresponding platform including serial ports, video adapters, on-board disk interfaces, and PropIO/ParPortProp boards @@ -165,49 +174,61 @@ Depending on how you got your hardware, you may have already been provided with a pre-programmed ROM chip. If so, use that initially. Otherwise, you will need to use a ROM programmer to initially program your ROM chip. Please refer to the documentation that came with your ROM -programmer for more information. Once you have a running RomWBW system, -you can generally update your ROM to a newer version in-situ with the -included ROM Flashing tool (Will Sowerbutts' FLASH application) as -described in the Upgrading section of this document. +programmer for more information. The Binary directory of the distribution contains the pre-built ROM and -disk images. The ROM image files all end in ".rom". Based on the table -below, **carefully** pick the appropriate ROM image for your hardware. - -| **Description** | **Bus** | **ROM Image File** | **Baud Rate** | -|----------------------------------------------------------------|---------|--------------------|--------------:| -| [RetroBrew Z80 SBC]^1^ | ECB | SBC_std.rom | 38400 | -| [RetroBrew Z80 SimH]^1^ | - | SBC_simh.rom | 38400 | -| [RetroBrew N8 Z180 SBC]^1^ (date code >= 2312) | ECB | N8_std.rom | 38400 | -| [Zeta Z80 SBC]^2^, ParPortProp | - | ZETA_std.rom | 38400 | -| [Zeta V2 Z80 SBC]^2^, ParPortProp | - | ZETA2_std.rom | 38400 | -| [Mark IV Z180 SBC]^3^ | ECB | MK4_std.rom | 38400 | -| [RCBus Z80 CPU Module]^4^, 512K RAM/ROM | RCBus | RCZ80_std.rom | 115200 | -| [RCBus Z80 CPU Module]^4^, 512K RAM/ROM, KIO | RCBus | RCZ80_kio.rom | 115200 | -| [RCBus Z180 CPU Module]^4^ w/ external banking | RCBus | RCZ180_ext.rom | 115200 | -| [RCBus Z180 CPU Module]^4^ w/ native banking | RCBus | RCZ180_nat.rom | 115200 | -| [RCBus Z280 CPU Module]^4^ w/ external banking | RCBus | RCZ180_ext.rom | 115200 | -| [RCBus Z280 CPU Module]^4^ w/ native banking | RCBus | RCZ180_nat.rom | 115200 | -| [Easy Z80 SBC]^2^ | RCBus | RCZ80_easy.rom | 115200 | -| [Tiny Z80 SBC]^2^ | RCBus | RCZ80_tiny.rom | 115200 | -| [Z80-512K CPU/RAM/ROM Module]^2^ | RCBus | RCZ80_skz.rom | 115200 | -| [Small Computer SC126 Z180 SBC]^5^ | BP80 | SCZ180_sc126.rom | 115200 | -| [Small Computer SC130 Z180 SBC]^5^ | RCBus | SCZ180_sc130.rom | 115200 | -| [Small Computer SC131 Z180 Pocket Computer]^5^ | - | SCZ180_sc131.rom | 115200 | -| [Small Computer SC140 Z180 CPU Module]^5^ | Z50 | SCZ180_sc140.rom | 115200 | -| [Small Computer SC503 Z180 CPU Module]^5^ | Z50 | SCZ180_sc503.rom | 115200 | -| [Small Computer SC700 Z180 CPU Module]^5^ | RCBus | SCZ180_sc700.rom | 115200 | -| [Dyno Z180 SBC]^6^ | Dyno | DYNO_std.rom | 38400 | -| [Nhyodyne Z80 MBC]^1^ | MBC | MBC_std.rom | 38400 | -| [Rhyophyre Z180 SBC]^1^ | - | RPH_std.rom | 38400 | -| [Z80 ZRC CPU Module]^7^ | RCBus | RCZ80_zrc.rom | 115200 | -| [Z180 Z1RCC CPU Module]^7^ | RCBus | RCZ180_z1rcc.rom | 115200 | -| [Z280 ZZRCC CPU Module]^7^ | RCBus | RCZ280_zzrc.rom | 115200 | -| [Z280 ZZ80MB SBC]^7^ | RCBus | RCZ280_zz80mb.rom | 115200 | -| [Z80-Retro SBC]^8^ | - | Z80RETRO_std.rom | 38400 | -| [S100 Computers Z180]^9^ | S100 | S100_std.rom | 38400 | -| [Duodyne Z80 System]^1^ | Duo | DUO_std.rom | 38400 | -| [Heath H8 Z80 System]^10^ | H8 | HEATH_std.rom | 115200 | +disk images. Refer to [Supported Platforms] below to identify the +correct ROM image for your system. + +Once you have a running RomWBW system, you can generally update your ROM +to a newer version in-situ with the included ROM Flashing tool (Will +Sowerbutts' FLASH application) as described in the [Upgrading] chapter +of this document. + +## Supported Platforms + +The table below summarizes the hardware platforms currently supported +by RomWBW along with the standard pre-built ROM image(s). RomWBW does +allow for the creation of ROM images with custom configurations. This +is discussed in [Customizing RomWBW]. + +| **Description** | **Bus** | **ROM Image File** | **Baud Rate** | +|----------------------------------------------------------------|---------|-----------------------|--------------:| +| [RetroBrew Z80 SBC]^1^ | ECB | SBC_std.rom | 38400 | +| [RetroBrew Z80 SimH]^1^ | - | SBC_simh.rom | 38400 | +| [RetroBrew N8 Z180 SBC]^1^ (date code >= 2312) | ECB | N8_std.rom | 38400 | +| [Zeta Z80 SBC]^2^, ParPortProp | - | ZETA_std.rom | 38400 | +| [Zeta V2 Z80 SBC]^2^, ParPortProp | - | ZETA2_std.rom | 38400 | +| [Mark IV Z180 SBC]^3^ | ECB | MK4_std.rom | 38400 | +| [RCBus Z80 CPU Module]^4^, 512K RAM/ROM | RCBus | RCZ80_std.rom | 115200 | +| [RCBus Z80 CPU Module]^4^, 512K RAM/ROM, KIO | RCBus | RCZ80_kio.rom | 115200 | +| [RCBus Z180 CPU Module]^4^ w/ external banking | RCBus | RCZ180_ext.rom | 115200 | +| [RCBus Z180 CPU Module]^4^ w/ native banking | RCBus | RCZ180_nat.rom | 115200 | +| [RCBus Z280 CPU Module]^4^ w/ external banking | RCBus | RCZ180_ext.rom | 115200 | +| [RCBus Z280 CPU Module]^4^ w/ native banking | RCBus | RCZ180_nat.rom | 115200 | +| [Easy Z80 SBC]^2^ | RCBus | RCZ80_easy.rom | 115200 | +| [Tiny Z80 SBC]^2^ | RCBus | RCZ80_tiny.rom | 115200 | +| [Z80-512K CPU/RAM/ROM Module]^2^ | RCBus | RCZ80_skz.rom | 115200 | +| [Small Computer SC126 Z180 SBC]^5^ | BP80 | SCZ180_sc126.rom | 115200 | +| [Small Computer SC130 Z180 SBC]^5^ | RCBus | SCZ180_sc130.rom | 115200 | +| [Small Computer SC131 Z180 Pocket Computer]^5^ | - | SCZ180_sc131.rom | 115200 | +| [Small Computer SC140 Z180 CPU Module]^5^ | Z50 | SCZ180_sc140.rom | 115200 | +| [Small Computer SC503 Z180 CPU Module]^5^ | Z50 | SCZ180_sc503.rom | 115200 | +| [Small Computer SC700 Z180 CPU Module]^5^ | RCBus | SCZ180_sc700.rom | 115200 | +| [Dyno Z180 SBC]^6^ | Dyno | DYNO_std.rom | 38400 | +| [Nhyodyne Z80 MBC]^1^ | MBC | MBC_std.rom | 38400 | +| [Rhyophyre Z180 SBC]^1^ | - | RPH_std.rom | 38400 | +| [Z80 ZRC CPU Module]^7^ | RCBus | RCZ80_zrc.rom | 115200 | +| [Z80 ZRC CPU Module]^7^ ROMless | RCBus | RCZ80_zrc_ram.rom | 115200 | +| [Z180 Z1RCC CPU Module]^7^ | RCBus | RCZ180_z1rcc.rom | 115200 | +| [Z280 ZZRCC CPU Module]^7^ | RCBus | RCZ280_zzrcc.rom | 115200 | +| [Z280 ZZRCC CPU Module]^7^ ROMless | RCBus | RCZ280_zzrcc_ram.rom | 115200 | +| [Z280 ZZ80MB SBC]^7^ | RCBus | RCZ280_zz80mb.rom | 115200 | +| [Z80-Retro SBC]^8^ | - | Z80RETRO_std.rom | 38400 | +| [S100 Computers Z180]^9^ | S100 | S100_std.rom | 57600 | +| [Duodyne Z80 System]^1^ | Duo | DUO_std.rom | 38400 | +| [Heath H8 Z80 System]^10^ | H8 | HEATH_std.rom | 115200 | +| [EP Mini-ITX Z180]^11^ | RCBus? | EPITX_std.rom | 115200 | | ^1^Designed by Andrew Lynch | ^2^Designed by Sergey Kiselev @@ -219,6 +240,7 @@ below, **carefully** pick the appropriate ROM image for your hardware. | ^8^Designed by Peter Wilson | ^9^Designed by John Monahan | ^10^Designed by Les Bird +| ^11^Designed by Alan Cox RCBus refers to Spencer Owen's RC2014 bus specification and derivatives including RC26, RC40, RC80, and BP80. @@ -246,8 +268,8 @@ of the ROM chip (address 0). Most of the pre-built images are program the image into the first 512KB of the ROM for now. Initially, don't worry about trying to write a disk image to any disk -(or CF/SD) devices you have. This will be covered later. You will be -able to boot and check out your system with just the ROM. +(or CF/SD/USB) devices you have. This will be covered later. You will +be able to boot and check out your system with just the ROM. Connect a serial terminal or computer with terminal emulation software to the primary serial port of your CPU board. You may need to refer to @@ -331,7 +353,8 @@ with the system. At the Boot Loader prompt, you can type `H ` for help. You can type `L ` to list the available built-in ROM applications. If your terminal supports ANSI escape sequences, you can try the -'G' command to play a simple on-screen game. +'P' command to play a simple on-screen game. Instructions for the +game are found in $doc_romapps$. If all of this seems fine, your ROM has been successfully programmed. See the [Boot Loader Operation] section of this document for further @@ -359,7 +382,7 @@ example, the platform is the RCBus running a configuration named There are 0 memory wait states and 1 I/O wait state. Z80 interrupt mode 2 is active and the bank memory manager is type "Z2" which is standard for RCBus. The system has 512KB of ROM total and 512KB of RAM total. -Finally, a verification of the checksum of the critical ROM banks is +Finally, a verification of the checksums of the critical ROM banks is shown (all 4 should be 00). RomWBW attempts to detect the running configuration of the @@ -474,7 +497,8 @@ system supports up to two drives, but there is only one actual drive attached. A unit number is assigned to all available devices regardless of whether they have actual media installed at boot time. -Note that Character Unit 0 is normally the initial system console. +Note that Character Unit 0 is the initial system console unless modified +in a customized ROM image. If your system has an RTC/NVRAM device, it will not be listed in the unit summary table. Since only a single RTC/NVRAM device can exist in @@ -490,7 +514,9 @@ select and launch a desired application or operating system. It also has the ability to configure some aspects of system operation. After starting your system, following the hardware initialization, you -will see the RomWBW Boot Loader prompt. Below is an example: +will see the RomWBW Boot Loader prompt. Below is an example. Note +that the text preceding "Boot Loader" will vary and identifies your +specific system and configuration. ``` Mark IV [MK4_wbw] Boot Loader @@ -573,12 +599,19 @@ prompt: | Play | A simple video game (requires ANSI terminal emulation) | | Network Boot | Boot system via Wiznet MT011 device | | Flash Update | Upload and flash a new ROMWBW image using xmodem | +| User App | User written application placeholder | + +The User App is provided as a way to access a custom written +ROM module. In the pre-built ROMs, selecting User App will just +return to the Boot Loader menu. If you are interested in creating a +custom application to run here, review the "usrrom.asm" file in the +Source/HBIOS folder of the distribution. Each of the ROM Applications is documented in $doc_romapps$. Some of the applications (such as BASIC) also have their own independent manual in the Doc directory of the distribution. The OSes included in the ROM (CP/M 2.2 & Z-System) are described in the Operating Systems -section of this document. +chapter of this document. In general, the command to exit any of these applications and restart the system is `BYE`. The exceptions are the Monitor which uses `B` and @@ -703,7 +736,7 @@ drive assignments during initialization. In this case, you can use the The Boot Loader simply launches whatever is in the disk unit/slice you have specified. It does not know what operating system is at that location. The layout of operating systems on disk media is described in -the Using Disks section of this document. +the [Disk Images] section of this document. ### Auto-Submit Batch Files @@ -727,37 +760,45 @@ task you want to perform. ## System Management -### Listing Disk Device Inventory +### Listing Device Inventory -The disk device units available in your system are listed in the +The device units available in your system are listed in the boot messages. However, if that list has scrolled off of your screen, you can use the 'D' command to display a list of them at any time from the Boot Loader prompt. ``` -Boot [H=Help]: d - -Disk Devices: - - Disk Unit 0 on MD0: - Disk Unit 1 on MD1: - Disk Unit 2 on FD0: - Disk Unit 3 on FD1: - Disk Unit 4 on IDE0: - Disk Unit 5 on IDE1: - Disk Unit 6 on IDE2: - Disk Unit 7 on IDE3: - Disk Unit 8 on IDE4: - Disk Unit 9 on IDE5: - Disk Unit 10 on SD0: - Disk Unit 11 on PRPSD0: +Unit Device Type Capacity/Mode +---------- ---------- ---------------- -------------------- +Char 0 ASCI0: RS-232 38400,8,N,1 +Char 1 ASCI1: RS-232 38400,8,N,1 +Char 2 UART0: RS-232 38400,8,N,1 +Char 3 UART1: RS-232 38400,8,N,1 +Char 4 UART2: RS-232 38400,8,N,1 +Char 5 UART3: RS-232 38400,8,N,1 +Char 6 TERM0: Terminal Video 0,ANSI +Char 7 PRPCON0: Terminal Term Module,ANSI +Disk 0 MD0: RAM Disk 352KB,LBA +Disk 1 MD1: Flash Drive 384KB,LBA +Disk 2 FD0: Floppy Disk 3.5",DS/HD,CHS +Disk 3 FD1: Floppy Disk 3.5",DS/HD,CHS +Disk 4 IDE0: CompactFlash 3815MB,LBA +Disk 5 IDE1: Hard Disk -- +Disk 6 IDE2: CompactFlash 3823MB,LBA +Disk 7 IDE3: Hard Disk -- +Disk 8 IDE4: Hard Disk -- +Disk 9 IDE5: Hard Disk -- +Disk 10 SD0: SD Card -- +Disk 11 PRPSD0: SD Card 15193MB,LBA +Video 0 TMS0: CRT Text,40x24 +Sound 0 SND0: AY-3-8910 3+1 CHANNELS ``` ### Rebooting the System The 'R' command within the Boot Loader performs a software reset of -the system. It is the software equivalent of pressing the reset -button. +the system. The system will perform a startup just like powering +up or pressing the hardware reset button. There is generally no need to do this, but it can be convenient when you want to see the boot messages again or ensure your system is in @@ -873,7 +914,7 @@ switches can be used to select any of the first 8 slices. The systems supported by RomWBW all have the ability to use persistent disk media. A wide variety of disk devices are supported including -floppy drives, hard disks, CF Cards, and SD Cards. RomWBW also +floppy drives, hard disks, CF Cards, SD Cards, etc. RomWBW also supports the use of extra RAM and ROM memory as pseudo-disk devices. RomWBW supports a variety of storage devices which will be discussed @@ -882,7 +923,7 @@ in more detail later. * ROM Disk * RAM Disk * Floppy Disk -* Hard Disk (includes CF Cards and SD Cards) +* Hard Disk (includes CF Cards, SD Cards, USB Drives, etc.) We will start by discussing each of these types of storage devices and how to prepare them so files can be stored on them. Subsequently, we @@ -915,10 +956,10 @@ Once your system has working disk devices, they will be accessible from any operating system you choose to run. Disk storage is available whether you boot your OS from ROM or from the disk media itself. -Referring back to the Boot Loader section on "Launching from ROM", you -could start CP/M 2.2 using the 'C' command. As the operating system -starts up, you should see a list of drive letters assigned to the disk -media you have installed. Here is an example of this: +Referring back to [Starting Applications from ROM], you could start CP/M +2.2 using the 'C' command. As the operating system starts up, you +should see a list of drive letters assigned to the disk media you have +installed. Here is an example of this: ``` Configuring Drives... @@ -943,7 +984,7 @@ interface like IDE0. This is important as it is telling you what each drive letter refers to. Also notice that mass storage disks (like IDE) will normally have multiple drive letters assigned. The extra drive letters refer to additional "slices" on the disk. The concept of slices -is described below in the Slices section. +is described below in the [Slices] section. ## Drive Letter Assignment @@ -1005,14 +1046,14 @@ system. The drive letter assignments **do not** change during an OS session unless you use the `ASSIGN` command yourself to do it. Additionally, the -assignments at boot will stay the same on each boot as long as you do + assignments at boot will stay the same on each boot as long as you do not make changes to your hardware configuration. Note that the assignments **are** dependent on the media currently inserted in hard disk drives when the operating system is started. So, notice that if you -insert or remove an SD Card or CF Card, the drive assignments will -change. Since drive letter assignments can change, you must be careful -when doing destructive things like using `CLRDIR` to make sure the drive -letter you use is referring to the desired media. + insert or remove an SD Card, CF Card or USB Drive, the drive +assignments will change. Since drive letter assignments can change, you +must be careful when doing destructive things like using `CLRDIR` to +make sure the drive letter you use is referring to the desired media. When performing a ROM boot of an operating system, note that A: will be your RAM disk and B: will be your ROM disk. When performing a disk @@ -1151,12 +1192,12 @@ adapts to double-density or high-density media. It cannot automatically detect 3.5" vs. 5.25" drive types -- the ROM must be pre-configured for the drive type. -Floppy media must be physically formatted before it can be used. This +Floppy media must be physically formatted before it can be used. This is normally accomplished by using the supplied Floppy Disk Utility (FDU) -application. This application interacts directly with your hardware -and therefore you must specify your floppy interface hardware at startup. -Additionally, you need to specify the floppy drive and media format to -use for formatting. +application. This application interacts directly with your hardware +and therefore you must specify your floppy interface hardware at +application startup. Additionally, you need to specify the floppy drive +and media format to use for formatting. Below is a sample session using FDU to format a 1.44M floppy disk in the first (primary) floppy disk drive: @@ -1245,7 +1286,9 @@ the appropriate OS/application documentation as needed. **WARNING:** Some of the operating systems provided with RomWBW require that a soft-reset be performed when swapping floppy disk media. For example, under CP/M 2.2, you must press control-C at the CP/M prompt -after inserting a new floppy disk. +after inserting a new floppy disk. The consequences of failing to +perform the soft-reset vary from unexpected error messages to full +disk directory corruption. ## Hard Disks @@ -1312,11 +1355,11 @@ assigned to the first 8 slices of that media. If you have two large storage devices, you will see that each device is allocated 4 drive letters. -Referring to slices within a storage device is done by appending a : -** where ** is the device relative slice number from 0-255. For -example, if you have an IDE device, it will show up as IDE0: in the -boot messages meaning the first IDE device. To refer to the fourth -slice of IDE0, you would type "IDE0:3". Here are some examples: +Referring to slices within a storage device is done by appending a +`:` where \ is the device relative slice number from 0-255. +For example, if you have an IDE device, it will show up as IDE0: in the +boot messages meaning the first IDE device. To refer to the fourth slice +of IDE0, you would type "IDE0:3". Here are some examples: | | | |----------|------------------------------| @@ -1405,14 +1448,16 @@ to the size of the disk media -- if you attempted to read/write to a slice that would exceed the disk size, you would see I/O errors. This is considered the "legacy" disk layout for RomWBW. -RomWBW has subsequently been enhanced to support the concept of +Starting with v3.2, RomWBW has been enhanced to support the concept of partitioning. The partition mechanism is entirely compliant with Master Boot Record (MBR) Partition Tables introduced by IBM for the PC. The Wikipedia article on the [Master Boot Record](https://en.wikipedia.org/wiki/Master_boot_record) is excellent if you are not familiar with them. This is considered the "modern" disk layout for RomWBW. RomWBW uses the partition type id -0x2E. RomWBW does not support extended partitions -- only a single +0x2E. This partition type id does not equate to any existing well-known +partition types -- it was chosen because it is not generally used. +RomWBW does not support extended partitions -- only a single primary partition can be used. Both the legacy and modern disk layouts continue to be fully supported @@ -1427,6 +1472,8 @@ the legacy disk layout contain 512 directory entries. The modern disk layout filesystems provide 1024 directory entries. In fact, you will subsequently see that the prefixes "hd512" and "hd1k" are used to identify disk images appropriate for the legacy and modern format. +These prefixes were chosen specifically to highlight the number of +directory entries supported. You **cannot** mix disk layouts on a single disk device. To say it another way, the existence of a partition table entry for RomWBW on @@ -1449,7 +1496,9 @@ recommended for the following reasons: ### Checking Hard Disk Layout If you are not sure which hard disk layout was used for your existing -media, you can use the CP/M `STAT` command to determine this. This +media, you can use the OSes command to display the number of directory +entries for a drive letter on the corresponding hard disk. For example, +the `STAT` command is used in CP/M 2.2 to determine this. This command displays the number of directory entries on a filesystem. If it indicates 512, your disk layout is legacy (hd512). If it indicates 1024, your disk layout is modern (hd1k). @@ -1460,9 +1509,9 @@ and boot to Z-System in ROM by using the 'Z' command at the Boot Loader. As Z-System starts, we see the following disk assignments: ``` -Boot [H=Help]: z +Boot [H=Help]: c -Loading Z-System... +Loading CP/M 2.2... CBIOS v3.1.1-pre.194 [WBW] @@ -1483,7 +1532,7 @@ Configuring Drives... 1081 Disk Buffer Bytes Free -ZSDOS v1.1, 54.0K TPA +CP/M-80 v2.2, 54.0K TPA ``` You can see that the IDE0 interface (which contains the CF Card) has @@ -1539,7 +1588,7 @@ less than 62.5MB of actual space (using the RomWBW definition that will support 7 slices just fine because 7 * 8,320KB = 58.24MB (hd512) or 1024KB + (7 * 8192MB) = 57MB (hd1k). -The cost of high capacity CF and SD Cards has become very reasonable. +The cost of high capacity CF/SD/USB Media has become very reasonable. I highly recommend upgrading to 1GB or greater media. This size will support all features of the RomWBW Combo Disk Image with 64 slices and a 384MB FAT filesystem (see [Combo Hard Disk Image]). @@ -1567,13 +1616,13 @@ below under Disk Initialization. In this scenario, you will need to subsequently copy any files you want to use onto the newly initialized disk (see [Transferring Files]). -You will notice that in the following instructions there is no mention -of specific hardware. Because the RomWBW firmware provides a -hardware abstraction layer, all disk images will work on all -hardware variations. Yes, this means you can remove an CF/SD Card from -one RomWBW system and put it in a different RomWBW system. The only -constraint is that the applications on the disk media must be up to date -with the firmware on the system being used. +You will notice that in the following instructions there is no mention +of specific hardware. Because the RomWBW firmware provides a hardware +abstraction layer, all disk images will work on all hardware variations. +Yes, this means you can remove disk media from one RomWBW system and +put it in a different RomWBW system. The only constraint is that the +applications on the disk media must be up to date with the firmware on +the system being used. ## Disk Images @@ -1609,6 +1658,9 @@ You will find 3 sets of these .img files in the distribution. The "hd512" for a legacy layout hard disk image, and "hd1K" for a modern layout hard disk image. +In the case of xxx_dos65.img, only an hd512 variant is provided. This +is a constraint of the DOS65 distribution. + There is also an image file called "psys.img" which contains a bootable p-System hard disk image. It contains 6 p-System filesystem slices, but these are not interoperable with the CP/M slices described above. This @@ -1633,7 +1685,9 @@ image onto it. You can do this with RomWBW using FDU as described in the [Floppy Disks] section of this document. You can also format the floppy using your modern computer, but using FDU on RomWBW is preferable because it will allow you to use optimal physical sector -interleaving. +interleaving. FDU defaults to a sector interleave of 2 which will +result in faster floppy disk I/O. Other interleaves will work, but +will be slower. RomWBW includes a Windows application called RawWriteWin in the Tools directory of the distribution. This simple application will let you @@ -1651,7 +1705,7 @@ command prompt. ### Hard Disk Images -Keeping in mind that a RomWBW hard disk (including CF/SD Cards) +Keeping in mind that a RomWBW hard disk (including CF/SD/USB devices) allows you to have multiple slices (CP/M filesystems), there are a couple ways to image hard disk media. The easiest approach is to use the "combo" disk image. This image is already prepared @@ -1694,7 +1748,7 @@ Alternatively, the FAT partition can be formatted on a modern computer. The combo disk image layout was designed to fit well on a 1GB hard disk. The 64 CP/M slices (approximately 512MB) and 384MB FAT filesystem all fit well within a 1GB hard disk. This size choice was a bit arbitrary, -but based on the idea that a 1GB CF or SD Card is easy and cheap to +but based on the idea that 1GB CF/SD/USB Media is easy and cheap to acquire. It is fine if your hard disk is smaller than 1GB. It just means that it will not be possible to use the pre-allocated FAT filesystem partition and any CP/M filesystem slices that don't fit. You @@ -1780,8 +1834,8 @@ using your modern computer. Note that you **do not** run `CLRDIR` or the disk will be partitioned and setup with 1 or more slices containing ready-to-run bootable operating systems. -To write a hard disk image file onto your actual media (actual hard -disk or CF/SD Card), you need to use an image writing utility on your +To write a hard disk image file onto your actual media (actual hard disk + or CF/SD/USB Media), you need to use an image writing utility on your modern computer. Your modern computer will need to have an appropriate interface or slot that accepts the media. To actually copy the image, you can use the `dd` command on Linux or MacOS. On Windows, in the @@ -1817,7 +1871,7 @@ survive re-imaging, you **must** follow these rules: Once you have copied the image onto the hard disk media, you can move the media over to your RomWBW system. You can then boot to the -operating system slices by specify "." at the +operating system slices by specifying "." at the RomWBW Boot Loader command prompt. ## In-situ Disk Preparation @@ -1861,6 +1915,9 @@ are not sure. #### Partition Setup +**WARNING**: Modifying the partition table of existing media will +make the data on the media inaccessible. + Since the disk layout is determined by the existence (or lack) of a RomWBW partition, you must start by running `FDISK80`. When FDISK80 starts, enter the disk unit number of the new media. At this point, @@ -1939,10 +1996,10 @@ You can use the `ASSIGN` command to handle this. Once you have your slice(s) initialized, you can begin transferring files to the associated drive letters. Refer to the [Transferring -Files] section for options to do this. If you want to make a slice +Files] chapter for options to do this. If you want to make a slice bootable, you will need to use `SYSCOPY` to setup the system track(s) of the slice. The use of `SYSCOPY` depends on the operating system -and is described in the [Operating Systems] section of this document. +and is described in the [Operating Systems] chapter of this document. As an example, let's assume you want to setup C: as a bootable Z-System disk and add to it all the files from the ROM disk. To @@ -2460,9 +2517,8 @@ the [MIT licence](https://www.freertos.org/a00114.html) and further general information is available at [FreeRTOS](https://www.freertos.org/RTOS.html). -You can also contact Phillip for detailed information on the Z180 -implementation of FreeRTOS for RomWBW. -[feilipu](https://github.com/feilipu) +Phillip may be contacted via his +[GitHub Page](https://github.com/feilipu). ## Fuzix @@ -2565,7 +2621,7 @@ directory of the distribution. # FAT Filesystem -The FAT filesystem format that originated with MS-DOS has been almost +The FAT filesystem format that originated with MS-DOS is almost ubiquitous across modern computers. Virtually all operating systems now support reading and writing files to a FAT filesystem. For this reason, RomWBW now has the ability to read and write files on FAT @@ -2658,10 +2714,10 @@ filesystem disk. You can use your modern computer to format the disk (floppy, CF Card, SD Card, etc.), then insert the disk in your RomWBW computer and access it using `FAT` based on its RomWBW unit number. -**WARNING**: Microsoft Windows will sometimes suggest reformatting -partitions that it does not recognize. If you are prompted to format -a partition of your SD/CF Card when inserting the card into a Windows -computer, you probably want to select Cancel. +**WARNING**: Microsoft Windows will sometimes suggest reformatting +partitions that it does not recognize. If you are prompted to format a +partition of your SD/CF/USB Media when inserting the card into a Windows + computer, you probably want to select Cancel. ## FAT Application Usage @@ -3248,8 +3304,12 @@ computers terminal program to complete the process. The `XM` application generally tries to detect the hardware you are using and adapt to it. However, you must ensure that you have a reliable serial connection. You must also ensure that the speed of -the connection is not too fast for XModem to service. Alternatively, -you can ensure that hardware flow control is working properly. +the connection is not too fast for XModem to service. If your +file transfer attempts are failing, try either of the following: + +- Check that hardware flow control is enabled in your terminal + emulation software. +- Reduce the speed of your serial port connection. There is an odd interaction between XModem and partner terminal programs that can occur. Essentially, after launching `XM`, you must @@ -3264,7 +3324,7 @@ scope of this document. It is possible to pass disk images between your RomWBW system and your modern computer. This assumes you have an appropriate media slot on your modern computer for the media you want to use (CF Card, SD -Card, or floppy drive). +Card, floppy drive, etc.). The general process to get files from your modern computer to a RomWBW computer is: @@ -3272,8 +3332,8 @@ computer is: 1. Use `cpmtools` on your modern computer to create a RomWBW CP/M filesystem image. -2. Insert your RomWBW media (CF Card, SD Card, or floppy disk) in your -modern computer. +2. Insert your RomWBW media (CF Card, SD Card, floppy disk, etc.) in +your modern computer. 3. Use a disk imaging tool to copy the RomWBW filesystem image onto the media. @@ -3298,11 +3358,11 @@ detail in the Source/Images directory of the distribution. ## FAT Filesystem Transfers -The ability to interact with FAT filesystems was covered in [FAT -Filesystem]. This capability means that you can generally use your -modern computer to make an SD Card or CF Card with a standard FAT32 -filesystem on it, then place that media in your RomWBW computer and -access the files. +The ability to interact with FAT filesystems was covered in +[FAT Filesystem]. This capability means that you can generally use your + modern computer to make an SD Card, CF Card, or USB Drive with a +standard FAT32 filesystem on it, then place that media in your RomWBW +computer and access the files. When formatting the media on your modern computer, be sure to pick the FAT filesystem. NTFS and other filesystems will not work. As previously @@ -3376,7 +3436,9 @@ environment on your computer. RomWBW can be built on modern Windows, Linux, or MacOS computers. The process for building a custom ROM is documented in the ReadMe.txt file -in the Source directory of the distribution. +in the Source directory of the distribution. Any modern version of +Windows, MacOS, or Linux released in the last 10 years should be able +to run the build process. For those who are interested in more than basic system customization, note that all source code is provided (including the operating @@ -3454,17 +3516,62 @@ existing, working ROM chip and program a new one with the new firmware. If the new one fails to boot, you can easily return to the known working ROM. +For each ROM that comes with the RomWBW distribution, you will find +that there are actually 3 different variants: + +- `.rom` contains the complete ROM chip image +- `.upd` contains the system code, but omits the ROM Disk contents +- `.com` contains a CP/M executable version of the ROM code + +So, for example, RCZ80_std contains the following files: + +- `SBC_std.rom` +- `SBC_std.upd` +- `SBC_std.com` + +The use of the `.com` variant is described below in [Application Boot]. + +As previously discussed, the ROM in most RomWBW systems contains both +the system code as well as a ROM Disk with files on it. The `.rom` +variant of the ROM contains a full ROM chip image including both the +system code and the Rom Disk contents. The `.upd` variant of the ROM +contains only the system code portion of the ROM. If you apply the +`.upd` variant to your system, it will overlay the system code, but +will not overlay the ROM Disk contents (they remain intact). You may +use either the `.rom` or the `.upd` file when updating your ROM chip +(this does not apply to Application Boot). It is best to use the +`.rom` file for your upgrade because the files on your ROM Disk should +be updated whenever you update your system code. The advantage of the +`.upd` variant is that is much smaller, so you can upload and apply it +faster. The ROM update instructions below generally refer to using +the `.rom` variant. However, you may substitute the `.upd` variant +if desired. + +## Application Boot + Prior to attempting to reprogram your actual ROM chip, you may wish to "try" the update to ensure it will work on your system. With RomWBW, you can upload a new ROM image executable and load it from the command line. For each ROM image file (.rom) in the Binary directory, you will find a corresponding application file (.com). For example, for -SBC_std.rom, there is also an SBC_std.com file. You can upload the .com -file to your system using XModem, then simply run the .com file. You -will see your system go through the normal startup process just like it -was started from ROM. However, your ROM has not been updated and the -next time you boot your system, it will revert to the system image -contained in ROM. +SBC_std.rom, there is also an SBC_std.com file. + +You can upload the `.com` file to your system using XModem, then simply +run the `.com` file. You will see your system go through the normal +startup process just like it was started from ROM. However, your +physical ROM has not been updated and the next time you boot your +system, it will revert to the system image contained in ROM. + +Using this `.com` version of a ROM is an excellent way to confirm that +the new ROM code you intend to program will work correctly. If it +does not, then you can just reboot and your old ROM will be loaded. + +When the `.com` file is loaded, you will be taken to the normal +Boot Loader menu. However, you will find that the only OS that is +available to boot from ROM is ZSDOS. There is only room for a +single OS in the .com file. Even if you don't normally use ZSDOS, +this will still confirm that your system operates well under the +new ROM code. ## Upgrading via Flash Utility @@ -3473,13 +3580,19 @@ possible to reprogram your system ROM using the FLASH utility from Will Sowerbutts. This application, called FLASH.COM, can be found on the ROM drive of any running system. In this case, you would need to transfer the new ROM image (.rom) over to your system using XModem (or -one of the other mechanisms described in the Transferring Files +one of the other mechanisms described in the [Transferring Files] section). The ROM image is too large to fit on your RAM drive, so you will need to transfer it to a larger storage drive. Once the ROM image is on your system, you can use the FLASH application to update your ROM. The following is a typical example of transferring ROM image using XModem and flashing the chip in-situ. +**NOTE**: The FLASH utility **can not** determine the type of your +ROM chip if it is write protected. Additionally, it has not way to +even determine if it is write protected. If the FLASH utility +indicates it does not recognize your ROM chip, check to ensure the +chip is not write protected. + ``` E>xm r rom.rom @@ -3514,15 +3627,18 @@ occurred. ## Upgrading via XModem Flash Updater Similar to using the Flash utility, the system ROM can be updated -or upgraded through the ROM based updater utility. This works by -by reprogrammed the flash ROM as the file is being transferred. +or upgraded through the ROM-based updater utility. This works by +reprogramming the flash ROM as the file is being transferred. -This has the advantage that secondary storage is not required to -hold the new image. +Using the ROM-based updater has the advantage that secondary storage is +not required to hold the new image. In other words, it is not +necessary to have a mass storage device available to store the +ROM image. From the Boot Loader menu select X (Xmodem Flash Updater) and then -U (Begin Update). Then initiate the Xmodem transfer of the .img or -.upd file. +U (Begin Update). Then initiate the Xmodem transfer of the `.rom` file. +Since the XModem Flash Updater will be relatively slow, you may wish +to use the `.upd` varient of the ROM. More information can be found in the ROM Applications document. @@ -3573,6 +3689,10 @@ images. * FAT.COM * TUNE.COM +**WARNING**: If you run a RomWBW-specific application that is not +the appropriate for the version of RomWBW you are running, the +application will generate an error message and abort. + ## System Update As previously described, a RomWBW ROM contains ROM applications as well @@ -3794,6 +3914,15 @@ Also feel free to email $doc_author$ at [$doc_authmail$](mailto:$doc_authmail$). ## Appendix A - Pre-built ROM Images +This appendix contains a summary of the system configuration target +for each of the pre-built ROM images included in the RomWBW +distribution. It is intended to help you select the correct ROM +image and understand the basic hardware components supported. +Detailed hardware system configuration information should be obtained +from your system provider/designer. I am happy to provide support +adapting RomWBW to new or modified systems -- see [Getting Assistance] +for contact information. + The standard ROM images will detect and install support for certain devices and peripherals that are on-board or frequently used with each platform as documented below. If the device or peripheral is @@ -3823,84 +3952,129 @@ the RomWBW HBIOS configuration. ### RetroBrew Z80 SBC +#### ROM Image File: SBC_std.rom + | | | |-------------------|---------------| -| ROM Image File | SBC_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 8.000 MHz | | Interrupts | None | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 8.000 MHz assumed - - Hardware auto-detected: - - Onboard DS1302 RTC - - Onboard UART Serial Adapter - - Onboard PPIDE Hard Disk Interface - - Zilog Peripherals SIO Serial Interface - - CVDU Display Adapter - - VGA3 Display Adapter - - DiskIO V3 Floppy Disk Controller w/ 3.5" HD Drives - - PropIO Video, Keyboard, & SD Card - - SBC V1 has a known race condition in the bank switching - circuit which is likely to cause system instability. SBC V2 - does not have this issue. +| System Timer | None | +| Serial Default | 38400 Baud | +| Memory Manager | SBC | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- SIO +- VGA +- CVDU +- PRP +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### RetroBrew Z80 SimH +#### ROM Image File: SBC_simh.rom + | | | |-------------------|---------------| -| ROM Image File | SBC_simh.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 8.000 MHz | | Interrupts | Mode 1 | +| System Timer | SimH | +| Serial Default | 38400 Baud | +| Memory Manager | SBC | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- SIMRTC +- UART +- SIO +- MD +- HDSK + +##### Notes: + +- Image for SimH emulator +- CPU speed and Serial configuration not relevant in emulator - - System timer is generated by SimH - - Hardware auto-detected: - - SimH emulated 8250 Serial Adapter - - SimH emulated hard disk drives - - SimH RTC - `\clearpage`{=latex} ### RetroBrew N8 Z180 SBC +#### ROM Image File: N8_std.rom + | | | |-------------------|---------------| -| ROM Image File | N8_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 18.432 MHz | | Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - Onboard DS1302 RTC - - Onboard Z180 ASCI Serial Ports - - Onboard Floppy Disk Controller w/ 3.5" HD Drives - - Onboard TMS9918 Video Controller - - Onboard PS/2 Keyboard Controller - - Onboard SD Card Interface via CSIO - - Assumes N8 with date code >= 2312 for CSIO interface to SD Card +| System Timer | Z180 | +| Serial Default | 38400 Baud | +| Memory Manager | N8 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- ASCI +- UART +- TMS +- PPK +- MD +- FD +- SD +- AY38910 + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives +- SD Card interface is configured for CSIO (N8 date code >= 2312) `\clearpage`{=latex} ### Zeta Z80 SBC +#### ROM Image File: ZETA_std.rom + | | | |-------------------|---------------| -| ROM Image File | ZETA_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 8.000 MHz | | Interrupts | None | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 20.000 MHz assumed - - Hardware auto-detected: - - Onboard DS1302 RTC - - Onboard UART Serial Adapter - - Onboard Floppy Disk Controller w/ 1 3.5" HD Drive - - ParPortProp Video, Keyboard, & SD Card - - If ParPortProp is installed, initial console output is determined - by JP1: +| System Timer | None | +| Serial Default | 38400 Baud | +| Memory Manager | SBC | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- PPP +- MD +- FD + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives +- If ParPortProp is installed, initial console output is + determined by JP1: - Shorted: console to on-board serial port - Open: console to ParPortProp video and keyboard @@ -3908,23 +4082,33 @@ the RomWBW HBIOS configuration. ### Zeta V2 Z80 SBC +#### ROM Image File: ZETA2_std.rom + | | | |-------------------|---------------| -| ROM Image File | ZETA2_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 8.000 MHz | | Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 8.000 MHz assumed - - System timer is generated by onboard CTC - - Hardware auto-detected: - - Onboard DS1302 RTC - - Onboard CTC - - Onboard UART Serial Adapter - - Onboard Floppy Disk Controller w/ 1 3.5" HD Drive - - ParPortProp Video, Keyboard, & SD Card - - If ParPortProp is installed, initial console output is determined - by JP1: +| System Timer | CTC | +| Serial Default | 38400 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- PPP +- MD +- FD +- CTC + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives +- If ParPortProp is installed, initial console output is + determined by JP1: - Shorted: console to on-board serial port - Open: console to ParPortProp video and keyboard @@ -3932,564 +4116,974 @@ the RomWBW HBIOS configuration. ### Mark IV Z180 SBC +#### ROM Image File: MK4_std.rom + | | | |-------------------|---------------| -| ROM Image File | MK4_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 18.432 MHz | | Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - Onboard DS1302 RTC - - Onboard Z180 ASCI Serial Ports - - UART Serial Interfaces (CAS, MFP, UART4) - - CVDU Display Adapter - - VGA3 Display Adapter - - Onboard SD Card Interface via CSIO - - Onboard IDE CF Card Interface - - DIDE Floppy Disk Controller w/ 3.5" HD Drives - - DIDE IDE Hard Disk Controller - - PropIO Video, Keyboard, & SD Card +| System Timer | Z180 | +| Serial Default | 38400 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- ASCI +- UART +- VGA +- CVDU +- KBD +- PRP +- MD +- FD +- IDE +- SD + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### RCBus Z80 CPU Module +#### ROM Image File: RCZ80_std.rom + | | | |-------------------|---------------| -| ROM Image File | RCZ80_std.rom | -| Console Baud Rate | 115200 | +| Default CPU Speed | 7.372 MHz | | Interrupts | Mode 1 | +| System Timer | None | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 7.3728 MHz assumed - - Requires 512K RAM/ROM Module - - Hardware auto-detected: - - DS1302 RTC - - ACIA Serial Interface Module - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Serial baud rate is usually determined by hardware for ACIA and - SIO interfaces +- DSRTC +- UART +- SIO +- ACIA +- MD +- FD +- IDE +- PPIDE +- CTC + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives + +`\clearpage`{=latex} + +#### ROM Image File: RCZ80_kio.rom | | | |-------------------|---------------| -| ROM Image File | RCZ80_kio.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 7.372 MHz | | Interrupts | Mode 2 | - - - Equivalent to RCZ80_std w/ following modifications: - - KIO-SIO Serial Interface uses KIO port standards - - KIO-CTC generates system timer - - SIO Serial baud rate managed by KIO-CTC - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts +| System Timer | CTC | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- KIO +- CTC + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives +- SIO Serial baud rate managed by CTC `\clearpage`{=latex} ### RCBus Z180 CPU Module -| | | -|-------------------|----------------| -| ROM Image Files | RCZ180_ext.rom | -| | RCZ180_nat.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z180 ASCI Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Specific ROM image determined by memory module used: - - RCZ180_ext - Bank switching on memory module (external of CPU) - - RCZ180_nat - Linear memory module (native CPU bank switching) - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts +#### ROM Image File: RCZ180_ext.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- For use with Z2 bank switched memory board (Z2 external memory management) +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives + +`\clearpage`{=latex} + +#### ROM Image File: RCZ180_nat.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- For use with linear memory board (Z180 native memory management) +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### RCBus Z280 CPU Module -| | | -|-------------------|----------------| -| ROM Image Files | RCZ280_ext.rom | -| | RCZ280_nat.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 1 (ext) | -| | Mode 3 (nat) | - - - CPU speed is assumed to be 12 MHz (24 MHz oscillator) - - System timer is generated by Z280 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z280 Z2U Serial Ports - - ACIA Serial Interface Module (ext only) - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Serial baud rate is usually determined by hardware for ACIA and - SIO interfaces - - Requires 512K RAM/ROM module - - Specific ROM image determined by memory module used: - - RCZ180_ext - Bank switching on memory module (external of CPU) - - RCZ180_nat - Linear memory module (native CPU bank switching) +#### ROM Image File: RCZ280_ext.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 6.000 MHz | +| Interrupts | Mode 1 | +| System Timer | None | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- Z2U +- UART +- SIO +- ACIA +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- For use with linear memory board (Z280 native memory management) +- FD configured for 3.5" HD floppy drives + +#### ROM Image File: RCZ280_nat.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 6.000 MHz | +| Interrupts | Mode 3 | +| System Timer | Z280 | +| Serial Default | 115200 Baud | +| Memory Manager | Z280 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- Z2U +- UART +- SIO +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- For use with Z2 bank switched memory board (Z2 external memory management) +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Easy Z80 SBC -| | | -|-------------------|----------------| -| ROM Image File | RCZ80_easy.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 10.000 MHz assumed - - System timer is generated by onboard CTC - - Hardware auto-detected: - - DS1302 RTC - - Onboard SIO Serial Interface - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - SIO Serial baud rate managed by CTC +#### ROM Image File: RCZ80_easy.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 10.000 MHz | +| Interrupts | Mode 2 | +| System Timer | CTC | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- CTC + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Tiny Z80 SBC -| | | -|-------------------|----------------| -| ROM Image File | RCZ80_tiny.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 16.000 MHz assumed - - System timer is generated by onboard CTC - - Hardware auto-detected: - - DS1302 RTC - - Onboard SIO Serial Interface - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - SIO Serial baud rate managed by CTC +#### ROM Image File: RCZ80_easy.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 16.000 MHz | +| Interrupts | Mode 2 | +| System Timer | CTC | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- CTC + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Z80-512K CPU/RAM/ROM Module -| | | -|-------------------|----------------| -| ROM Image File | RCZ80_skz.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 1 | - - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 7.3728 MHz assumed - - Hardware auto-detected: - - DS1302 RTC - - ACIA Serial Interface Module - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Serial baud rate is determined by hardware for ACIA and SIO - interfaces +#### ROM Image File: RCZ80_skz.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 7.372 MHz | +| Interrupts | Mode 1 | +| System Timer | None | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- SIO +- ACIA +- MD +- FD +- IDE +- PPIDE +- CTC + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Small Computer SC126 Z180 SBC -| | | -|-------------------|------------------| -| ROM Image Files | SCZ180_sc126.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z180 ASCI Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Onboard SD Card Interface - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts +#### ROM Image File: SCZ180_sc126.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- SD +- AY38910 + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Small Computer SC130 Z180 SBC -| | | -|-------------------|------------------| -| ROM Image Files | SCZ180_sc130.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z180 ASCI Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Onboard SD Card Interface - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts +#### ROM Image File: SCZ180_sc130.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- SD +- AY38910 + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Small Computer SC131 Z180 Pocket Computer -| | | -|-------------------|------------------| -| ROM Image Files | SCZ180_sc131.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | +#### ROM Image File: SCZ180_sc131.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): - - CPU speed assumed to be 18.432 MHz - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - Interrupt-driven RTC - - Z180 ASCI Serial Ports - - Onboard SD Card Interface +- INTRTC +- ASCI +- MD +- SD + +##### Notes: `\clearpage`{=latex} ### Small Computer SC140 Z180 CPU Module -| | | -|-------------------|------------------| -| ROM Image Files | SCZ180_sc140.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z180 ASCI Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Onboard SD Card Interface - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts +#### ROM Image File: SCZ180_sc140.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- SD + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Small Computer SC503 Z180 CPU Module -| | | -|-------------------|------------------| -| ROM Image Files | SCZ180_sc503.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z180 ASCI Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Onboard SD Card Interface - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts +#### ROM Image File: SCZ180_sc503.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- SD + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Small Computer SC700 Z180 CPU Module -| | | -|-------------------|------------------| -| ROM Image Files | SCZ180_sc700.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z180 ASCI Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Onboard SD Card Interface - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts +#### ROM Image File: SCZ180_sc700.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE +- SD + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Dyno Z180 SBC -| | | -|-------------------|----------------| -| ROM Image Files | DYNO0_std.rom | -| Console Baud Rate | 38400 | -| Interrupts | Mode 2 | +#### ROM Image File: DYNO_std.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 38400 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | - - CPU speed is assumed to be 18.432 MHz - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - BQ4845P RTC - - Z180 ASCI Serial Ports - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - Onboard PPIDE Hard Disk Interface Module +##### Supported Hardware (see [Appendix B - Device Summary]): + +- BQRTC +- ASCI +- MD +- FD +- PPIDE + +##### Notes: + +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Nhyodyne Z80 MBC +#### ROM Image File: MBC_std.rom + | | | |-------------------|---------------| -| ROM Image File | MBC_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 8.000 MHz | | Interrupts | None | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 8.000 MHz assumed - - System timer is generated by CTC if available - - Hardware auto-detected: - - DS1302 RTC - - Zilog CTC - - Zilog DMA Module - - UART Serial Adapter - - SIO Serial Interface - - LPT Printer Interface - - Zilog Parallel Interface - - CVDU Display Adapter - - TMS9938/58 Display Adapter - - PS/2 Keyboard Interface - - AY-3-8910/YM2149 Sound Module - - Floppy Disk Controller w/ 3.5" HD Drives - - PPIDE Hard Disk Interface - - Interrupts may be enabled in build options +| System Timer | None | +| Serial Default | 38400 Baud | +| Memory Manager | MBC | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- PKD +- DSRTC +- UART +- SIO +- PIO +- LPT +- CVDU +- TMS +- KBD +- ESP +- MD +- FD +- PPIDE +- SPK + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Rhyophyre Z180 SBC +#### ROM Image File: RPH_std.rom + | | | |-------------------|---------------| -| ROM Image File | RPH_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 18.432 MHz | | Interrupts | None | +| System Timer | None | +| Serial Default | 38400 Baud | +| Memory Manager | RPH | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - Onboard Z180 ASCI Serial Ports - - Onboard PPIDE CF Interface - - Onboard PS/2 Keyboard Controller - - Interrupts may be enabled in build options +- DSRTC +- ASCI +- GDC +- KBD +- MD +- PPIDE + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present `\clearpage`{=latex} ### Z80 ZRC CPU Module -| | | -|-------------------|--------------------| -| ROM Image Files | RCZ80_zrc.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 1 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 14.7456 MHz assumed - - Hardware auto-detected: - - DS1302 RTC - - ACIA Serial Interface Module - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - Onboard IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - VGARC Video & Keyboard Module - - Serial baud rate is usually determined by hardware for ACIA and - SIO interfaces - +#### ROM Image File: RCZ80_zrc.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 14.745 MHz | +| Interrupts | Mode 1 | +| System Timer | None | +| Serial Default | 115200 Baud | +| Memory Manager | ZRC | +| ROM Size | 512 KB | +| RAM Size | 1536 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- SIO +- ACIA +- VRC +- KBD +- MD +- FD +- IDE +- PPIDE +- CTC + +##### Notes: + +- ZRC is actually contains no ROM and 2MB of RAM. The first 512KB + of RAM is loaded from disk and then handled like ROM. +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives + +`\clearpage`{=latex} + +#### ROM Image File: RCZ80_zrc_ram.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 14.745 MHz | +| Interrupts | Mode 1 | +| System Timer | None | +| Serial Default | 115200 Baud | +| Memory Manager | ZRC | +| ROM Size | 0 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- SIO +- ACIA +- VRC +- KBD +- MD +- FD +- IDE +- PPIDE +- CTC + +##### Notes: + +- ROMless boot -- HBIOS is loaded from disk at boot +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives + +`\clearpage`{=latex} + ### Z180 Z1RCC CPU Module -| | | -|-------------------|--------------------| -| ROM Image Files | RCZ180_z1rcc.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 18.432 MHz assumed - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z180 ASCI Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Use of Interrupt Mode 2 requires proper IEI/IEO configuration - for all peripherals generating interrupts - +#### ROM Image File: RCZ180_z1rcc.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 0 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- INTRTC +- ASCI +- UART +- SIO +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- ROMless boot -- HBIOS is loaded from disk at boot +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives + `\clearpage`{=latex} ### Z280 ZZRCC CPU Module -| | | -|-------------------|--------------------| -| ROM Image Files | RCZ280_zzrc.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 3 | - - - CPU speed is assumed to be 12 MHz (24 MHz oscillator) - - System timer is generated by Z280 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z280 Z2U Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - Onboard IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - VGARC Video & Keyboard Module - - Serial baud rate is usually determined by hardware for ACIA and - SIO interfaces +#### ROM Image File: RCZ280_zzrcc.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 14.745 MHz | +| Interrupts | Mode 3 | +| System Timer | Z280 | +| Serial Default | 115200 Baud | +| Memory Manager | Z280 | +| ROM Size | 256 KB | +| RAM Size | 256 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- Z2U +- UART +- SIO +- VRC +- KBD +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- ZZRCC actually contains no ROM and 512KB of RAM. The first 256KB + of RAM is loaded from disk and then handled like ROM. +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives + +`\clearpage`{=latex} + +#### ROM Image File: RCZ280_zzrcc_ram.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 14.745 MHz | +| Interrupts | Mode 3 | +| System Timer | Z280 | +| Serial Default | 115200 Baud | +| Memory Manager | Z280 | +| ROM Size | 0 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- Z2U +- UART +- SIO +- VRC +- KBD +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- ROMless boot -- HBIOS is loaded from disk at boot +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Z280 ZZ80MB SBC -| | | -|-------------------|-------------------| -| ROM Image Files | RCZ280_zz80mb.rom | -| Console Baud Rate | 115200 | -| Interrupts | Mode 3 | - - - CPU speed is assumed to be 12 MHz (24 MHz oscillator) - - System timer is generated by Z280 CPU - - Hardware auto-detected: - - DS1302 RTC - - Z280 Z2U Serial Ports - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - Onboard IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - VGARC Video & Keyboard Module - - Serial baud rate is usually determined by hardware for ACIA and - SIO interfaces +#### ROM Image File: RCZ280_zz80mb.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 12.000 MHz | +| Interrupts | Mode 3 | +| System Timer | Z280 | +| Serial Default | 115200 Baud | +| Memory Manager | Z280 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- Z2U +- UART +- SIO +- VRC +- KBD +- MD +- FD +- IDE +- PPIDE + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} ### Z80-Retro SBC -| | | -|-------------------|------------------| -| ROM Image File | Z80RETRO_std.rom | -| Console Baud Rate | 38400 | -| Interrupts | Mode 2 | +#### ROM Image File: Z80RETRO_std.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 14.745 MHz | +| Interrupts | Mode 2 | +| System Timer | None | +| Serial Default | 38400 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- SIO +- MD +- SD +- CTC - - CPU speed is assumed to be 14.7456 MHz - - Hardware auto-detected: - - SIO Serial Interface Module - - Onboard CTC +##### Notes: `\clearpage`{=latex} ### S100 Computers Z180 +#### ROM Image File: S100_std.rom + | | | |-------------------|---------------| -| ROM Image File | S100_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 18.432 MHz | | Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 57600 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- INTRTC +- ASCI +- SCON +- MD +- SD - - CPU speed assumed to be 18.432 MHz - - System timer is generated by Z180 CPU - - Hardware auto-detected: - - Interrupt-driven RTC - - Z180 ASCI Serial Ports - - Onboard SD Card Interface +##### Notes: `\clearpage`{=latex} ### Duodyne Z80 System +#### ROM Image File: DUO_std.rom + | | | |-------------------|---------------| -| ROM Image File | DUO_std.rom | -| Console Baud Rate | 38400 | +| Default CPU Speed | 8.000 MHz | | Interrupts | Mode 2 | - - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 8.000 MHz assumed - - System timer is generated by CTC if available - - Hardware auto-detected: - - DS1302 RTC - - Zilog DMA Module - - UART Serial Adapter +| System Timer | CTC | +| Serial Default | 38400 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- PCF +- UART +- SIO +- PIO +- LPT +- DMA +- CH +- ESP +- MD +- SPK + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present `\clearpage`{=latex} ### Heath H8 Z80 System +#### ROM Image File: HEATH_std.rom + | | | |-------------------|---------------| -| ROM Image File | HEATH_std.rom | -| Console Baud Rate | 115200 | +| Default CPU Speed | 7.372 MHz | | Interrupts | Mode 1 | +| System Timer | None | +| Serial Default | 115200 Baud | +| Memory Manager | Z2 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | - - CPU speed is detected at startup if DS1302 RTC is active - - Otherwise 7.3728 MHz assumed - - Hardware auto-detected: - - DS1302 RTC - - ACIA Serial Interface Module - - SIO Serial Interface Module - - EP Dual UART Serial Interface Module - - WDC Floppy Disk Controller w/ 3.5" HD Drives - - IDE Hard Disk Interface Module - - PPIDE Hard Disk Interface Module - - Serial baud rate is usually determined by hardware for ACIA and - SIO interfaces +##### Supported Hardware (see [Appendix B - Device Summary]): + +- DSRTC +- UART +- SIO +- ACIA +- MD +- FD +- IDE +- PPIDE +- CTC + +##### Notes: + +- CPU speed will be dynamically measured at startup if DSRTC is present +- FD configured for 3.5" HD floppy drives + +`\clearpage`{=latex} + +### EP Mini-ITX Z180 + +#### ROM Image File: EPITX_std.rom + +| | | +|-------------------|---------------| +| Default CPU Speed | 18.432 MHz | +| Interrupts | Mode 2 | +| System Timer | Z180 | +| Serial Default | 115200 Baud | +| Memory Manager | Z180 | +| ROM Size | 512 KB | +| RAM Size | 512 KB | + +##### Supported Hardware (see [Appendix B - Device Summary]): + +- INTRTC +- ASCI +- UART +- TMS +- MD +- FD +- SD + +##### Notes: + +- FD configured for 3.5" HD floppy drives `\clearpage`{=latex} @@ -4504,6 +5098,9 @@ may be discovered by RomWBW in your system. | ASCI | Char | Zilog Z180 CPU Built-in Serial Ports | | AY | Audio | AY-3-8910/YM2149 Programmable Sound Generator | | BQRTC | RTC | BQ4845P Real Time Clock | +| CH | System | CH375/376 USB Controller | +| CHSD | Disk | CH37x SD Card Interface | +| CHUSB | Disk | CH37x USB Drive Interface | | CTC | System | Zilog Clock/Timer | | CVDU | Video | MC8563-based Video Display Controller | | DMA | System | Zilog DMA Controller | @@ -4513,10 +5110,12 @@ may be discovered by RomWBW in your system. | DUART | Char | SCC2681 or compatible Dual UART | | EMM | Disk | Disk drive on Parallel Port emm interface (Zip Drive) | | FD | Disk | 8272 or compatible Floppy Disk Controller | +| FP | System | Simple LED & Switch Front Panel | | GDC | Video | uPD7220 Video Display Controller | | HDSK | Disk | SIMH Simulator Hard Disk | -| IDE | Disk | IDE/ATA/ATAPI Hard Disk Interface | +| I2C | System | I2C Interface | | ICM | DsKy | ICM7218-based Display/Keypad on PPI | +| IDE | Disk | IDE/ATA/ATAPI Hard Disk Interface | | IMM | Disk | IMM Zip Drive on PPI | | INTRTC | RTC | Interrupt-based Real Time Clock | | KBD | Kbd | 8242 PS/2 Keyboard Controller | @@ -4524,16 +5123,15 @@ may be discovered by RomWBW in your system. | LPT | Char | Parallel I/O Controller | | MD | Disk | ROM/RAM Disk | | MSXKYB | Kbd | MSX Compliant Matrix Keyboard | -| I2C | System | I2C Interface | -| PIO | Char | Zilog Parallel Interface Controller | | PKD | DsKy | P8279-based Display/Keypad on PPI | -| PPIDE | Disk | 8255 IDE/ATA/ATAPI Hard Disk Interface | +| PIO | Char | Zilog Parallel Interface Controller | | PPA | Disk | PPA Zip Drive on PPI | +| PPIDE | Disk | 8255 IDE/ATA/ATAPI Hard Disk Interface | | PPK | Kbd | Matrix Keyboard | -| PPPSD | Disk | ParPortProp SD Card Interface | | PPPCON | Serial | ParPortProp Serial Console Interface | -| PRPSD | Disk | PropIO SD Card Interface | +| PPPSD | Disk | ParPortProp SD Card Interface | | PRPCON | Serial | PropIO Serial Console Interface | +| PRPSD | Disk | PropIO SD Card Interface | | RF | Disk | RAM Floppy Disk Interface | | RP5C01 | RTC | Ricoh RPC01A Real-Time Clock w/ NVRAM | | SD | Disk | SD Card Interface | diff --git a/Source/HBIOS/Config/RCZ280_zzrcc.asm b/Source/HBIOS/Config/RCZ280_zzrcc.asm index 220577e2..33a63785 100644 --- a/Source/HBIOS/Config/RCZ280_zzrcc.asm +++ b/Source/HBIOS/Config/RCZ280_zzrcc.asm @@ -28,7 +28,7 @@ ; #include "cfg_rcz280.asm" ; -CPUOSC .SET 14745600 ; CPU OSC FREQ IN MHZ +CPUOSC .SET 29491200 ; CPU OSC FREQ IN MHZ INTMODE .SET 3 ; INTERRUPTS: 0=NONE, 1=MODE 1, 2=MODE 2 CRTACT .SET FALSE ; ACTIVATE CRT (VDU,CVDU,PROPIO,ETC) AT STARTUP ; diff --git a/Source/HBIOS/Config/RCZ280_zzrcc_ram.asm b/Source/HBIOS/Config/RCZ280_zzrcc_ram.asm index b7bf48c6..ad0e9ea9 100644 --- a/Source/HBIOS/Config/RCZ280_zzrcc_ram.asm +++ b/Source/HBIOS/Config/RCZ280_zzrcc_ram.asm @@ -28,7 +28,7 @@ ; #include "cfg_rcz280.asm" ; -CPUOSC .SET 14745600 ; CPU OSC FREQ IN MHZ +CPUOSC .SET 29491200 ; CPU OSC FREQ IN MHZ INTMODE .SET 3 ; INTERRUPTS: 0=NONE, 1=MODE 1, 2=MODE 2 CRTACT .SET FALSE ; ACTIVATE CRT (VDU,CVDU,PROPIO,ETC) AT STARTUP ; diff --git a/Source/HBIOS/Config/RCZ80_zrc.asm b/Source/HBIOS/Config/RCZ80_zrc.asm index bdb2a0fc..8e9424ed 100644 --- a/Source/HBIOS/Config/RCZ80_zrc.asm +++ b/Source/HBIOS/Config/RCZ80_zrc.asm @@ -27,13 +27,15 @@ #DEFINE BOOT_DEFAULT "H" ; DEFAULT BOOT LOADER CMD ON OR AUTO BOOT ; #include "cfg_rcz80.asm" +; CPUOSC .SET 14745600 ; CPU OSC FREQ IN MHZ CRTACT .SET FALSE ; ACTIVATE CRT (VDU,CVDU,PROPIO,ETC) AT STARTUP ; FPLED_ENABLE .SET TRUE ; FP: ENABLES FRONT PANEL LEDS -FPSW_ENABLE .SET TRUE ; FP: ENABLES FRONT PANEL SWITCHES +FPSW_ENABLE .SET TRUE ; FP: ENABLES FRONT PANEL SWITCHES ; -RAMSIZE .SET 1536 ; SIZE OF RAM IN KB (MUST MATCH YOUR HARDWARE!!!) +RAMSIZE .SET 512 ; SIZE OF RAM IN KB (MUST MATCH YOUR HARDWARE!!!) +ROMSIZE .SET 256 ; SIZE OF ROM IN KB (MUST MATCH YOUR HARDWARE!!!) MEMMGR .SET MM_ZRC ; MEMORY MANAGER: MM_[SBC|Z2|N8|Z180] ; UARTENABLE .SET TRUE ; UART: ENABLE 8250/16550-LIKE SERIAL DRIVER (UART.ASM) diff --git a/Source/HBIOS/Config/RCZ80_zrc_ram.asm b/Source/HBIOS/Config/RCZ80_zrc_ram.asm index b520fba1..59993996 100644 --- a/Source/HBIOS/Config/RCZ80_zrc_ram.asm +++ b/Source/HBIOS/Config/RCZ80_zrc_ram.asm @@ -28,7 +28,7 @@ ; #include "cfg_rcz80.asm" ; -CPUOSC .SET 7372800 ; CPU OSC FREQ IN MHZ +CPUOSC .SET 14745600 ; CPU OSC FREQ IN MHZ CRTACT .SET FALSE ; ACTIVATE CRT (VDU,CVDU,PROPIO,ETC) AT STARTUP ; FPLED_ENABLE .SET TRUE ; FP: ENABLES FRONT PANEL LEDS @@ -50,7 +50,7 @@ TMSTIMENABLE .SET FALSE ; TMS: ENABLE TIMER INTERRUPTS (REQUIRES IM1) TMSMODE .SET TMSMODE_MSX ; TMS: DRIVER MODE: TMSMODE_[SCG|N8|MBC|MSX|MSX9958|MSXKBD|COLECO] MKYENABLE .SET FALSE ; MSX 5255 PPI KEYBOARD COMPATIBLE DRIVER (REQUIRES TMS VDA DRIVER) VRCENABLE .SET TRUE ; VRC: ENABLE VGARC VIDEO/KBD DRIVER (VRC.ASM) -VDAEMU_SERKBD .SET 0 ; VDA EMULATION: SERIAL KBD UNIT #, OR $FF FOR HW KBD +VDAEMU_SERKBD .SET $FF ; VDA EMULATION: SERIAL KBD UNIT #, OR $FF FOR HW KBD ; AY38910ENABLE .SET FALSE ; AY: AY-3-8910 / YM2149 SOUND DRIVER AYMODE .SET AYMODE_RCZ80 ; AY: DRIVER MODE: AYMODE_[SCG|N8|RCZ80|RCZ180|MSX|LINC] diff --git a/Source/HBIOS/cfg_zeta.asm b/Source/HBIOS/cfg_zeta.asm index df6ff3da..091f4bb5 100644 --- a/Source/HBIOS/cfg_zeta.asm +++ b/Source/HBIOS/cfg_zeta.asm @@ -28,7 +28,7 @@ BOOT_DELAY .EQU 0 ; FIXED BOOT DELAY IN SECONDS PRIOR TO CONSOLE OUTPUT ; CPUSPDCAP .EQU SPD_FIXED ; CPU SPEED CHANGE CAPABILITY SPD_FIXED|SPD_HILO CPUSPDDEF .EQU SPD_HIGH ; CPU SPEED DEFAULT SPD_UNSUP|SPD_HIGH|SPD_LOW -CPUOSC .EQU 20000000 ; CPU OSC FREQ IN MHZ +CPUOSC .EQU 8000000 ; CPU OSC FREQ IN MHZ INTMODE .EQU 0 ; INTERRUPTS: 0=NONE, 1=MODE 1, 2=MODE 2, 3=MODE 3 (Z280) DEFSERCFG .EQU SER_38400_8N1 | SER_RTS ; DEFAULT SERIAL LINE CONFIG (SEE STD.ASM) ; diff --git a/Source/HBIOS/std.asm b/Source/HBIOS/std.asm index 91bf211b..1cd47116 100644 --- a/Source/HBIOS/std.asm +++ b/Source/HBIOS/std.asm @@ -507,6 +507,25 @@ CPUKHZ .SET CPUKHZ / 2 ; Z180 PHI IS ALWAYS 1/2 OSC #ENDIF ; CPUMHZ .EQU CPUKHZ / 1000 ; CPU FREQ IN MHZ +; + .ECHO "ASSUMED CPU SPEED: " + .ECHO CPUKHZ + .ECHO " KHZ\r\n" +; + .ECHO "INTERRUPTS: " +#IF (INTMODE == 0) + .ECHO "NONE" +#ENDIF +#IF (INTMODE == 1) + .ECHO "MODE 1" +#ENDIF +#IF (INTMODE == 2) + .ECHO "MODE 2" +#ENDIF +#IF (INTMODE == 3) + .ECHO "MODE 3" +#ENDIF + .ECHO "\r\n" ; ; SYSTEM PERIODIC TIMER MODE ; @@ -564,6 +583,61 @@ SYSTIM .SET TM_Z280 .ECHO "\n" ; #ENDIF +; + .ECHO "DEFAULT SERIAL CONFIGURATION: " + +; .ECHO ((DEFSERCFG & %1111100000000) == SER_BAUD9600 + +#IF ((DEFSERCFG & %1111100000000) == SER_BAUD9600 + .ECHO "9600" +#ENDIF +#IF ((DEFSERCFG & %1111100000000) == SER_BAUD38400 + .ECHO "38400" +#ENDIF +#IF ((DEFSERCFG & %1111100000000) == SER_BAUD57600 + .ECHO "57600" +#ENDIF +#IF ((DEFSERCFG & %1111100000000) == SER_BAUD115200 + .ECHO "115200" +#ENDIF + .ECHO " BAUD\r\n" +; +; +; + .ECHO "MEMORY MANAGER: " +#IF (MEMMGR == MM_SBC) + .ECHO "N8VEM (SBC)" +#ENDIF +#IF (MEMMGR == MM_Z2) + .ECHO "ZETA 2 (Z2)" +#ENDIF +#IF (MEMMGR == MM_N8) + .ECHO "N8 ONBOARD (N8)" +#ENDIF +#IF (MEMMGR == MM_Z180) + .ECHO "Z180 NATIVE (Z180)" +#ENDIF +#IF (MEMMGR == MM_Z280) + .ECHO "Z280 NATIVE (Z280)" +#ENDIF +#IF (MEMMGR == MM_ZRC) + .ECHO "ZRC ONBOARD (ZRC)" +#ENDIF +#IF (MEMMGR == MM_MBC) + .ECHO "NHYODYNE (MBC)" +#ENDIF +#IF (MEMMGR == MM_RPH) + .ECHO "RHYOPHYRE ONBOARD (RPH)" +#ENDIF + .ECHO "\r\n" +; + .ECHO "ROM SIZE: " + .ECHO ROMSIZE + .ECHO " KB\r\n" +; + .ECHO "RAM SIZE: " + .ECHO RAMSIZE + .ECHO " KB\r\n" ; ; MEMORY BANK CONFIGURATION ; diff --git a/Source/ver.inc b/Source/ver.inc index 8b4e4d9e..cc253650 100644 --- a/Source/ver.inc +++ b/Source/ver.inc @@ -2,7 +2,7 @@ #DEFINE RMN 4 #DEFINE RUP 0 #DEFINE RTP 0 -#DEFINE BIOSVER "3.4.0-dev.24" +#DEFINE BIOSVER "3.4.0-dev.25" #define rmj RMJ #define rmn RMN #define rup RUP diff --git a/Source/ver.lib b/Source/ver.lib index 0944f99c..f3857cdc 100644 --- a/Source/ver.lib +++ b/Source/ver.lib @@ -3,5 +3,5 @@ rmn equ 4 rup equ 0 rtp equ 0 biosver macro - db "3.4.0-dev.24" + db "3.4.0-dev.25" endm