Shop OBEX P1 Docs P2 Docs Learn Events
Any benefit of DOS-on-chip versus just using FSRW for SD card? — Parallax Forums

Any benefit of DOS-on-chip versus just using FSRW for SD card?

Don MDon M Posts: 1,653
edited 2010-02-19 17:38 in Propeller 1
Or maybe I should ask for the pros / cons ?

Comments

  • Kal_ZakkathKal_Zakkath Posts: 72
    edited 2010-02-17 21:29
    I'm no expert (I'm sure someone who is will chime in sooner or later) but I belive fsrw is designed for reading/writing files, rather than traversing or modifying the FAT structure (i.e. moving files/creating directories/etc). For instance I think fsrw still deals with files only in the root directory.
    For most uses this is fine, I think a lot of the directory handling stuff has been deliberately left out of fsrw to keep the code size down.

    There is also Kye's file system driver: http://forums.parallax.com/showthread.php?p=871049
    I haven't tried it myself but looks like it does pretty much everything you could want when playing with file systems (including folders/subfolders/attributes/etc)

    Obviously using either of these two saves you having to add an extra component.
    To be fair I should point out that I have never used DOS-on-chip, but so far fsrw has done everything I've needed it for.


    Edit: Just checked the thread with Kye's version in, it looks like it works but is not a 'final stable' release. Use at your own risk [noparse]:)[/noparse]

    Post Edited (Kal_Zakkath) : 2/17/2010 9:38:22 PM GMT
  • KyeKye Posts: 2,200
    edited 2010-02-18 03:42
    The driver on the first page is stable, if it works for you. The ones after that are not stable.

    There is a faster version buried in the thread that is stable called FATEngine Lonesock. Use that one if you can find it.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Nyamekye,
  • ericballericball Posts: 774
    edited 2010-02-19 17:38
    Dos-on-chip provides an I2C/SPI/serial interface with 1 byte commands. So to interface to it you'd need a SPIN API layer and an I2C/SPI/serial layer, which would replace the two FSRW layers. Depending on your application, the API layer would probably be quite thin, and you might be able to leverage the I2C/SPI/serial layer for other purposes in your program. If you used the I2C connection you could save 2 pins, but at the cost of the board area & power for the extra chip. No idea about performance.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Composite NTSC sprite driver: Forum
    NTSC & PAL driver templates: ObEx Forum
    OnePinTVText driver: ObEx Forum
Sign In or Register to comment.