ZuluSCSI Blaster Quick Start Guide - Revision history

Aperez: /* Step 1: Prep your SD card */

2025-03-11T22:50:30Z

Step 1: Prep your SD card

← Older revision		Revision as of 15:50, 11 March 2025
Line 2:		Line 2:

	=== Step 1: Prep your SD card ===		=== Step 1: Prep your SD card ===
	Load your SD card with at least one disk image~~. Make sure that you name it appropriately based on the device it's representing as well as its ID number on the SCSI bus~~. If you~~'re using a hard drive~~ image, ~~name~~ the ~~image <code>HD0.img</code>, and if it's an optical drive image~~, ~~name it <code>CD0.iso</code>~~ or ~~<code>CD0.bin</code> and <code>CD0.cue</code> depending on which format it's in. Alternatively,~~ the ZuluSCSI ~~firmware can create an unformatted image file~~ for you ~~if you create~~ an empty text file with the following naming convention: <code>Create 1024M HD0.txt</code>		Load your SD card with at least one disk image. If you do not have an existing source image file, you can create one for yourself with the SD card inserted in to a modern computer, or instruct the ZuluSCSI to do so for you, by creating an empty text file on the SD card, with the following naming convention: <code>Create 1024M HD0.txt</code>

	If the firmware detects such a file, upon initialization (power up), it will attempt to create an image file of the type and SCSI ID defined in the text file. Depending on the size of the requested image file, this may take a while. It's generally best to start with smaller image files, especially if you're unfamiliar with this process, as many older operating systems have their own limitations when it comes to maximum supported disk sizes.		If the firmware detects such a file, upon initialization (power up), it will attempt to create an image file of the type and SCSI ID defined in the text file. Depending on the size of the requested image file, this may take a while. It's generally best to start with smaller image files, especially if you're unfamiliar with this process, as many older operating systems have their own limitations when it comes to maximum supported disk sizes.

			Make sure that you name it appropriately based on the device it's representing as well as its ID number on the SCSI bus. If you're using a hard drive image, name the image <code>HD0.img</code>, and if it's an optical drive image, name it <code>CD0.iso</code> or <code>CD0.bin</code> and <code>CD0.cue</code> depending on which format it's in. Alternatively, the ZuluSCSI firmware can create an unformatted image file for you if you

	Plug the SD card into the slot on the ZuluSCSI board. Assuming one or more image files are detected, the LED will blink once.		Plug the SD card into the slot on the ZuluSCSI board. Assuming one or more image files are detected, the LED will blink once.

Aperez at 22:41, 11 March 2025

2025-03-11T22:41:37Z

← Older revision		Revision as of 15:41, 11 March 2025
Line 1:		Line 1:
	You've just received your new ZuluSCSI Blaster board from Rabbit Hole Computing. Now what?		You've just received your new ZuluSCSI Blaster board from Rabbit Hole Computing. Now what?

	=== Step 1: Prep your SD card. ===		=== Step 1: Prep your SD card ===
	Load ~~either~~ your SD ~~card or microSD~~ card with a disk image. Make sure that you name it appropriately based on the device it's representing as well as its ID number on the SCSI bus. If you're using a hard drive image, name the image <code>HD0.img</code>, and if it's an optical drive image, name it <code>CD0.iso</code> or <code>CD0.bin</code> and <code>CD0.cue</code> depending on which format it's in.		Load your SD card with at least one disk image. Make sure that you name it appropriately based on the device it's representing as well as its ID number on the SCSI bus. If you're using a hard drive image, name the image <code>HD0.img</code>, and if it's an optical drive image, name it <code>CD0.iso</code> or <code>CD0.bin</code> and <code>CD0.cue</code> depending on which format it's in. Alternatively, the ZuluSCSI firmware can create an unformatted image file for you if you create an empty text file with the following naming convention: <code>Create 1024M HD0.txt</code>

	~~Plug~~ the ~~SD card into~~ the ~~slot~~ on the ~~ZuluSCSI board~~.		If the firmware detects such a file, upon initialization (power up), it will attempt to create an image file of the type and SCSI ID defined in the text file. Depending on the size of the requested image file, this may take a while. It's generally best to start with smaller image files, especially if you're unfamiliar with this process, as many older operating systems have their own limitations when it comes to maximum supported disk sizes.

	=== Step 2: Prep the ZuluSCSI board. ===		Plug the SD card into the slot on the ZuluSCSI board. Assuming one or more image files are detected, the LED will blink once.

			=== Step 2: Prep the ZuluSCSI board ===
	Plug the 50-pin ribbon cable, or adapter, into the ZuluSCSI Blaster		Plug the 50-pin ribbon cable, or adapter, into the ZuluSCSI Blaster

Aperez: /* Further reference material */

2025-03-11T22:32:44Z

Further reference material

@@ Line 23: / Line 23: @@
 === Step 3: Turn on your device! ===
 Once you've prepared the SD card and attached your ZuluSCSI to the cable and host computer, switch things on and go! Your ZuluSCSI should be recognized by your SCSI controller, and the device will mount images as described above, and you should see your device(s) populate in your system.
 === Further reference material ===
