The FreeRTOS kernel is now an
AWS open source project
, and these pages are being updated accordingly.
The FreeRTOS Ecosystem Showcase . . .
A Selection of Add-on and Complementary Products
Contact / Enquiries
to be enabled.
view a static menu.
Thread aware TCP/IP stack
Thread aware file system
File System Error Code
FreeRTOS Embedded File System API
Error codes returned by the embedded file system API functions are detailed in the table below.
The specified drive does not exist.
The volume is not formatted.
The directory specified is not valid.
The file name specified is not valid.
The file or directory could not be found.
The file or directory already exists.
The volume is full.
A function cannot complete because the file is not open.
End of file.
An invalid parameter was passed into f_seek().
The file is already opened for writing / appending.
The necessary physical read and/or write functions are not available for the volume.
The directory cannot be deleted because it is not empty.
No init function is available for the driver, or the function generated an error.
The card is not present.
There is a non-recoverable error on the drive.
A sector has developed an error.
There was an error when reading the volume.
There was an error when writing to the volume.
The media is not recognised.
The access semaphore was not obtained before the timeout expired.
The FAT type is not recognised.
Media is too small for the type of format requested.
Media is too big for the type of format requested.
The sector size is not supported. The only supported sector size is 512 bytes.
There was a memory allocation error.
[ Back to the top ]
[ About FreeRTOS ]
[ FreeRTOS+ Sitemap ]
[ Main FreeRTOS Sitemap ]
Report an error on this page (with anti-spam)
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.