Replies: 2 comments 11 replies
-
@guytaylor how are you powering the Fireball SE? Each device should have termination enabled. |
Beta Was this translation helpful? Give feedback.
9 replies
-
@guytaylor I'm able to replicate this behavior while attempting to dump a 1.2GB Quantum Fireball, model 655-0394, with my ZuluSCSI. Other Quantum drives I tested worked fine, so this seems like some sort of possible/likely bug. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to get Initiator Mode working.
My understanding is that it allows the Zulu to image a drive, which is what I would like to do.
I have a full size RP2040, and have the latest firmware installed, v2023.07.01 and the drive is a Quantum Fireball SE (which was an a Yamaha A3000 sampler)
The drive was working fine in the sampler. The drive SCSI ID is 0
What I have tried is, connecting the ZuluSCSI directly to the drive using a 50 pin cable, and powering both.
I set the 'Initiator' jumper on the Zulu as well as the debug out.
But I can't get it to see the drive. I tried all 4 combos of SCSI termination, and here are the logs.
I wait for 60 seconds for each run, and the logs just repeat, I trimmed the log output as they just are repeating
Any tips to what I may be doing wrong?
Zulu Termination: On Drive Termination: On
Zulu Termination: Off Drive Termination: On
Zulu Termination: Off Drive Termination: Off
Zulu Termination: On Drive Termination: Off
Beta Was this translation helpful? Give feedback.
All reactions