My new GPY keeps core dumping

[cblims]

Hi, Just got a new GPY on my desk, and I've successfully uploaded code to change the led color in an infinite loop. But suddenly my device just reboots(core dumps). Why does this happen? It keeps doing it all the time (once every 5 seconds). I'm trying to upload new code, but it fails every now and then. Also tried to upgrade firmware, and that works without failure, but after boot the same core dump happens.

btw, does firmware update reset everything to factory default? Is everything erased?

>>> Guru Meditation Error: Core  0 panic'ed (InstrFetchProhibited)
. Exception was unhandled.
Register dump:
PC      : 0x00000000  PS      : 0x00060930  A0      : 0x8010eff5  A1      : 0x3ffbd650
A2      : 0x00000000  A3      : 0x00000037  A4      : 0xffffffaa  A5      : 0x3fbc1e24
A6      : 0x00000008  A7      : 0x00000000  A8      : 0x8011a308  A9      : 0x3ffbd640
A10     : 0x3fbc1e40  A11     : 0x00000037  A12     : 0xffffffaa  A13     : 0x3ffbd6e4
A14     : 0x77778dee  A15     : 0x77778dee  SAR     : 0x00000010  EXCCAUSE: 0x00000014
EXCVADDR: 0x00000000  LBEG    : 0x40099a9d  LEND    : 0x40099ad1  LCOUNT  : 0xffffffff

Backtrace: 0x00000000:0x3ffbd650 0x4010eff2:0x3ffbd670 0x4010ffff:0x3ffbd740 0x401265f1:0x3ffbd760 0x40128153:0x3ffbd7b0

[cmisztur]

@cblims said in My new GPY keeps core dumping:

InstrFetchProhibited

can you post the code?

[cblims]

Any code make the chip go haywire, even after flashing firmware with erase option makes it reboot without any code:

import pycom
import time
​
pycom.heartbeat(False)
for cycles in range(10): # stop after 10 cycles
    pycom.rgbled(0x007f00) # green
    time.sleep(5)
    pycom.rgbled(0x7f7f00) # yellow
    time.sleep(1.5)
    pycom.rgbled(0x7f0000) # red
    time.sleep(4)

[leifarne]

Has there been any resolution to this? I have the same problem with all my 4 Pycom circuits - I have both GPy and WiPy circuits and Expansion board 3.0. It happens even if there is no program loaded. It happens with or without the Expansion board. If I cover the circuit in my hand, it does not happen. If I remove my hand, it starts core dumping again. So it has to be an electrical problem of some kind.

Any idea why, and how to fix it?

[aarpi3]

I had/have the same issue with my new Lopy4 (1.18.2.r7) board also.
I was added "pycom.wifi_on_boot(False)" in the blink example (before hartbeat) and was able to upload it in one of the reboots. I just hit upload as soon as I saw >>. Had to try several times!

[andreas]

Dear @cblims, @leifarne and @aarpi3,

if you feel lucky, you might want to try one of our custom builds just released at [1,2,3]. More background about this is available through [4].

Please be aware that you will have to erase your device completely before flashing in order to keep things straight. You will find respective references to this on the forum. Hint: Use pycom-fwtool-cli --port /dev/ttyUSB0 erase_all, see also [5].

With kind regards,
Andreas.

[1] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/WiPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz
[2] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/GPy-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz
[3] https://packages.hiveeyes.org/hiveeyes/foss/pycom/vanilla/LoPy4-1.20.1.r1-0.6.0-vanilla-dragonfly.tar.gz
[4] https://community.hiveeyes.org/t/investigating-random-core-panics-on-pycom-esp32-devices/2480
[5] https://community.hiveeyes.org/t/installing-the-recent-pycom-firmware-1-20-1-r1-requires-erasing-the-flash-memory-completely/2688