Re: D9060 with OpenCBM

one of the Problem of connecting SASI to SCSI is termpower...

termpower PIN on a SCSI is connected to +5v  (some controller have a fuse)

the same PIN on SASI it's not connected or connected to GND so 
connecting SASI to SCSI often produce a short circuit

the termpower has to be disabled on the controller, or the cable modified



On 20/08/2017 21:53, Ethan Dicks wrote:
> On Sun, Aug 20, 2017 at 8:17 AM, smf <smf@null.net> wrote:
>> On 20/08/2017 09:59, didier derny wrote:
>>> this board: http://www.codesrc.com/mediawiki/index.php?title=SCSI2SD may
>>> work too
> Reading up on it, the SCSI2SD appears to now support internally
> mapping ID 0 LUN 1 as ID 1, so that part might be OK.
>
>> However like all good standards people ignore the details of the
>> specification & implement their device to work with other peoples
>> implementations.
> One thing that's different about the D9060/D9090 vs "modern" machines,
> is block size.  256 bytes per block, not 512.  Any new SCSI/SASI
> device would have to support, at least in some fashion, the low-level
> formatting routines (or at least respond in such a way that the ROM
> header command would still work.  There's no need to really low-level
> format, of course, so it's likely that just a "N0:DISKNAME" and not a
> "N0:DISKNAME,ID" would work.  The block size still has to work, of
> course and few modern devices deal with physical blocks under 512
> bytes.  That might take some additional mods to SCSI2SD beyond the LUN
> mapper fix.
>
> -ethan
>
>         Message was sent through the cbm-hackers mailing list


       Message was sent through the cbm-hackers mailing list