From db81d1a28b7ad4709f1572e355541815737504b2 Mon Sep 17 00:00:00 2001 From: Wayne Warthen Date: Thu, 12 Mar 2020 11:40:11 -0700 Subject: [PATCH] Add SC131 Support Also cleaned up some ReadMe files. --- Binary/DiskList.txt | 167 ++++++++++++++++++++++++++ Binary/ReadMe.txt | 24 ++-- Binary/RomList.txt | 7 +- ReadMe.txt | 16 +-- Source/HBIOS/Config/SCZ180_131.asm | 55 +++++++++ Source/HBIOS/Makefile | 1 + Source/Images/ReadMe.txt | 181 ++++++++--------------------- Source/ReadMe.txt | 40 +++++-- Source/ver.inc | 2 +- Source/ver.lib | 2 +- Tools/simh/Sim.cfg | 8 +- 11 files changed, 330 insertions(+), 173 deletions(-) create mode 100644 Binary/DiskList.txt create mode 100644 Source/HBIOS/Config/SCZ180_131.asm diff --git a/Binary/DiskList.txt b/Binary/DiskList.txt new file mode 100644 index 00000000..8ecedd63 --- /dev/null +++ b/Binary/DiskList.txt @@ -0,0 +1,167 @@ +*********************************************************************** +*** *** +*** R o m W B W *** +*** *** +*** Z80/Z180 System Software *** +*** *** +*********************************************************************** + +This directory ("Binary") is part of the RomWBW System Software +distribution archive. Refer to the ReadMe.txt file in this +directory for more information on the overall contents of the +directory. + +RomWBW includes a set of disk images that are ready to copy onto +a floppy or hard/CF/SD disk. You can use your modern computer +(Windows/Linux/Mac) to copy the disk image file onto your disk +media. The disk media will then be ready to use in your RomWBW +System. + +A description of the disk images is provided later in this file. +For more information on the creatioin of these images including +instructions for customizing them or creating your own, refer to +the ReadMe.txt file in the Source\Images directory. + +Installing Images +----------------- + +The following instructions apply to Windows computers. Alternatively, +you can use the "dd" command on Linux or Mac. + +First of all, a MAJOR WARNING!!!! The tools described below are +quite capable of obliterating your running Windows system drive. Use +with extreme caution and make sure you have backups. + +To install a floppy image on floppy media, you can use the tool +called RaWriteWin. This tool is included in the Tools directory of +the distribution. This tool will write your floppy image (fd_xxx.img) +to a floppy disk using a raw block transfer. The tool is GUI based +and it's operation is self explanatory. + +To install a hard disk image on a CF card or SD card, you must have +the appropriate media card slot on your computer. If you do, you can +use the tool called Win32DiskImager. This tool is also included in +the Tools directory of the distribution. It will write your +hard disk image (hd_xxx.img) to the designated media card. This tool +is also GUI based and self explanatory. + +The use of the SIMH emulator is outside of the scope of this document. +However, if you use SIMH, you will find that you can attach the hard +disk images to the emulator with lines such as the following in your +SIMH configuration file: + + | attach hdsk0 hd_cpm22.img + | set hdsk0 format=HDSK + | set hdsk0 geom=T:2048/N:256/S:512 + | set hdsk0 wrtenb + +Making Disk Images Bootable +--------------------------- + +The Operating System disk images below are ready to boot by the +RomWBW Boot Loader. However, if you update your RomWBW ROM, then +you should also update the system tracks of your bootable disk +images. You would use SYSCOPY to do this. SYSCOPY can also be +used to make a disk bootable if it is not already bootable. + +You would use a command like the following to make drive C bootable: + + | B>SYSCOPY C:=CPM.SYS + +The system file to use depends on the operating system you are trying +to boot from the slice you are initializing with SYSCOPY: + + CP/M 2.2 - cpm.sys + ZSDOS 1.1 - zsys.sys + CP/M 3 - cpmldr.sys + ZPM3 - cpmldr.sys + +Slices +------ + +A RomWBW CP/M filesystem is fixed at 8MB. This is because it is the +largest size filesystem supported by all common CP/M variants. Since +all modern hard disks (including SD Cards and CF Cards) are much +larger than 8MB, RomWBW supports the concept of "slices". This +simply means that you can concatenate multiple CP/M filesystems (up +to 256 of them) on a single physical hard disk and RomWBW will allow +you to assign drive letters to them and treat them as multiple +independent CP/M drives. + +With the exception of the hd_combo image, each of the disk images +includes a single CP/M file system (i.e., a single slice). However, +you can easily create a multi-slice disk image by merely concatenating +multiple images together. For example, if you wanted to create a 2 +slice disk image that has ZSDOS in the first slice and Wordstar in +the second slice, you could use the following command from a Windows +command prompt: + + | C:\RomWBW\Binary>copy /b hd_zsdos.img + hd_ws.img hd_multi.img + +You can now write hd_multi.img onto your SD or CF Card and you will +have ZSDOS in the first slice and Wordstar in the second slice. + +The hd_combo disk image is an example of this. It contains several +slices in one image file. The contents of this special disk image +are described below. + +The concept of slices applies ONLY to hard disks. Floppy disks are +not large enough to support multiple slices. + +Disk Image Contents +------------------- + +What follows is a brief description of the contents of the +disk images automatically provided in the RomWBW distribution. +Note that all of the OS images include the RomWBW custom +support apps. + +cpm22 - DRI CP/M 2.2 (Bootable Floppy and Hard Disk) + + Standard DRI CP/M 2.2 distribution files along with a few commonly + used utilities. + +zsdos - ZCPR1 + ZSDOS 1.1 (Bootable Floppy and Hard Disk) + + Contains ZCPR1 and ZSDOS 1.1. This is roughly equivalent to the + ROM boot contents, but provides a full set of the applications + and related files that would not all fit on the ROM drive. + +nzcom - NZCOM (Bootable Floppy and Hard Disk) + + Standard NZCOM distribution. Note that you will need to run the + NZCOM setup before this will run properly. You will need + to refer to the NZCOM documentation. + +cpm3 - DRI CP/M3 (Bootable Floppy and Hard Disk) + + Standard DRI CP/M 3 adaptation for RomWBW that is ready to run. + It can be started by running CPMLDR. + +zpm3 - ZPM3 (Bootable Floppy and Hard Disk) + + Simeon Cran's ZCPR 3 compatible OS for CP/M 3 adapted for RomWBW and + ready to run. It can be started by running CPMLDR (which seems + wrong, but ZPMLDR is somewhat broken). + +ws4 - WordStar 4 (Floppy and Hard Disk) + + Micropro Wordstar 4 full distribution. This image is not bootable + and is intended to be added as an additional slice to an OS image. + +bp - BPBIOS (Hard Disk only) + + Adaptation of BPBIOS for RomWBW. This is NOT complete and NOT + useable in it's current state. + +combo - Multi-Boot Combination (Bootable Hard Disk) + + A pre-created combo image that contains the following slices. The + slices are identical to the individual images listed above. + + Slice 0: cpm22 (bootable) + Slice 1: zsdos (bootable) + Slice 2: nzcom (bootable) + Slice 3: cpm3 (bootable) + Slice 4: zpm3 (bootable) + Slice 5: ws4 (not bootable) diff --git a/Binary/ReadMe.txt b/Binary/ReadMe.txt index 9a0be0d4..70156630 100644 --- a/Binary/ReadMe.txt +++ b/Binary/ReadMe.txt @@ -48,28 +48,17 @@ ROM Executable Images (_.com) When a ROM image (".rom") is created, an executable version of the ROM is also created. These files have the same naming convention as the ROM Image files, but have the extension ".com". These files can -be copied to a working system and run like a normal application. +be copied to a working system and run like a normal CP/M application. When run on the target system, they install in RAM just like they had -been programmed into the ROM. This allows a new ROM build to be -tested without reprogramming the actual ROM. +been loaded from ROM. This allows a new ROM build to be tested +without reprogramming the actual ROM. WARNING: In a few cases the .com file is too big to load. If you get a message like "Full" or "BAD LOAD" when trying to load one of the .com files, it is too big. In these cases, you will not be able to test the ROM prior to programming it. -ROM Binary Images (_.img) ------------------------------------ - -Also when a ROM image is created, a third variation of the ROM is -created again with the same naming convention, but with the extension -of .img. These files are similar to the .com files in that they can -be used to test a ROM build without actually programming a new ROM. -The .img files are specifically for loading via UNA from a FAT file -system. The functionality of the UNA FAT file system loader is -beyond the scope of this document. - VDU ROM Image (vdu.rom) ----------------------- @@ -103,10 +92,13 @@ intended to be copied to the start of any type of hard disk media (typically a CF Card or SD Card). The resulting media will be usable on any RomWBW-based system that accepts the corresponding media type. -Note that the contents of the floppy/hard disk images are created by +Documentation of the pre-built disk images is contained in the +DiskList.txt file in this directory. + +The contents of the floppy/hard disk images are created by the BuildImages.cmd script in the Source directory. Additional information on how to generate custom disk images is found in the -Source\Images directory. +Source\Images ReadMe.txt file. Propeller ROM Images (*.eeprom) ------------------------------- diff --git a/Binary/RomList.txt b/Binary/RomList.txt index 16562db5..5a380395 100644 --- a/Binary/RomList.txt +++ b/Binary/RomList.txt @@ -191,7 +191,7 @@ RCZ180 (RCZ180_nat.rom & RCZ180_ext.rom): - RCZ180_ext.rom uses external bank management to access memory, such as the 512K RAM/ROM module. -SCZ180 (SCZ180_126.rom & SCZ180_130.rom): +SCZ180 (SCZ180_126.rom, SCZ180_130.rom, SCZ180_131.rom): - Assumes CPU oscillator of 18.432 MHz - Console on Z180 onboard primary ASCI serial port at 115200 baud - Includes support for Compact Flash Module @@ -199,8 +199,9 @@ SCZ180 (SCZ180_126.rom & SCZ180_130.rom): - Support for alternative serial modules may be enabled in config - Support for Scott Baker floppy controllers (SMC & WDC) may be enabled in config - - The _126 and _130 variants are functionally identical, they just - display a different system label at startup + - The 3 different variants of SCZ180 are provided to match the + 3 corresponding systems (SC126, SC130, and SC131) designed by + Stephen Cousins. EZZ80 (EZZ80_std.rom): - Assumes CPU oscillator of 10.000 MHz diff --git a/ReadMe.txt b/ReadMe.txt index bbb625f3..3140b02f 100644 --- a/ReadMe.txt +++ b/ReadMe.txt @@ -7,7 +7,7 @@ *********************************************************************** Wayne Warthen (wwarthen@gmail.com) -Version 2.9.2-pre.34, 2020-03-05 +Version 2.9.2-pre.35, 2020-03-12 https://www.retrobrewcomputers.org/ RomWBW is a ROM-based implementation of CP/M-80 2.2 and Z-System for @@ -26,8 +26,8 @@ Pre-built ROM images are included for all platforms. Detailed system customization is achieved by making simple modifications to a configuration file and running a build script to generate a custom ROM image. All source and build tools are included in the -distribution. As distributed, the build scripts run under any modern -32 or 64 bit version of Microsoft Windows. +distribution. Build scripts are provided for most modern computers +including Windows (32 or 64 bit compatible), Linux, or Mac. John Coffman's UNA hardware BIOS is fully supported by RomWBW. In the case of UNA, a single ROM image (pre-built) is used for all supported @@ -215,10 +215,12 @@ customize your ROM image to include support for the added board(s). Essentially, the creation of a custom ROM is accomplished by updating a small configuration file, then running a script to compile the -software and generate the custom ROM image. At this time, the build -process runs on Windows 32 or 64 bit versions. All tools (compilers, -assemblers, etc.) are included in the distribution, so it is not -necessary to setup a build environment on your computer. +software and generate the custom ROM image. + +Build scripts are provided for Windows (32 or 64 bit versions), Linux, +and Mac. All tools (compilers, assemblers, etc.) are included in the +distribution, so it is not necessary to setup a build environment +on your computer. For those who are interested in more than basic system customization, note that all source code is included (including the operating diff --git a/Source/HBIOS/Config/SCZ180_131.asm b/Source/HBIOS/Config/SCZ180_131.asm new file mode 100644 index 00000000..7824f728 --- /dev/null +++ b/Source/HBIOS/Config/SCZ180_131.asm @@ -0,0 +1,55 @@ +; +;================================================================================================== +; SC131 STANDARD CONFIGURATION +;================================================================================================== +; +; THE COMPLETE SET OF DEFAULT CONFIGURATION SETTINGS FOR THIS PLATFORM ARE FOUND IN THE +; CFG_.ASM INCLUDED FILE WHICH IS FOUND IN THE PARENT DIRECTORY. THIS FILE CONTAINS +; COMMON CONFIGURATION SETTINGS THAT OVERRIDE THE DEFAULTS. IT IS INTENDED THAT YOU MAKE +; YOUR CUSTOMIZATIONS IN THIS FILE AND JUST INHERIT ALL OTHER SETTINGS FROM THE DEFAULTS. +; EVEN BETTER, YOU CAN MAKE A COPY OF THIS FILE WITH A NAME LIKE _XXX.ASM AND SPECIFY +; YOUR FILE IN THE BUILD PROCESS. +; +; THE SETTINGS BELOW ARE THE SETTINGS THAT ARE MOST COMMONLY MODIFIED FOR THIS PLATFORM. +; MANY OF THEM ARE EQUAL TO THE SETTINGS IN THE INCLUDED FILE, SO THEY DON'T REALLY DO +; ANYTHING AS IS. THEY ARE LISTED HERE TO MAKE IT EASY FOR YOU TO ADJUST THE MOST COMMON +; SETTINGS. +; +; N.B., SINCE THE SETTINGS BELOW ARE REDEFINING VALUES ALREADY SET IN THE INCLUDED FILE, +; TASM INSISTS THAT YOU USE THE .SET OPERATOR AND NOT THE .EQU OPERATOR BELOW. ATTEMPTING +; TO REDEFINE A VALUE WITH .EQU BELOW WILL CAUSE TASM ERRORS! +; +; PLEASE REFER TO THE CUSTOM BUILD INSTRUCTIONS (README.TXT) IN THE SOURCE DIRECTORY (TWO +; DIRECTORIES ABOVE THIS ONE). +; +#DEFINE PLATFORM_NAME "SC131" +; +#include "cfg_scz180.asm" +; +CPUOSC .SET 18432000 ; CPU OSC FREQ IN MHZ +; +Z180_CLKDIV .SET 1 ; Z180: CHK DIV: 0=OSC/2, 1=OSC, 2=OSC*2 +Z180_MEMWAIT .SET 0 ; Z180: MEMORY WAIT STATES (0-3) +Z180_IOWAIT .SET 1 ; Z180: I/O WAIT STATES TO ADD ABOVE 1 W/S BUILT-IN (0-3) +; +LEDENABLE .SET TRUE ; ENABLES STATUS LED (SINGLE LED) +; +DIAGENABLE .SET FALSE ; ENABLES OUTPUT TO 8 BIT LED DIAGNOSTIC PORT +; +DSRTCENABLE .SET FALSE ; DSRTC: ENABLE DS-1302 CLOCK DRIVER (DSRTC.ASM) +; +ASCIENABLE .SET TRUE ; ASCI: ENABLE Z180 ASCI SERIAL DRIVER (ASCI.ASM) +; +ACIAENABLE .SET FALSE ; ACIA: ENABLE MOTOROLA 6850 ACIA DRIVER (ACIA.ASM) +; +SIOENABLE .SET FALSE ; SIO: ENABLE ZILOG SIO SERIAL DRIVER (SIO.ASM) +; +FDENABLE .SET FALSE ; FD: ENABLE FLOPPY DISK DRIVER (FD.ASM) +FDMODE .SET FDMODE_RCWDC ; FD: DRIVER MODE: FDMODE_[DIO|ZETA|DIDE|N8|DIO3] +; +IDEENABLE .SET FALSE ; IDE: ENABLE IDE DISK DRIVER (IDE.ASM) +; +PPIDEENABLE .SET FALSE ; PPIDE: ENABLE PARALLEL PORT IDE DISK DRIVER (PPIDE.ASM) +; +SDENABLE .SET TRUE ; SD: ENABLE SD CARD DISK DRIVER (SD.ASM) +; diff --git a/Source/HBIOS/Makefile b/Source/HBIOS/Makefile index d33fb0ae..1c5bb84c 100644 --- a/Source/HBIOS/Makefile +++ b/Source/HBIOS/Makefile @@ -17,6 +17,7 @@ OBJECTS += SCZ180_126.rom SCZ180_126.com OBJECTS += SCZ180_126_mtx.rom SCZ180_126_mtx.com OBJECTS += SCZ180_130.rom SCZ180_130.com OBJECTS += SCZ180_130_mtx.rom SCZ180_130_mtx.com +OBJECTS += SCZ180_131.rom SCZ180_131.com OBJECTS += UNA_std.rom OBJECTS += ZETA_std.rom ZETA_std.com OBJECTS += ZETA2_std.rom ZETA2_std.com diff --git a/Source/Images/ReadMe.txt b/Source/Images/ReadMe.txt index b4fea94a..fb4338e2 100644 --- a/Source/Images/ReadMe.txt +++ b/Source/Images/ReadMe.txt @@ -26,6 +26,9 @@ PowerShell. It is included in all versions after Windows XP. If you are using Windows XP, you will need to download it from Microsoft and install it (free download). +Although not documented here, the Linux/Mac build process will also +create disk images using a similar process based on Makefiles. + The cpmtools toolset is used to generate the actual disk images. This toolset is included in the distribution, so you do not need to download or install it. @@ -89,6 +92,54 @@ BuildHD.cmd with a single parameter specifying the disk name. After completion of the script, the resultant image files are placed in the Binary directory with names such as fd_xxx.img and hd_xxx.img. +Sample output from running Build.cmd is provided at the end of +this file. + +Be aware that the script always builds the image file from scratch. +It will not update the previous contents. Any contents of a +pre-existing image file will be permanently destroyed. + +Slices +------ + +A RomWBW CP/M filesystem is fixed at 8MB. This is because it is the +largest size filesystem supported by all common CP/M variants. Since +all modern hard disks (including SD Cards and CF Cards) are much +larger than 8MB, RomWBW supports the concept of "slices". This +simply means that you can concatenate multiple CP/M filesystems (up +to 256 of them) on a single physical hard disk and RomWBW will allow +you to assign drive letters to them and treat them as multiple +independent CP/M drives. + +The disk image creation scripts in this directory will only create a +single CP/M file system (i.e., a single slice). However, you can +easily create a multi-slice disk image by merely concatenating +multiple images together. For example, if you wanted to create a 2 +slice disk image that has ZSDOS in the first slice and Wordstar in +the second slice, you could use the following command from a Windows +command prompt: + + | C:\RomWBW\Binary>copy /b hd_zsdos.img + hd_ws.img hd_multi.img + +You can now write hd_multi.img onto your SD or CF Card and you will +have ZSDOS in the first slice and Wordstar in the second slice. + +The concept of slices applies ONLY to hard disks. Floppy disks are +not large enough to support multiple slices. + +Disk Images +----------- + +The standard RomWBW build process builds the disk images defined +in this directory. The resultant images are placed in the Binary +directory and are ready to copy to your media. + +A description of the specific image files is found in the file +called DiskList.txt in the Binary directory of the distribution. + +Sample Run +---------- + Below is sample output from building the hard disk images: C:\Users\Wayne\Projects\RBC\Build\RomWBW\Source\Images>Build.cmd @@ -408,133 +459,3 @@ C:\Users\Wayne\Projects\RBC\Build\RomWBW\Source\Images>Build.cmd | cpmcp -f wbw_hd0 hd_ws4.img d_ws4/u0/*.* 0: | Moving image hd_ws4.img into output directory... | 1 file(s) moved. - -Be aware that the script always builds the image file from scratch. -It will not update the previous contents. Any contents of a -pre-existing image file will be permanently destroyed. - -Installing Images ------------------ - -First of all, a MAJOR WARNING!!!! The tools described below are -quite capable of obliterating your running Windows system drive. Use -with extreme caution and make sure you have backups. - -To install a floppy image on floppy media, you can use the tool -called RaWriteWin. This tool is included in the Tools directory of -the distribution. This tool will write your floppy image (fd_xxx.img) -to a floppy disk using a raw block transfer. The tool is GUI based -and it's operation is self explanatory. - -To install a hard disk image on a CF card or SD card, you must have -the appropriate media card slot on your computer. If you do, you can -use the tool called Win32 Disk Imager. This tool is also included in -the Tools directory of the distribution. This tool will write your -hard disk image (hd_xxx.img) to the designated media card. This tool -is also GUI based and self explanatory. - -Use of the SIMH emulator is outside of the scope of this document. -However, if you use SIMH, you will find that you can attach the hard -disk images to the emulator with lines such as the following in your -SIMH configuration file: - - | attach hdsk0 hd_cpm22.img - | set hdsk0 format=HDSK - | set hdsk0 geom=T:520/N:256/S:512 - | set hdsk0 wrtenb - -Making Disk Images Bootable ---------------------------- - -The current generation of these scripts does not make the resultant -media bootable. This is primarily because there are multiple choices -for what you can put on the boot tracks of the media and that is a -choice best left to the user. - -The simplest way to make a resultant image bootable is to do it from -your running CP/M system. Boot your system using the ROM selection, -then use the SYSCOPY command to make the desired drive bootable. - -You would use a command like the following to make drive C bootable: - - | B>SYSCOPY C:=CPM.SYS - -Slices ------- - -A RomWBW CP/M filesystem is fixed at 8MB. This is because it is the -largest size filesystem supported by all common CP/M variants. Since -all modern hard disks (including SD Cards and CF Cards) are much -larger than 8MB, RomWBW supports the concept of "slices". This -simply means that you can concatenate multiple CP/M filesystems (up -to 256 of them) on a single physical hard disk and RomWBW will allow -you to assign drive letters to them and treat them as multiple -independent CP/M drives. - -The disk image creation scripts in this directory will only create a -single CP/M file system (i.e., a single slice). However, you can -easily create a multi-slice disk image by merely concatenating -multiple images together. For example, if you wanted to create a 2 -slice disk image that has ZSDOS in the first slice and Wordstar in -the second slice, you could use the following command from a Windows -command prompt: - - | C:\RomWBW\Binary>copy /b hd_zsdos.img + hd_ws.img hd_multi.img - -You can now write hd_multi.img onto your SD or CF Card and you will -have ZSDOS in the first slice and Wordstar in the second slice. - -The concept of slices applies ONLY to hard disks. Floppy disks are -not large enough to support multiple slices. - -Disk Images ------------ - -RomWBW comes with several disk images. These disk images are -created from this directory using the process described above. -This is a brief description of the disk images: - -cpm22 - DRI CP/M 2.2 (Floppy and Hard Disk) - -Standard DRI CP/M 2.2 distribution files along with a few commonly -used utilities. - -zsdos - ZCPR1 + ZSDOS 1.1 (Floppy and Hard Disk) - -Contains ZCPR1 and ZSDOS 1.1. This is roughly equivalent to the -ROM boot contents, but provides a full set of the applications -are related files that would not all fit on the ROM drive. - -nzcom - NZCOM (Floppy and Hard Disk) - -Standard NZCOM distribution. Note that you will need to run the -NZCOM setup before this will run properly. You will need -to refer to the NZCOM documentation. - -cpm3 - DRI CP/M3 (Floppy and Hard Disk) - -Standard DRI CP/M 3 adaptation for RomWBW that is ready to run. -It can be started by running CPMLDR. - -zpm3 - ZPM3 (Floppy and Hard Disk) - -Simeon Cran's ZCPR 3 compatible OS for CP/M 3 adapted for RomWBW and -ready to run. It can be started by running CPMLDR (which seems -wrong, but ZPMLDR is somewhat broken). - -ws4 - WorkStar 4 (Floppy and Hard Disk) - -Micropro Wordstar 4 full distribution. - -bp - BPBIOS (Hard Disk only) - -Adaptation of BPBIOS for RomWBW. This is not complete and NOT -useable in it's current state. - -Notes ------ - -I realize these instructions are very minimal. I am happy to answer -questions. You will find the RetroBrew Computers Forum at -https://www.retrobrewcomputers.org/forum/ to be a great source of -information as well. \ No newline at end of file diff --git a/Source/ReadMe.txt b/Source/ReadMe.txt index 50f41b8c..7f3895b2 100644 --- a/Source/ReadMe.txt +++ b/Source/ReadMe.txt @@ -26,16 +26,19 @@ Thought not necessary, advanced users can easily modify any of the software including the operating systems. A cross-platform approach is used to build the RomWBW firmware. -The software is built using a Microsoft Windows computer, then the -resulting firmware image is programmed into the ROM of your -RetroBrew Computer CPU board. +The software is built using a modern Windows, Linux, or Mac +computer, then the resulting firmware image is programmed into +the ROM of your RetroBrew Computer CPU board. Build System Requirements ------------------------- -All that is required to build the firmware is a computer running -Microsoft Windows and the RomWBW distribution zip archive file. -The zip archive package includes all of the required source code +For Linux/Mac computers, refer to the ReadMe.unix file in the +top directory of the distribution. + +For Microsoft Windows computers, All that is required to build the +firmware is the RomWBW distribution zip archive file. The zip +archive package includes all of the required source code (including the operating systems) and the programs required to run the build. @@ -101,7 +104,7 @@ to determine the component of the configuration filename: RC2014 w/ Z80 RCZ80_std.rom RC2014 w/ Z180 RCZ180_nat.rom (native Z180 memory addressing) RC2014 w/ Z180 RCZ180_ext.rom (external 512K RAM/ROM module) - SCZ180 SC126, SC130 + SCZ180 SC126, SC130, SC131 Easy Z80 EZZ180_std.rom Dyno DYNO_std.rom @@ -161,6 +164,11 @@ to free up some space. 3. Run the Build Process ------------------------ +This section describes the build process for Microsoft Windows +computers. The build process for Linux/Mac computers is described +in the ReadMe.unix file in the top level directory of the +distribution. + The build involves running commands at the command prompt. Open a command prompt window for the Source directory. If you unzipped the distribution to "C:\", then your command prompt should look @@ -237,6 +245,19 @@ used: SD occupies 2191 bytes. HBIOS space remaining: 21434 bytes. +Optionally, you can run one more command that will create the +RomWBW disk images that can be subsequently written to actual +disk media. + + C:\RomWBW\Source> BuildImages + +After running this command, you will find the resultant +disk image file in the Binary directory with names in the +format fd_xxx.img for floppy media or hd_xxx.img for +hard disk media. Refer to the DiskList.txt file in the +Binary directory for more information on using the disk +image files. + 4. Deploy the ROM ----------------- @@ -251,9 +272,6 @@ Three output files will be created for a single BuildROM run: _.com - executable version of the system image that can be copied via X-Modem to a running system to test the build. - _.img - system image that can be written to an - SD/CF Card and loaded via the UNA FS FAT - loader. The actual ROM image is the file ending in .rom. It should be exactly 512KB. Simply burn the .rom image to your ROM and install @@ -267,7 +285,7 @@ information on the other two file extensions created. Specifying Build Options on Command Line ---------------------------------------- -If you don't want to be prompteded for the options to the "BuildROM" +If you don't want to be prompted for the options to the "BuildROM" command, you can specify the options right on the command line. For example: diff --git a/Source/ver.inc b/Source/ver.inc index 67178022..dda78577 100644 --- a/Source/ver.inc +++ b/Source/ver.inc @@ -2,4 +2,4 @@ #DEFINE RMN 9 #DEFINE RUP 2 #DEFINE RTP 0 -#DEFINE BIOSVER "2.9.2-pre.34" +#DEFINE BIOSVER "2.9.2-pre.35" diff --git a/Source/ver.lib b/Source/ver.lib index 9f3f8d3b..870f44ee 100644 --- a/Source/ver.lib +++ b/Source/ver.lib @@ -3,5 +3,5 @@ rmn equ 9 rup equ 2 rtp equ 0 biosver macro - db "2.9.2-pre.34" + db "2.9.2-pre.35" endm diff --git a/Tools/simh/Sim.cfg b/Tools/simh/Sim.cfg index 7a8d6d04..8c8af2bf 100644 --- a/Tools/simh/Sim.cfg +++ b/Tools/simh/Sim.cfg @@ -23,12 +23,12 @@ attach n8vem0 %1 ; hard disks ;set hdsk debug=read;write;verbose -attach hdsk0 ..\..\Binary\hd0.img -attach hdsk1 ..\..\Binary\hd1.img +attach hdsk0 ..\..\Binary\hd_combo.img +attach hdsk1 ..\..\Binary\hd_combo.img set hdsk0 format=HDSK set hdsk1 format=HDSK -set hdsk0 geom=T:520/N:256/S:512 -set hdsk1 geom=T:520/N:256/S:512 +set hdsk0 geom=T:2048/N:256/S:512 +set hdsk1 geom=T:2048/N:256/S:512 set hdsk0 wrtenb set hdsk1 wrtenb