The arm-none-eabi GCC port and it's accompanying newlib (I got mine from Codesourcery but I suspect this applies to all) clearly has hooks in it to add a filesystem into an application.
I've Googled around and haven't found anything that seems to really be definitive -- Is there any really good documentation on how to do this, preferably from the point of view of the newlib developers?
TIA.
In the source tree, look in libgloss/ (sibling to newlib/). There are various implementations of the I/O layer, from "nosys" which does nothing, to simulator syscalls, to various os-specific layers. The libgloss library lets you provide low-level open/read/write/close/exit/etc functions. Newlib's I/O functions (like stdio) are built on top of these.
Most ports just have a write() equivalent that's used for debug printfs, and exit().
I referred to this when I did it:
(It is rather old now)
In general it is probably a useful approach for larger projects. But it does bring in all of stdio, malloc and so forth. So it can severely bloat the code if you don't really need it.
What I'm doing qualifies as a "larger project" in that regard. I'm using some off-the-shelf software that's going to be happier with stdio and malloc -- I'm probably saving work by at least a factor of 3:1, while using more memory at a factor of 5:1 or so. At the anticipated sales volume for the product, it's worth it.
Said so: for an application I used FatFS:
Hope this helps
Bye Jack
I've used that too, a really nice little system, very easy to incorporate into a project.
tto:
om
t,
ard.
Yup, I've also used the above pair; only a tiny bit of work to integrate.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required