RE: (Fwd) Re: cbm 9060/9090 scsi command set

From: didier derny <>
Date: Thu, 14 Nov 2013 22:45:37 +0100
Message-ID: <000301cee182$dbc741f0$9355c5d0$@org>

I'm building a sdcard adapter for the replica 1 multi i/o board
(almost the same as the scsi board I was using in 1982)

So I was thinking to use the SASI / SCSI 1 protocol to communicate between
The multi I/O board and an avr with a sdcard.

The multi i/o board just lack the line drivers.

At the same time, if the sdcard adapter is able to talk to a sasi board...
It can also be used as a scsi disk :)

Btw: there are 2 command set in sasi/scsi 1, the standard set and the oem

If the 9060/9090 are only using the standard set  it's relatively easy

I already have the sdcard  driver working in the avr..

It could also be used in others ancient equipment using SASI / SCSI 1 disks

The other problem is the identification string, (if the 9060 is checking it)
It could be programmed with a console (serial port)  and stored in the


-----Message d'origine-----
De :
[] De la part de Nate Lawson
Envoyé : jeudi 14 novembre 2013 20:24
À :
Objet : Re: (Fwd) Re: cbm 9060/9090 scsi command set

On Nov 14, 2013, at 8:12 AM, Ethan Dicks wrote:

>> a second solution could be to replace the EPROM by one with my own 
>> content; not having to use this weird SASI protocol, it would 
>> simplify the interfacing.
> I think it might be possible to tweak the ROM code to properly support 
> SCSI command packets, but it would probably take a lot more tweaking 
> to support partial sector writes to a drive that was formatted to 512 
> bytes per sector.  The DOS 3.0 filesystem maxes out around 16MB anyway 
> (if you were to rewrite the code that expects a ~300-cylinder drive 
> with 32 sectors per track and either 4 or 6 heads) so there's no real 
> loss in giving up half of each sector.  Even my smallest embedded SCSI 
> drive is 50MB, so I couldn't address every block.
> I see two approaches to the same destination - put a SCSI bus analyzer 
> on a working drive and watch the transactions for format, reads, and 
> writes, and disassemble the DOS Board ROMs and look for every command 
> packet that the board sends to the SASI-MFM board.  It's probably only 
> about half a dozen kinds.  Once we know what the SASI commands are, 
> that's a long way to sticking a replacement on the bus.

Early SCSI is extremely simple. You don't have complex commands like READ
DEFECT DATA or the like.

With an Atmel with USB support, you could easily emulate the SASI interface
on one side and talk to a USB flash drive on the other. You could do this
either at the filesystem level (generate FAT commands to write to a storage
file) or the raw level (using only 20 MB out of a 4 GB drive, hehe) via
command translation. The former would pretty much be sd2iec but for SASI.


       Message was sent through the cbm-hackers mailing list

       Message was sent through the cbm-hackers mailing list
Received on 2013-11-15 02:01:04

Archive generated by hypermail 2.2.0.