Lopy4 Guru meditation error
robert-hh last edited by robert-hh
@bjsi9 That's strange. I have a Lopy here running since 5 weeks in a row as Lora nanogateway, and some Fipy's for testing, but they never crashed.
- When crashing, do your devices run code or are they just waiting in the REPL prompt?
- Do you always connect the devices in the same way - same expansion board, same cable, same USB port?
I dont care about my code anymore, i just want the LoPy4 to work as from factory.
I have tried with a new expansionboard, LoPy4 with erased filesystem and downgrading to 1.15.0.b1.
Still chrash chrash chrash every 2 seconds.
No luck after manually flash-reset, or FTP upload standard boot and main.
Safe boot dosent chrash.
Hi @robert-hh , still no luck.
The LoPy4 boots, and are ready for commands. But after some seconds it chrashes with the Guru error. Then it boots again, and chrashes again.. and so on.
Very sad story for my 2 Sipy's and 2 LoPy4's. But i'm sure we will find a solution at some point. Any suggestions are welcome :)
@bjsi9 Looking into the sources, this is the code in the embedded _boot.py, which is executed on any boot, even the safe boot:
# _boot.py -- always run on boot-up, even during safe boot import os from machine import UART os.dupterm(UART(0, 115200))
So this code is not required in boot.py, and you can drop it. Do the file copying with ftp. The youre sure about what you get.
I just updated my Sipy (which have been working for half year). And now i have the exsact same problem with Guru error.
(i dont know which firmware was on before the upgrade, i will try to find out)
Update: its 1.15.0.b1
@bjsi9 main.py looks definitely uncritical. I'm a little bit thinking about boot.py, because setting REPL to UART0 is the default. I have to check this evening back home what I have on my devices. But you could try to comment that out. During safe boot you will still have access to the file system via ftp. I would not use Pymakr for that basic debug stuff. It has its own complications.
@robert-hh Thanks, good point.
Here is fresh pictures of what is in the boot and main, that still gives me error:
@robert-hh Hi, no error if i safe boot!
But when i remove the jumper, the errors comes back.
Also after reset.
@bjsi9 Does that also happen with the safe boot (P12 at 3.3v during reset)?
@jmarcelino I managed to sneak in the
But still no luck. see pictures:
So this is what i know so far:
- New Lopy4 (from package) updated to latest stable firmware connected to Pymakr. No error.
- Upload my code, the guru meditation error comes
- Upload and overwrite the main.py back to standard (empty). Reboot. Still dumb error.
@jmarcelino Thank you for response.
I have "erased the flash file system" via the Updater tool. I cannot do it manually in the line command, because the error keeps re-displaying.
It did not help to erase the filesystem. This is what the code does before the chrash:
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:1 load:0x3fff8028,len:8 load:0x3fff8030,len:1728 load:0x4009fa00,len:0 load:0x4009fa00,len:14584 entry 0x400a059c MicroPython v1.8.6-849-83e2f7f on 2018-03-19; LoPy4 with ESP32 Type "help()" for more information. >>> Guru Meditation Error: Core 0 panic'ed (InstrFetchProhibited) . Exception was unhandled. Register dump:```
jmarcelino last edited by
Does the code do anything visible before this crash?
Have you tried erasing the erasing the filesystem with
os.mkfs('/flash')and re-uploading your code?