-
Notifications
You must be signed in to change notification settings - Fork 3k
LocalFileSystem & wait() triggers MbedOS Fault Handler #6624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sounds like it's probably the same root cause as #6578 . |
@ARMmbed/team-nxp Please review |
@ARMmbed/team-nxp Any update on this? |
Have you configure it? |
@maclobdell Is this on your radar? |
@yennster thank you for raising this issue.Please take a look at the following comments: Could you add some more detail to the description? A good description should be at least 25 words. NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered. |
We've updated our automation, I will fix the requirements . |
Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers. |
We closed this issue because it has been inactive for quite some time and we believe it to be low priority. If you think that the priority should be higher, then please reopen with your justification for increasing the priority. |
Uh oh!
There was an error while loading. Please reload this page.
Description of defect
I'm observing an MbedOS hard fault when using the LocalFileSystem and wait(). I added a wait() command inside a loop that was writing multiple values to a CSV file. The hard fault seemed to occur when the wait() function was called.
Target(s) affected by this defect ?
LPC1768
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM & Online Compiler
What version of Mbed-os are you using (tag or sha) ?
n/a
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
gcc-arm-none-eabi-7-2017-q4-major
mbed-cli version: 1.5.0
How is this defect reproduced ?
I wrote up a simple
LocalFileSystem
example for the Mbed Application board that writes 100 integer values to a .csv file:The above code works and a
TEST.CSV
file is created in the local filesystem with integer values 0-99. However, when I add await
function to thefor
loop, the MbedOS Fault Handler is triggered:No values are stored into the csv file as the application doesn't get to
fclose(fp);
Expected behavior
That the fault handler is not triggered and the for loop waits for 0.05 seconds, then saves a test.csv file with the 100 integer values.
Actual behavior
Output to the serial terminal of the Fault Handler error message:
The text was updated successfully, but these errors were encountered: