-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
nrf52 telnet_shell panic. Mutex using in ISR. #22697
Labels
Comments
Reproduced with telnet sample running over BLE IPSP. I'll try to put |
Fast solution. Works for me.
|
Yeah, I've originally thought of something similar, but eventually, I've ended up using a |
rlubos
added a commit
to rlubos/zephyr
that referenced
this issue
Feb 11, 2020
A `k_timer` callback is called from the ISR context on certain devices (nRF), which resulted in an assert in the kernel, as `telnet_send`, and thus `net_context_send` used a mutex. Fix the issue by replacing a timer used by the `shell_telnet` module with a delayed work, which will execute it's callback in a system workqueue context. Fixes zephyrproject-rtos#22697 Signed-off-by: Robert Lubos <[email protected]>
jukkar
pushed a commit
that referenced
this issue
Feb 12, 2020
A `k_timer` callback is called from the ISR context on certain devices (nRF), which resulted in an assert in the kernel, as `telnet_send`, and thus `net_context_send` used a mutex. Fix the issue by replacing a timer used by the `shell_telnet` module with a delayed work, which will execute it's callback in a system workqueue context. Fixes #22697 Signed-off-by: Robert Lubos <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Stack is
Since timer handlers in nrf52 is in ISR and network uses mutexes we got panic. Maybe moving
telnet_send
in separate thread will resolve this issue.The text was updated successfully, but these errors were encountered: