Re: [lwip-users] lwip on pico_w

[Christoph M. Wintersteiger]

Hi Edward,

 

Great to hear that your panics have gone away!

 

I don’t think this is properly documented. Core locking is described briefly here: https://www.nongnu.org/lwip/2_1_x/group__lwip__opts__lock.html

The tricky bit is that the pico SDK uses lwIP for the wifi ( “cyw43” is the wifi chip) and the documentation doesn’t tell you how that part of lwIP is configured. It so happens that it requires applications to take the lock, but the MQTT client application doesn’t support that (and LOCK_TCPIP_CORE doesn’t do anything either). I think it would be a good idea to add that to the MQTT client, but I haven’t had the time to do so myself. Similarly, it would also be a good idea to improve at least the documentation of the pico SDK!

 

Cheers,

Christoph

 

From: lwip-users-bounces+christoph=winterstiger.at@nongnu.org <lwip-users-bounces+christoph=winterstiger.at@nongnu.org> On Behalf Of Edward Vidal
Sent: Saturday, April 29, 2023 4:08 PM
To: lwip-users@nongnu.org
Subject: [lwip-users] lwip on pico_w

 

Hello All

The fix provided by Christoph M. Wintersteiger appears to have solved the panic issue on the pico_w. I would be interested in finding where this is documented.

The lwip was recently added to the pico-sdk . The fix appears to have come from a separate package cyw43-driver.

I had started with https://github.com/lwip-tcpip/lwip/blob/239918ccc173cb2c2a62f41a40fd893f57faf1d6/contrib/examples/mqtt/mqtt_example.c

which was  written over 5 years.  An update to repo would help others not going down this rabbit that I worked on for months.  First I tried enabling debug for lwip to the point that the debug from running the mqtt app.  Let me know if I can provide additional information.

This makes a $6 device very powerful. 

 

 

 

Edward Vidal Jr. e-mail develone@sbcglobal.net 915-595-1613