Hello together,
unfortunately my favorite vintage mac gadget stopped working a few days ago. The Pi seems fine as I can access it with the web browser, ftp or ssh, but three different Macs no longer regognize the attached SCSI devices through RaSCSI while other devices (I tried a BlueSCSI and a Zip drive) work. The issue can be reproduced with different cables on different Macs (and I also tried to turn off termination on the RaSCSI and daisychain it to an SE and an external drive. The internal drive and the external one were seen, the RaSCSI was not.
This is what I see in SCSIProbe:
ID 5 is a disk image
ID 6 is the DaynaPort adapter.
I tried to reinstall RaSCSI from scratch which did nothing so I assumed that I have a hardware problem. What makes the thing even worse is that currently the RaSCSI kits are out of stock and Pis are also not available.
Next I got a set of jumper leads to create a loopback cable as described in the troubleshooting guide...
The result of the loopback test was:
Apparently I lost the D signal/voltage. I just measured the voltages on the underside of the PCB. D0 to DP were all around 3.08V as stated in the troubleshooting guide, TPWR was 4.9V.
Do I have a bad Pi or bad bus transceiver chips?
I am using a RaSCSI 2.4a with a Pi Zero 2W btw.
unfortunately my favorite vintage mac gadget stopped working a few days ago. The Pi seems fine as I can access it with the web browser, ftp or ssh, but three different Macs no longer regognize the attached SCSI devices through RaSCSI while other devices (I tried a BlueSCSI and a Zip drive) work. The issue can be reproduced with different cables on different Macs (and I also tried to turn off termination on the RaSCSI and daisychain it to an SE and an external drive. The internal drive and the external one were seen, the RaSCSI was not.
This is what I see in SCSIProbe:
ID 5 is a disk image
ID 6 is the DaynaPort adapter.
I tried to reinstall RaSCSI from scratch which did nothing so I assumed that I have a hardware problem. What makes the thing even worse is that currently the RaSCSI kits are out of stock and Pis are also not available.
Next I got a set of jumper leads to create a loopback cable as described in the troubleshooting guide...
Troubleshooting
PiSCSI allows a Raspberry Pi to function as emulated SCSI devices (hard disk, CD-ROM, and others) for vintage SCSI-based computers and devices. This is a fork of the RaSCSI project by GIMONS. - Pi...
github.com
The result of the loopback test was:
Code:
pi@RaSCSI:~/RASCSI/python/loopback_test $ python3 test.py
Error: GPIO D0 should drive ACK low, but did not
Error: GPIO D1 should drive SEL low, but did not
Error: GPIO D2 should drive ATN low, but did not
Error: GPIO D3 should drive RST low, but did not
Error: GPIO D4 should drive CD low, but did not
Error: GPIO D5 should drive IO low, but did not
Error: GPIO D6 should drive MSG low, but did not
Error: GPIO D7 should drive REQ low, but did not
Error: GPIO DP should drive BSY low, but did not
!!!!!!!! Test FAILED !!!!!!!!
Total errors: 9
Apparently I lost the D signal/voltage. I just measured the voltages on the underside of the PCB. D0 to DP were all around 3.08V as stated in the troubleshooting guide, TPWR was 4.9V.
Do I have a bad Pi or bad bus transceiver chips?
I am using a RaSCSI 2.4a with a Pi Zero 2W btw.
Last edited: