hello m_ezwan86, please try to read the file after writing to it - close the file and reopen it in writing mode, read it, and inform me of your findings. as for FAT32_Dir() - there is a handling function FAT32_Dev_PutChar() in __Lib_FAT32_Driver.c file. FAT32_Dir() invokes FAT32_Dev_PutChar() when i...

hello m_ezwan86, FAT32_Dir ( ) invokes another function, FAT32_Dev_PutChar ( ). this function is available in __Lib_FAT32_Driver.c, and it can be modified to suit your needs and wishes. you don't need to access this data directly - though there is a way to do so - you need to initialize LCD and use ...

Serge,

Thank you kindly for the info. There is little I can do at this point, unfortunately.
Please contact our Support department, hopefully they will have more success.


Kind regards,
MiloVan

Serge, There is one additional thing I would like you to try. The hex file in the attachment was tested on two PIC32MX4 boards and several cards. Please try to program your board with this hex. If the problem persists, please contact our Support department directly on support@mikroe.com , and they w...

Hi Serge, Thank you very much for the info. It seems we are getting somewhere, with not the best of news, though. As stated before, the example was tested on PIC32MX4 board and LV32MX v6 board, even with 8GB cards, and it worked fine. Before reaching any final conclusion, I will conduct additional t...

No problem Serge :) As for the error code - ouch. It suggests that the FAT32_Dev_Init( ) routine (which invokes Mmc_Init( ) routine) failed for some reason, before any FAT32 operation commenced. Serge, could you please try several times to invoke FAT32_Dev_Init( ) routine before FAT32_Init( ) and ch...

Serge, Thank you for the info. Though it is yet unclear why FAT32_Init( ) failed, the LEDs should blink on every sec after "init failed" message. Now, I have few suggestions if you are willing to help me in this: - Invoke FAT32_GetError( ) function right after the FAT32_Init( ) function. - Convert t...

Hello Serge, As Janko stated prevously, the example was tested and should work on PIC32MX4 board, as well as LV24-33A board. It was tested on both PIC32MX4 board and LV32MX development system. The problem with PIC24 may be due to high SPI baud rate. Please try the example with lower SPI clock speed ...

Hello linspire,

Yes, the library will be available on PIC18F4520.
However, please note that the new library has greater memory requirements.

Kind regards,
Milovan

Hi Vojin, There is no dedicated function to handle your request - which is quite in place in my opinion - but there is a workaround. You could create entirely new file (don't forget to name it differently!), and copy the contents of the original into it's copy except for those 100 bytes. After that ...

hello nuno,

a function for file listing of the current directory is present in the library.
listing of entire medium was considered, but it was decided not to go with it in this release.
you are correct, this would be a fine addition to the library.

Hi everyone, FAT32 Library for C is going to be available very soon on Libstock. You are very encouraged to try and use it, and please report any suspicious behavior. File Handler mechanism is implemented, which means several files may be opened at once, with easy read/write from one to another. The...

stevenindon, Thank you for your interest in the FAT32 library, and I am so glad that MikroE can be of service to you. PIC32 is really good platform and, to be honest, my personal favorite. As for PIC16 controllers - unfortunately, FAT32 it is not intended to be available for PIC16 platforms, due to ...

Hello stevenindon, As a developer of FAT32 library for MMC/SD cards, let me assure you that FAT32 will be available on PIC32 for certain, and on all platforms with sufficient RAM. I cannot say how much "sufficient" is just yet, though it is most likely that all platforms with at least 1.6kB of RAM w...

Hello everyone, FAT32 library for MMC/SD cards is under "heavy" development. Unlike FAT16 library, it will have C-like library interface for file management. Files will need to be opened, read/written, and eventually closed by user. This library is not likely to be included in future compiler releas...