MicroPython Forum (Archive)

I too was able to replicate this.

It took a while but I was able to setup the esp sdk toolchain required to build a firmware with the frozen bytecode. Once built everything ran fine with no memory issues.

It worked with the frozen files. Thanks for the help.

Thanks. I figured something like that was needed. I will look up how to build.

As an aside, the demo code for the writer.py (writer_demo.py) worked just fine on my esp32 (which of course has lots more memory).

I have the same issue. I don't think that there is enough memory on the ESP8266.

viewtopic.php?t=1747

The font file is quite big for me. ~18 K. while the available memory is only about 22-25 K. Maybe that is the reason that this module cannot run.

I do have an esp8266 somewhere in my box. Will look for it and see what happens.

Also realized that on the esp32 I'm using the Loboris micropython firmware. I will try on the regular micropython.

I don't have an ESP8266 but an ESP32. Here is my simple example. I copied over writer.py, arial_clock.py. You would need to modify the Pin numbers. from machine import Pin, I2C from ssd1306 import SSD1306_I2C WIDTH = const(128) HEIGHT = const (64) sda_pin = Pin(26) scl_pin = Pin(25) i2c = I2C(scl=sc...

I have used Peter Hinch's (@ pythoncoder) Writer and font_to_py tools.

https://github.com/peterhinch/micropyth ... er_demo.py

https://github.com/peterhinch/micropyth ... T_TO_PY.md

https://github.com/peterhinch/micropython-font-to-py

Can you do an I2C_bus.scan()? That should give you the address. I don't have the device but from reading the datasheet (https://www.st.com/resource/en/datasheet/vl53l0x.pdf), the device address is 0 1 0 1 0 0 1 followed by R/W bit. So it is 0x29 << 1 + 1/0 for read/write. Thus, 0x52 for write to and...

Mike,

This is excellent. Appreciate your github repository.