Mass storage Reader / Writer...
Kaos Kidd
Posts: 614
As stated throughout several threads, I though a single thread for this might come in handy.
With the choices for mass storage being as big as they are, one would need to narrow the field some before a consolidated project could work.· For example, with minor coding changes, MMC & SD can work together as a single project.· USB Thumb and 1" Glass drives (along with the correct supporting hardware) is a nice and very portable answer.··Finally, power hungry·IDE and CDRW drives.· I delibertly didn't metion the FRAM or any of the other types of data storage.· WHat I'm hoping to focus on is std access to std storage media.
As every one knows, it's not just the aspect of connecting and reading or writing to any storage device, it's making that data available to other hardware that is the hard part.··In this case, we're talking something a PC can read or write to, which indicates a file system of one kind or another.
Currently, there are two trains of thought:
·In any case, if you want your data to be transportable, you as the developer must decide early on how you are going to do it.· In some cases, a completly 100% custom approch is fine, where as in other cases, a FAT?? system is required.· I myself have been playing with custom BAM (throw back to the Commodore days as a Block Allaocation Map) and software on both sides (the PC and the uController) to manage the data exchange.· Even with a 100% custom approch, you will still need to rely on the low level data transfer of commands, data and status codes.
· Well, I'm willing to share and work on it... any other takers?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Just tossing my two bits worth into the bit bucket
KK
·
With the choices for mass storage being as big as they are, one would need to narrow the field some before a consolidated project could work.· For example, with minor coding changes, MMC & SD can work together as a single project.· USB Thumb and 1" Glass drives (along with the correct supporting hardware) is a nice and very portable answer.··Finally, power hungry·IDE and CDRW drives.· I delibertly didn't metion the FRAM or any of the other types of data storage.· WHat I'm hoping to focus on is std access to std storage media.
As every one knows, it's not just the aspect of connecting and reading or writing to any storage device, it's making that data available to other hardware that is the hard part.··In this case, we're talking something a PC can read or write to, which indicates a file system of one kind or another.
Currently, there are two trains of thought:
- Impliment a form of FAT12/16/32 (Or... NTFS)
- Ready made solutions like this one:· http://www.ghielectronics.com/uALFAT-SD.htm
- Home made solutions from info like this:
- http://technet2.microsoft.com/WindowsServer/en/Library/50cd4ffc-1389-423d-9d02-1a898b2eb39f1033.mspx?mfr=true· (FAT16/32)
- http://technet2.microsoft.com/WindowsServer/en/Library/8cc5891d-bf8e-4164-862d-dac5418c59481033.mspx?mfr=true· (NTFS)
- Self Managed mass storage.
- Based on the information like·in this pdf:· http://www.ghielectronics.com/uALFAT-SD.htm
- and something like this to connect it:· http://www.sparkfun.com/commerce/product_info.php?products_id=204
- And some help from here:· http://www.kingmax.com/product/storage/KDxxxSC.pdf
(the above link list is only a primer-> something to get us(me) started.)
·In any case, if you want your data to be transportable, you as the developer must decide early on how you are going to do it.· In some cases, a completly 100% custom approch is fine, where as in other cases, a FAT?? system is required.· I myself have been playing with custom BAM (throw back to the Commodore days as a Block Allaocation Map) and software on both sides (the PC and the uController) to manage the data exchange.· Even with a 100% custom approch, you will still need to rely on the low level data transfer of commands, data and status codes.
· Well, I'm willing to share and work on it... any other takers?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Just tossing my two bits worth into the bit bucket
KK
·