5f1fd16f3c
This assumes that the original Z3 Fast map line in the config has not been edited. Z3 Fast is autoconfed before this on newer Kickstarts, so they're unaffected by this as the memory range will no longer sit around at $10000000. 1.3 PiSCSI autoboot still doesn't work.
PiSCSI Interface/Device driver for Amiga
A high performance replacement for scsi.device, allowing automatic booting and mounting of raw hard disk (RDB/RDSK) images.
While this driver is considered mostly stable, it's still work in progress. Do not use it in conjunction with any critical one of a kind data that you need to survive.
Compatibility
- PiSCSI requires some Fast RAM to be mapped on your PiStorm to work.
- This may change at some point, but for now make sure that you configure at the very least a few megabytes of Fast RAM so that the boot ROM can load and initialize properly.
PiSCSI only supports 512 byte block size for virtual SCSI devices.The block size is hard coded, this will probably be addressed relatively soon (TM). If you need very large partitions, please use PFS3AIO or a similar file system instead of FFS.Selecting a different block size may appear to work in some cases, but in reality it does not. Do not change the block size from the default 512 bytes.
[WIP]Theoretically, PiSCSI should now be compatible with any block size up to 64KB, but this is not very thoroughly tested when you are reading this particular piece of text.- Autobooting, Kickstart 2.0 and up
- PiSCSI does NOT work with Kickstart 1.3 yet, as it is missing some code needed to properly add boot nodes with old Kickstarts.
- Mounting RDSK/RDB disk images, physical devices with a file system the Amiga can use
- PiSCSI does NOT work with specifically UAE single partition disk images prepared and formatted using WinUAE yet. You can check what type the disk image is using a hex editor, if it starts with
RDSK, it is a full drive RDSK/RDB image, if it starts withDOSit is most likely a UAE single partition disk image. - It does however work with any UAE disk image prepared using the Full drive/RDB mode selected in the Hardfile settings. Using Full drive/RDB mode in for instance WinUAE requires you to click the button labeled with this exact piece of text.
- When mounting a physical drive for use with PiSCSI, please read the
A big word of cautionat the bottom of this page
- PiSCSI does NOT work with specifically UAE single partition disk images prepared and formatted using WinUAE yet. You can check what type the disk image is using a hex editor, if it starts with
- TrackDisk, TrackDisk64 and Direct SCSI
Instructions
To use the PiSCSI interface, simply enable it by uncommenting the setvar piscsi line in default.cfg, or add it to the config file you're currently using.
Add disk images to the PiSCSI interface by uncommenting the piscsi0 and piscsi1 lines and editing them to point at the disk image(s) you want to use.
Physical drives can also be mounted using their mount point files on Linux, such as /dev/sda for a USB stick, but keep in mind that this is dangerous as it can destroy the contents of the disk if you're unluck or you repartition it.
You can mount up to 7 disk images using setvar piscsi0 through piscsi6.
For preparing a disk image on your Amiga with a PiStorm connected, you can for instance make a copy of the Workbench tool HDToolBox, and then edit the tooltypes (Icon -> Information menu) to use pi-scsi.device instead of scsi.device.
No copying of the pi-scsi.device driver to DEVS: or anything like that is necessary, as the driver is loaded from ROM on boot/config time.
If you want EVEN MORE speed, either adjust the size of your hard drive image so that it gets properly detected with 16 heads in HDToolBox or manually edit the Cylinders/Heads settings when setting up your drive. Creating a disk image that is a multiple of 504 megabytes seems suitable for this purpose.
(The trackdisk device on the Amiga seems to enable transfers bigger than 512 bytes (one sector) only if the drive is identified as having more than one drive head/surface.)
Making changes to the driver
If you make changes to the driver, you can always test these on the Amiga as a regular file in DEVS:, but the Z2 device has to be disabled for this to work properly. Disabling the Z2 device requires you to comment out the line add_z2_pic(ACTYPE_PISCSI, 0); in amiga-platform.c.
Steps to create an updated boot ROM, all of these are done in the device_driver_amiga directory:
- (Optional) If you've made changes to bootrom.s, first run
./build.sh. - (Optional) If you've had build.sh create a new
bootromfile, you need to chop off the first few bytes of it, since VASM adds a single hunk to the beginning of it. Simply delete all bytes up until you bump into the value0x90, this is the first value in the boot ROM identifier. - Compile the new
pi-scsi.deviceusing./build2.sh. - (Optional) If you haven't previously compiled the
makerombinary, or the code for it has been updated since last time, simply rungcc makerom.c -o makerom - Run
./makeromto assemble the boot ROM file, it's automatically in the correct place for the emulator to find it.
Some quick instructions for mounting a FAT32 disk image or disk using PiSCSI
- Download giggledisk from http://www.geit.de/eng_giggledisk.html or https://aminet.net/package/disk/misc/giggledisk to make MountLists for attached devices.
Place the giggledisk binary in
C:or something so that it's available in the search path. - It might be a good idea to have fat95 installed on your Amiga, in case you want to use FAT32 images or other file systems that fat95 can handle: https://aminet.net/package/disk/misc/fat95
Now open a new CLI, and type something like:
giggledisk device=pi-scsi.device unit=0 to=RAM:PI0
This will create a MountList file called PI0 on the RAM disk, which contains almost all the information needed to mount the drive and its partitions in Workbench.
Note: PiSCSI uses the standard nibble ordering for SCSI devices, so the second unit (piscsi1) will actually be unit=10 rather than unit=1 as you might expect. Similarly, piscsi2 through piscsi6 will be unit=20 through unit=60.
You'll have to start up your favorite (or least hated) text editor and change the contents of the file a bit.
Above the FileSystem line, you'll notice a drive identifier. This line might say something along the lines of DH0 or PDH0, etc, and it must be removed, otherwise the file can't be parsed.
The FileSystem line will usually be empty, so you have to fill this out yourself. For instance, you can set it to something like L:FastFileSystem to use the standard file system for the drive, or L:fat95 in case the image is in a format that fat95 can handle.
Thus, an edited line would look something like FileSystem = L:FastFileSystem
If the MountList has several partitions listed in it, it must be split up into separate files for all partitions to be mounted.
Once you've edited a MountList file, simply copy/move it to SYS:Devs/DOSDrivers, and the drive will be mounted automatically the next time you boot into Workbench.
If you don't want it to be mounted automatically, simply use the Mount command from CLI.
A big word of caution
While the PiSCSI interface can be used to mount physical drives that are available as block device nodes on the Pi, you should not do this unless you are absolutely sure what you're doing.
Directly mounting a block device connected to the Pi may corrupt or destroy the data on the device, depending on what you or the file system drivers do with this disk on the Amiga side.