Lpc2000

Bertrik Sikken wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Tom Walsh wrote:
>  
>
>>I have posted my project for the MMC FAT16 DOS driver system.  This is 
>>build on NewLib stubs and the RDCF2 filesystem driver code.  Also, the 
>>project has support for the gettimeofday() and settimeofday() library 
>>functions, as well as the fopen(), fclose(), fread(), fwrite(), etc..
>>
>>The site is http://openhardware.net 
>>
>>and for the impatient:  
>><http://www.openhardware.net/?title=RDCF2%20DOS%20FAT%20Filesystem%20for%20LPC2138&dir=rdcf2&file=rdcf2lpc2138.html> 
>>    
>>
>
>This is cool stuff. Also nice to release it under BSD style license!
>
>  
>
Thanks.  The original author had released the source into public 
domain.  I felt it appropriate to continue with the spirit in which I 
had received it.  FAT16 filesystem is not some huge, mind-boggling thing 
of which only uber-programmers can achieve.  It is a simple filesystem 
which is actually based on the original CP/M-80 filesystem, which was 
based on ...


>By the way, I think the Keil USB mass storage example for LPC214x
>would be a nice complement to this software, see:
>http://www.keil.com/download/docs/307.asp
>This would allow you to use the LPC to write files on the SD/MMC
>card, then plug the LPC into a PC's USB port and let the PC
>access the SD/MMC card like it was a removeable drive (and read
>the files).
>The device layer needs to be sufficiently independent, which
>already seems to be the case in your code, although the API
>probably needs to be a bit more elaborate. For example not just
>read / write sector, but also functions to get card info (for the
>SCSI INQUIRY command) and to get the size of the card (for the
>SCSI GET CAPACITY command), etc.
>
>I am myself thinking of using FAT32. I found this driver (GPL)
>that already provides FAT32 read support:
>http://www.robs-projects.com/filelib.html
>I am investigating if it is possible to add write support to it.
>
>  
>
I would suspect that you are more interested in long filenames as 
opposed to a FAT32 FAT table?

Be carefull of long filenames, I do believe that Microsoft has patented 
that.  While as a hobbist this may not be much of a concern, what do you 
if you come up with a cool product and start selling it?  There are 
"entrance fees" to Microsoft technologies, the per-unit royalty may be 
attractive, but you have that "entrance fee" + a minimum usage / year 
requirement.

A company I had worked for, 15 years ago, looked into licensing of MSDOS 
Version 3.x filesystem.  We were told at that time that a minimum order 
of 500 licenses per year for every year that we shipped product.  If we 
did not use the purchased licenses, we were to destroy the remaining 
licenses and purchase another 500.  Each license was $70 per, this 
translated into a minimum of $35K / year just to include MSDOS into the 
product.  Keep in mind, MSDOS 3.x was retailing off-the-shelf for around 
$30 at that time.  Microsoft's response to that had been that "they are 
volume dealers".  No, we could not purchase MSDOS 3.x from those 
dealers, pre-install it into our product and pass it along to our 
customers: this was not allowed, we needed a re-seller license!


>There really should be something small, portable and configureable
>for FAT like lwIP (light-weight IP) is for embedded TCP/IP stacks.
>Would be cool to call that "light-weight FAT" :)
>
>  
>
Something like that, RDCF2 is a bit lame.  :-/

TomW


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------