It is not non-W, as far as I can tell, it was some kind of a nightly build or something, because it does support WIFI. It is currently deployed and works on pico Ws. The problem is still there but I have solved it by soft resetting if it occurs and that way initiating the connection early on in the program seems to be able to grab a hold of the needed memory. Unfortunately though, almost any further additions to the program make this not the case anymore and render it completely unable to connect, basically soft resetting stops helping. That's why I'm trying to figure out if it is possible to reserve the memory somehow, because as I said, there is reported more than 100kb of free memory so I'm far from hitting the limits, I just need to be able to reserve a chunk for my socket connection to succeed..So what is the situation; you have Pico (non-W) code which works and is deployed, you are trying to adapt that for use on a W, you have code for W which works but some recent change has made it stop working, or something else ?I'm stuck with using that because there are several hundreds of devices already in use in many different locations and will be quite a hurdle to update the firmware of as the hardware does not allow for that to happen over the air.
Basically, how did it go from working to not working ?
Statistics: Posted by pico_nub_qq — Mon Jan 13, 2025 11:13 pm