Welcome, Guest. Please login or register.

Author Topic: SCSi2SD V6.0 board  (Read 5802 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline wmaciv

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 45
  • Country: us
  • Gender: Male
    • Show all replies
    • My linkedin profile
Re: SCSi2SD V6.0 board
« on: March 19, 2017, 05:14:59 PM »
Finally got mine to work, mostly.  I have a Sandisk 16MB Extreme Plus in it right now, with a small WB partition (310 MB), a large Work partition (1.9 GB), and a 1.9 GB non-partitioned area on the "backside" of the card I had to leave unformatted, as any time I try to set a partition to the end of the virtual disk, I can never format it, it always refuses to format and displays the "not a Dos disk" message.  Speed and access times are really good for what is working, 2,200,000 - 2,300,000 average.
 
 In use with A2091 with 14mHz physical hack (jumper wire; no patched software), with C= 7.0 ROM's, 2MB 60ns RAM on board.  Board is single device on the chain, native passive termination on the 2091 (resistor packs), V6 is set to device 0, SCSI termination on, 4GB volume size, and SCSI2 option enabled in options.
 
 Realize this is after wrestling with another set of cards that "should" have worked, the ones Alex sent with the cards I purchased, also SanDisk , just one speed grade below what I am using now.  
 
 Here is the weird thing.  When Alex from Inertial sent the boards (I have two), they worked initially, but as I started running into problems and reformatting, they got worse and worse about not reading drive geometry and not retaining whatever I attempted to write to the virtual disk (RDB info).  
 
 It is as though minimal fiddling = greater success?  Did I somehow overwrite a low-level formatting required to allow the cards to work?  I know SD cards have the (invisible to the average user) security partition.  Is it possible Michaels v6 board overwrites that area with the virtual volume infomation, as it is the last two blocks of the card space, and that that space is more critical to the card operation than just security protocols?  Just spit balling here...
 
 A more basic possibility that there is an issue with the Amiga side (HD Toolbox) overwriting something critical where Michael stores the volume parameters on the card, or the reverse, that the location on the SD card where the volume info is stored somehow prevents the Amiga side software from being able to write to the card.
 
 The logic seems to fit if I cannot partition the "last" segment of any given virtual volume, as though that area has to remain off limits for the v6 to use.
 
 Would love thoughts from the group.
 
 Mac
 

Offline wmaciv

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 45
  • Country: us
  • Gender: Male
    • Show all replies
    • My linkedin profile
Re: SCSi2SD V6.0 board
« Reply #1 on: March 21, 2017, 01:21:29 AM »
Finally! Got the v.6 working correctly. They are EXTREMELY picky about termination. Amiga 2000 with A2091, passive terminating resistor packs on the card desoldered, active terminator on the DB 25 external connector, 6.13 guru rom on board, all partitions firing on all cylinders. I have 4 SCSI devices, each set a 3 GB, and each partitioned into two equal parts (about 1.5 GB). NO errors, and that is with the SCSI 2 and cache toggle set active. I am getting consistent 2.4 MB/sec on my A2000 with stock CPU!

I have a SupraTurbo28 and GVP A2000-HC+8 on the way due to arrive next week. Curious to see if they play well or help with the speed.

This thing rocks!

Mac
 
 Oops, forgot to mention I went from 1.85 MB/sec to the 2.4 just by applying the 14 MHz hack. I actually applied the hack right after getting everything stable a 1.85 and it did not upset the setup. Woot!

Mac
 

Offline wmaciv

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 45
  • Country: us
  • Gender: Male
    • Show all replies
    • My linkedin profile
Re: SCSi2SD V6.0 board
« Reply #2 on: April 02, 2017, 11:05:49 PM »
   Okay, just updated to 6.1 firmware; no issues updating, but lost significant speed on the A2091/GuruROM setup. Went from almost 2.95 MB/sec to 2.35. Not sure what happened, but probably going back to 6.0.13 for the time being.