Overview Features Coding ApolloOS Performance Forum Downloads Products Order Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
Please visit our Apollo-Discord Server for support.



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
The team will post updates and news about our project here

SAGA SD Driver Newspage  1 2 3 

Philippe Flype
(Apollo Team Member)
Posts 299
29 Apr 2016 13:43


The driver is now stable.
             
  You can download last version here :
 
  EXTERNAL LINK   
  Will be hosted on Apollo-Accelerator.com soon.
 
  FAT, FFS, PFS File Systems have been tested with success.
   
  I personally tried 2 8GB SDHC cards. They both works.
 
  With PFS i have a single partition of 7.x GB.
   
  Speed isn't yet amazing but it is reliable and reach about 2 MB as you can see on this SysInfo screenshot (SD0 formatted in PFS) :
   
 
   
 


A1k Walter01

Posts 21
29 Apr 2016 15:53


Great


Philippe Flype
(Apollo Team Member)
Posts 299
30 Apr 2016 09:05


It is read from the dedicated MicroSD connector of the Vampire 600. Then the driver communicates with a dedicated interface in SAGA core. Amiga-side, all is done by the Driver in conjonction to the APOLLO CPU. The USB isn't related at all here.

Operation => FileSystem (either pfs3_aio-handler, FastFileSystem, FATFileSystem...) => sagasd.device => Core SD interface => HW => Card.


Chris Marsden

Posts 36
30 Apr 2016 10:34


Trying out the new sagasd.device - have one problem so far with my 32gb card - the last partition formats but quickly becomes corrupt (SD4:NDOS/BUSY). other partitions appear fine.
 
  using pfs3-aio,
  Mask
  0x7FFFFFFE
  MaxT
  0X0001FE00
  buffers 200 each part
 
  firstcylinder 2 last 35136
  sd0 - 2G
  sd1 - 5.1G
  sd2 - 7.2G
  sd3 - 12G
  sd4 - 2.4G <-----problem partition
 
  formatting with:
  pfsformat drive <drive> name <name> noicons quick fnsize 107

Additionally:

the included script (sdmount) that uses giggledisk doesnt correctly add the 'FileSystem' to the mount files it creates - i had to set the to PFS/3 by hand.


Philippe Flype
(Apollo Team Member)
Posts 299
30 Apr 2016 11:25


how did you build the mountlists ?

GiggleDisk ?


Chris Marsden

Posts 36
30 Apr 2016 11:40


the included script (sdmount) that uses giggledisk doesnt correctly add the 'FileSystem' to the mount files it creates - i had to set the to PFS/3 by hand.


Philippe Flype
(Apollo Team Member)
Posts 299
30 Apr 2016 12:00


here is my mountlist for PFSaio partition

/*
** Mount file automatically created by GiggleDisk
**
** GiggleDisk (c)2005 Guido Mersmann
**
*/


FileSystem      = L:pfs3_aio-handler
Device          = sagasd.device
Unit            = 0
BlockSize        = 512
Surfaces        = 16
SectorsPerBlock  = 1
BlocksPerTrack  = 64
Reserved        = 2
PreAlloc        = 0
Interleave      = 0
MaxTransfer      = 0x0001FE0
Mask            = 0x7FFFFFFE
LowCyl          = 2
HighCyl          = 15159
Buffers          = 600
BufMemType      = 0
StackSize        = 16384
Priority        = 0
GlobVec          = -1
DosType          = 0x50465303
Activate        = 1
Mount            = 1
/* Bootable      = FALSE */
#



Philippe Flype
(Apollo Team Member)
Posts 299
30 Apr 2016 12:01


For the FileSystem line, always use the one you see in your L: folder.

FileSystem      = L:pfs3_aio-handler
FileSystem      = L:FastFileSystem
FileSystem      = L:SmartFileSystem

and such


Chris Marsden

Posts 36
30 Apr 2016 12:15


to clarify PFS/3 was incorrect should be:

FileSystem      = L:pfs3_aio-handler

thanks Flype!


Philippe Flype
(Apollo Team Member)
Posts 299
30 Apr 2016 12:52


