Lopy continues to restart and then stops !!!

[james]

@robert-hh in what way to update the loader ???
Regards

[robert-hh]

@james I assumed you used the pycom upgrader from here:
https://pycom.io/downloads/
In that case, delete the one already on your computer and reinstall it.
If you used the developement environment, just update from github and redo a make and make flash. And be sure to use a LoPy image for the L01 module.
B.t.w: There is a new firmware version out there.

[james]

@robert-hh
I downloaded the last and tried but nothing,
I am preparing the development environment now, so far I did not need it for what I'm doing.

But where do I find the firmware for the LY01 version of lopy ??
So far i just launched the update, and downgrade I unsure the versions for lopy 868 but not l01, maybe the problem might be this.

Thank you
Regards

[james]

@robert-hh
I've updated the latest version ...
it stays silent

Thank's
Regards

[robert-hh]

@james As far as I know, the difference between L01 and LoPy is the form factor and whether antenna and power regulator are on board. L01:
https://pycom.io/product/l01/
LoPy:
https://pycom.io/hardware/lopy-specs/
The frequency mode 868 or 915 us defined by the firmware image you load. The question I have is: How do you interface to you L01. Do you have a kind of adapter or

[james]

@robert-hh
I connected the L01 module equal to Lopy with a base later sent by pycom ..
their development base because I had a problem with lora then discovered it was a bug firmware.

A usb ftdi module is attached to the base.
in fact I do not know if unlike the LoPy no OEM lacks pullup qulche that can cause this ..
in real life until long ago I did not have problems ... everything worked pretty regularly ...

I attach you a photo:

the two jumper are related to the safeboot and the upgrades,
then I mounted a reset key that is in reality and is already on the module

I also have some mounted only with the necessary pins without any base but the same
(only power, antennas, and serial)

I also compiled everything from sources but the result is the same

excuse for my easy english...

Thank's
Regards

[robert-hh]

@james That setup looks good. It's. strange that version 1.6 works, but 1.7.9 or 1.8.0 not. So I'm out of my tips now. Maybe someone from Pycom could have another hint, especially about the stack dump values.

[james]

@robert-hh
I tried with 1.6.7.b1 but nothing, continue restart

Thanks a thousand though for your help :-)
Regards

[jmarcelino]

@james
For the L01 I think you need to build your own toolchain (the xtensa compiler and build chain) from a special branch

https://github.com/espressif/crosstool-NG/tree/xtensa-1.22.x-ext_ram_patch

Here's instructions how to build the toolchain: http://esp-idf.readthedocs.io/en/latest/get-started/linux-setup-scratch.html

Note: In order to get the psram version, in the instructions at the 'git clone' command, replace 'xtensa-1.22.x' with 'xtensa-1.22.x-ext_ram_patch"

This is because the L01 is not all like the LoPy, it has a 4MB RAM chip (hence the psRAM branch) and a new revision of the ESP32.

Once that's done you should be able to compile the firmware using this new buildchain

[james]

@jmarcelino
As soon as I can try to compile toolchains from the git you have reported and firmware and see what happens.
Thank you
Regards

[james]

@jmarcelino
I have recompiled with the branch ext_ram, after the flash the module remains in position as in the picture below and no longer signs of life.

do you have any idea about this !!!
Thank you

Regards

[james]

@jmarcelino , @robert-hh

After the flash is deleted and the refresh seems to work with the latest release ...
we hope well..

Thanks to everyone for help
Regards