Macintosh Plus not Seeing PiSCSI

[Jeremiahdmass]

Info

• Which version of Pi are you using: RPI 3 B v1.2
• Which GitHub revision of software: November 2023 release
• Which board version: PiScsi Zero v1.0 FULLSPEC
• Which computer is the PiSCSI connected to: Macintosh Plus
• Which OS you are using (output of 'lsb_release -a'): Raspbian GNU/Linux 11 (bullseye)

Describe the issue

I can't get the Macintosh to recognize the PiScsi at all. I have tried several different disk images, none of which have worked. The Macintosh boots to the question mark no matter what I have attached on the PiScsi. I believe it may have something to do with the Plus's weird SCSI standards.

I think it may have something to do with the Unit Attention, SCSI Selection Delay, and the SCSI selection pulses, because that has caused issues on the SCSI2SD. I have no idea how these settings could be adjusted on
the PiScsi though. [https://www.codesrc.com/mediawiki/index.php/Mac_Plus]

[rdmark]

@Jeremiahdmass This sounds like either a SCSI termination or cablage issue. Please go through all the steps in https://github.com/PiSCSI/piscsi/wiki/Troubleshooting and see if it makes a difference.

FWIW there are known quirks and limitations with piscsi and the Mac Plus. See #656 for more info.

[Jeremiahdmass]

Thanks for the reply. I put a glob of solder on the termination pads and have the db25 connector plugged directly into the Mac's SCSI port so I don't think either of those could be an issue. However, I forgot to mention that when I look in the logs, there's nothing there besides it saying that I mounted whatever I was trying to boot from.

[rdmark]

Are other SCSI mass storage devices working properly with the same Plus and SCSI cablage?

[Jeremiahdmass]

I have a 20mb seagate scsi drive but it doesn't work. The mac boots to a sad mac saying its not bootable. The HD SC software on mac os sees it but can't format it. Thats the only other scsi thing I have.

[Jeremiahdmass]

I tried some images formatted with the silver lining driver, and still nothing. I would think a driver issue would boot to a sad Mac instead of just waiting for a floppy.

[rdmark]

Your symptoms make me think the signals aren’t getting through on the SCSI bus. Which suggests it’s either bad cablage, heavy oxidation on the DB25 ports, fault on the piscsi board or fault on the Plus logic board.

What’d I would do first is to try other SCSI cables and other Macs to eliminate those factors. And also work some contact cleaner into those DB25s to clear out any oxidation.

[Jeremiahdmass]

Unfortunately I don't have another Mac to try it on. I have worked some contact cleaner into the port but I guess I can try some more. I definitely am going to buy some more cables though.

[Jeremiahdmass]

I have confirmed that my connections are good. The PiScsi is now showing some activity. When the Mac is searching for a SCSI device, the ENB light flashes on once. But the Mac still says it can't find any SCSI devices. I've tried several different hard drive configurations and disk images but to no avail.

[rdmark]

Did you try the Plus specific Silverlining formatted image that I shared in the issue ticket linked above?

If that one doesn't work either, please share piscsi trace logs from when the Plus is powered on.

[Jeremiahdmass]

I have tried a Silverlining formatted disk. However, there is nothing in the logs except the attached device even after the light blinks and the Mac can't find it.
Here are the logs.
Mar 23 23:25:52 piscsi PISCSI[495]: [2024-03-23 23:25:52.109] [info] Validating: operation=ATTACH, command params='locale=en', 'token=???', device=6:0, type=SCHD, device params='file=HD1-100MB_HFS.hda', vendor='', product='', revision='', block size=0 Mar 23 23:25:52 piscsi PISCSI[495]: [2024-03-23 23:25:52.110] [info] Executing: operation=ATTACH, command params='locale=en', 'token=???', device=6:0, type=SCHD, device params='file=HD1-100MB_HFS.hda', vendor='', product='', revision='', block size=0 Mar 23 23:25:52 piscsi PISCSI[495]: [2024-03-23 23:25:52.111] [info] Attached SCHD 6:0

[rdmark]

"HD1-100MB_HFS.hda" doesn't look like the file name of the Silverlining formatted image. Are the logs from a different attempt? Anyways, there's nothing in this log message that gives any hint. Can you please make sure you enabled trace level logging?

Where did you get the piscsi board from? You might want to double check with them that the board was tested before it was shipped.

[Jeremiahdmass]

That isn't the image from that issue ticket, but I have also tried it and gotten nothing. The "HD1-100MB_HFS.hda" image was from somewhere random but it should also be Silverlining formatted.

'[2024-03-26 22:04:06.452] [info] Validating: operation=ATTACH, command params='locale=en', 'token=???', device=6:0, type=SCHD, device params='file=HD1-100MB_HFS.hda', vendor='', product='', revision='', block size=0
[2024-03-26 22:04:06.453] [info] Executing: operation=ATTACH, command params='locale=en', 'token=???', device=6:0, type=SCHD, device params='file=HD1-100MB_HFS.hda', vendor='', product='', revision='', block size=0
[2024-03-26 22:04:06.453] [info] Attached SCHD 6:0
[2024-03-26 22:04:06.488] [trace] Received CHECK_AUTHENTICATION command
[2024-03-26 22:04:06.492] [trace] Received SERVER_INFO command
[2024-03-26 22:04:06.507] [trace] Received DEVICES_INFO command
[2024-03-26 22:04:06.511] [trace] Received DEFAULT_IMAGE_FILES_INFO command
[2024-03-26 22:04:06.518] [trace] Received DEVICE_TYPES_INFO command
[2024-03-26 22:04:06.528] [trace] Received DEFAULT_IMAGE_FILES_INFO command
[2024-03-26 22:04:06.535] [trace] Received SERVER_INFO command
[2024-03-26 22:04:06.560] [trace] Received NETWORK_INTERFACES_INFO command
[2024-03-26 22:04:06.597] [trace] Received DEVICE_TYPES_INFO command
[2024-03-26 22:04:06.606] [trace] Received DEVICE_TYPES_INFO command
[2024-03-26 22:04:06.614] [trace] Received DEVICE_TYPES_INFO command
[2024-03-26 22:04:06.621] [trace] Received DEVICE_TYPES_INFO command
[2024-03-26 22:04:06.630] [trace] Received SERVER_INFO command
[2024-03-26 22:04:06.985] [trace] Received CHECK_AUTHENTICATION command
[2024-03-26 22:04:44.799] [trace] (ID 6) - ++++ Starting processing for initiator ID 7
[2024-03-26 22:04:44.799] [trace] (ID 6) - Selection phase
[2024-03-26 22:04:44.799] [trace] (ID 6) - Selection completed
[2024-03-26 22:04:44.799] [trace] (ID 6) - Command phase
[2024-03-26 22:04:45.275] [trace] (ID 6) - Received unknown command: $0
[2024-03-26 22:04:45.275] [debug] (ID 6) - Error status: Sense Key $05, ASC $20
[2024-03-26 22:04:45.275] [trace] (ID 6) - Status phase, status is $02
[2024-03-26 22:04:45.275] [trace] (ID 6) - Sending data, offset: 0, length: 1
[2024-03-26 22:04:46.216] [trace] (ID 6) - Bus Free phase
[2024-03-26 22:04:46.463] [trace] (ID 6) - ++++ Starting processing for initiator ID 7
[2024-03-26 22:04:46.463] [trace] (ID 6) - Selection phase
[2024-03-26 22:04:46.463] [trace] (ID 6) - Selection completed
[2024-03-26 22:04:46.463] [trace] (ID 6) - Command phase
[2024-03-26 22:04:47.799] [trace] (ID 6) - Received unknown command: $0
[2024-03-26 22:04:47.799] [debug] (ID 6) - Error status: Sense Key $05, ASC $20
[2024-03-26 22:04:47.799] [trace] (ID 6) - Status phase, status is $02
[2024-03-26 22:04:47.799] [trace] (ID 6) - Sending data, offset: 0, length: 1
[2024-03-26 22:04:48.625] [trace] (ID 6) - ++++ Starting processing for initiator ID 7
[2024-03-26 22:04:48.625] [trace] (ID 6) - Selection phase
[2024-03-26 22:04:48.625] [trace] (ID 6) - Selection completed
[2024-03-26 22:04:48.625] [trace] (ID 6) - Command phase
Segmentation fault
'

I bought a kit from eBay with just the SMD parts soldered and did the rest myself, so it wasn't tested. I have checked it multiple times and my solder work is good.

[rdmark]

Look at that, it’s a segmentation fault at the end of the logs. Would it be possible to get a stack trace from that segfault?

[Jeremiahdmass]

Sorry, I don't really know what that means. I'm not good at this kind of stuff.