What’s Different in FullFAT 1.1.0
Under General Discussion
Discuss, 1 Comment.
Follow any responses to this entry through the RSS 2.0 feed.
Posted on Saturday, February 20th, 2010 at 5:08 pm
Under General Discussion
Discuss, 1 Comment.
Follow any responses to this entry through the RSS 2.0 feed.
Posted on Saturday, February 20th, 2010 at 5:08 pm
FullFAT 1.1.0 is coming very soon. There have been some huge changes since the 1.0.x series. I’ve tried to ensure that all API’s remain the same, however some have changed their behaviour slightly, to ensure that FullFAT works more consistently. Here is a list of the changes so far:
There may be some other differences not noted here, however they will appear in documentation shortly.
Expect an official release in approximately 1 or 2 weeks time. (Grab from SVN to test).
James
© 2009 James Walmsley. All rights reversed. Contact us.
01-Apr-10
Hi James!
Sorry for my english!
I try to use your last trunk version (r349).
In file ff_dir.c on a line 1790 where are:
*((FF_T_UINT16 *) &EntryBuffer[FF_FAT_LFN_NAME_1 + x]) = Name[i];
If you will be use your sources on a processor which require align to word boundary, then error occured.
Example:
///////////////////////////////////////////////////////
U8 EntryBuffer[32];
U16 Name[16];
*((U16*)&EntryBuffer[1]) = Name[0];// error
////////////////////////////////////////////////////
You need to use macros. Something like this:
#define write16(a,v) (ADR(a)=(U8)(((U16)(v))&0xff), ADR(a+1)=(U8)(((U16)(v))>>8))