-https://github.com/ZuluSCSI/ZuluSCSI-firmware/wiki/USB-Mass-Storage
+Also see this [https://github.com/ZuluSCSI/ZuluSCSI-firmware/blob/main/zuluscsi.ini example zuluscsi.ini file]

Aperez at 22:23, 11 March 2025

2025-03-11T22:23:52Z

← Older revision		Revision as of 15:23, 11 March 2025
Line 10:		Line 10:

	The DIP switch block has three DIP switches:		The DIP switch block has three DIP switches:
	* '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.
	* '''~~DBG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card.~~		# '''INITIATOR''': Initiator mode allows you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system. This DIP switch must be on the off position for the ZuluSCSI to be detected as a storage device. If it is accidentally enabled, it will not be detected, and its SCSI ID will likely conflict with the SCSI ID of the SCSI controller of the attached machine.
	* '''~~INITIATOR~~:~~''' Allows~~ you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system. This DIP switch ''must'' be on the off position for the ZuluSCSI to be detected as a storage device. If it is accidentally enabled, it will not be detected, and its SCSI ID will likely conflict with the SCSI ID of the SCSI controller of the attached machine.		# '''DEBUG LOG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card. This will negatively affect disk performance, but produces log output that is far more verbose, and far more useful for troubleshooting problems.
			# '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.

	If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.		If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.
Line 22:		Line 23:
	=== Step 3: Turn on your device! ===		=== Step 3: Turn on your device! ===
	Once you've prepared the SD card and attached your ZuluSCSI to the cable and host computer, switch things on and go! Your ZuluSCSI should be recognized by your SCSI controller, and the device will mount images as described above, and you should see your device(s) populate in your system.		Once you've prepared the SD card and attached your ZuluSCSI to the cable and host computer, switch things on and go! Your ZuluSCSI should be recognized by your SCSI controller, and the device will mount images as described above, and you should see your device(s) populate in your system.

			=== Further reference material ===


			https://github.com/ZuluSCSI/ZuluSCSI-firmware/wiki/USB-Mass-Storage

Aperez at 22:18, 11 March 2025

2025-03-11T22:18:53Z

← Older revision		Revision as of 15:18, 11 March 2025
Line 7:		Line 7:

	=== Step 2: Prep the ZuluSCSI board. ===		=== Step 2: Prep the ZuluSCSI board. ===
	Plug the 50 pin ribbon cable (or adapter), into the ZuluSCSI.		Plug the 50-pin ribbon cable, or adapter, into the ZuluSCSI Blaster

	The DIP switch block has three DIP switches:		The DIP switch block has three DIP switches:
Line 21:		Line 21:

	=== Step 3: Turn on your device! ===		=== Step 3: Turn on your device! ===
	Once you've prepared the SD card and attached your ZuluSCSI to the cable and host computer, switch things on and go! Your ZuluSCSI should be recognized by your SCSI ~~implementation~~ and the device will mount images as described above, and you should see your device(s) populate in your system.		Once you've prepared the SD card and attached your ZuluSCSI to the cable and host computer, switch things on and go! Your ZuluSCSI should be recognized by your SCSI controller, and the device will mount images as described above, and you should see your device(s) populate in your system.

Aperez at 22:15, 11 March 2025

2025-03-11T22:15:39Z

← Older revision		Revision as of 15:15, 11 March 2025
Line 1:		Line 1:
	You've just received your new ZuluSCSI Blaster ~~box~~ from Rabbit Hole Computing. Now what?		You've just received your new ZuluSCSI Blaster board from Rabbit Hole Computing. Now what?

	=== Step 1: Prep your SD card. ===		=== Step 1: Prep your SD card. ===

Aperez at 22:15, 11 March 2025

2025-03-11T22:15:15Z

← Older revision		Revision as of 15:15, 11 March 2025
Line 12:		Line 12:
	* '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.		* '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.
	* '''DBG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card.		* '''DBG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card.
	* '''INITIATOR:''' Allows you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system.		* '''INITIATOR:''' Allows you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system. This DIP switch ''must'' be on the off position for the ZuluSCSI to be detected as a storage device. If it is accidentally enabled, it will not be detected, and its SCSI ID will likely conflict with the SCSI ID of the SCSI controller of the attached machine.

	If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.		If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.

Aperez: /* Step 2: Prep the ZuluSCSI board. */

2025-03-11T22:12:01Z

Step 2: Prep the ZuluSCSI board.

← Older revision		Revision as of 15:12, 11 March 2025
Line 7:		Line 7:

	=== Step 2: Prep the ZuluSCSI board. ===		=== Step 2: Prep the ZuluSCSI board. ===
	Depending on how the system is connected together, you may need to run DB25 cables, IDC-50 pin cables, or use an interposer to switch cable types. Once you've determined whether or not you need to do this, plug the 50 pin ribbon cable (or adapter), into the ZuluSCSI.		Plug the 50 pin ribbon cable (or adapter), into the ZuluSCSI.

	The DIP switch block has three DIP switches:		The DIP switch block has three DIP switches:
Line 16:		Line 16:
	If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.		If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.

	If you are looking to mount your ZuluSCSI ~~board~~ internally, the four mounting holes on the ZuluSCSI Blaster board are designed to line up with the bottom holes of any 2.5" hard drive footprint. Any standard 2.5"-to-3.5" mounting adapter can fit the mounting holes on a ZuluSCSI board using M3 screws.		If you are looking to mount your ZuluSCSI Blaster internally, the four mounting holes on the ZuluSCSI Blaster board are designed to line up with the bottom holes of any 2.5" hard drive footprint. Any standard 2.5"-to-3.5" mounting adapter can fit the mounting holes on a ZuluSCSI board using M3 screws.

	If you want to have an external activity LED, you can populate footprint '''J304''' on the board with a standard 0.1" pin header and run a case LED to this header for that purpose. The cathode (negative) end of the LED is marked by a '''C''' on the board.		If you want to have an external activity LED, you can populate footprint '''J304''' on the board with a standard 0.1" pin header and run a case LED to this header for that purpose. The cathode (negative) end of the LED is marked by a '''C''' on the board.

Aperez: Initial content for ZuluSCSI Blaster QSG

2025-03-11T22:10:53Z

Initial content for ZuluSCSI Blaster QSG

← Older revision		Revision as of 15:10, 11 March 2025
Line 7:		Line 7:

	=== Step 2: Prep the ZuluSCSI board. ===		=== Step 2: Prep the ZuluSCSI board. ===
	Depending on how the system is connected together, you may need to run DB25 cables, IDC-50 pin cables, or use an interposer to switch cable types. Once you've determined whether or not you need to do this, plug the ~~appropriate~~ cable into the ZuluSCSI. ~~Your ZuluSCSI model may only incorporate one type of connection.~~		Depending on how the system is connected together, you may need to run DB25 cables, IDC-50 pin cables, or use an interposer to switch cable types. Once you've determined whether or not you need to do this, plug the 50 pin ribbon cable (or adapter), into the ZuluSCSI.

	The DIP switch block has three DIP switches:		The DIP switch block has three DIP switches:
	* '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.		* '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.
	* '''DBG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card.		* '''DBG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card.
	* '''INITIATOR ~~(RP2040-based devices only)~~:''' Allows you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system.		* '''INITIATOR:''' Allows you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system.

	If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.		If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.

Aperez: Create ZuluSCSI Blaster specific QSG

2025-03-11T22:05:57Z

Create ZuluSCSI Blaster specific QSG

New page

You've just received your new ZuluSCSI Blaster box from Rabbit Hole Computing. Now what?

=== Step 1: Prep your SD card. ===
Load either your SD card or microSD card with a disk image. Make sure that you name it appropriately based on the device it's representing as well as its ID number on the SCSI bus. If you're using a hard drive image, name the image <code>HD0.img</code>, and if it's an optical drive image, name it <code>CD0.iso</code> or <code>CD0.bin</code> and <code>CD0.cue</code> depending on which format it's in.

Plug the SD card into the slot on the ZuluSCSI board.

=== Step 2: Prep the ZuluSCSI board. ===
Depending on how the system is connected together, you may need to run DB25 cables, IDC-50 pin cables, or use an interposer to switch cable types. Once you've determined whether or not you need to do this, plug the appropriate cable into the ZuluSCSI. Your ZuluSCSI model may only incorporate one type of connection.

The DIP switch block has three DIP switches:
* '''TERM:''' Termination on/off. If your device is the last one on the bus, or the only one on the bus, turn this switch on.
* '''DBG:''' If on, produce a debug log to a text file called <code>zululog.txt</code> that gets placed in the root directory of your SD card.
* '''INITIATOR (RP2040-based devices only):''' Allows you to use your ZuluSCSI to capture an image of all SCSI devices currently in your system.

If your device doesn't provide termination power, such as a Mac IIsi, you'll need to provide bus power to it either connecting power to the 4-pin Molex floppy power connector on your board or alternatively by attaching a USB cable to the port on the front of the board.

If you are looking to mount your ZuluSCSI board internally, the four mounting holes on the ZuluSCSI Blaster board are designed to line up with the bottom holes of any 2.5" hard drive footprint. Any standard 2.5"-to-3.5" mounting adapter can fit the mounting holes on a ZuluSCSI board using M3 screws.

If you want to have an external activity LED, you can populate footprint '''J304''' on the board with a standard 0.1" pin header and run a case LED to this header for that purpose. The cathode (negative) end of the LED is marked by a '''C''' on the board.

=== Step 3: Turn on your device! ===
Once you've prepared the SD card and attached your ZuluSCSI to the cable and host computer, switch things on and go! Your ZuluSCSI should be recognized by your SCSI implementation and the device will mount images as described above, and you should see your device(s) populate in your system.