-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Shell FS sample halts with a usage fault error #39340
Comments
I will take a look at it tomorrow. But I can only try to reproduce it on Nordic DKs because I do not have mimxrt1064_evk. |
Thanks so much, if it only reproduces on NXP parts that would narrow down the bug |
@danieldegrasse Example did not compile on qemu_cortex_m0 due to not enough SRAM for the default configuration. Are you able to debug this example in order to find out what is the root cause of the crash? |
@jakub-uC It appears the bug was resolved by commit eb3375f. I debugged the issue further using commit 30cd046 and it appears to be something wrong with NXP's LPUART driver. The actual fault occurs on line 234 of isr_wrapper.S of Zephyr's software ISR wrapper. The bug occurs directly after calling When I narrowed down the issue, GDB was reporting that "program memory was no longer writable", and instructions were failing to execute correctly (for example, the call to |
Describe the bug
After flashing the shell filesystem example (samples/subsys/shell/fs) on an MIMXRT1064 evk, the example halts and prints a usage fault error. This bug reproduces on the latest version of the main branch, but not on v2.7.0-rc4. The bug first appears at commit 0a50ebe.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The UART shell should start and display the
uart:~$
promptLogs and console output
Here is what the console outputs after the usage fault:
Environment:
Additional Context
The issue appears to only occur in the filesystem shell example. It does not occur in other shell examples, and enabling the shell in the "hello world" example did not trigger the bug.
The text was updated successfully, but these errors were encountered: