OpenCores
URL https://opencores.org/ocsvn/w11/w11/trunk

Subversion Repositories w11

[/] [w11/] [tags/] [w11a_V0.6/] [doc/] [w11a_os_guide.txt] - Diff between revs 18 and 20

Go to most recent revision | Show entire file | Details | Blame | View Log

Rev 18 Rev 20
Line 1... Line 1...
# $Id: w11a_os_guide.txt 469 2013-01-05 12:29:44Z mueller $
# $Id: w11a_os_guide.txt 511 2013-04-27 13:51:46Z mueller $
 
 
Guide to run operating system images on w11a systems
Guide to run operating system images on w11a systems
 
 
  Table of content:
  Table of content:
 
 
Line 11... Line 11...
 
 
 
 
1. I/O emulation setup ----------------------------------------------------
1. I/O emulation setup ----------------------------------------------------
 
 
   All UNIBUS peripherals which exchange data (currently DL11, LP11, PC11, RK11)
   All UNIBUS peripherals which exchange data (currently DL11, LP11, PC11, RK11)
   are currently emulated via a backend process. In the current version the
   are currently emulated via a backend process. The communication between
   communication between FPGA board and backend is via the serial port, either
   FPGA board and backend server can be via
   directly or via a USB-RS232 adapter. A direct connection is limited to 115k
 
   Baud on most PCs, while a connection via a USB-RS232 adapter was tested up
   - Serial port
   to 460k Baud.
     - via direct (/dev/ttySx) or via a USB-RS232 adapter. A direct connection
 
       is limited to 115k Baud on most PCs, while a connection via a USB-RS232
 
       adapter was tested up to 460k Baud. A USB-RS232 adapter is thus highly
 
       recommended
 
     - via integrated USB-RS232 adapter, like on nexys3 board. This is much
 
       faster, allows bitrates up to 2 M Baud.
 
 
   Notes: - A USB-RS232 cable with a Prolific Technology PL2303 chip simply
   Notes: - A USB-RS232 cable with a Prolific Technology PL2303 chip simply
            never gave reliable connections for higher Baud rates.
            never gave reliable connections for higher Baud rates.
          - A USB-RS232 cable with a FTDI FT232R chip, like the cable offered
          - A USB-RS232 cable with a FTDI FT232R chip, like the cable offered
            by FTDI as US232R-100 worked fine.
            by FTDI as US232R-100 worked fine.
          - On older linux kernels (prior 2.6.32) it is essential to set the
          - On older linux kernels (prior 2.6.32) it is essential to set the
            latency timer for the FTDI USB-RS232 cable to 1 ms (from the power
              latency timer for the FTDI USB-RS232 cable to 1 ms (from the
            in default of 16 ms), e.g. with
              power up default of 16 ms), e.g. with
              sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
              sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
            For linux kernel 2.6.32 or newer the default is 1 ms already.
            For linux kernel 2.6.32 or newer the default is 1 ms already.
          - the following assumes that a USB-RS232 cable with FTDI chip is used
            - The rest assumes that a USB-RS232 cable with FTDI chip is used
 
            - A 460k Baud connection gives in practice a disk throughput of
   A 460k Baud connection gives in practice a disk throughput of about 20 kB/s.
              about 20 kB/s. This allows to test the system but is a bit slow
   This allows to test the system but is a bit slow to real usage.  In an OS
              to real usage.  In an OS with good disk caching like 2.11BSD the
   with good disk caching like 2.11BSD the impact of such a 'slow disk' is
              impact of such a 'slow disk' is actually smaller than the bare
   actually smaller than the bare numbers suggest.
              numbers suggest.
 
 
 
   - Direct USB connection using a Cypress FX2 USB controller
 
     - is supported on the nexys2 and nexys3 FPGA boards
 
     - clearly much faster than serial port connections
 
     - also allows to configure the FPGA over the same USB connection
 
 
2. FPGA Board setup -------------------------------------------------------
2. FPGA Board setup -------------------------------------------------------
 
 
 
   - Using serial port
   - for s3board and nexys2
   - for s3board and nexys2
     - connect the USB-RS232 cable to the RS232 port of the s3board or nexys2
     - connect the USB-RS232 cable to the RS232 port of the s3board or nexys2
     - for kernel < 2.6.32: set the latency timer of the USB-RS232, e.g. with
     - for kernel < 2.6.32: set the latency timer of the USB-RS232, e.g. with
         sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
         sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
     - ensure that all 8 switches are in the indicated positions (SWI=xxxxxxxx)
       - ensure that all 8 switches are in the indicated positions (SWI=...)
     - load the w11a design into the FPGA, e.g. via impact
     - load the w11a design into the FPGA, e.g. via impact
 
 
   - for nexys3
   - for nexys3
     - connect USB cable to the 'usb uart' port (next to the 5 buttons)
     - connect USB cable to the 'usb uart' port (next to the 5 buttons)
     - ensure that all 8 switches are in the indicated positions (SWI=xxxxxxxx)
       - ensure that all 8 switches are in the indicated positions (SWI=...)
     - load the w11a design into the FPGA, e.g. via impact
     - load the w11a design into the FPGA, e.g. via impact
 
 
 
   - Using Cypress FX2 USB controller
 
     - for nexys2
 
       - connect USB cable to mini-USB connector (between RS232 and PS/2 port)
 
         ! Must be connected to a USB port able to deliver 500 mA !
 
 
3. Unix V5 system ---------------------------------------------------------
3. Unix V5 system ---------------------------------------------------------
 
 
   - A disk set is available from
   - A disk set is available from
       http://www.retro11.de/data/oc_w11/unix_v5_rkset.tgz
       http://www.retro11.de/data/oc_w11/unix_v5_rkset.tgz
     Download, unpack and copy the disk images (*.dsk) to
     Download, unpack and copy the disk images (*.dsk) to
       $RETROBASE/rtl/sys_gen/w11a/tb
       $RETROBASE/rtl/sys_gen/w11a/tb
 
 
   - Setup USB-RS232 cable, start xterm in vt100 mode and the server backend
   - Using old (pi_rri) backend server (serial port only)
     Note: It is essential that the settings of the board switches are correct
 
           in the following indicated by SWI = xxxxxxxx.
 
 
 
       cd $RETROBASE/rtl/sys_gen/w11a/tb
       cd $RETROBASE/rtl/sys_gen/w11a/tb
       sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
 
       telnet_starter -d DL0 &
       telnet_starter -d DL0 &
 
 
     [for s3,n2:]
     [for s3,n2:]
       SWI = 00000010
       SWI = 00000010
       dorri -u0,460,1,2   @uv5_boot.pcmd
       dorri -u0,460,1,2   @uv5_boot.pcmd
     [for n3:]
     [for n3:]
       SWI = 00000010
       SWI = 00000010
       dorri -u0,2000,1,2  @uv5_boot.pcmd
       dorri -u0,2000,1,2  @uv5_boot.pcmd
 
 
 
   - Using new (ti_rri) backend server (serial and fx2 supported)
 
 
 
       cd $RETROBASE/rtl/sys_gen/w11a/tb
 
       telnet_starter -d DL0 &
 
 
 
     [for s3,n2 over serial:]
 
       SWI = 00000010
 
       torri -tu0,460k,break,xon   @uv5_boot.tcl
 
     [for n3 over serial:]
 
       SWI = 00000010
 
       torri -tu0,2M,break,xon     @uv5_boot.tcl
 
 
 
     [for n2,n3 over fx2:]
 
       SWI = 00000100
 
       torri -u     @uv5_boot.tcl
 
 
   - the boot dialog in the console xterm window will look like
   - the boot dialog in the console xterm window will look like
     (required input is in {..}, with {} denoting a carriage return:
     (required input is in {..}, with {} denoting a carriage return:
 
 
       @{unix}
       @{unix}
 
 
Line 99... Line 128...
   - A disk set is available from
   - A disk set is available from
       http://www.retro11.de/data/oc_w11/211bsd_rkset.tgz
       http://www.retro11.de/data/oc_w11/211bsd_rkset.tgz
     Download, unpack and copy the disk images (*.dsk) to
     Download, unpack and copy the disk images (*.dsk) to
       $RETROBASE/rtl/sys_gen/w11a/tb
       $RETROBASE/rtl/sys_gen/w11a/tb
 
 
   - Setup USB-RS232 cable, start two xterm in vt100 mode and the server backend
   - Using old (pi_rri) backend server (serial port only)
     Note: It is essential that the settings of the board switches are correct
 
           in the following indicated by SWI = xxxxxxxx.
 
 
 
       cd $RETROBASE/rtl/sys_gen/w11a/tb
       cd $RETROBASE/rtl/sys_gen/w11a/tb
       sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
       sudo $RETROBASE/tools/bin/set_ftdi_lat USB0 1
       telnet_starter -d DL0 &
       telnet_starter -d DL0 &
       telnet_starter -d DL1 &
       telnet_starter -d DL1 &
 
 
     [for s3,n2:]
     [for s3,n2:]
       SWI = 00000010
       SWI = 00000010
       dorri -u0,460,1,2   @211bsd_rk_boot.pcmd
       dorri -u0,460,1,2   @211bsd_rk_boot.pcmd
     [for n3:]
     [for n3:]
       SWI = 00000010
       SWI = 00000010
       dorri -u0,2000,1,2  @211bsd_rk_boot.pcmd
       dorri -u0,2000,1,2  @211bsd_rk_boot.pcmd
 
 
 
   - Using new (ti_rri) backend server (serial and fx2 supported)
 
 
 
       cd $RETROBASE/rtl/sys_gen/w11a/tb
 
       telnet_starter -d DL0 &
 
 
 
     [for s3,n2 over serial:]
 
       SWI = 00000010
 
       torri -tu0,460k,break,xon   @211bsd_rk_boot.tcl
 
     [for n3 over serial:]
 
       SWI = 00000010
 
       torri -tu0,2M,break,xon     @211bsd_rk_boot.tcl
 
 
 
     [for n2,n3 over fx2:]
 
       SWI = 00000100
 
       torri -u     @211bsd_rk_boot.tcl
 
 
   - the boot dialog in the console xterm window will look like
   - the boot dialog in the console xterm window will look like
     (required input is in {..}, with {} denoting a carriage return:
     (required input is in {..}, with {} denoting a carriage return:
 
 
       70Boot from rk(0,0,0) at 0177404
       70Boot from rk(0,0,0) at 0177404
       : {}
       : {}
Line 154... Line 198...
       standard daemons: update cron accounting.
       standard daemons: update cron accounting.
       starting lpd
       starting lpd
       starting local daemons:Sun Jan  4 16:46:37 PST 2009
       starting local daemons:Sun Jan  4 16:46:37 PST 2009
       January  4 16:46:37 init: kernel security level changed from 0 to 1
       January  4 16:46:37 init: kernel security level changed from 0 to 1
       January  4 16:46:40 getty: /dev/tty01: Device not configured
       January  4 16:46:40 getty: /dev/tty01: Device not configured
 
       ...
 
 
       January  4 16:46:40 getty: /dev/tty00: Device not configured
 
 
 
 
 
       2.11 BSD UNIX (curly.2bsd.com) (console)
       2.11 BSD UNIX (curly.2bsd.com) (console)
 
 
       login: {root}
       login: {root}
       erase, kill ^U, intr ^C
       erase, kill ^U, intr ^C
Line 185... Line 226...
       /dev/rk4h on /usr
       /dev/rk4h on /usr
       # {halt}
       # {halt}
       syncing disks... done
       syncing disks... done
       halting
       halting
 
 
     Now the server process can be stopped with two ^D.
     Now the server process can be stopped with ^D.
     Now the server process can be stopped with ^D.
     Now the server process can be stopped with ^D.

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.