Lopy4 Guru meditation error

[robert-hh]

@bjsi9 Duplicating the dupterm code in boot.py does not hurt, at least in my test with a FiPy and a WiPy.

[bjsi9]

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]

New update:
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.

[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?

[bjsi9]

@robert-hh Hi, yes its very strange. I have also some Sipy's for testing, never had any problems. But after upgrade they chrashes all the time, even when downgrading and flash-reset.

• The device starts up, and waits in the prompt with: >>>>
  After som seconds, it chrashes.
• I have two expansionsboard, and tested with different USB ports also. Its the same cable i've used since i started working with pycom device the past year.

Remember: the safe boot works

[robert-hh]

@bjsi9 Looking at the code, this is hard to understand:
With safeboot, only _boot.py is executed.
with normal boot, _boot.py, boot.py, _main.py and main.py are run (in that order). That is mostly th whole difference. This is the section in the file mptask.c, which I'm talking about (line 282 ff):

    if (!safeboot) {
        // run boot.py
        int ret = pyexec_file("boot.py");
        if (ret & PYEXEC_FORCED_EXIT) {
            goto soft_reset_exit;
        }
        if (!ret) {
            // flash the system led
            mperror_signal_error();
        }
    }

    if (!safeboot) {
        // execute the frozen main first
        pyexec_frozen_module("_main.py");

        // run the main script from the current directory.
        if (pyexec_mode_kind == PYEXEC_MODE_FRIENDLY_REPL) {
            const char *main_py;
            if (MP_STATE_PORT(machine_config_main) == MP_OBJ_NULL) {
                main_py = "main.py";
            } else {
                main_py = mp_obj_str_get_str(MP_STATE_PORT(machine_config_main));
            }
            int ret = pyexec_file(main_py);
            if (ret & PYEXEC_FORCED_EXIT) {
                goto soft_reset_exit;
            }
            if (!ret) {
                // flash the system led
                mperror_signal_error();
            }
        }
    }

[bjsi9]

@robert-hh Okay, maybe _boot.py or _main.py is corrupted? What could i do about that, any suggestions? Thanks

[robert-hh]

@bjsi9 _boot.py should be OK, because that is executed always. _main.py is inside the frozen bytecode and comes as part of the firmware image. I have my doubts whether that is wrong.
Did you meanwhile try another (short) cable? Cables and especially connectors can wear.

[bjsi9]

@robert-hh Just tried another cable, no luck. Same chrashes, after erase file system and firmware update (done with the updater tool)
I know its a long shot, but i'm gonna try older version of the updater tool now.

[bjsi9]

No luck using updater tool 1.13.1.b5

[bjsi9]

@robert-hh Hi, quick question. sys, lib and cert folders are all empty when i view them in filezilla FTP (Show hidden files are on). Should these folders be empty?

[robert-hh]

@bjsi9 Yes. They can be empty and are empty on fresh installe devices. lib is used for storing python code of library style. It is also named in uos.path. But that is convention.

[bjsi9]

@jmarcelino I've sent my code to you. Do you think its possible that the code, compined with the firmware update, burned the circuit? :) I'm running out of ideas.

[bjsi9]

I just deleted the boot.py and main.py on one of my LoPy4's via the FTP. When i start the device same chrash every other second.

[robert-hh]

@bjsi9 Can you try to erase the flash completely using esptool.py, subcommand erase_flash, and specifying the flash size. That will delete EVERYTHING including configuration and registration options. That will be restored with a pycom update, you can run afterwards.
If you have the firmware creating environment set up, you can also run the command:
make erase
As always, you need to tie P2 to GND to activate the ROM bootloader.

[bjsi9]

@robert-hh I found the esptool.py on this link, and copied to a file on my desktop: https://github.com/pycom/pycom-micropython-sigfox/blob/master/esp32/tools/esptool.py

I need som guidelines on how to proceed. I think this file goes to the lib folder, and i have to command it from the pymakr.
If this is correct, what is the exact command to execute til esptool? Thank you

[robert-hh]

@bjsi9 Esptool.py is executed on your PC from the command line (cmd on Windows, terminal on Linux/Max). It is also used internally by the pycom update tool. Just call :

python3 esptool.py --help

to erase, run

python3 esptool.py -p <portname> -c esp32 erase_flash

Edit: Esptool is also here: https://github.com/espressif/esptool

[jmarcelino]

@bjsi9
Could you a test please, go into safe boot so you have control and do

import pycom
pycom.wifi_on_boot(False)

To disable WiFi hostAP on boot until activated again.

Then let me know if stops crashing.

Thanks!

[bjsi9]

@jmarcelino Success! My two LoPy4's with firmware 1.17.3.b1 and my own code running, no chrashes so far. Haven't tested for more than 10 minutes, but looks fine. Will test SiPy's tomorrow.
THANK YOU

Update: Still running 1+ hours. Great succes

[robert-hh]

@jmarcelino Good to know that WiFi on boot is also disabled on safe boot. Or am I wrong?