Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
What is the size of the image and what is the image format?
What format it is (card format FAT16 or FAT32)?
(Sorry I can't help u in this even if u answer for my question because I didn't did these tests with SD/MMC. Still I'm struggling. If u can pls share some codes.
But if someone wants to help u those who worked on it this info will be helpful)
i had cleared that problem....successfully created the image file..but now the protocol is not executing....i need "spi protocol for mmc card in pic16f series"...
SD card project is very easy with mikroC PRO. It has SPI and MMC libraries. Post your project files and Proteus file in a zip file. Here is SD card project I did. https://www.edaboard.com/threads/271146/
I created mmc image fpr Proteus using WinImage 8.5
hi all, thanks for ur guidence.....now i'm having the dobt that from where i'll get this function "spi_write(0xff);"....i'm using HITECH PICC TOOLSUITE......
you cannot use 16F877A mcu for interfacing with MMC as it does not have sufficient RAM to read and write data to the MMC.
MMC or sdcards read and write using 512 Bytes of data, you need to reserve at least 512 bytes of RAM as buffer, maybe you could write data once but cannot edit it as you will need to read the data into the RAM.
Better option is to use an mcu like 18LF2620, this is a 28 pin mcu runs on 3.3V this makes the mcu voltage levels compatible with the MMC, you do not need resistance dividers or level translators for converting from 5V to 3.3V and vice-versa.
That is not true. Many people have already interfaced a simple PIC such as the 16F877A with a MMC/SD card. You only need the 512 bytes if your program relies on buffering.
They probably use an external RAM for buffering, or use only a part of the 512 bytes, say 300 bytes...the first technique would make the transfer slow, and the other is wasteful..
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.