Thanks for the prompt response.
After some careful placing of cyw43_arch_lwip_begin/cyw43_arch_lwip_end tightly around any lwIP call called from my main function I eventually got better results (long term stability test I did not do yet).
As a suggestion:
- Could this be better pointed out in the pico SDK examples? It seems that usage of cyw43_arch_lwip_begin/cyw43_arch_lwip_end is not been done anywhere there and may lead beginner to think it is no-issue, which it isn't obviously.
- Could the Pico SDK provide a meaningful implemenation of LWIP_ASSERT_CORE_LOCKED (for asyny_context_thread_background) which is exactly meant to help developers avoid such issue?
After some careful placing of cyw43_arch_lwip_begin/cyw43_arch_lwip_end tightly around any lwIP call called from my main function I eventually got better results (long term stability test I did not do yet).
As a suggestion:
- Could this be better pointed out in the pico SDK examples? It seems that usage of cyw43_arch_lwip_begin/cyw43_arch_lwip_end is not been done anywhere there and may lead beginner to think it is no-issue, which it isn't obviously.
- Could the Pico SDK provide a meaningful implemenation of LWIP_ASSERT_CORE_LOCKED (for asyny_context_thread_background) which is exactly meant to help developers avoid such issue?
Statistics: Posted by christiank2510 — Fri Jan 19, 2024 8:12 pm
