-There are three major connector types used in hardware samplers: DB25, CN50, and HD50. Although RaSCSI uses a DB25 connector, the SCSI standard ensures that every connector is compatible with the others. The most convenient way to connect a RaSCSI to a sampler with CN50 or HD50 is to buy a cable with DB25 on one end and the appropriate SCSI connector for your sampler on the other end. You can also use adapters, but they do tend to put stress on the SCSI jacks that they are connected to which might cause maintenance issues.
+There are three major connector types used in hardware samplers: DB25, CN50, and HD50. Although PiSCSI uses a DB25 connector, the SCSI standard ensures that every connector is compatible with the others. The most convenient way to connect a PiSCSI to a sampler with CN50 or HD50 is to buy a cable with DB25 on one end and the appropriate SCSI connector for your sampler on the other end. You can also use adapters, but they do tend to put stress on the SCSI jacks that they are connected to which might cause maintenance issues.
DB25 is the oldest of the connector types, and was also common among Macintosh computers. The prevalence of the Macintosh computer in studios of all levels through the 80's and 90's is probably why the vast majority of hardware samplers used this connector.
@@ -440,8 +440,8 @@ SD Card|Sandisk Ultra 32GB
Device|Analog Odyssey (32MB)|Vintage Combo (16MB)|Moog Synths (8MB)
---|---|---|---
-RaSCSI (4B 8GB)|0:31|0:17|0:09
-RaSCSI (pi Zero)|0:33|0:19|0:09
+PiSCSI (4B 8GB)|0:31|0:17|0:09
+PiSCSI (pi Zero)|0:33|0:19|0:09
SCSI2SD 5.5|0:58|0:31|0:16
SCSI2SD 6.0|0:26|0:15|0:08
@@ -458,7 +458,7 @@ SD Card|Sandisk Ultra 32GB
Device|Analog Odyssey (32MB)|Vintage Combo (16MB)|Moog Synths (8MB)
---|---|---|---
-RaSCSI|0:50|0:30|0:16
+PiSCSI|0:50|0:30|0:16
SCSI2SD 5.5|1:10|0:41|0:21
SCSI2SD 6.0|0:51|0:32|0:16
@@ -475,7 +475,7 @@ SD Card|Sandisk Ultra 32GB
Device|Analog Odyssey (32MB)|Vintage Combo (16MB)|Moog Synths (8MB)
---|---|---|---
-RaSCSI|1:40|0:53|0:27
+PiSCSI|1:40|0:53|0:27
SCSI2SD 5.5|1:39|0:53|0:27
SCSI2SD 6.0|1:39|0:53|0:27
@@ -490,7 +490,7 @@ SD Card|Sandisk Ultra 32GB
Device|Partition A (32MB)|Partition M (24MB)
---|---|---
-RaSCSI|0:00|0:00
+PiSCSI|0:00|0:00
SCSI2SD 5.5|1:13|0:00
SCSI2SD 6.0|0:37|0:00
@@ -505,7 +505,7 @@ SD Card|Sandisk Ultra 32GB
Device|24bit G Piano (320MB)
---|---
-RaSCSI|6:36
+PiSCSI|6:36
SCSI2SD 5.5|
SCSI2SD 6.0|
USB CD|8:30
diff --git a/PowerView---SuperView.md b/PowerView---SuperView.md
index f211a47..3c49e17 100644
--- a/PowerView---SuperView.md
+++ b/PowerView---SuperView.md
@@ -8,13 +8,13 @@
* The web interface will NOT work with this feature branch (yet)
* To use this branch, perform the following:
```
-cd ~/RASCSI
+cd ~/piscsi
git checkout feature_powerview
git pull
./easyinstall.sh
# After easyinstall is completed...
-rasctl -c attach -i 4 -f powerview
-# Currently, there is a special case in RaSCSI where it keys off the filename "powerview"
+scsictl -c attach -i 4 -f powerview
+# Currently, there is a special case in PiSCSI where it keys off the filename "powerview"
```
* I've never tried to emulate multiple PowerViews at the same time.
diff --git a/RaSCSI-Control-Android-App.md b/RaSCSI-Control-Android-App.md
deleted file mode 100644
index 6b8749a..0000000
--- a/RaSCSI-Control-Android-App.md
+++ /dev/null
@@ -1,3 +0,0 @@
-## Managing RaSCSI with a smartphone or tablet
-
-With the RaSCSI Control app for Android you manage the virtual SCSI devices, the image files and much more. In addition, you stay up to date by push messages with RaSCSI-related news. The app is directly connected to the RaSCSI server (rascsi) on the Pi. The RaSCSI Control website provides more information.
\ No newline at end of file
diff --git a/Roadmap.md b/Roadmap.md
index 5d673c4..6d847b1 100644
--- a/Roadmap.md
+++ b/Roadmap.md
@@ -3,9 +3,9 @@ This page summarizes the status of major new features for PiSCSI.
# Current
Project|Details|References|Status
---|---|---|---
-SCSI Video Card | Emulating a PowerView SCSI video card | [wiki](https://github.com/akuker/RASCSI/wiki/PowerView---SuperView), [branch](https://github.com/akuker/RASCSI/tree/feature_powerview) | On Hold
-New Web UI | Modern and flexible Web UI that can be easily customized for particular use cases. This is not meant to replace the old Web UI, but rather builds upon the same endpoints. The old Web UI is still valuable as the "vintage" version that works on really old browsers. | [branch](https://github.com/akuker/RASCSI/tree/eric/newweb) | On Hold
-Super UPS | A Supercapacitor UPS hat for graceful shutdown on loss of power | [wiki](https://github.com/akuker/RASCSI/wiki/supercapacitor-ups) | Active
+SCSI Video Card | Emulating a PowerView SCSI video card | [wiki](https://github.com/piscsi/piscsi/wiki/PowerView---SuperView), [branch](https://github.com/piscsi/piscsi/tree/feature_powerview) | On Hold
+New Web UI | Modern and flexible Web UI that can be easily customized for particular use cases. This is not meant to replace the old Web UI, but rather builds upon the same endpoints. The old Web UI is still valuable as the "vintage" version that works on really old browsers. | [branch](https://github.com/piscsi/piscsi/tree/eric/newweb) | On Hold
+Super UPS | A Supercapacitor UPS hat for graceful shutdown on loss of power | [wiki](https://github.com/piscsi/piscsi/wiki/supercapacitor-ups) | Active
Banana Pi Support | The ability to use PiSCSI with Pi-like single-board computers | [branch](https://github.com/piscsi/piscsi/tree/develop) | Active
LaserWriter SC | Emulating a SCSI Printer with compatible Macintosh drivers| Examples: [Personal LaserWriter SC](https://apple.fandom.com/wiki/Personal_LaserWriter_SC) [LaserWriter II SC](https://apple.fandom.com/wiki/LaserWriter_IISC) | Future
Fast Booting "Embedded" Image | Create customized Linux distro with a boot time < 5 seconds | | Future
diff --git a/Robot-Framework-Notes.md b/Robot-Framework-Notes.md
index 2a7cdc4..0068aff 100644
--- a/Robot-Framework-Notes.md
+++ b/Robot-Framework-Notes.md
@@ -18,8 +18,8 @@ sudo apt install genisoimage sshpass
# Running tests
To run the test suite, run the following commands:
```
-git clone https://github.com/akuker/RASCSI.git
-cd RASCSI/test/robot
+git clone https://github.com/piscsi/piscsi.git
+cd piscsi/test/robot
robot ./
```
If everything works, you should see something like this:
diff --git a/Rules-for-adding-new-device-types.md b/Rules-for-adding-new-device-types.md
index cc3e095..a7d7c48 100644
--- a/Rules-for-adding-new-device-types.md
+++ b/Rules-for-adding-new-device-types.md
@@ -6,7 +6,7 @@ Steps for adding a new device type:
2. Add code for creating the device type to the DeviceFactory class in `devices/device_factory.cpp`.
3. Add the device type specific implementation in new .cpp/.h files located in the devices folder.
4. Ensure to initialize the device type with its device type properties and supported SCSI commands in the Init() method.
-5. Verify that _rasctl -s_ reports the correct device type properties.
+5. Verify that _scsictl -s_ reports the correct device type properties.
6. Update the manpages.
Devices have to be subclasses of PrimaryDevice or ModeSenseDevice. Only devices backed by image files may be subclasses of the StorageDevice class. See the implementations of the Host Services (SCHS) and the SCSI Printer (SCLP) for device implementations with low complexity.
diff --git a/SCSI-Bus-Capture.md b/SCSI-Bus-Capture.md
index aeac7f2..757e6de 100644
--- a/SCSI-Bus-Capture.md
+++ b/SCSI-Bus-Capture.md
@@ -4,7 +4,7 @@ This page is intended for developers and/or advanced users only.
The scsimon tool allows you to capture all of the traffic on the SCSI bus and log it to a file. The data is stored in a "Value Change Data" VCD file that can be read by GTKWave
```
+---------+ +-----------+ +----------+
-| | | RaSCSI | | Other |
+| | | PiSCSI | | Other |
| HOST | | running | | SCSI |
| PC | | scsimon | | device(s)|
| | | | | |
@@ -16,18 +16,18 @@ The scsimon tool allows you to capture all of the traffic on the SCSI bus and lo
# Checkout and build scsimon
-scsimon is included in the main installation of RaSCSI. It should be located in `/usr/local/bin/scsimon`. If its not, you may need to upgrade to a newer version of the RaSCSI software.
+scsimon is included in the main installation of PiSCSI. It should be located in `/usr/local/bin/scsimon`. If its not, you may need to upgrade to a newer version of the PiSCSI software.
-## Special RaSCSI 1.5/1.6 modification
-If you're using a RaSCSI 2.x board ("FULLSPEC"), you do not need this modification!
+## Special PiSCSI 1.5/1.6 modification
+If you're using a PiSCSI 2.x board ("FULLSPEC"), you do not need this modification!
-If you're using a RaSCSI version 1.5 or 1.6, you will need to make the following modification to your board. This will force all of the transceivers into a RECEIVE-ONLY mode.
+If you're using a PiSCSI version 1.5 or 1.6, you will need to make the following modification to your board. This will force all of the transceivers into a RECEIVE-ONLY mode.
# Capture data
-Make sure you've stopped the RaSCSI service. Then run scsimon. If you're trying to capture a specific scenario, you'll want to wait to start scsimon until immediately before the scenario.
+Make sure you've stopped the PiSCSI service. Then run scsimon. If you're trying to capture a specific scenario, you'll want to wait to start scsimon until immediately before the scenario.
```
sudo ./scsimon
```
diff --git a/SCSI-Network-Card.md b/SCSI-Network-Card.md
index 6e765dd..420c89b 100644
--- a/SCSI-Network-Card.md
+++ b/SCSI-Network-Card.md
@@ -1,26 +1,26 @@
# SCSI Network Card emulation
-The aim is to provide network capabilities through SCSI interface emulated by RaSCSI.
+The aim is to provide network capabilities through SCSI interface emulated by PiSCSI.
This documentation is for developer who would like to contribute to this project.
## Current status
This is not yet ready and still under development.
-Packets go through `ras0` tun/tap and are read by RaSCSI service, and are sent to SCSI. I haven't been able to verify the packet arrived on the Mac yet.
+Packets go through `piscsi0` tun/tap and are read by PiSCSI service, and are sent to SCSI. I haven't been able to verify the packet arrived on the Mac yet.
## How does it work?
-Packets can come from `wlan0` or from localhost, they are sent to a tun/tap virtual interface named `ras0`.
-The RaSCSI software connects to `ras0` and reads the packets, then write those packets to the SCSI interface.
+Packets can come from `wlan0` or from localhost, they are sent to a tun/tap virtual interface named `piscsi0`.
+The PiSCSI software connects to `piscsi0` and reads the packets, then write those packets to the SCSI interface.
On the Mac, the device driver, reads the packets from the SCSI physical port of the Mac and provide them to the System.
Same operation happen in the other direction when packets are sent from the Mac to the SCSI (thanks the driver).
-RaSCSI reads the packets from the SCSI emulation and write then to the virtual network interface `ras0`, packets can then travel to the internet through `wlan0`.
+PiSCSI reads the packets from the SCSI emulation and write then to the virtual network interface `piscsi0`, packets can then travel to the internet through `wlan0`.
```
- [ wlan0 ] <---> [ ras0 ] <---> [ RaSCSI + SCSI NIC Emulation ] <---> SCSI <--> [ Mac OS Device Driver ] <-> [ Mac System ]
- [ internet ] [ tun virtual ] [ read packets from ras0 and ]
+ [ wlan0 ] <---> [ piscsi0 ] <---> [ PiSCSI + SCSI NIC Emulation ] <---> SCSI <--> [ Mac OS Device Driver ] <-> [ Mac System ]
+ [ internet ] [ tun virtual ] [ read packets from piscsi0 and ]
[ interface ] [ write them to the SCSI. ]
[ read the packets from SCSI ]
- [ and write them to ras0. ]
+ [ and write them to piscsi0. ]
```
@@ -41,14 +41,14 @@ tail -f /var/log/rascsi.log
## Tools
### arping
```
-arping -c 5 -I ras0 D6:90:8C:7A:17:6E
-arping -c 5 -I ras0 192.168.0.1
+arping -c 5 -I piscsi0 D6:90:8C:7A:17:6E
+arping -c 5 -I piscsi0 192.168.0.1
```
### TCP Dump
Filter tcp traffic on the tun/tap interface
```
-sudo tcpdump -I ras0 tcp
+sudo tcpdump -I piscsi0 tcp
```
diff --git a/SCSI-Printer.md b/SCSI-Printer.md
index c5cbb0c..50d2646 100644
--- a/SCSI-Printer.md
+++ b/SCSI-Printer.md
@@ -1,12 +1,12 @@
-A SCSI printer is implemented as ''SCLP'' device since RaSCSI release 22.05.
+A SCSI printer is implemented as ''SCLP'' device since PiSCSI release 22.05.
-Device drivers for [Atari ST/TT/Falcon and the Milan](https://github.com/akuker/RASCSI/wiki/RaSCSI-Client-Tools) are available. The device driver sources are [provided on GitHub](https://github.com/uweseimet/atari_public/tree/main/RASCSI).
+Device drivers for [Atari ST/TT/Falcon and the Milan](https://github.com/piscsi/piscsi/wiki/PiSCSI-Client-Tools) are available. The device driver sources are [provided on GitHub](https://github.com/uweseimet/atari_public/tree/main/RASCSI).
# Development Resources
## Classic Macintosh
-Apple produced *two* SCSI printers which could be emulated. They made the low cost [LaserWriter SC], which uses bitmaps like the ImageWriter while the [LaserWriter IISC] is a higher cost PostScript printer. Emulating these devices in RaSCSI would be one way to support printing using Apple drivers.
+Apple produced *two* SCSI printers which could be emulated. They made the low cost [LaserWriter SC], which uses bitmaps like the ImageWriter while the [LaserWriter IISC] is a higher cost PostScript printer. Emulating these devices in PiSCSI would be one way to support printing using Apple drivers.
[LaserWriter SC]: https://lowendmac.com/1990/personal-laserwriter-sc
[LaserWriter IISC]: https://lowendmac.com/1988/laserwriter-iisc
diff --git a/Setup-Instructions.mediawiki b/Setup-Instructions.mediawiki
index 3ee2539..171677e 100644
--- a/Setup-Instructions.mediawiki
+++ b/Setup-Instructions.mediawiki
@@ -1,20 +1,20 @@
= Raspberry Pi operating system installation =
-'''Important:''' We distribute pre-configured Raspberry Pi OS images with RaSCSI ready to be used out of the box. Please find links on the [https://tracker.iplocation.net/jtdd/ Releases] page.
+'''Important:''' We distribute pre-configured Raspberry Pi OS images with PiSCSI ready to be used out of the box. Please find links on the [https://tracker.iplocation.net/jtdd/ Releases] page.
-The RaSCSI software some basic software requirements, and should work on any reasonably modern version of Linux. However, development and testing for this project is done on [https://www.raspberrypi.org/downloads/raspberry-pi-os/ Raspberry Pi OS] (formerly called Raspbian). The following instructions are written with the assumption you are using Raspberry Pi OS 10. Raspberry Pi OS 11 requires additional compiler flags, see below.
+The PiSCSI software some basic software requirements, and should work on any reasonably modern version of Linux. However, development and testing for this project is done on [https://www.raspberrypi.org/downloads/raspberry-pi-os/ Raspberry Pi OS] (formerly called Raspbian). The following instructions are written with the assumption you are using Raspberry Pi OS 10. Raspberry Pi OS 11 requires additional compiler flags, see below.
To get going, if you haven't already, follow the official [https://www.raspberrypi.org/documentation/installation/ Raspberry Pi OS installation instructions].
-'''Note:''' Installing the desktop environment on your Raspberry Pi is not required to run RaSCSI. Consider installing Raspberry Pi OS (32-bit) Lite to save on disk space.
+'''Note:''' Installing the desktop environment on your Raspberry Pi is not required to run PiSCSI. Consider installing Raspberry Pi OS (32-bit) Lite to save on disk space.
In the spirit of not running unnecessary cables, if you need to setup a WiFi connection on your Raspberry Pi, follow [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md these steps]
__TOC__
-= Clone & build the RaSCSI software =
-The next step is to download the RaSCSI software from GitHub and build it.
+= Clone & build the PiSCSI software =
+The next step is to download the PiSCSI software from GitHub and build it.
'''1.''' [https://tutorials-raspberrypi.com/raspberry-pi-default-login-password/ Log into the Raspberry Pi.]
@@ -22,38 +22,38 @@ The next step is to download the RaSCSI software from GitHub and build it.
'''1b.''' If you've installed Raspberry Pi OS Lite, ssh into your Raspberry Pi.
-'''2.''' Install the git, libspdlog-dev, protobuf-compiler, and libpcap-dev packages. Git is used to clone the RaSCSI repository to your system so we can build the software. For more information on git, check [https://en.wikipedia.org/wiki/Git this Wikipedia article]. spdlog is a logging library which is used by the RaSCSI software. More information on spdlog can be [https://github.com/gabime/spdlog/wiki found here].
+'''2.''' Install the git, libspdlog-dev, protobuf-compiler, and libpcap-dev packages. Git is used to clone the PiSCSI repository to your system so we can build the software. For more information on git, check [https://en.wikipedia.org/wiki/Git this Wikipedia article]. spdlog is a logging library which is used by the PiSCSI software. More information on spdlog can be [https://github.com/gabime/spdlog/wiki found here].
```
sudo apt-get update && sudo apt-get install --yes git libspdlog-dev protobuf-compiler libpcap-dev
```
-'''3.''' The next step is to clone the RaSCSI Git repository, build the software, and install it on your Raspberry Pi. Enter the following commands in your terminal/ssh session.
+'''3.''' The next step is to clone the PiSCSI Git repository, build the software, and install it on your Raspberry Pi. Enter the following commands in your terminal/ssh session.
```
cd ~
-git clone https://github.com/akuker/RASCSI.git
+git clone https://github.com/piscsi/piscsi.git
```
-'''4.''' Determine which board you have. The two common options are "STANDARD" or "FULLSPEC". Information on which model you have can be found at the [https://github.com/akuker/RASCSI/wiki/Hardware-Versions Hardware Versions] page. If you purchased your RaSCSI from Tindie, you will have version 2.2 or newer, which are all "FULLSPEC" boards. You can also check the silkscreen on the RaSCSI board for the version number. Enter the following commands in your terminal/ssh session.
+'''4.''' Determine which board you have. The two common options are "STANDARD" or "FULLSPEC". Information on which model you have can be found at the [https://github.com/piscsi/piscsi/wiki/Hardware-Versions Hardware Versions] page. If you purchased your PiSCSI from Tindie, you will have version 2.2 or newer, which are all "FULLSPEC" boards. You can also check the silkscreen on the PiSCSI board for the version number. Enter the following commands in your terminal/ssh session.
The ''AIBOM'' and ''GAMERNIUM'' board types are supported as well, but are not actively tested by the authors.
'''Note:''' You can also use the easyinstall.sh script, that will automate all the steps described below for you. After cloning the repository on your Raspberry Pi, execute the following (defaults to FULLSPEC):
```
-cd ~/RASCSI
+cd ~/piscsi
./easyinstall.sh
```
Or, if you have a '''STANDARD''' board:
```
-cd ~/RASCSI
+cd ~/piscsi
./easyinstall.sh -c=STANDARD
```
-If you ''don't'' use the script, here follows the manual steps to compile and install RaSCSI. If you have the '''FULLSPEC''' board (version 2.1 or newer) use this...
+If you ''don't'' use the script, here follows the manual steps to compile and install PiSCSI. If you have the '''FULLSPEC''' board (version 2.1 or newer) use this...
```
-cd ~/RASCSI/src/raspberrypi
+cd ~/piscsi/src/raspberrypi
make all CONNECT_TYPE=FULLSPEC
sudo make install CONNECT_TYPE=FULLSPEC
```
@@ -62,16 +62,16 @@ If you have the '''STANDARD''' board (version 1.6 or older) use this...
```
cd ~
-git clone https://github.com/akuker/RASCSI.git
-cd ~/RASCSI/src/raspberrypi
+git clone https://github.com/piscsi/piscsi.git
+cd ~/piscsi/src/raspberrypi
make all CONNECT_TYPE=STANDARD
sudo make install CONNECT_TYPE=STANDARD
```
-'''Note:''' Be sure to select the correct connection type in the above step. If you compile for STANDARD and have a FULLSPEC board, the RaSCSI software will not not behave properly, and you will not see images presented on the SCSI bus.
+'''Note:''' Be sure to select the correct connection type in the above step. If you compile for STANDARD and have a FULLSPEC board, the PiSCSI software will not not behave properly, and you will not see images presented on the SCSI bus.
-'''5.''' The last step is to restart the rsyslog daemon (which enables logging), configure systemd to start RaSCSI at boot, start the RaSCSI service, and verify that it is running.
+'''5.''' The last step is to restart the rsyslog daemon (which enables logging), configure systemd to start PiSCSI at boot, start the PiSCSI service, and verify that it is running.
```
sudo systemctl restart rsyslog
@@ -79,34 +79,34 @@ sudo systemctl enable rascsi # optional - start rascsi at boot
sudo systemctl start rascsi
sudo systemctl status rascsi
```
-'''6.''' If the above steps complete successfully, you are now done cloning and building the RaSCSI software.
+'''6.''' If the above steps complete successfully, you are now done cloning and building the PiSCSI software.
== Installing required Linux packages ==
-To actually run the RaSCSI software, you may need to install Linux packages that the software depends on. Without those packages, the software will not run properly, and throw an error when you try to launch it.
+To actually run the PiSCSI software, you may need to install Linux packages that the software depends on. Without those packages, the software will not run properly, and throw an error when you try to launch it.
-If you use the easyinstall.sh script to install RaSCSI it will take care of installing the dependencies for you. But if you are installing manually, you will have to use the package manager on your Linux system to install the required packages yourself:
+If you use the easyinstall.sh script to install PiSCSI it will take care of installing the dependencies for you. But if you are installing manually, you will have to use the package manager on your Linux system to install the required packages yourself:
```
sudo apt-get update && sudo apt-get install git libspdlog-dev libpcap-dev genisoimage python3 python3-venv nginx libpcap-dev protobuf-compiler bridge-utils python3-dev libev-dev libevdev2 -y
```
-Note that when moving to a major new version of RaSCSI there may have been new dependencies introduced, for instance when trying out '''develop''' after having used '''master'''. It is good practice to run the easyinstall.sh script again in these cases.
+Note that when moving to a major new version of PiSCSI there may have been new dependencies introduced, for instance when trying out '''develop''' after having used '''master'''. It is good practice to run the easyinstall.sh script again in these cases.
== Upgrading an existing installation to the latest ==
-As this project is still under active development, many of you will want to upgrade your existing RaSCSI software. That's super easy, just follow these steps.
+As this project is still under active development, many of you will want to upgrade your existing PiSCSI software. That's super easy, just follow these steps.
-'''Note:''' Performing the following will stop and restart the RaSCSI software. This will make your RaSCSI presented images disappear and re-appear on the SCSI bus when the service is stopped, and restarted.
+'''Note:''' Performing the following will stop and restart the PiSCSI software. This will make your PiSCSI presented images disappear and re-appear on the SCSI bus when the service is stopped, and restarted.
If you have the '''FULLSPEC''' board (version 2.1 or newer) use this...
```
-cd ~/RASCSI
+cd ~/piscsi
sudo systemctl stop rascsi
sudo apt-get update && sudo apt-get install git libspdlog-dev libpcap-dev genisoimage python3 python3-venv nginx libpcap-dev protobuf-compiler bridge-utils python3-dev libev-dev libevdev2 -y
git pull
-cd ~/RASCSI/src/raspberrypi
+cd ~/piscsi/src/raspberrypi
make clean
make all CONNECT_TYPE=FULLSPEC
sudo make install CONNECT_TYPE=FULLSPEC
@@ -117,11 +117,11 @@ sudo systemctl status rascsi
If you have the '''STANDARD''' board (version 1.6 or older) use this...
```
-cd ~/RASCSI
+cd ~/piscsi
sudo systemctl stop rascsi
sudo apt-get update && sudo apt-get install git libspdlog-dev libpcap-dev genisoimage python3 python3-venv nginx libpcap-dev protobuf-compiler bridge-utils python3-dev libev-dev libevdev2 -y
git pull
-cd ~/RASCSI/src/raspberrypi
+cd ~/piscsi/src/raspberrypi
make clean
make all CONNECT_TYPE=STANDARD
sudo make install CONNECT_TYPE=STANDARD
@@ -129,29 +129,29 @@ sudo systemctl start rascsi
sudo systemctl status rascsi
```
-= Reviewing the RaSCSI service logs =
+= Reviewing the PiSCSI service logs =
-Logging for the RaSCSI daemon can be found in /var/log/rascsi.log
+Logging for the PiSCSI daemon can be found in /var/log/rascsi.log
Once you've completed the steps above, you can confirm the daemon is running by checking /var/log/rascsi.log
```
-pi@raspberrypi:~/RASCSI/src/raspberrypi $ cat /var/log/rascsi.log
-Nov 5 08:52:40 rasp32 RASCSI[32588]: SCSI Target Emulator RaSCSI Reloaded version 22.11 (Oct 26 2022 11:49:27)
-Nov 5 08:52:40 rasp32 RASCSI[32588]: Powered by XM6 TypeG Technology / Copyright (C) 2016-2020 GIMONS
-Nov 5 08:52:40 rasp32 RASCSI[32588]: Copyright (C) 2020-2022 Contributors to the RaSCSI Reloaded project
-Nov 5 08:52:40 rasp32 RASCSI[32588]: Connect type: FULLSPEC
+pi@raspberrypi:~/piscsi/src/raspberrypi $ cat /var/log/rascsi.log
+Nov 5 08:52:40 rasp32 piscsi[32588]: SCSI Target Emulator PiSCSI Reloaded version 22.11 (Oct 26 2022 11:49:27)
+Nov 5 08:52:40 rasp32 piscsi[32588]: Powered by XM6 TypeG Technology / Copyright (C) 2016-2020 GIMONS
+Nov 5 08:52:40 rasp32 piscsi[32588]: Copyright (C) 2020-2022 Contributors to the PiSCSI Reloaded project
+Nov 5 08:52:40 rasp32 piscsi[32588]: Connect type: FULLSPEC
```
-If you see output similar to the above, the RaSCSI service has compiled without issue, and you've created and started the service successfully.
+If you see output similar to the above, the PiSCSI service has compiled without issue, and you've created and started the service successfully.
= I have the software, what next? =
-With the above steps completed, we proceed to [[Connecting the RaSCSI]]. This document covers SCSI devices, termination and how to connect your RaSCSI device to a computer.
+With the above steps completed, we proceed to [[Connecting the PiSCSI]]. This document covers SCSI devices, termination and how to connect your PiSCSI device to a computer.
= (Optional) Cross-Compile Instructions =
-This section does not apply to most users. If you want to cross-compile RaSCSI from an Ubuntu host, you first need to install the cross compiler packages:
+This section does not apply to most users. If you want to cross-compile PiSCSI from an Ubuntu host, you first need to install the cross compiler packages:
```
sudo apt install gcc-arm-linux-gnueabihf g++-arm-linux-gnueabihf binutils-arm-linux-gnueabihf
@@ -177,8 +177,8 @@ To explicitly build for ARM (ARM is also the default, so this shouldn't be neces
= Compiling on x86/x86_64 Linux PCs =
-A lot of the rascsi code does not require the RaSCSI hardware and can be run and tested on a regular Linux PC. rasctl can be run on a Linux PC without restrictions and can access rascsi on the Pi remotely with the -h option.
-With these environment settings the complete RaSCSI code compiles with g++ or clang++ (faster than g++) on x86/x86_64 PCs:
+A lot of the rascsi code does not require the PiSCSI hardware and can be run and tested on a regular Linux PC. scsictl can be run on a Linux PC without restrictions and can access rascsi on the Pi remotely with the -h option.
+With these environment settings the complete PiSCSI code compiles with g++ or clang++ (faster than g++) on x86/x86_64 PCs:
```
EXTRA_FLAGS="-DSPDLOG_FMT_EXTERNAL -DFMT_HEADER_ONLY"
@@ -188,28 +188,28 @@ Using the Eclipse IDE for development helps with browsing, refactoring and unit-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/Sharp-X68000.mediawiki b/Sharp-X68000.mediawiki
index fc3c3f4..73f0bdb 100644
--- a/Sharp-X68000.mediawiki
+++ b/Sharp-X68000.mediawiki
@@ -3,44 +3,44 @@ RaSCSI was originally developed using the SCSI controller code of the X68000 emu
Other users have reported it working on a first gen X68000, ACE, EXPERT, XVI, PRO2, SUPER, etc. It is safe to say that it works well on the X68000 platform. The SCSI interface of a SUPER or later is recommended. Multiple SCSI interfaces in one system work well too.
-As of RaSCSI Reloaded v22.10.01, SASI support has been deprecated.
+As of PiSCSI Reloaded v22.10.01, SASI support has been deprecated.
== X68000 OS support ==
Human68k 3.02 is recommended to use all functions, because the Ethernet function and the remote drive function are provided only by the Human68k device driver. If you are using only SCSI mass storage devices, it is no problem to use NetBSD etc.
= X68000 Features =
-RaSCSI implements a virtual SCSI device called the Host Bridge in order to bridge the Raspberry Pi host system and the X68000. The Host Bridge together with the following X68000 specific drivers enables a range of features.
+PiSCSI implements a virtual SCSI device called the Host Bridge in order to bridge the Raspberry Pi host system and the X68000. The Host Bridge together with the following X68000 specific drivers enables a range of features.
There are two special drivers for the X68000 that enable these features.
* RASDRV.SYS -- Host Drive driver
* RASETHER.SYS -- Ethernet driver
-They can either be build from C source code, found under src/x68k/, or in the RASDRIVER.XDF and RASDRIVER.HDS drive images that are found under bin/x68k/. For convenience, it is recommended to mount these image directly with RaSCSI to easily get the drivers as well as other support programs on to your X68000 system.
+They can either be build from C source code, found under src/x68k/, or in the RASDRIVER.XDF and RASDRIVER.HDS drive images that are found under bin/x68k/. For convenience, it is recommended to mount these image directly with PiSCSI to easily get the drivers as well as other support programs on to your X68000 system.
== Ethernet driver ==
Provides equivalent networking functionality of a Neptune-X Ethernet adapter, which is an Ethernet box that's connected over the SCSI bus. It uses a TAP device on the Raspberry Pi to translate network traffic. Similar to Ether+.
It was developed while referencing Shi-MAD's ''ether_ne.sys ver0.03 +M01 +1 +L12'' driver which itself is a modified version of the ''ether_ne.sys'' driver for the ISA bus bridge Ethernet adapter Neptune-X. Its use shall therefore be governed by the terms & conditions of those drivers.
-It is also possible to use the original Neptune-X driver with RaSCSI.
+It is also possible to use the original Neptune-X driver with PiSCSI.
Source code available at [https://github.com/rdmark/RASCSI-X68k/tree/main/src/x68k/RASETHER]
== Host File System driver ==
Provides a similar functionality as WindrvXM, which has become the de-facto standard on X68000 emulators. This makes it possible to mount the Raspberry Pi file system as a remote drive by connecting the X68000 to the host using a Host Bridge device.
-You can attach the Host Bridge device to RaSCSI just like any other device, either by passing 'bridge' as the file parameter, or using the 'scbr' device type.
+You can attach the Host Bridge device to PiSCSI just like any other device, either by passing 'bridge' as the file parameter, or using the 'scbr' device type.
```
/usr/local/bin/rascsi -ID6 bridge
--or- /usr/local/bin/rasctl -i 6 -c attach -t bridge
+-or- /usr/local/bin/scsictl -i 6 -c attach -t bridge
```
Source code available at [https://github.com/rdmark/RASCSI-X68k/tree/main/src/x68k/RASDRV]
== RASCTL.X ==
-Similarly to rasctl for RaSCSI on the host side, a similar utility has been implemented in a Human68k executable called RASCTL.X which enables you to attach, detach, change media, set protection flags, stop rascsi, and shut down the Raspberry Pi from the X68000 system.
+Similarly to rasctl for PiSCSI on the host side, a similar utility has been implemented in a Human68k executable called RASCTL.X which enables you to attach, detach, change media, set protection flags, stop rascsi, and shut down the Raspberry Pi from the X68000 system.
Usage is very similar to rasctl, so refer to its man page.
@@ -119,7 +119,7 @@ Extended options for RASETHER
```
== Configure the Raspberry Pi ==
-FOR WIFI REFER TO [https://github.com/akuker/RASCSI/wiki/Dayna-Port-SCSI-Link]
+FOR WIFI REFER TO [https://github.com/piscsi/piscsi/wiki/Dayna-Port-SCSI-Link]
FOR LAN REFER TO ...
@@ -130,10 +130,10 @@ Create the TAP interface like this, for example:
```
[Add to your startup script, such as /etc/rc.local]
- ip tuntap add ras0 mode tap user root
- ip link set ras0 up
- ifconfig ras0 inet 192.168.68.1/8 up
- route add -net 192.168.68.0 netmask 255.255.255.0 dev ras0
+ ip tuntap add piscsi0 mode tap user root
+ ip link set piscsi0 up
+ ifconfig piscsi0 inet 192.168.68.1/8 up
+ route add -net 192.168.68.0 netmask 255.255.255.0 dev piscsi0
```
-OUTDATED END-
@@ -142,7 +142,7 @@ This enables a network connection between the Raspberry Pi on 10.10.20.2 and X68
Additional configuration may be required depending on your environment. For WiFi, please utilize RASCSI Reloaded to mount the RASCI BRIDGE using 10.10.20.1/24.
= Host Filesystem Integration =
-RaSCSI provides similar functionality to Windrv and WindrvXM that are commonly used with X68000 emulators XM6/XM6 Kai/TypeG. Using the RASDRV.SYS driver you can mount and access the Raspberry Pi file system from your X68000 and carry out any file operations.
+PiSCSI provides similar functionality to Windrv and WindrvXM that are commonly used with X68000 emulators XM6/XM6 Kai/TypeG. Using the RASDRV.SYS driver you can mount and access the Raspberry Pi file system from your X68000 and carry out any file operations.
Registering the device driver is simple. F.e. add this to latter part of CONFIG.SYS:
@@ -163,4 +163,4 @@ If you're using SUSIE, please configure RASDRV.SYS to be loaded before SUSIE. It
For other options, refer to the documentation for WindrvXM.
= Other Versions =
-[https://github.com/RaSCSI/RaSCSI RaSCSI] contains the original RaSCSI codebase by GIMONS. It maintains the original feature set geared towards X68000, such as the Net Device and Host Services. You may want to try this version of the software out instead if you're using your RaSCSI with a X68000. It's expected to be compatible with RaSCSI Reloaded hardware.
\ No newline at end of file
+[https://github.com/rascsi/rascsi RaSCSI] contains the original RaSCSI codebase by GIMONS. It maintains the original feature set geared towards X68000, such as the Net Device and Host Services. You may want to try this version of the software out instead if you're using your RaSCSI with a X68000. It's expected to be compatible with PiSCSI and RaSCSI hardware.
\ No newline at end of file
diff --git a/Supercapacitor-UPS.md b/Supercapacitor-UPS.md
index f5bd93f..70414a2 100644
--- a/Supercapacitor-UPS.md
+++ b/Supercapacitor-UPS.md
@@ -1,10 +1,10 @@
# Background
-The RaSCSI service caches data in RAM. When power is pulled from a RaSCSI/Raspberry Pi setup, it is possible to lose some or all of this data. In order to allow a graceful shutdown of the RaSCSI service and the Raspberry Pi OS, a USP can be added to the assembly. This way, when power is removed, the Raspberry Pi will have enough saved power to properly shut down.
+The PiSCSI service caches data in RAM. When power is pulled from a PiSCSI/Raspberry Pi setup, it is possible to lose some or all of this data. In order to allow a graceful shutdown of the PiSCSI service and the Raspberry Pi OS, a USP can be added to the assembly. This way, when power is removed, the Raspberry Pi will have enough saved power to properly shut down.
# Prototype Phase: Dr. Scott M. Baker design
-Dr. Scott M. Baker has designed two different UPS versions that will work with the RaSCSI. He has generously made these available on this blog for other people to use. [Tutorial video](https://www.youtube.com/watch?v=j5Bv8r3TVPM).
+Dr. Scott M. Baker has designed two different UPS versions that will work with the PiSCSI. He has generously made these available on this blog for other people to use. [Tutorial video](https://www.youtube.com/watch?v=j5Bv8r3TVPM).
## Assembly
![image](https://user-images.githubusercontent.com/34318535/165860429-e71abe1e-e8b8-42eb-8194-94afd55ff2b6.png)
@@ -31,6 +31,6 @@ For me, the pin names were very confusing. Here's my conversion table:
You'll need to install the [TinyWireS](https://github.com/nadavmatalon/TinyWireS) library following [these instructions](https://www.baldengineer.com/installing-arduino-library-from-github.html).
-# "Official" RaSCSI version
+# "Official" PiSCSI version
-For the RaSCSI, akuker will be focusing on the 12v version of Dr. Baker's UPS. A modified version of this is being designed and will be offered in the Tindie store (when it is ready).
\ No newline at end of file
+For the PiSCSI, akuker will be focusing on the 12v version of Dr. Baker's UPS. A modified version of this is being designed and will be offered in the Tindie store (when it is ready).
\ No newline at end of file
diff --git a/Supported-Device-Types.md b/Supported-Device-Types.md
index ee5d51c..cc68ec3 100644
--- a/Supported-Device-Types.md
+++ b/Supported-Device-Types.md
@@ -1,20 +1,20 @@
# Overview
-This page summarizes the emulated device supported by RaSCSI, with notes on compatibility and device drivers for various platforms.
+This page summarizes the emulated device supported by PiSCSI, with notes on compatibility and device drivers for various platforms.
# Device Types
Device|Key|Supported Platforms|Notes
---|---|---|---
Hard Disk Drive|SCHD|all|
-CD/DVD Drive|SCCD|all|The [Apple CD-ROM drivers](https://github.com/akuker/RASCSI/wiki/Drive-Setup#Mounting_CD_ISO_or_MO_images) in combination with RaSCSI is known to lead to incompatibility with particular ISO images
+CD/DVD Drive|SCCD|all|The [Apple CD-ROM drivers](https://github.com/piscsi/piscsi/wiki/Drive-Setup#Mounting_CD_ISO_or_MO_images) in combination with PiSCSI is known to lead to incompatibility with particular ISO images
Removable Disk Drive|SCRM|all*|*Functionality may depend on INQUIRY masquerading and proprietary device drivers, f.e. [Iomega Floptical](Iomega-Floptical)
Magneto-Optical Drive|SCMO|NeXT, X68000, etc.|
DaynaPORT SCSI/Link|SCDP|Macintosh, Atari ST|Requires [device drivers](Dayna-Port-SCSI-Link)
Host Bridge|SCBR|X68000|Enables ethernet networking and mounting a remote file system. Requires [device drivers](https://github.com/rdmark/RASCSI-X68k/wiki)
-Host Services|SCHS|Atari ST|Enables remote control of the RaSCSI. Requires [device drivers](RaSCSI-Client-Tools)
-Printer|SCLP|Atari ST|Requires [device drivers](RaSCSI-Client-Tools)
+Host Services|SCHS|Atari ST|Enables remote control of the PiSCSI. Requires [device drivers](PiSCSI-Client-Tools)
+Printer|SCLP|Atari ST|Requires [device drivers](PiSCSI-Client-Tools)
# Image Types
-This describes the file endings that RaSCSI will recognize automatically, with usage notes. For non-recognized image types, you will have to specify the device type to use it as when attaching.
+This describes the file endings that PiSCSI will recognize automatically, with usage notes. For non-recognized image types, you will have to specify the device type to use it as when attaching.
Image Type|File ending|Usage notes
---|---|---
diff --git a/Transceiver-Comparison.md b/Transceiver-Comparison.md
index 01e47bb..7665d46 100644
--- a/Transceiver-Comparison.md
+++ b/Transceiver-Comparison.md
@@ -1,9 +1,9 @@
-The original RaSCSI uses the [SN74LS641](https://www.ti.com/lit/ds/symlink/sn74ls641.pdf) bus transceiver. However, with each device needed 4 of these @ $3.30 each, the amounts to a significant percentage of the cost. The following contains some notes regarding what other SCSI emulators have used.
+The original PiSCSI uses the [SN74LS641](https://www.ti.com/lit/ds/symlink/sn74ls641.pdf) bus transceiver. However, with each device needed 4 of these @ $3.30 each, the amounts to a significant percentage of the cost. The following contains some notes regarding what other SCSI emulators have used.
-| Suitable for RaSCSI? | Product | Chip and Datasheet | Cost ($) | Qty needed | Notes |
+| Suitable for PiSCSI? | Product | Chip and Datasheet | Cost ($) | Qty needed | Notes |
| - | - | - | - | - | - |
-| ✅ | RaSCSI Original Version | [SN74LS641-1](https://www.mouser.com/ProductDetail/Texas-Instruments/SN74LS641-1DW?qs=SL3LIuy2dWxXHvPKLk%252BfLw%3D%3D) | [$3.66 US](https://www.mouser.com/ProductDetail/Texas-Instruments/SN74LS641-1DW?qs=SL3LIuy2dWxXHvPKLk%252BfLw%3D%3D)| 4 | VCC is 5v |
+| ✅ | PiSCSI Original Version | [SN74LS641-1](https://www.mouser.com/ProductDetail/Texas-Instruments/SN74LS641-1DW?qs=SL3LIuy2dWxXHvPKLk%252BfLw%3D%3D) | [$3.66 US](https://www.mouser.com/ProductDetail/Texas-Instruments/SN74LS641-1DW?qs=SL3LIuy2dWxXHvPKLk%252BfLw%3D%3D)| 4 | VCC is 5v |
| ✅❓ | Potential Candidate | [SN74ALS245A-1](https://www.ti.com/lit/ds/symlink/sn74als245a.pdf) | [$1.42 US](https://www.mouser.com/ProductDetail/Texas-Instruments/SN74ALS245A-1NSR?qs=zhgwDAIOVxtxt0cXsshpuw%3D%3D) | 4 | VCC 5v, -1 unit will sink 48mA |
| ✅❓ | Potential Candidate | [SN74F245DW](https://www.ti.com/lit/ds/symlink/sn74f245.pdf?)| [$1.11 US](https://www.mouser.com/ProductDetail/Texas-Instruments/SN74F245DW?qs=rshUhwi3fbYzYsqSsk5U6A%3D%3D) | 4 | Low state current can sink 48mA|
| ✅❓ | Potential Candidate | [SN74ABT245B](https://www.ti.com/lit/ds/symlink/sn74abt245b.pdf) | [$1.00 - $1.30 US](https://www.mouser.com/c/semiconductors/logic-ics/bus-transceivers/?m=Texas%20Instruments&series=SN74ABT245B) | 4 | |
@@ -16,7 +16,7 @@ The original RaSCSI uses the [SN74LS641](https://www.ti.com/lit/ds/symlink/sn74l
| ❌ | Unsuitable| [SN7406DRG4](https://www.ti.com/lit/ds/symlink/sn7406.pdf?HQS=TI-null-null-digikeymode-df-pf-null-wwe&ts=1599282149626)| 1.34 | 4 | Can only sink 40mA. Will require new layout and increase in chip count as it has less i/o than above. |
| ❌ | Unsuitable | [74HCT245D](https://assets.nexperia.com/documents/data-sheet/74HC_HCT245.pdf) | [$0.69 US](https://www.mouser.com/ProductDetail/Nexperia/74HCT245D653?qs=P62ublwmbi%2FKRO6CQW%252BPyg%3D%3D) | 4 | VCC is 5v. Datasheet reads input clamping current -20mA |
-Note: as of 2020-08-04 the **SN74LS641-1** is the transceiver suggested when building the RaSCSI.
+Note: as of 2020-08-04 the **SN74LS641-1** is the transceiver suggested when building the PiSCSI.
Some additional parts
@@ -95,8 +95,8 @@ See [section 5.4 of the SCSI-2 standard](https://www.staff.uni-mainz.de/tacke/sc
configurations, it is recommended that the nominal switching threshold be approximately 1.4 V.
-### RaSCSI
-From [the v1.6 schematic](https://github.com/akuker/RASCSI/blob/master/hw/rascsi_1p6/rascsi_din.sch.pdf), the following signals need to be bidirectional:
+### PiSCSI
+From [the v1.6 schematic](https://github.com/piscsi/piscsi/blob/master/hw/rascsi_1p6/rascsi_din.sch.pdf), the following signals need to be bidirectional:
> DP, D0, D1, D2, D3, D4, D5, D6, D7
@@ -120,7 +120,7 @@ They should probably be Schmitt-trigger inputs on the SCSI bus side. See the "Si
0.5v SCSI Maximum Output Voltage for Asserted Signal
0.2v Typical Driver-Asserted Signal
-From [the 2.x schematic](https://github.com/akuker/RASCSI/blob/master/hw/rascsi_2p1/rascsi_2p1_sch.pdf), all signals are bidirectional, switched on three different signals.
+From [the 2.x schematic](https://github.com/piscsi/piscsi/blob/master/hw/rascsi_2p1/rascsi_2p1_sch.pdf), all signals are bidirectional, switched on three different signals.
Switched by `PI-DTD`:
diff --git a/Troubleshooting.mediawiki b/Troubleshooting.mediawiki
index 7f3e1c2..19dc782 100644
--- a/Troubleshooting.mediawiki
+++ b/Troubleshooting.mediawiki
@@ -1,18 +1,18 @@
= Hardware troubleshooting =
== Schematics ==
-Schematics for the RaSCSI Reloaded are available in pdf format. Choose the one that corresponds to the hardware revision of your particular board.
+Schematics for the PiSCSI Reloaded are available in pdf format. Choose the one that corresponds to the hardware revision of your particular board.
=== Full-size ===
-* [/akuker/RASCSI/wiki/sch/rascsi_1p5_sch.pdf 1p5]
-* [/akuker/RASCSI/wiki/sch/rascsi_1p6_sch.pdf 1p6]
-* [/akuker/RASCSI/wiki/sch/rascsi_2p2_sch.pdf 2p2]
-* [/akuker/RASCSI/wiki/sch/rascsi_2p3_sch.pdf 2p3]
-* [/akuker/RASCSI/wiki/sch/rascsi_2p4_sch.pdf 2p4]
-* [/akuker/RASCSI/wiki/sch/rascsi_2p5_sch.pdf 2p5]
+* [/piscsi/piscsi/wiki/sch/rascsi_1p5_sch.pdf 1p5]
+* [/piscsi/piscsi/wiki/sch/rascsi_1p6_sch.pdf 1p6]
+* [/piscsi/piscsi/wiki/sch/rascsi_2p2_sch.pdf 2p2]
+* [/piscsi/piscsi/wiki/sch/rascsi_2p3_sch.pdf 2p3]
+* [/piscsi/piscsi/wiki/sch/rascsi_2p4_sch.pdf 2p4]
+* [/piscsi/piscsi/wiki/sch/rascsi_2p5_sch.pdf 2p5]
=== Zero ===
-* [/akuker/RASCSI/wiki/sch/rascsi_zero_1p0_sch.pdf 1p0]
+* [/piscsi/piscsi/wiki/sch/rascsi_zero_1p0_sch.pdf 1p0]
== Termination ==
First step in troubleshooting is to check the termination. Seriously. Check this.
@@ -23,11 +23,11 @@ https://lowendmac.com/1998/termination-explained/
Re-check it again.
== Loopback Testing ==
-A way to check out the RaSCSI hardware is to create a loopback cable. This can be done using jumper wires or a specially-constructed DB25 male jack connector can be created to allow easy re-use.
+A way to check out the PiSCSI hardware is to create a loopback cable. This can be done using jumper wires or a specially-constructed DB25 male jack connector can be created to allow easy re-use.
[[images/loopback_picture.jpg | height = 150px]][[images/loopback_option_2.jpg | height=200px]]
-The diagram for the loopback connections is shown here. Note that the RaSCSI connector is a FEMALE connector. If you are using a gender changer (as in the previous picture), you want to use the MALE connector pinout
+The diagram for the loopback connections is shown here. Note that the PiSCSI connector is a FEMALE connector. If you are using a gender changer (as in the previous picture), you want to use the MALE connector pinout
{|
| '''FEMALE connector pinout''' [[images/SCSI_Loopback_Female.png]]
@@ -35,13 +35,13 @@ The diagram for the loopback connections is shown here. Note that the RaSCSI con
|}
[https://drive.google.com/file/d/1LOT1FmA7XpJ3NWiGojUwsjnxTC_x_HD8/view?usp=sharing Link to original drawing]
-Once you have the loopback connections made, you can checkout the RaSCSI source code and run the loopback test python script. (Note: This requires python3 to run)
+Once you have the loopback connections made, you can checkout the PiSCSI source code and run the loopback test python script. (Note: This requires python3 to run)
'''Before running this test:'''
- '''Ensure that you have termination enabled before running this test!!'''
-- '''Ensure that the RaSCSI service is NOT running''' `sudo systemctl stop rascsi`
+- '''Ensure that the PiSCSI service is NOT running''' `sudo systemctl stop rascsi`
- '''Double check your loopback that you do NOT have TERM POWER connected to Ground!!!'''
@@ -49,16 +49,16 @@ Once you have the loopback connections made, you can checkout the RaSCSI source
```
cd ~
-git clone https://github.com/akuker/RASCSI.git
-cd ~/RASCSI
+git clone https://github.com/piscsi/piscsi.git
+cd ~/piscsi
# FOR NOW, the code is only available on the 'develop' branch
git checkout develop
-cd ~/RASCSI/src/loopback_test/
+cd ~/piscsi/src/loopback_test/
pip install RPi.GPIO
./test.py
```
-The Python test script will list all of the SCSI signals that are not working properly. You can the use the [https://github.com/akuker/RASCSI/raw/master/hw/rascsi_2p3/rascsi_2p3_sch.pdf schematic]to debug if there are any broken traces, lifted pads or bad solder joints.
+The Python test script will list all of the SCSI signals that are not working properly. You can the use the [https://github.com/piscsi/piscsi/raw/master/hw/rascsi_2p3/rascsi_2p3_sch.pdf schematic]to debug if there are any broken traces, lifted pads or bad solder joints.
Note: this concept was original created by Saybur for the Scuznet board: https://github.com/saybur/scuznet/tree/master/testing
@@ -75,12 +75,12 @@ You can test each individual SCSI signal using a multimeter. This procedure is l
Turn on the termination DIP switches
-Pull out your trusty multimeter. With the RaSCSI software running, disconnect all SCSI devices and check the voltages:
+Pull out your trusty multimeter. With the PiSCSI software running, disconnect all SCSI devices and check the voltages:
* TPWR should be 5v
* D0-D7 should be around 3.08v
* Control signals should be around 3.08v
-STOP the RaSCSI service `sudo systemctl stop rascsi`.
+STOP the PiSCSI service `sudo systemctl stop rascsi`.
* Check the LEDS
raspi-gpio set 4 op dh # ACT LED should be ON
@@ -222,7 +222,7 @@ STOP the RaSCSI service `sudo systemctl stop rascsi`.
== SCSI cable issues ==
-SCSI is sensitive to cable length and cabling quality issues. If you are experiencing failures with certain operations in your sampler, try using a shorter cable! Note that failures may not necessarily show up as errors in the RaSCSI logs, since it might be sending messages perfectly fine that are being lost in transit.
+SCSI is sensitive to cable length and cabling quality issues. If you are experiencing failures with certain operations in your sampler, try using a shorter cable! Note that failures may not necessarily show up as errors in the PiSCSI logs, since it might be sending messages perfectly fine that are being lost in transit.
= Software =
== SPDLOG compile error ==
@@ -258,9 +258,9 @@ dtoverlay=disable-bt
dtoverlay=disable-wifi
```
-== The RaSCSI is behaving erratically ==
+== The PiSCSI is behaving erratically ==
-If your RaSCSI setup is starting up but behaving erratically, it may not be getting enough power from the power supply or SCSI bus. Symptoms include the network interface going down randomly, or the SCSI host not recognizing attached devices due to lack of termination power.
+If your PiSCSI setup is starting up but behaving erratically, it may not be getting enough power from the power supply or SCSI bus. Symptoms include the network interface going down randomly, or the SCSI host not recognizing attached devices due to lack of termination power.
One way to determine that the Raspberry Pi isn't getting enough power, is to observe the syslog and look for Under-voltage detected! messages.
diff --git a/Vintage-Web-Proxy.md b/Vintage-Web-Proxy.md
index f4923b4..15c36e7 100644
--- a/Vintage-Web-Proxy.md
+++ b/Vintage-Web-Proxy.md
@@ -1,16 +1,16 @@
# Introduction
-If you're reading this, you may just have gotten your vintage computer online, through RaSCSI's [DaynaPORT adapter emulation](https://github.com/akuker/RASCSI/wiki/Dayna-Port-SCSI-Link), other any other means. And now you're asking yourself, what's next?
+If you're reading this, you may just have gotten your vintage computer online, through PiSCSI's [DaynaPORT adapter emulation](https://github.com/piscsi/piscsi/wiki/Dayna-Port-SCSI-Link), other any other means. And now you're asking yourself, what's next?
While a vintage computer is excellent for [telneting into a BBS](https://www.pcmag.com/news/7-modern-bbses-worth-calling-today) such as Level 29, or browsing websites made for vintage computers such as http://www.theoldnet.com or http://68k.news, the broader modern Web is an unforgiving place for a vintage computer and its equally vintage browsers. The sheet amount of data that they send to the user agent, javascript libraries thousands of lines long, massive images in exotic formats, multimedia, etc... It may take minutes to load a page, and minutes more to parse and reflow the DOM over and over, and you're lucky if it doesn't crash when running out of memory.
And the biggest practical hurdle: the move to enforcing encrypted https connections on a vast majority of sites (I blame Google for that) that even the last versions of classic Mac OS (or AmigaOS, Windows 98, etc.) aren't able to decrypt due to expired root certificates or other cryptographic limitations.
-Vintage Web Proxy servers to the rescue! The Raspberry Pi that RaSCSI runs on is a versatile little device, and if it is not already overburdened by other software, it should be able to run a proxy server in parallel with RaSCSI. This page will cover a few options, tested in particular with older Macs.
+Vintage Web Proxy servers to the rescue! The Raspberry Pi that PiSCSI runs on is a versatile little device, and if it is not already overburdened by other software, it should be able to run a proxy server in parallel with PiSCSI. This page will cover a few options, tested in particular with older Macs.
# Macproxy
-*Note:* As of RaSCSI 21.11.01, easyinstall.sh has an option to install Macproxy for you.
+*Note:* As of PiSCSI 21.11.01, easyinstall.sh has an option to install Macproxy for you.
Despite the name, the use of Macproxy is not at all limited to Macs. It is a super light-weight proxy implemented as a Python script running a Flask app, which will translate https requests to http, and strip out the vast majority of linked contents such as style sheets and JavaScript, while suppressing inline scripts as well. It has support for binary file downloading, and will retain embedded images to be decoded by vintage browsers.
@@ -41,7 +41,7 @@ The author has tested and recommends the _0.11.1-noffmpeg_ release for ARM. By u
Follow the [Linux installation](https://github.com/atauenis/webone/wiki/Linux-installation) instructions on that project's wiki to install and configure WebOne.
-By default, WebOne will run on port 8080 which conflicts with the RaSCSI Web Interface. After installing the software, you'd want to edit `/etc/webone.conf` and change the `Port` line in the [Server] section to something like:
+By default, WebOne will run on port 8080 which conflicts with the PiSCSI Web Interface. After installing the software, you'd want to edit `/etc/webone.conf` and change the `Port` line in the [Server] section to something like:
```
Port=8088
diff --git a/Web-Interface.mediawiki b/Web-Interface.mediawiki
index 5919edd..045dedb 100644
--- a/Web-Interface.mediawiki
+++ b/Web-Interface.mediawiki
@@ -1,17 +1,17 @@
= Security Notice! =
-By default, there is no user authentication for the RaSCSI Web Interface! If you intend to use it on a public network, it is strongly recommended that you [[Web Interface#Enable Authentication|enable authentication]].
+By default, there is no user authentication for the PiSCSI Web Interface! If you intend to use it on a public network, it is strongly recommended that you [[Web Interface#Enable Authentication|enable authentication]].
Without authentication, anyone on your local network can do things to your Raspberry Pi like delete data, fill up your drive, reboot, etc.
__TOC__
-= Setup RaSCSI Web Interface =
+= Setup PiSCSI Web Interface =
These instructions assume you've worked through the [[Setup Instructions]] and [[Drive Setup]] articles. If you have not done so already, visit those pages first, as there are dependencies in this article that rely on those instructions being completed already.
-The RaSCSI web interface is written in Python and served up with NGINX Server.
+The PiSCSI web interface is written in Python and served up with NGINX Server.
NOTE: This process is not required if you've ran `easyinstall.sh`
@@ -20,7 +20,7 @@ NOTE: This process is not required if you've ran `easyinstall.sh`
sudo apt install genisoimage python3 python3-venv nginx unzip protobuf-compiler
```
-'''2.''' Gives nginx the needed permissions to manage the RaSCSI service and reboot the Raspberry Pi. Enter the following command to edit your sudoers file
+'''2.''' Gives nginx the needed permissions to manage the PiSCSI service and reboot the Raspberry Pi. Enter the following command to edit your sudoers file
```
sudo visudo
@@ -40,19 +40,19 @@ Once done, save your changes and exit.
'''4.''' Compile the Python protobuf library
-This expects that you have checked out the RaSCSI code to ~/RASCSI as the pi user.
+This expects that you have checked out the PiSCSI code to ~/piscsi as the pi user.
```
-protoc -I=/home/pi/RASCSI/src/raspberrypi --python_out=/home/pi/RASCSI/python/web/src rascsi_interface.proto
+protoc -I=/home/pi/piscsi/src/raspberrypi --python_out=/home/pi/piscsi/python/web/src rascsi_interface.proto
```
'''5.''' Create the new service
```
- sudo cp -f ~/RASCSI/python/web/service-infra/nginx-default.conf /etc/nginx/sites-available/default
- sudo cp -f ~/RASCSI/python/web/service-infra/502.html /var/www/html/502.html
+ sudo cp -f ~/piscsi/python/web/service-infra/nginx-default.conf /etc/nginx/sites-available/default
+ sudo cp -f ~/piscsi/python/web/service-infra/502.html /var/www/html/502.html
- sudo cp ~/RASCSI/src/web/service-infra/rascsi-web.service /etc/systemd/system/rascsi-web.service
+ sudo cp ~/piscsi/src/web/service-infra/rascsi-web.service /etc/systemd/system/rascsi-web.service
sudo systemctl daemon-reload
sudo systemctl enable rascsi-web
sudo systemctl start rascsi-web
@@ -60,7 +60,7 @@ protoc -I=/home/pi/RASCSI/src/raspberrypi --python_out=/home/pi/RASCSI/python/we
'''6.''' Adjust permissions on the Images Directory
-The RaSCSI web interface expects the disk images to be stored in /home/pi/images . That directory should already exist, as it is covered in the [[Drive Setup]] document. If you haven't done so already, follow the instructions in the [[Drive Setup]] document before proceeding.
+The PiSCSI web interface expects the disk images to be stored in /home/pi/images . That directory should already exist, as it is covered in the [[Drive Setup]] document. If you haven't done so already, follow the instructions in the [[Drive Setup]] document before proceeding.
For NGINX to have permissions to read and write to /home/pi/images, we will adjust permissions on /home/pi/images and add the www-data account to the pi group. Run the following command to make these changes.
@@ -84,7 +84,7 @@ www-data : www-data pi
'''7.''' Create the config dir
-The RaSCSI Web Interface stores configuration files in a directly, by default ~/.config/rascsi . You need to create and adjust the permissions on this directory.
+The PiSCSI Web Interface stores configuration files in a directly, by default ~/.config/rascsi . You need to create and adjust the permissions on this directory.
```
mkdir -p ~/.config/rascsi
@@ -97,7 +97,7 @@ chmod -R 775 ~/.config/rascsi
If you are not using the rascsi-web service, or have stopped the service, you can launch the Web Interface manually like this:
```
-cd ~/RASCSI/python/web
+cd ~/piscsi/python/web
./start.sh
```
@@ -143,7 +143,7 @@ In our example, the IPv4 IP address of the Pi is 10.0.0.185
= Using the web interface directly from your Mac =
-If your Mac has a network connection, and can communicate with your Raspberry Pi, you can manage RaSCSI from that computer.
+If your Mac has a network connection, and can communicate with your Raspberry Pi, you can manage PiSCSI from that computer.
The functionality of the web interface has been tested with the following "vintage" web browsers. The formatting doesn't look as good as a modern browser, but its still fully usable!
* Netscape 3.x
@@ -154,9 +154,9 @@ The functionality of the web interface has been tested with the following "vinta
= Enable Authentication =
-As of v21.11.01, RaSCSI has opt-in Web Interface user authentication. While the Web Interface still communicates over unencrypted http, this won't protect against sophisticated malicious users and network sniffing, it does protect against casual attacks and misuse.
+As of v21.11.01, PiSCSI has opt-in Web Interface user authentication. While the Web Interface still communicates over unencrypted http, this won't protect against sophisticated malicious users and network sniffing, it does protect against casual attacks and misuse.
-'''Note:''' The below process has been automated in the easyinstall.sh script. Launch the script and choose the ''enable authentication for the RaSCSI Web Interface'' option to enable authentication and grant access to the user who launched the script.
+'''Note:''' The below process has been automated in the easyinstall.sh script. Launch the script and choose the ''enable authentication for the PiSCSI Web Interface'' option to enable authentication and grant access to the user who launched the script.
The Web Interface will enable authentication if the rascsi group exists on the system.
@@ -172,4 +172,4 @@ $ sudo usermod -a -G rascsi pi
Now when you load the Web Interface, you should see a login form in the header of the page. The login session will be stored in a browser cookie and retained as long as the cookie is alive. Use the Log Out function in the header to terminate the session.
-When authentication is enabled, anonymous users will only be able to carry out certain basic actions such as viewing device info or accessing RaSCSI logs.
\ No newline at end of file
+When authentication is enabled, anonymous users will only be able to carry out certain basic actions such as viewing device info or accessing PiSCSI logs.
\ No newline at end of file
diff --git a/_Sidebar.md b/_Sidebar.md
index 9e78b12..2532b35 100644
--- a/_Sidebar.md
+++ b/_Sidebar.md
@@ -1,15 +1,15 @@
-* [Home](/akuker/RASCSI/wiki)
+* [Home](/piscsi/PiSCSI/wiki)
* [Roadmap](./Roadmap)
* Initial Setup
- * [Assembly - Full Size](./Full-Size-RaSCSI-Assembly)
- * [Assembly - RaSCSI Zero](./RaSCSI-Zero-Assembly)
- * [Connecting the RaSCSI](./Connecting-the-RaSCSI)
+ * [Assembly - Full Size](./Full-Size-PiSCSI-Assembly)
+ * [Assembly - PiSCSI Zero](./PiSCSI-Zero-Assembly)
+ * [Connecting the PiSCSI](./Connecting-the-PiSCSI)
* [Setup Instructions](./Setup-Instructions)
* [Drive Setup](./Drive-Setup)
* [OLED Status Display (Optional)](./OLED-Status-Display-\(Optional\))
- * [Control Board (Optional)](./RaSCSI-Control-Board)
+ * [Control Board (Optional)](./PiSCSI-Control-Board)
* [Troubleshooting](./Troubleshooting)
* Documentation
* [Hardware Versions](./Hardware-Versions)
@@ -23,8 +23,8 @@
* Companion Apps
* [AFP File Sharing](./AFP-File-Sharing)
* [Vintage Web Proxy](./Vintage-Web-Proxy)
- * [RaSCSI Control Android App](./RaSCSI-Control-Android-App)
- * [RaSCSI Client Tools for Atari Computers](./RaSCSI-Client-Tools)
+ * [PiSCSI Control Android App](./PiSCSI-Control-Android-App)
+ * [PiSCSI Client Tools for Atari Computers](./PiSCSI-Client-Tools)
* Developer Notes
* [Robot Framework Notes](./Robot-Framework-Notes)
* [Transceiver Comparison](./Transceiver-Comparison)
diff --git a/sch/home.md b/sch/home.md
index 0496642..0bfa2d0 100644
--- a/sch/home.md
+++ b/sch/home.md
@@ -1,6 +1,6 @@
-= What is RaSCSI =
+= What is PiSCSI =
{|
-|RaSCSI is a virtual [https://en.wikipedia.org/wiki/Parallel_SCSI SCSI] device emulator that runs on a [https://en.wikipedia.org/wiki/Raspberry_Pi Raspberry Pi]. It is a two piece solution, with a hardware and software component. RaSCSI can emulate multiple SCSI devices concurrently, provides a control interface to attach / detach drives, as well as insert and eject removable media. Simply connect the RaSCSI interface board to your system, launch the RaSCSI software on the Raspberry Pi, and the virtual devices will be accessible as physical SCSI devices!
+|PiSCSI is a virtual [https://en.wikipedia.org/wiki/Parallel_SCSI SCSI] device emulator that runs on a [https://en.wikipedia.org/wiki/Raspberry_Pi Raspberry Pi]. It is a two piece solution, with a hardware and software component. PiSCSI can emulate multiple SCSI devices concurrently, provides a control interface to attach / detach drives, as well as insert and eject removable media. Simply connect the PiSCSI interface board to your system, launch the PiSCSI software on the Raspberry Pi, and the virtual devices will be accessible as physical SCSI devices!
|[[images/rascsi_logo2_scaled.png]]
|}
@@ -11,7 +11,7 @@
|
- [https://www.tindie.com/stores/landogriffin/ [[images/tindie-logo-small.png]] akuker's Tindie Store]
- - Support the maintainer of the Github repository ;]
-- - All RaSCSI configurations, daisy chain daughter board plus others
+- - All PiSCSI configurations, daisy chain daughter board plus others
- [https://samplerzone.com/products/chicken-rascsi-sd-scsi-drive SamplerZone]
- - Configured and ready to go, out of the box
- [https://www.vintagecomputercenter.com/product/rascsi Vintage Computer Center]
@@ -30,7 +30,7 @@
|[[images/320px-Flag_of_the_United_Kingdom.svg.png]]
|
- intriguing industries
-- - Complete virtually Plug&Play RaSCSI in PotatoFi Cases and DIY Kits
+- - Complete virtually Plug&Play PiSCSI in PotatoFi Cases and DIY Kits
- - Comprehensive selection of accessories and other Mac Upgrades
- [http://amigakit.amiga.store/rascsi-adapter-board-p-91280.html?aksid=bjnke5i310a60fqi2mq80ttda4¤cy=GBP&aksid=bjnke5i310a60fqi2mq80ttda4 AmigaKit]
@@ -38,12 +38,12 @@
|-
|[[images/320px-Flag_of_Japan.svg.png]]
| - [https://gimons.booth.pm/ Gimons Developer Works]
-- - Original creator of the RaSCSI
+- - Original creator of the PiSCSI
|-
|[[images/do_it_yourself.png]]
|
- You are welcome to build your own!
-- - The [https://github.com/akuker/RASCSI/raw/master/hw/rascsi_2p4/gerbers/gerbers_rascsi_2p4a.zip Gerber files] are available in the Github repo. You can order these from any PCB manufacturer.
+- - The [https://github.com/piscsi/piscsi/raw/master/hw/rascsi_2p4/gerbers/gerbers_rascsi_2p4a.zip Gerber files] are available in the Github repo. You can order these from any PCB manufacturer.
- - [https://www.jlcpcb.com JLCPCB] is commonly used, since they are able to pre-install the tiny resistors in the factory for a low fee.
|}
@@ -60,28 +60,28 @@ RaSCSI was originally developed by [http://retropc.net/gimons/rascsi/ by GIMONS]
The purpose of this repository is to take the awesome work by GIMONS and build upon it, using the open source community. This project was forked from version 1.47 of GIMONS' RaSCSI project. Over time, this project has had significant updates and architectural changes, providing unique capabilities beyond the original RaSCSI project.
-RaSCSI has been demonstrated on dozens of retro computing platforms and digital samplers. A [https://github.com/akuker/RASCSI/wiki/Compatibility compatibility list] is available showing which platforms have been tested. Additional testing is appreciated, along with updating the system comparability table with your findings.
+PiSCSI has been demonstrated on dozens of retro computing platforms and digital samplers. A [https://github.com/piscsi/piscsi/wiki/Compatibility compatibility list] is available showing which platforms have been tested. Additional testing is appreciated, along with updating the system comparability table with your findings.
== Select Tutorial Videos ==
-Warning: Older videos may contain outdated information, since RaSCSI is a rapidly developing project.
+Warning: Older videos may contain outdated information, since PiSCSI is a rapidly developing project.
* [https://www.youtube.com/watch?v=-qRG-0Pne-I The Macintosh Librarian tutorial and demonstration on a Color Classic] (Dec 30, 2021)
-* [https://www.youtube.com/watch?v=dMgAJnxiYGQ Introduction to using RaSCSI on DEC VAXstation / Alphaserver] (Nov 6, 2021)
+* [https://www.youtube.com/watch?v=dMgAJnxiYGQ Introduction to using PiSCSI on DEC VAXstation / Alphaserver] (Nov 6, 2021)
* [https://www.youtube.com/watch?v=Pat42MNRhhA Mac84 tutorial and DaynaPORT Ethernet interface how-to] (Jul 31, 2021)
-* [https://www.youtube.com/watch?v=kLyDP9FLHlk Demonstration of RaSCSI in use on a SE/30] (Oct 11, 2020)
-* [https://www.youtube.com/watch?v=tUgxcchH2yg Livestream of RaSCSI assembly] (Oct 10, 2020)
+* [https://www.youtube.com/watch?v=kLyDP9FLHlk Demonstration of PiSCSI in use on a SE/30] (Oct 11, 2020)
+* [https://www.youtube.com/watch?v=tUgxcchH2yg Livestream of PiSCSI assembly] (Oct 10, 2020)
= Project Comparison =
{|class="wikitable"
!scope="col"|
-!scope="col"| RaSCSI (68kmla edition)
+!scope="col"| PiSCSI (68kmla edition)
!scope="col"| RaSCSI (GIMONS)
!scope="col"| BlueSCSI
!scope="col"| SCSI2SD
!scope="col"| MacSD
|-
|Links to more information
-|[https://github.com/akuker/RASCSI/wiki Wiki], [https://github.com/akuker/RASCSI GitHub]
+|[https://github.com/piscsi/piscsi/wiki Wiki], [https://github.com/piscsi/piscsi GitHub]
|[http://retropc.net/gimons/rascsi/ Homepage]
|[http://scsi.blue Homepage]
|[http://www.codesrc.com/mediawiki/index.php/SCSI2SD Wiki]
@@ -189,16 +189,16 @@ Warning: Older videos may contain outdated information, since RaSCSI is a rapidl
= Raspberry Pi and System compatibility =
-With many people working on and testing RaSCSI on their own systems, you can find details on what Raspberry Pis and which computers work together. Check out the [https://github.com/akuker/RASCSI/wiki/Compatibility Compatibility] page.
+With many people working on and testing PiSCSI on their own systems, you can find details on what Raspberry Pis and which computers work together. Check out the [https://github.com/piscsi/piscsi/wiki/Compatibility Compatibility] page.
= Benchmarks =
-Benchmark testing has been performed with the RaSCSI on a few different Raspberry Pi models. Please check the [https://github.com/akuker/RASCSI/wiki/Benchmarks benchmarks] page for additional details.
+Benchmark testing has been performed with the PiSCSI on a few different Raspberry Pi models. Please check the [https://github.com/piscsi/piscsi/wiki/Benchmarks benchmarks] page for additional details.
-----
= Hardware Component =
== Connection Method ==
-The hardware component of RaSCSI interfaces with GPIO pins on the Raspberry Pi to read/control the SCSI signals. As the Raspberry Pi GPIO pins operate at 3.3v and SCSI signalling is 5v, the RaSCSI interface uses bus transceivers allowing the Raspberry Pi to safely communicate on the SCSI bus. The SCSI I/O signal is used to control the direction of the Data signals, and a dedicated GPIO pin is used to control the direction of several control signals. As of Sept 2020, the suggested transceiver is the SN74LS641-1 from Texas Instruments. As development is still underway, a [[Transceiver-Comparison|comparison of different transceivers]] has been compiled.
+The hardware component of PiSCSI interfaces with GPIO pins on the Raspberry Pi to read/control the SCSI signals. As the Raspberry Pi GPIO pins operate at 3.3v and SCSI signalling is 5v, the PiSCSI interface uses bus transceivers allowing the Raspberry Pi to safely communicate on the SCSI bus. The SCSI I/O signal is used to control the direction of the Data signals, and a dedicated GPIO pin is used to control the direction of several control signals. As of Sept 2020, the suggested transceiver is the SN74LS641-1 from Texas Instruments. As development is still underway, a [[Transceiver-Comparison|comparison of different transceivers]] has been compiled.
{|
|[[images/rascsi.png | width = 275px]]
@@ -206,25 +206,25 @@ The hardware component of RaSCSI interfaces with GPIO pins on the Raspberry Pi t
|}
== Assembling your own ==
-For those who have purchased the DIY kit on [https://www.tindie.com/products/landogriffin/rascsi-macintosh-version/ Tindie], or have procured your own PCBs and components, check the [[assembly]] page for instructions on building your own RaSCSI board.
+For those who have purchased the DIY kit on [https://www.tindie.com/products/landogriffin/rascsi-macintosh-version/ Tindie], or have procured your own PCBs and components, check the [[assembly]] page for instructions on building your own PiSCSI board.
== Alternate Connection Method ==
Some people have reported successfully connecting the Raspberry Pi GPIO pins directly to a SCSI interface. This may work, but runs the Raspberry Pi GPIO beyond the specifications, and ''is not recommended''.
== Expansion options ==
-The RaSCSI board has had an additional header installed exposing the I2C bus. With this you can install additional features like an OLED display. Read more on how to [[OLED Status Display (Optional)|connect an OLED display to the RaSCSI ]].
+The PiSCSI board has had an additional header installed exposing the I2C bus. With this you can install additional features like an OLED display. Read more on how to [[OLED Status Display (Optional)|connect an OLED display to the PiSCSI ]].
-----
= Software Component =
== Downloading and installing the software ==
-Once you have an RaSCSI board, instructions on how to setup your Raspberry Pi, and downloading and installing the RaSCSI software can be found on the [[Setup Instructions]] page.
+Once you have an PiSCSI board, instructions on how to setup your Raspberry Pi, and downloading and installing the PiSCSI software can be found on the [[Setup Instructions]] page.
-== Connecting RaSCSI to your computer ==
-Now that you have the RaSCSI board connected to your Raspberry Pi, and have the software downloaded and installed, next is to connect the RaSCSI device to your computer. Details on SCSI devices, termination and cabling can be found on the [[Connecting the RaSCSI]] page.
+== Connecting PiSCSI to your computer ==
+Now that you have the PiSCSI board connected to your Raspberry Pi, and have the software downloaded and installed, next is to connect the PiSCSI device to your computer. Details on SCSI devices, termination and cabling can be found on the [[Connecting the PiSCSI]] page.
== I have the software and everything connected, what next? ==
-With the RaSCSI board attached to your computer, and RaSCSI downloaded and installed, instructions on creating and attaching disk images can be found on the [[Drive Setup]] page.
+With the PiSCSI board attached to your computer, and PiSCSI downloaded and installed, instructions on creating and attaching disk images can be found on the [[Drive Setup]] page.
Additionally, a web interface can be used to attach and detach images, manage the images, and the Raspberry Pi itself. More details on the web interface and how to set it up can be found on the [[Web Interface]] page.
@@ -233,16 +233,16 @@ Additionally, a web interface can be used to attach and detach images, manage th
= Additional Information =
== What is 68kmla? ==
-[https://68kmla.org/forums/ 68kmla] is the “68k Mac Liberation Army”. Its a group of vintage Mac (and Apple) enthusiasts who talk about nerdy stuff on the forum. This development started as [https://68kmla.org/bb/index.php?threads/rascsi-development-thread.6868/ part of a forum thread]. This RaSCSI project has grown far beyond the original 68k MLA community though.
+[https://68kmla.org/forums/ 68kmla] is the “68k Mac Liberation Army”. Its a group of vintage Mac (and Apple) enthusiasts who talk about nerdy stuff on the forum. This development started as [https://68kmla.org/bb/index.php?threads/rascsi-development-thread.6868/ part of a forum thread]. This PiSCSI project has grown far beyond the original 68k MLA community though.
----
= Reference =
-== RaSCSI manpages ==
-* [https://raw.githubusercontent.com/akuker/RASCSI/master/doc/rascsi_man_page.txt rascsi manpage]
-* [https://raw.githubusercontent.com/akuker/RASCSI/master/doc/rasctl_man_page.txt rasctl manpage]
-* [https://raw.githubusercontent.com/akuker/RASCSI/master/doc/scsimon_man_page.txt scsimon manpage]
+== PiSCSI manpages ==
+* [https://raw.githubusercontent.com/piscsi/piscsi/master/doc/rascsi_man_page.txt rascsi manpage]
+* [https://raw.githubusercontent.com/piscsi/piscsi/master/doc/scsictl_man_page.txt scsictl manpage]
+* [https://raw.githubusercontent.com/piscsi/piscsi/master/doc/scsimon_man_page.txt scsimon manpage]
== Software ==
@@ -265,7 +265,7 @@ Additionally, a web interface can be used to attach and detach images, manage th
* [http://mirror.informatimago.com/next/developer.apple.com/documentation/macos8/pdf/NSL_Mgr.pdf Network Services Location manager Developers Kit]
* [https://www.staff.uni-mainz.de/tacke/scsi/SCSI2.html Very detailed, thorough document]
* [https://www.t10.org/drafts.htm T10 Working Drafts for the SCSI standard]
-* [https://www.rascsi.de RaSCSI Control App for Android]
+* [https://www.rascsi.de PiSCSI Control App for Android]
== Hardware ==
|