Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
playground:wwarthen:start [2018/01/31 20:26]
wwarthen
playground:wwarthen:start [2018/09/13 23:40] (current)
wwarthen
Line 10: Line 10:
 **Download:​** **Download:​**
  
-  ​* [[https://​www.retrobrewcomputers.org/​lib/​exe/​fetch.php?​media=software:​firmwareos:​romwbw:​romwbw-2.9.0-package.zip|RomWBW v2.9.0 Distribution Package]]+   * [[https://​www.retrobrewcomputers.org/​lib/​exe/​fetch.php?​media=software:​firmwareos:​romwbw:​romwbw-2.9.0-package.zip|RomWBW v2.9.0 Distribution Package]]
   * [[https://​www.retrobrewcomputers.org/​lib/​exe/​fetch.php?​media=software:​firmwareos:​romwbw:​romwbw_architecture.pdf|RomWBW Architecture Document]]   * [[https://​www.retrobrewcomputers.org/​lib/​exe/​fetch.php?​media=software:​firmwareos:​romwbw:​romwbw_architecture.pdf|RomWBW Architecture Document]]
  
Line 37: Line 37:
 RomWBW is distributed as a package (zip archive) containing the pre-built ROM images, source code, and all required build tools. To use a pre-built ROM image, download the distribution package to a modern computer (Windows, Mac, Linux, etc.). Unzip the archive using any of the common zip management applications. You will see that the distribution is broken up into a few sub-directories. The Binary directory contains the pre-built ROM images. Based on the table below, pick the appropriate ROM image: RomWBW is distributed as a package (zip archive) containing the pre-built ROM images, source code, and all required build tools. To use a pre-built ROM image, download the distribution package to a modern computer (Windows, Mac, Linux, etc.). Unzip the archive using any of the common zip management applications. You will see that the distribution is broken up into a few sub-directories. The Binary directory contains the pre-built ROM images. Based on the table below, pick the appropriate ROM image:
  
-^**Platform**^**ROM Image File**^**Built-in Device Support** ​                                                                             ^ +^**Platform** ^**ROM Image File** ^**Built-in Device Support** ​  | 
-|SBC V1/V2   ​|SBC_std.rom ​      ​|Supports onboard PPIDE disk, VGA3/CVDU video/kbd, PropIO (video, kbd, SD Card)                           ​+|SBC V1/V2  |SBC_std.rom ​ |Supports onboard PPIDE disk, VGA3/CVDU video/kbd, PropIO (video, kbd, SD Card)  
-|Zeta V1 ​    |ZETA_std.rom ​     |Supports ParPortProp (video, kbd, SD Card)                                                               ​+|Zeta V1  ​|ZETA_std.rom ​ |Supports ParPortProp (video, kbd, SD Card)  
-|Zeta V2 ​    |ZETA2_std.rom ​    ​|Supports ParPortProp (video, kbd, SD Card)                                                               ​+|Zeta V2  ​|ZETA2_std.rom ​ |Supports ParPortProp (video, kbd, SD Card)  
-|N8          |N8_std.rom ​       |Supports onboard SD Card, video, keyboard; production board assumed (date code >= 2312)                  +|N8  |N8_std.rom ​ |Supports onboard SD Card, video, keyboard; production board assumed (date code >= 2312)  
-|Mark IV ​    |MK4_std.rom ​      ​|Supports onboard SD Card, IDE Disk, VGA3/CVDU video/kbd, PropIO (video, kbd, SD Card)                    +|Mark IV  ​|MK4_std.rom ​ |Supports onboard SD Card, IDE Disk, VGA3/CVDU video/kbd, PropIO (video, kbd, SD Card)  
-|RC2014 ​     |RC_std.rom ​       |Requires Scott Baker 512KB RAM/ROM module; supports ACIA, SIO/2, Compact Flash, PPIDE, and Floppy modules|+|RC2014 ​ |RC_std.rom ​ |Requires Scott Baker 512KB RAM/ROM module; supports ACIA, SIO/2, Compact Flash, PPIDE, and Floppy modules|
  
-Your system does **not** need to have all the devices listed above to use the pre-built ROM. The devices will be detected and used only if present. All you need to have is the CPU board with ROM/RAM and a serial port. All pre-built ROM images are simple 512KB binary images. If your system utilizes a 1MB ROM, you can just program the image into the first 512KB of the ROM. The ReadMe.txt file in the Binary directory has more detailed information on the pre-built ROM images.+Your system does **not** ​ need to have all the devices listed above to use the pre-built ROM. The devices will be detected and used only if present. All you need to have is the CPU board with ROM/RAM and a serial port. All pre-built ROM images are simple 512KB binary images. If your system utilizes a 1MB ROM, you can just program the image into the first 512KB of the ROM. The ReadMe.txt file in the Binary directory has more detailed information on the pre-built ROM images.
  
 Connect a serial terminal or computer with terminal emulation software to the primary RS-232 port of your CPU board. A null-modem connection will generally be required. Set the line characteristics to 38400 baud, 8 data bits, 1 stop bit, no parity, and no flow control. Select VT-100 terminal emulation. RC2014 serial port baud rate is determined by hardware, but is typically 115200 baud. Connect a serial terminal or computer with terminal emulation software to the primary RS-232 port of your CPU board. A null-modem connection will generally be required. Set the line characteristics to 38400 baud, 8 data bits, 1 stop bit, no parity, and no flow control. Select VT-100 terminal emulation. RC2014 serial port baud rate is determined by hardware, but is typically 115200 baud.
Line 68: Line 68:
  ​B>​SYSCOPY C:​=B:​ZSYS.SYS  ​B>​SYSCOPY C:​=B:​ZSYS.SYS
 </​code>​ </​code>​
 +
 If you have copies of any of the system utilities on drives other than the ROM disk drive, you need to copy the latest version of the programs from the ROM drive (B:) to any drives containing these programs. For example, if you have a copy of the ASSIGN.COM program on C:, you would update it from the new ROM using the COPY command: If you have copies of any of the system utilities on drives other than the ROM disk drive, you need to copy the latest version of the programs from the ROM drive (B:) to any drives containing these programs. For example, if you have a copy of the ASSIGN.COM program on C:, you would update it from the new ROM using the COPY command:
  
Line 73: Line 74:
  ​B>​COPY B:​ASSIGN.COM C:  ​B>​COPY B:​ASSIGN.COM C:
 </​code>​ </​code>​
 +
 The following programs are maintained with the ROM images and all copies of these programs should be updated when upgrading to a new ROM version: The following programs are maintained with the ROM images and all copies of these programs should be updated when upgrading to a new ROM version:
  
Line 91: Line 93:
 The following custom applications are included on the ROM disk to enhance the operation of RomWBW: The following custom applications are included on the ROM disk to enhance the operation of RomWBW:
  
-^**Appplication**^**Description** ​                                                                                                                    ^ +^**Appplication** ^**Description** ​  | 
-|ASSIGN.COM ​     |Add, change, and delete drive letter assignments. Use ASSIGN /? for usage instructions. ​                                            ​+|ASSIGN.COM ​ |Add, change, and delete drive letter assignments. Use ASSIGN /? for usage instructions. ​ 
-|SYSCOPY.COM ​    ​|Copy system image to a device to make it bootable. Use SYSCOPY with no parms for usage instructions. ​                               +|SYSCOPY.COM ​ |Copy system image to a device to make it bootable. Use SYSCOPY with no parms for usage instructions. ​ 
-|FDU.COM ​        ​|Format and test floppy disks. Menu driven interface. ​                                                                               +|FDU.COM ​ |Format and test floppy disks. Menu driven interface. ​ 
-|OSLDR.COM ​      ​|Load a new OS on the fly. For example, you can switch to Z-System when running CP/M. Use OSLDR with no parms for usage instructions.| +|OSLDR.COM ​ |Load a new OS on the fly. For example, you can switch to Z-System when running CP/M. Use OSLDR with no parms for usage instructions.| 
-|FORMAT.COM ​     |Will someday be a command line tool to format floppy disks. Currently does nothing! ​                                                ​+|FORMAT.COM ​ |Will someday be a command line tool to format floppy disks. Currently does nothing! ​ 
-|MODE.COM ​       |Reconfigures serial ports dynamically. ​                                                                                             +|MODE.COM ​ |Reconfigures serial ports dynamically. ​ 
-|XM.COM ​         |XModem file transfer program adapted to hardware. Automatically uses primary serial port on system. ​                                ​+|XM.COM ​ |XModem file transfer program adapted to hardware. Automatically uses primary serial port on system. ​ 
-|FLASH.COM ​      ​|Will Sowerbutts’ in-situ ROM programming utility. ​                                                                                  ​|+|FLASH.COM ​ |Will Sowerbutts’ in-situ ROM programming utility. ​ |
  
 Please see the [[https://​www.retrobrewcomputers.org/​doku.php?​id=software:​firmwareos:​romwbw:​apps|RomWBW Applications]] page for more information on using these applications. Please see the [[https://​www.retrobrewcomputers.org/​doku.php?​id=software:​firmwareos:​romwbw:​apps|RomWBW Applications]] page for more information on using these applications.
Line 107: Line 109:
 ===== UNA Hardware BIOS ===== ===== UNA Hardware BIOS =====
  
-John Coffman has produced a new generation of hardware BIOS called UNA. The standard RomWBW distribution includes it’s own hardware BIOS. However, RomWBW can alternatively be constructed with UNA as the hardware BIOS portion of the ROM. If you wish to use the UNA variant of RomWBW, then just program your ROM with the ROM image called “UNA_std.rom” in the Binary directory. This one image is suitable on **all** of the platforms and hardware UNA supports.+John Coffman has produced a new generation of hardware BIOS called UNA. The standard RomWBW distribution includes it’s own hardware BIOS. However, RomWBW can alternatively be constructed with UNA as the hardware BIOS portion of the ROM. If you wish to use the UNA variant of RomWBW, then just program your ROM with the ROM image called “UNA_std.rom” in the Binary directory. This one image is suitable on **all** ​ of the platforms and hardware UNA supports.
  
 UNA is customized dynamically using a ROM based setup routine and the setup is persisted in the system NVRAM of the RTC chip. This means that the single UNA-based ROM image can be used on most of the RetroBrew platforms and is easily customized. UNA also supports FAT file system access that can be used for in-situ ROM programming and loading system images. UNA is customized dynamically using a ROM based setup routine and the setup is persisted in the system NVRAM of the RTC chip. This means that the single UNA-based ROM image can be used on most of the RetroBrew platforms and is easily customized. UNA also supports FAT file system access that can be used for in-situ ROM programming and loading system images.
Line 122: Line 124:
 Please refer to the [[https://​www.retrobrewcomputers.org/​doku.php?​id=software:​firmwareos:​una:​start|UNA BIOS Firmware Page]] for more information on UNA. Please refer to the [[https://​www.retrobrewcomputers.org/​doku.php?​id=software:​firmwareos:​una:​start|UNA BIOS Firmware Page]] for more information on UNA.
  
-===== CP/M vs. Z-System =====+===== CP/M vs. Z-System =====
  
 There are two OS variants included in this distribution and you may choose which one you prefer to use. Both variants are now included in the pre-built ROM images. You will be given the choice to boot either CP/M or Z-System at startup. There are two OS variants included in this distribution and you may choose which one you prefer to use. Both variants are now included in the pre-built ROM images. You will be given the choice to boot either CP/M or Z-System at startup.
Line 146: Line 148:
 All source code and distributions are maintained on GitHub. Code contributions are very welcome. All source code and distributions are maintained on GitHub. Code contributions are very welcome.
  
-https://​github.com/​wwarthen/​RomWBW+[[https://​github.com/​wwarthen/​RomWBW|https://​github.com/​wwarthen/​RomWBW]]
  
 ===== Distribution Directory Layout ===== ===== Distribution Directory Layout =====
Line 152: Line 154:
 The RomWBW distribution is a compressed zip archive file organized in a set of directories. Each of these directories has it’s own ReadMe.txt file describing the contents in detail. In summary, these directories are: The RomWBW distribution is a compressed zip archive file organized in a set of directories. Each of these directories has it’s own ReadMe.txt file describing the contents in detail. In summary, these directories are:
  
-^**Directory**^**Contents** ​                                                                                                                          ^ +^**Directory** ^**Contents** ​  | 
-|Binary ​      ​|The final output files of the build process are placed here. Most importantly,​ are the ROM images with the file names ending in “.rom”.| +|Binary ​ |The final output files of the build process are placed here. Most importantly,​ are the ROM images with the file names ending in “.rom”.| 
-|Doc          |Contains various detailed documentation including the operating systems, RomWBW architecture,​ etc.                                     ​+|Doc  |Contains various detailed documentation including the operating systems, RomWBW architecture,​ etc.  
-|Source ​      ​|Contains the source code files used to build the software and ROM images. ​                                                             +|Source ​ |Contains the source code files used to build the software and ROM images. ​ 
-|Tools ​       |Contains the MS Windows programs that are used by the build process or that may be useful in setting up your system. ​                  ​|+|Tools ​ |Contains the MS Windows programs that are used by the build process or that may be useful in setting up your system. ​ |
  
 ===== Acknowledgements ===== ===== Acknowledgements =====
Line 174: Line 176:
 The best way to get assistance with RomWBW or any aspect of the RetroBrew Computers projects is via the community forum. The best way to get assistance with RomWBW or any aspect of the RetroBrew Computers projects is via the community forum.
  
-https://​www.retrobrewcomputers.org/​forum/​+[[https://​www.retrobrewcomputers.org/​forum/​|https://​www.retrobrewcomputers.org/​forum/​]]
  
 Also feel free to email Wayne Warthen at <​wwarthen@gmail.com>​. Also feel free to email Wayne Warthen at <​wwarthen@gmail.com>​.
 +
 +\\
  
  
playground/wwarthen/start.txt · Last modified: 2018/09/13 23:40 by wwarthen
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0