[lwip-users] lwip on pico_w

2023-05-23 Thread Edward Vidal
hello allI was able to fix the pico_w mqtt lwip such that now if the broker is not present the the pico_w will continue to to restart. Features commit d649e05894fc8393da066d371e329ecae80dbf45 (HEAD -> dev, origin/dev)Author: Edward Vidal Jr Date:   Tue May 23 07:47:11 2023 -0600 ver 0.0.09 url

[lwip-users] lwip on pico_w

2023-05-22 Thread Edward Vidal
hello all.static mqtt_client_t* saved_mqtt_client = NULL; static u8_t mqtt_connected = 1; static u8_t check_mqtt_connected; check_mqtt_connected = mqtt_client_is_connected(saved_mqtt_client); if (check_mqtt_connected == 0) { mqtt_client_free(saved_mqtt_client);

[lwip-users] lwip on pico_w

2023-05-04 Thread Edward Vidal
Hello All,Posted the following on the raspberry pi forum. https://forums.raspberrypi.com/viewtopic.php?p=2104485#p2104485 Edward Vidal Jr. e-mail devel...@sbcglobal.net 915-595-1613___ lwip-users mailing list lwip-users@nongnu.org

[lwip-users] lwip on pico_w

2023-05-02 Thread Edward Vidal
Hello all, Adam Baron wrote " I'm just a user, but I believe the core locking has to be done on the port level.  I did put it there in my case. Then assertion of is core locked will tell you exactly what MQTT client functions need core to be locked." Do you have examples of what you are

Re: [lwip-users] lwip on pico_w

2023-05-02 Thread Adam Baron
heers, > > Christoph > > > > *From:* lwip-users-bounces+christoph=winterstiger...@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 > > > >

Re: [lwip-users] lwip on pico_w

2023-04-30 Thread Christoph M. Wintersteiger
, 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

[lwip-users] lwip on pico_w

2023-04-29 Thread Edward Vidal
Hello AllThe 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

[lwip-users] lwip on pico_w

2023-04-28 Thread Edward Vidal
Hello AllMy code is found at https://github.com/develone/pico_w-mqtt.git in the dev branch. I have tried to document my build found at https://github.com/develone/pico_w-mqtt/blob/dev/doc/pico_w-debug.pdf I use RPi4 to build 6 remotes (remote1, remote2, remote3, remote4, remote5 and remote6). 

[lwip-users] lwip on pico_w

2023-04-27 Thread Edward Vidal
Hi Christoph Chrrisoph wrote "Yes, I’m using lwIP on Picos as well. In my case, the MQTT client was a bit of a pain and kept throwing me into random panics too. The problem is that it doesn’t take the state lock. Basically, all calls to mqtt_* functions have to be guarded by

Re: [lwip-users] lwip on pico_w

2023-04-26 Thread Christoph M. Wintersteiger
() / cyw43_arch_lwip_end(). Once I did that, everything became quite stable for me. Cheers, Christoph From: lwip-users-bounces+christoph=winterstiger...@nongnu.org On Behalf Of Edward Vidal Sent: Tuesday, April 25, 2023 11:08 PM To: lwip-users@nongnu.org Subject: [lwip-users] lwip on pico_w

[lwip-users] lwip on pico_w

2023-04-25 Thread Edward Vidal
Hello All:I have a pico_w running mqtt iperf tcp sever and ntp. I runs ok for several hours then I get panic*** which appears to be coming from pico-sdk runtime.c?Is any using lwip with pico_w?Thanks in advance. Edward Vidal Jr. e-mail devel...@sbcglobal.net