On first message i provided a link to the SD driver
   
  EXTERNAL LINK     
  PLEASE use only the SD driver inside this archive (sagasd.device, SDDiag and SDMount) !!!
 
  DO NOT USE RTG driver as it is BETA with a experimental stuff inside that should NOT be used.
 
  For RTG driver, still use the one that is hosted on Apollo-Accelerators.com
 
  Thanks.
 
  A fully packaged driver archive will be updated soon.


Philippe Flype
(Apollo Team Member)
Posts 299
30 Apr 2016 13:43


One early procedure could be :

1/ Download GiggleDisk

EXTERNAL LINK 
Copy Bin/GiggleDisk_AOS68K to C:GiggleDisk

----------------------------------------------------

2/ Download the beta SD driver

EXTERNAL LINK 
Copy only needed stuff

a) C/SDDiag to C:

b) Devs/sagasd.device to DEVS:

c) System/SDMount to SYS:System

----------------------------------------------------

3/ Insert your SD and Check it

a) Open a CLI

b) Type >C:SDDiag

If it detect your SD without error, then you are all good.

----------------------------------------------------

4/ You can create your partition(s) now

a) Change the Tooltype of your SYS:Tools/HDToolBox to

SCSI_DEVICE_NAME=sagasd.device

b) Do what you need in HDToolBox and save to disk.

----------------------------------------------------

5/ Open Workbench:System/SDMount

This is a script, so

a) DoubleClick on it from WB

b) Or from CLI >execute SDMount

This script runs GiggleDisk which is a tool that examine the Disk Geometry of your inserted SD card.

Once executed, GiggleDisk has created one or more 'mountlist' for you in RAM:T/SDMount

There is normally 1 mountlist per partition.

c) Open it (or them) in a Text Editor and Modify by hand the "FileSystem line" as follows :

FileSystem = L:pfs3_aio-handler
FileSystem = L:FastFileSystem
FileSystem = L:SmartFileSystem
or such... depends what you configured in HDToolBox (see step 6).

d) Save your mountlist(s) and place in your DEVS:DOSDrivers/SD0

----------------------------------------------------

6/ Reboot

----------------------------------------------------

7/ You should see on WB desktop the partitions as NON DOS.
Just format them with WB format in QuickFormat mode.

----------------------------------------------------

8/ You are ready.


Gunnar von Boehn
(Apollo Team Member)
Posts 6207
30 Apr 2016 16:07


Little improvement, more improvements will come soon
 



Gunnar von Boehn
(Apollo Team Member)
Posts 6207
01 May 2016 07:38


Again little improvement




James Conwell

Posts 8
01 May 2016 08:12


Why does GiggleDisk create so many tiny little partiiitions?

Why does it not create as few 107GB partitions as possible?

I don't want my puter filled with zilllionz of tiny partitions. :(

