Page 1 of 1

NNDK-2.8.6 - EFFS Not Working

Posted: Tue May 15, 2018 4:49 pm
by ecasey
Using NNDK 2.8.6 with a Mod5270B on a Mod-Dev-70 the file system for the SD card on the Mod-Dev-70 board does not see any files. I checked the SD card and it is fine. In my code I get f_chdrive() returning F_ERR_INVALIDDRIVE. After trying another Mod5270 and then another Mod-Dev-70CR board with the same results, I tried running the EFFS-FTP example in the Examples/StandardStack folder. It gives a traps on a segmentation fault at f_chdir('/'); (line 184) in ftp_f.cpp. It shows the Flash Card Memory usage correctly, but the Display Directory comes up empty.

My code worked fine in NNDK2.8.3. I did a roll back to make sure. I didn't see anything in the notes for NNDK2.8.4, 5 or 6 that looks like you touched the file system.

Can you give me some guidance on this?

Thanks

Ed

Re: NNDK-2.8.6 - EFFS Not Working

Posted: Tue May 15, 2018 5:30 pm
by Jon
Hi Ed,

You will want to replace the fatfile.a from your previous NNDK release with what is currently in the lib directory. This is a known issue that we are working to resolve for the next release. Sorry for any inconvenience it has caused you!

Kind Regards,
Jon

Re: NNDK-2.8.6 - EFFS Not Working

Posted: Tue May 15, 2018 6:17 pm
by ecasey
That worked.
Thanks Jon.

Ed

Re: NNDK-2.8.6 - EFFS Not Working

Posted: Tue May 22, 2018 9:17 am
by SeeCwriter
Jon,

I have the same issue with 2.8.6, and I'm confused by your answer. Is the "previous NNDK release" v2.8.3 or v2.8.6? Because it seems as if you are saying to replace fatfile.a in v2.8.3 with the same file from v2.8.6.

Re: NNDK-2.8.6 - EFFS Not Working

Posted: Tue May 22, 2018 1:14 pm
by TomNB
The FatFile.a library has not changed throughout all the 2.8.x revisions, so you can copy it from any of those releases.

Re: NNDK-2.8.6 - EFFS Not Working

Posted: Tue May 22, 2018 3:42 pm
by SeeCwriter
If nothing has changed, why would replacing FatFile.a solve the problem?

Re: NNDK-2.8.6 - EFFS Not Working

Posted: Wed May 23, 2018 1:41 pm
by TomNB
Somehow that file was corrupted when the release was created.