Hello,
I have some problems with two different applications running on Raspberry Pi Pico. Both of them lockup somewhere in the lwIP code after a while and the watchdog then makes a reset.
One of them is running on a Pico-W and uses WiFi. It is basically the NTP example plus some code around it to show the time.
The other implements Modbus-TCP using the raw API. It uses a Pico and an ENC28J60. The driver for the network chip is the following one:
https://git.sr.ht/~krystianch/pico-enc28j60/tree/master
I've been using about 1.5 year old version of Pico-SDK and lwIP. A friend tried pretty much latest code and said it is much worse. His version locks up in less than a minute while mine runs quite a bit longer.
In a very very old email i read that it could be a double free or accessing freed buffers of lwIP. Is there a HOWTO or some documentation how to debug such a situation?
Thank you,
- Martin
I have some problems with two different applications running on Raspberry Pi Pico. Both of them lockup somewhere in the lwIP code after a while and the watchdog then makes a reset.
One of them is running on a Pico-W and uses WiFi. It is basically the NTP example plus some code around it to show the time.
The other implements Modbus-TCP using the raw API. It uses a Pico and an ENC28J60. The driver for the network chip is the following one:
https://git.sr.ht/~krystianch/pico-enc28j60/tree/master
I've been using about 1.5 year old version of Pico-SDK and lwIP. A friend tried pretty much latest code and said it is much worse. His version locks up in less than a minute while mine runs quite a bit longer.
In a very very old email i read that it could be a double free or accessing freed buffers of lwIP. Is there a HOWTO or some documentation how to debug such a situation?
Thank you,
- Martin
Statistics: Posted by bw-a4ku — Fri Dec 27, 2024 12:42 pm — Replies 1 — Views 30