I've just had a quick fiddle with FozzTexx's RaSCSI fork, the one that works with the V9k, to get it to dump drives via the xebec controller:
github.com
Essentially sasidump needed updating slightly to 1) give a bit more of a delay in the selection negotiation as it was fouling up, and 2) download the drive parameters to the xebec card which will default to a 5MB geometry.
I link here in case it's useful: https://github.com/drdpj/RASCSI/tree/Victor9k
The way to work out the geometry is to dump the first block, and have a look at bytes 0x24 thru 0x2b. Those form the parameter block that needs to be uploaded to the controller. At present I've just hard coded the values for a 10MB drive in the parameters[] array at the top of sasidump.cpp - there are many more elegant ways of doing this, but it's a bit of a one shot thing for me as I've only got the one drive. I might try and do something a bit more user friendly in due course, but for now it works.
GitHub - drdpj/RASCSI at Victor9k
English fork of the Japanese RaSCSI project. RaSCSI allows a Raspberry Pi to function as emulated SCSI devices (hard disk, CD-ROM, and others) for vintage SCSI-based computers and devices. - GitHub...
github.com
Essentially sasidump needed updating slightly to 1) give a bit more of a delay in the selection negotiation as it was fouling up, and 2) download the drive parameters to the xebec card which will default to a 5MB geometry.
I link here in case it's useful: https://github.com/drdpj/RASCSI/tree/Victor9k
The way to work out the geometry is to dump the first block, and have a look at bytes 0x24 thru 0x2b. Those form the parameter block that needs to be uploaded to the controller. At present I've just hard coded the values for a 10MB drive in the parameters[] array at the top of sasidump.cpp - there are many more elegant ways of doing this, but it's a bit of a one shot thing for me as I've only got the one drive. I might try and do something a bit more user friendly in due course, but for now it works.
Last edited: