Driver:MIPS: Difference between revisions

From MAMEDEV Wiki
Line 82: Line 82:
== Installing RISC/os ==
== Installing RISC/os ==
=== Environment ===
=== Environment ===
After powering on the system, you should be presented with a firmware monitor prompt. The <code>help</code> command shows the syntax recognized, and additional information may be found in the manual[http://www.bitsavers.org/pdf/mips/PRM-01-DOC_PROM_Monitor_Ref_Jun92.pdf].
After powering on the system, you should be presented with the MIPS Monitor prompt. The <code>help</code> command shows the syntax recognized, and additional information may be found in the manual[http://www.bitsavers.org/pdf/mips/PRM-01-DOC_PROM_Monitor_Ref_Jun92.pdf].


To complete a network installation, it's important to set the system TCP/IP address to one compatible with the external networking environment, using the <code>setenv</code> command. The current environment settings are retained in non-volatile memory, and may be displayed using <code>printenv</code>.
To complete a network installation, it's important to set the system TCP/IP address to one compatible with the external networking environment, using the <code>setenv</code> command. The current environment settings are retained in non-volatile memory, and may be displayed using <code>printenv</code>.
Line 97: Line 97:
</pre>
</pre>


Once <code>format</code> is launched, answer the prompts as follows.
Once <code>format</code> is launched, accept the defaults for all prompts except the following.


{| class="wikitable" style="width: 50%;"
{| class="wikitable" style="width: 50%;"
Line 104: Line 104:
| name of device || dksd
| name of device || dksd
|-
|-
| controller number || 0
| device parameters || 13
|-
|-
| unit number || 0
| number of cylinders || 1731
|-
|-
| device parameters || 0
| number heads in vol 0 || 15
|-
|-
| fast file system || y
| number sectors per track || 80
|-
|-
| dump device parameters || n
| number bytes per sector || 512
|-
| modify device parameters || n
|-
| dump partition table || n
|-
| modify partition table || n
|-
| read factory defects || n
|-
| perform format || n
|-
| perform scan || n
|-
|-
| media defect command || q
| media defect command || q
|-
| perform mapping || n
|-
| dump bad sector table || n
|-
|-
| write new volume header || y
| write new volume header || y
Line 137: Line 121:


=== Miniroot Installation ===
=== Miniroot Installation ===
Launch the stand-alone shell <code>sash</code> and use it to copy the miniroot filesystem from TFTP to the root partition of the hard disk.
As with the <code>format</code> utility, there are two versions of the standalone shell (sash). <code>sash.std</code> is used for all but the RC2030 and RS2030 systems which have their own dedicated version <code>sash.2030</code>.
 
Launch the standalone shell and use the <code>cp</code> command to copy the miniroot filesystem from TFTP to the boot partition of the hard disk.
<pre>
<pre>
boot -f bfs()sash.2030
boot -f bfs()tree/stand/sash.2030
cp bfs()root.fs dksd(0,0,1)
cp bfs()root.fs dksd(0,0,1)
</pre>
</pre>
This process should take a little over 10 minutes to complete, after which RISC/os may be booted using a kernel from TFTP.
This process should take around 10 minutes to complete.
=== RISC/os Installation ===
After the miniroot has been copied to disk, RISC/os may be booted using it as a root file system with a kernel loaded from TFTP.
<pre>
<pre>
boot -f bfs()unix.i2000_std root=sdc0d0s1
boot -f bfs()unix.i2000_std root=sdc0d0s1
</pre>
</pre>
From the miniroot shell prompt, configure the environment to specify a network installation, and start the RISC/os installation utility.
From the miniroot shell prompt, configure the environment to specify a network installation and the name of the installation server, and start the RISC/os installation utility <code>inst</code>.
<pre>
<pre>
From=en
From=en
Server=host
inst
inst
</pre>
</pre>


| hostname of this machine || mame
Most of the prompts from <code>inst</code> are fairly straightforward, however there are some which may require further explanation:
| hostname of install server || xps13
* The "remote package root" and "remote packaging information tree" responses must correspond to the "tree" and "umips4.52" directories within the RISC/os network installation structure respectively.
| netmask || 255.255.255.0
* The "mh" package is damaged and cannot be installed successfully from the currently available installation media.
| broadcast address || 192.168.137.255
* It is recommended to skip the disk space check, as it can be quite time-consuming and is unnecessary if using a sufficiently-sized disk.
| inet address for mame || 192.168.137.2
* It is recommended to skip the "set up /etc/local_hostname and /etc/hosts" step, as it may cause <code>inst</code> to abort if unable to copy rsh configuration files from the host.
| inet address for xps13 || 192.168.137.1
 
| Ok || y
A minimal installation (root, rc2030, usr) should take about 10 minutes, after which the system should be shut down with <code>telinit</code>.
| server ||
| remote package root || /tree
| remote packaging information tree || /tree/umips4.52
| information above correct || y
| install kernel to miniroot || n
| install all subpackages || n
may install all except mh (error in archive)
confirm


minimal installation (root, rc2030, usr) should take about 10 minutes
<pre>
telinit 0
</pre>


set up /etc/local_hostname and /etc/hosts -> no (tries to rcp /etc/rhosts.equiv)
<gallery>
mips_monitor.png|MIPS Monitor|alt=A screenshot of the MIPS Monitor
mips_sash.png|MIPS Standalone Shell|alt=A screenshot of the MIPS Standalone Shell (sash)
mips_miniroot.png|RISC/os Miniroot|alt=A screenshot of RISC/os booted from the miniroot
</gallery>


== References ==
== References ==

Revision as of 07:59, 10 June 2019

MIPS

This article and the corresponding MAME driver focus on computers sold by MIPS Computer Systems which use MIPS R2000/R3000 processors and run RISC/os (also known as UMIPS), a port of UNIX System V release 3 with BSD extensions.

Introduction

Status

Hardware

MIPS Computer Systems range[1]
Model Board CPU Clock Slots Disk Package Notes
M/500 R2300 R2000 5MHz VME ESDI
M/800 R2600 R2000 8MHz VME ESDI
M/1000 R2800 R2000 10MHz VME ESDI
M/120-3 R2400 R2000 12.5MHz PC-AT SCSI Deskside aka Intrepid
M/120-5 R2400 R2000 16MHz PC-AT SCSI Deskside
M/180 R2400
M/2000-6 R3200 R3000 20MHz VMEx13 SMD Rack Cabinet
M/2000-8 R3200 R3000 25MHz VMEx13 SMD Rack Cabinet
M/2000-? RB3125 R3000 33MHz
RC2030 I2000 R2000 16MHz SCSI Desktop aka M/12, Jupiter
RS2030 I2000 R2000 16MHz SCSI Desktop aka M/12, Jupiter
RC3230 R3030 R3000 25MHz PC-ATx1 SCSI Desktop aka M/20, Pizazz
RS3230 R3030 R3000 25MHz PC-ATx1 SCSI Desktop aka M/20, Pizazz, Magnum 3000
RC3240 R3000 25MHz PC-ATx4 SCSI Deskside M/120 with CPU-board upgrade
RC3330 R3000 33MHz PC-AT SCSI Desktop
RS3330 R3000 33MHz PC-AT SCSI Desktop
RC3260 R3000 25MHz VMEx7 SCSI Pedestal
RC3360 RB3133 R3000 33MHz VME SCSI Pedestal
RC3370 RB3133
RC6260 R6300 R6000 66MHz VME SCSI Pedestal
RC6280 R6300 R6000 66MHz VMEx6 SMD Data Center
RC6380-100 R6000x1 66MHz VME SMD Data Center
RC6380-200 R6000x2 66MHz VME SMD Data Center
RC6380-400 R6000x4 66MHz VME SMD Data Center

Preparation

Prerequisites

TODO: mame version, riscos files, tap adapter

Network

TODO: set up the bfs and rsh networking tools and environment.

Storage

Use chdman createhd to prepare a new CHD for the operating system installation, and then chdman addmeta to apply a manufacturer string used to identify the drive make/model information that will be returned by the SCSI INQUIRY command. 

chdman createhd -o riscos.chd -c none -chs 1731,15,80
chdman addmeta -i riscos.chd -t IDNT -vt "SEAGATE ST11200N        1.00"

The SCSI INQUIRY response data (defined by the IDNT meta-data tag in the CHD) should consist of an 8 character manufacturer name, 16 character model number, and 4 character version number, all left justified and padded with spaces.

Configuration

TODO: mame configuration 

mame64 rs2030 -hard riscos.chd

Installing RISC/os

Environment

After powering on the system, you should be presented with the MIPS Monitor prompt. The help command shows the syntax recognized, and additional information may be found in the manual[2].

To complete a network installation, it's important to set the system TCP/IP address to one compatible with the external networking environment, using the setenv command. The current environment settings are retained in non-volatile memory, and may be displayed using printenv. 

setenv netaddr 192.168.137.2

Format

The format utility allows disks to be partitioned, labelled and formatted. There are two versions of this utility, with format.std being used for all but the Rx2030 system, which has its own dedicated version format.2030.

Launch the applicable format utility using the boot command, being sure to provide the path name matching your BFS or TFTP data path. 

boot -f bfs()tree/stand/format.2030

Once format is launched, accept the defaults for all prompts except the following.

Prompt Response
name of device dksd
device parameters 13
number of cylinders 1731
number heads in vol 0 15
number sectors per track 80
number bytes per sector 512
media defect command q
write new volume header y

Miniroot Installation

As with the format utility, there are two versions of the standalone shell (sash). sash.std is used for all but the RC2030 and RS2030 systems which have their own dedicated version sash.2030.

Launch the standalone shell and use the cp command to copy the miniroot filesystem from TFTP to the boot partition of the hard disk. 

boot -f bfs()tree/stand/sash.2030
cp bfs()root.fs dksd(0,0,1)

This process should take around 10 minutes to complete.

RISC/os Installation

After the miniroot has been copied to disk, RISC/os may be booted using it as a root file system with a kernel loaded from TFTP. 

boot -f bfs()unix.i2000_std root=sdc0d0s1

From the miniroot shell prompt, configure the environment to specify a network installation and the name of the installation server, and start the RISC/os installation utility inst. 

From=en
Server=host
inst

Most of the prompts from inst are fairly straightforward, however there are some which may require further explanation:

  • The "remote package root" and "remote packaging information tree" responses must correspond to the "tree" and "umips4.52" directories within the RISC/os network installation structure respectively.
  • The "mh" package is damaged and cannot be installed successfully from the currently available installation media.
  • It is recommended to skip the disk space check, as it can be quite time-consuming and is unnecessary if using a sufficiently-sized disk.
  • It is recommended to skip the "set up /etc/local_hostname and /etc/hosts" step, as it may cause inst to abort if unable to copy rsh configuration files from the host.

A minimal installation (root, rc2030, usr) should take about 10 minutes, after which the system should be shut down with telinit. 

telinit 0
  • A screenshot of the MIPS Monitor

    MIPS Monitor

  • A screenshot of the MIPS Standalone Shell (sash)

    MIPS Standalone Shell

  • A screenshot of RISC/os booted from the miniroot

    RISC/os Miniroot

References

The following are various documents pertaining to MIPS computer systems.

Reference Title Date Links
Reference Title MmmYY [3]
Retrieved from ‘https://wiki.mamedev.org/index.php?title=Driver:MIPS&oldid=6605’