MicroPython Forum (Archive)

The PIC32MZ EF Curoisity board seems to be a great platform to port MicroPython, not only becuase of the powerful MCU but the connectivity of the board, specially the two mikroelektronika click sockets. For details see http://ww1.microchip.com/downloads/en/DeviceDoc/70005282A.pdf I'm planning to gra...

Strange enough, after disconnecting power for few hours it works again.

Well, after updating LoPy to fw 0.9.1.b1 today it is crashing in 10 seconds after reset/boot without running any user program, just the stock boot.py It means can't connect to it via WiFi anymore.

Previous release was able to blink LED for 3 days.

idimitrakopoulos wrote:
Can be configured for any microcontroller (currently supported NodeMCU)

Do you mean any architecture, like PIC24, PIC32 or AVR?

Updated LoPy to 0.9.1.b1 firmware released today. Now free RAM is only 71152 bytes Also, every execution of gc.mem_free() is decresing it by 64 bytes

Reported the issue at the Pycom forum, Daniel confirmed the bug.

Now I remember, several month ago there was an issue opened at GitHub about a similar issue if I'm right. It looks the same here.

kfricke wrote:The LoPy firmware does only print a commit hash suffix but no MicroPython release number. So only Pycom knows which MicroPython release we do use there.

returns a tuple with release, version and other parameters. On my board release='0.9.0b' whatever it means.

Just started to play with LoPy and have a problem explained below. It is not LoPy specific but related to MicroPython I guess, it is why asking here. machine.freq()[0] / 1000 / 1000 returns 80.00003 which is OK But machine.freq()[0] / 1000000 returns 8.181962e-07 which doesn't look the right result ...

On a LoPy v1.0 board with stock firmware