Post Created date
FatFs disk_timerproc problem
clawson wrote: zu_adha wrote:so my problem is when i turn off disk_timerproc(), my program works fine. Have you actually looked at what disk_timerproc does? It has several...
Monday, 1 February 2016 - 17:55
FatFs disk_timerproc problem
anyone can help me?
Monday, 1 February 2016 - 10:26
f_lseek FatFs question
so the problem is solved, i change my 16MB  SanDisk FAT with 2GB SanDisk FAT32 and it works !! with 0 size file. its look like FatFs fail on FAT system
Sunday, 31 January 2016 - 11:08
f_lseek FatFs question
JohanEkdahl wrote: zu_adha wrote: JohanEkdahl wrote: "Words represent concepts. Use the wrong words, communicate the wrong concept."   sure....  "Words represent...
Sunday, 31 January 2016 - 10:59
f_lseek FatFs question
JohanEkdahl wrote: zu_adha wrote:btw is just a name Agreed, but the unclear written will not help you to think clearly.   sure....  "Words represent concepts. Use...
Sunday, 31 January 2016 - 09:44
f_lseek FatFs question
so this is my debugging code   UINT bw; res = f_open(&fin, "text.txt", FA_OPEN_ALWAYS | FA_WRITE); if(res == FR_OK) { if(f_lseek(&fin,f_size(&fin)) ==...
Sunday, 31 January 2016 - 09:32
f_lseek FatFs question
thanks for the reply, i'll take no 1.2.3 and yes no 4 ( none of above might help me,  but i can get the clue why it won't append on 0 size file) because i think you guys just...
Sunday, 31 January 2016 - 08:56
f_lseek FatFs question
theusch wrote: Your code is only looking for FR_OK, and that is not happening.   What return value >>are<< you getting? Once you know that, then you can look in...
Saturday, 30 January 2016 - 17:18
f_lseek FatFs question
  theusch wrote: What >>is<< the function returning?   I'd peek at the source.  F_EOF isn't listed as a return value, but is mentioned in the function...
Saturday, 30 January 2016 - 16:54
atmega328 and FatFS
problem solved !! after checking my connection, monitoring with oscilloscope, and digital analyzer just make me more crazy. then i changed the mmc module from this  ...
Friday, 29 January 2016 - 16:10
atmega328 and FatFS
still get same problem after i put #if 0 on #define SOCKINS and SOCKWP. any other pin that used on program that used pin beside SPI and sdcs? or maybe pin assignment that i have...
Friday, 29 January 2016 - 14:30
atmega328 and FatFS
clawson wrote: That would explain a lot. If it's reading the pins that are floating inputs then it could well be that poking a finger in their general direction grounds them....
Friday, 29 January 2016 - 14:20

Pages