100GB is small enough already :(

And why are the buffers set soooooo smalll on each partiion?

In the old days simply increasing buffersize gave us a tremendous speedup with OFS and FFS.

p.s. keep up the good work!



Simo Koivukoski
(Apollo Team Member)
Posts 601
01 May 2016 17:34


Testing FFS, FAT32, PFS3 and SFS filesystems with the 128 GB SD card:
 
  EXTERNAL LINK 
 SysSpeed V2.5  - TestResults
  ============================
 
  Your System :  CPU: 68000  FPU: -----  ChipSet: OCS  OS: 2.0
 
  FFS        :  CPU: 68040  FPU: -----  ChipSet: ECS  OS: 3.1
 
  FAT32      :  CPU: 68040  FPU: -----  ChipSet: ECS  OS: 3.1
 
  PFS3        :  CPU: 68040  FPU: -----  ChipSet: ECS  OS: 3.1
 
  SFS        :  CPU: 68040  FPU: -----  ChipSet: ECS  OS: 3.1
 
  CompareBase :  You        Compare :  FFS
 
  +-------------+---------+---------+---------+---------+---------+---------+
  |  Test      |  You  | FFS    | FAT32  | PFS3    | SFS    |Compare  |
  +-------------+---------+---------+---------+---------+---------+---------+
  |  Drive        Results in Op/s                                          |
  +-------------+---------+---------+---------+---------+---------+---------+
  | Create      |  ----  |  155    |  1296  |  1907  |  1295  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  | Open        |  ----  |  1133  |  1528  |  3416  |  3876  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  | DirScan    |  ----  |  1928  |  16160  |  19574  |  13271  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  | Delete      |  ----  |  3036  |  1653  |  2755  |  514    |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  | Seek/Read  |  ----  |  9931  |  8530  |  9660  |  5465  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  |  Drive        Results in MB/s                                          |
  +-------------+---------+---------+---------+---------+---------+---------+
  | CreateFile  |  ----  |  0.85  |  0.88  |  0.85  |  0.86  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  | WriteFile  |  ----  |  0.84  |  0.87  |  0.86  |  0.86  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  | ReadFile    |  ----  |  2.17  |  2.30  |  2.26  |  2.26  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+
  | RawRead    |  ----  |  ----  |  ----  |  ----  |  ----  |  ----  |
  +-------------+---------+---------+---------+---------+---------+---------+



Philippe Flype
(Apollo Team Member)
Posts 299
02 May 2016 08:56


@James
   
GiggleDisk only does what have been specified in HDToolBox.
 
It is up to the user to setup HDToolBox partitions correctely to fullfill your wishes, which is not always easy, sure.
 
For people that are not easy (i'm in) with HDToolBox,

Simo nicely made a really informative video :

EXTERNAL LINK 


Chris Marsden

Posts 36
05 May 2016 08:30


Any more news on compatibility, which cards work so far? The 32Gb card i am having problems with is a SanDisk 32Gb microSDHC UHS-1.

EXTERNAL LINK 
  What make/model is the 128Gb tested above?


Martin Soerensen

Posts 232
07 May 2016 09:06


I am using the same exact card.
 
It seems to work fine for me, however I have another partition layout.
1: ~1.8GB PFS3_AIO
2: ~12.8GB PFS3_AIO
3: ~12.5GB PFS3_AIO
 
What can you do to trigger the problem with your last partition? Just copy stuff to it?


Chris Marsden

Posts 36
07 May 2016 10:03


Martin Soerensen wrote:

I am using the same exact card.
   
  It seems to work fine for me, however I have another partition layout.
  1: ~1.8GB PFS3_AIO
  2: ~12.8GB PFS3_AIO
  3: ~12.5GB PFS3_AIO
   
  What can you do to trigger the problem with your last partition? Just copy stuff to it?

I doesn't see matter what partition scheme i use. if i go over a certain number (not sure how may yet) of cylinders then i get an NDOS after reboot.

if i set up a 1x 32gb partition reboot and format all appears fine - after a reboot the partition returns NDOS.

again, if i set up 4x 7gb partitions and reboot i can format all 4. on reboot the last partition is NDOS.

If I make the last partition not extend to the last cylinder it will format fine.
 




Simo Koivukoski
(Apollo Team Member)
Posts 601
07 May 2016 13:43


Chris Marsden wrote:

          Any more news on compatibility, which cards work so far? The 32Gb card i am having problems with is a SanDisk 32Gb microSDHC UHS-1.
           
            EXTERNAL LINK             
            What make/model is the 128Gb tested above?
         

128GB card is Samsung.
         
Let's test your SanDisk with the FAT32 format, because fat95 device has partition geometry autosense.
         
Format your SD card on PC to FAT32 fileformat in normal way. Do not use any Amiga tools like HDToolBox, SDMount or Giggledisk.
         
Make sure you have:
     
          DEVS:sagasd.devive (v0.9 05/05/2016)
          L:fat95 (v3.18 03/01/2013)
          DEVS:DOSDrivers/SD0
          DEVS:DOSDrivers/SD0.info
         
Make sure that your DEVS:DOSDrivers/SD0 mountlist uses partition geometry autosense, its contents must be like this:

        FileSystem    = l:fat95
        Unit          = 0
        Flags          = 0
        LowCyl        = 0
        HighCyl        = 0
        Surfaces      = 1
        BlocksPerTrack = 1
        BlockSize      = 512
        Buffers        = 20
        BufMemType    = 1
        BootPri        = 0
        Stacksize      = 4096
        Priority      = 5
        GlobVec        = -1
        DosType        = 0x46415401
        Device        = sagasd.device


posts 54page  1 2 3