CORE DUMP - MODETH Lib
-
Hi there!
I'm having some problems regarding some sporadic Core Dump Errors.
Traceback log is something like that:
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled. Core 1 register dump: PC : 0x40096ca3 PS : 0x00060833 A0 : 0x80095afd A1 : 0x3ffd1c00 A2 : 0x3ffd1e68 A3 : 0x00060823 A4 : 0x3ffd1e4c A5 : 0x00000001 A6 : 0x000000fe A7 : 0x3fbc2fec A8 : 0x00000000 A9 : 0x3ffd1e68 A10 : 0x3ffd1e68 A11 : 0x0000abab A12 : 0x3ffd1e4c A13 : 0x00000001 A14 : 0x000000fe A15 : 0x00000000 SAR : 0x0000001e EXCCAUSE: 0x0000001c EXCVADDR: 0x00000004 LBEG : 0x400929b0 LEND : 0x400929de LCOUNT : 0x00000000
Backtrace gives to me the following result:
uxListRemove /home/peter/docs/pycom-esp-idf/components/freertos/list.c:218 xTaskRemoveFromEventList /home/peter/docs/pycom-esp-idf/components/freertos/tasks.c:3092 xQueueGenericSend /home/peter/docs/pycom-esp-idf/components/freertos/queue.c:767 sys_sem_signal /home/peter/docs/pycom-esp-idf/components/lwip/port/esp32/freertos/sys_arch.c:133 sys_arch_unprotect /home/peter/docs/pycom-esp-idf/components/lwip/port/esp32/freertos/sys_arch.c:483 do_memp_malloc_pool /home/peter/docs/pycom-esp-idf/components/lwip/lwip/src/core/memp.c:346 memp_malloc /home/peter/docs/pycom-esp-idf/components/lwip/lwip/src/core/memp.c:398 tcpip_inpkt /home/peter/docs/pycom-esp-idf/components/lwip/lwip/src/api/tcpip.c:207 tcpip_input /home/peter/docs/pycom-esp-idf/components/lwip/lwip/src/api/tcpip.c:248 ethernetif_input /home/peter/docs/pycom-esp-idf/components/lwip/port/esp32/netif/ethernetif.c:224 tcpip_adapter_eth_input /home/peter/docs/pycom-esp-idf/components/tcpip_adapter/tcpip_adapter_lwip.c:1096 process_rx /media/Project/esp32/mods/modeth.c:249
Please could you help me in finding out some causes about that?
I would appreciate that.
Thank you very much.Greetings,
Andrea
-
I also noticed that somethings different happens into TCP packets:
As you can see I received plenty good packets without any errors.
Suddenly I start receiving some "TCP Retransmission" or "DUP ACK".
The situation doesn't change in time when that happens. I mean that these "abnormal" packets will be received forever.It seems that the at final stage it brings to the stuck of the Pycom Module and the Core Dump or WDT time out.