Discussion in "8051 Discussion Forum" started by    zachsmthsn    Apr 24, 2013.
Wed Apr 24 2013, 05:50 am
Hi all,

I am working on a project where I will be using an SD card to store sensor data and transmitting this data using an FTP to an iPhone app. The FTP is already developed and plans on using the SD card as a buffer. That is, the data will be sampled, and saved to an SD card. When a reading has completed, the data will be sent to the iPhone using the FTP that has been developed to send up to 20 kB files using 20 byte packets. What I need to do now is set up the SD card to be accessed using the SPI interface.

I have very little experience with this, but have been using the tutorial found on this website. (http://www.8051projects.net/mmc-sd-interface-fat16/) I seem to understand most everything in it, but am quite confused on the functions he talks about from pages 8-13. I understand their function and what is going on but I'm really not sure where they are being used. I feel like they have to be either added on to tff.c (I am actually using the petite version, though) or declared somewhere as deep, because they are used in the diskio.c to initialize everything and read/write to the SD card. If they are added to the tff.c file, the tff.h file would need to be modified (if I'm not mistaken) and I would think that this would have been addressed if it was the correct approach. It really is described more like these are functions you will be using to interface with this library, but I highly doubt that since they are used in the diskio.c file.

Thank you for any help you might be able to provide on this, and I might be coming back to this thread for more help. This was a last minute idea as a buffer for my senior design project, and the demo is next Thursday!
Thu Apr 25 2013, 10:21 am
Thanks for posting your doubt, Its fairly possible for a new user to learn about such abstract library. When I say abstract I mean library is written in a modular way such that it can be easily ported to different platforms and different storage media like SD card, hard drives etc. If your storage media changes driver will also change. Modular way of writing code ensures that any low level hardware change does not effect actual code which is hardware independent. So coders always write a small interface layer which is common to hardware independent code. In this case diskio.c is that layer.

All the top level function calls that deal with sd card goes to diskio.c which does your basic initialization of card, read and write operations. When you are working with petitfs you do not have tff.c file so I am not going to talk about it here. Its only pff.c which is as I said a hardware independent code. So neither tff nor pff.c needs to be modified.

diskio.c in petitfs package has skeleton functions which you need to fill up. Like disk_initialize, partial sector read, partial sector write.

Refer to SD Init for disk initialize:

Refer to SD Sector read/write:

Also refer to diskio.c mentioned here where most of your functions calls will go:

SPI related function will be replaced by your hardware spi functions. I did work on these myself. I might find something on my PC at home that I can share later on.

Do let us know if you still need anymore help.
Tags petitfsfatfselm-chan fatfsfat32fat16fat filesystemworking with fatfs8051 fat filesystem

Get Social


Powered by e107 Forum System



Tue May 21 2024, 02:06 am
Sun May 19 2024, 05:39 pm
Sun May 19 2024, 03:06 pm
Sun May 19 2024, 07:39 am
Sat May 18 2024, 07:28 am
Fri May 17 2024, 06:14 pm
Fri May 17 2024, 10:28 am
Fri May 17 2024, 10:19 am