2011/4/29 Sebastien Lelong <[email protected]> > > I'll perform more tests, and try to close SD card sector every 512 bytes > (it is required, right ?) >
Doesn't work either, still stuck on the same location. I also tried to directly move (seek) just before, avoiding long reading before getting there, and it gets stuck too. Moving just after works perfectly, I can read the remaining data (~56MB). I've just also tried to move just before the problematic location, and manually read content, that is, directly read contiguous data bytes, and... it works, I can read several blocks after ! This means my adressing logic is buggy... cheers, Seb > 2011/4/28 mattschinkel <[email protected]> > >> Why did you decide to read 4 bytes (0x3253FEFF) instead of two >> (0x3253)? >> >> What are the next bytes if you read after 0x3253FEFF? >> >> Matt. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "jallib" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/jallib?hl=en. >> >> > > > -- > Sébastien Lelong > http://www.sirloon.net > http://sirbot.org > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
