Yes, it is possible to do this. How depends on which LWIP mode you're using. In NO_SYS mode, you could put the TCP thread on the second core. In SYS mode, there's probably a way to set affinity for the LWIP FreeRTOS tasks, although I'm not sure what it is. You could also just leave it to run on whichever core it wants and set the priority of your timing sensitive IO tasks higher. There is probably some portion of the LWIP interactions that run in the calling thread no matter what, so you could also structure your application code such that you never call LWIP from core0, and instead send messages to another application thread on core 1 that does call LWIP.
That being said, on the Pico, it's often best for timing sensitive IO to run using PIO or DMA, which can reduce the likelihood of LWIP bothering you.
If you are more specific on exactly how you're running LWIP mode right now, maybe I could say more.
That being said, on the Pico, it's often best for timing sensitive IO to run using PIO or DMA, which can reduce the likelihood of LWIP bothering you.
If you are more specific on exactly how you're running LWIP mode right now, maybe I could say more.
Statistics: Posted by jags84 — Tue May 14, 2024 6:15 pm