@robert-hh This is not working well. During make skdconfig.h is replaced by make GENCONFIG (that is using wifi/scan/sdkconfig). The best is to modify that config. However moving the freq from 160 to 80 -> it saves only 7mA ... I expected to be more. So LoPY+shield with Wifi disable is consuming 35mA.

@dhblumenfeld1989 This cannot be the full script. At least a two lines are missing upfront, like: from network import WLAN wlan = WLAN(mode=WLAN.STA) And as a side note: The flash size you get with uos.getfree() is not relevant for memory errors. These are caused by RAM shortage. The size of free RAM is told by gc.mem_free(). And for all people trying to help it is useful to know the firmware version, which can be obtained by uos.uname().

@robert-hh Thanks I already know these aspects!

@robert-hh Thanks! I tried this and it works great! I tried also the new update with the freezing the _main.py which also solves the problem.

@robert-hh Thanks! Yeah I can do some stuff in the handler, but as far as I can understand it is recommended to keep the handler short and effective. In this case I would like to transmit (LoRaWAN), receive some data etc. Anyway - thanks for the help - I'll figure something out. :)

@colateral There aren't default pins for UART2 as far as know, just choose them at initialisation with pins=(TXD, RXD, RTS, CTS) option.

@yahia another option (if you have WiFi enabled) is just to copy the generated appimg.bin into /flash/sys using FTP.

See the following post on how to manually flash the firmware: https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users

@jmarcelino said in [SOLVED] Having issues build firmware from soure: https://dl.espressif.com/dl/xtensa-esp32-elf-linux32-1.22.0-61-gab8375a-5.2.0.tar.gz once again, @jmarcelino saved my day, thanks

@jmarcelino Thanks! Good to know (and that only leaves one--brown-out reset, which isn't all that important).

You don't need ulp for pin wakeup. You can do much less than 150ua if you sleep inside ulp program.

@robert-hh Thanks, You helped me a lot!

@jmarcelino Because we want preserve the Pycom WiPy firmware ad edit it with some frozen files and custom API C (like SSL and BT that have some problems).

@robert-hh Hi, thank you for the answer, I think I missed something during the procedure because I tried again from scratch and it works perfectly. I think I forgot an environment variable as you propose.

@Immondizia The current repo is pycom-micropython-sigfox for all 3 boards

@Colateral I used the same circuitry (10 pF capacitors) and a crystal with 12.5 pF load capacitance. The model is called MS1V-T1K from Micro Crystal Switzerland. It was the one easy to get from a local store. The 12.5 pF load capacitor would lead to ~22pF C1 C2 capacitors. Since I have a set-up with the LOPY4 development board + a carrier board +..., there is already a lot of unknown stray capacitance. Therefore the 10 pF work. I did however not run a test over a day yet to see the clock drift. I just measured the frequency of the crystal while running. But I can do this time drift test in the next days.

@karolalexander Have a look at the code for Lua ESP32 + LoRaWAN (Whitecat project). Should run on the LoPy and might be more to your liking: https://github.com/whitecatboard/Lua-RTOS-ESP32 In particular they ported the LMIC library for LoRaWAN which is older and less featured than Semtech's but simpler to understand (no HALs) so you might be able to borrow some of the code from there.

@Colateral Did you build mpy-cross? It is the Python byte code compiler needed in the build process. to do that, do to micopython/mpy-cross and issue: make mpy-cross then got back to microypthon/esp32 and retry the build. If it fails at the step, when loading into the device, the access rights for the port may be wrong. You can then either run under sudo, or put your account into the dialout group with: sudo addgroup <yourname> dialout