MicroPython Forum (Archive)

Is it possible to safely enable 2 core in esp32 in the latest version 1.14? The shutdown was due to a problem with ble init, in esp-idf 4.2 I see that it already works, can I turn it on without fear?

How to force intentional damage to partition or fs corrupt? I need for tests. Thanks.

Ok, there was a problem here, fat works much faster. I haven't noticed that as of 1.13, littlefs is created by default. Thank you for your answer.

Everything is clear, thank you for your answer and help!

I noticed that the more files there are (even without imports) in the filesystem, the slower it works

When I have frozen code in firmware, in main.py file on / flash I will do an import, import from frozen code, how to "force" to load from / first, and when it is not there with firmware? Thanks.

How to fix this problem in v.1.12? Is the only solution to going to core 0? (sometimes I have a crash panic) I noticed that in the latest 1.14 for esp32 there is "MicroPython and NimBLE tasks to core 0" How can you do that only when bluetooth is on?

in version 1.13 or 1.14 it is just as slower when importing the same libraries. nobody suggested that it was faster on 1.12? v.1.12: >>> time.ticks_ms();import uasyncio;time.ticks_ms() 2008736 2008754 sys.path.append('libs') >>> time.ticks_ms();from system_devices import *;time.ticks_ms() 2068585 20...

Thanks. I have one more question. If we have the same files, eg "ctrl.py" in the firmware (frozen) and in the filesystem, is it possible to force it to use ctrl.py with the firmware?

My project is based on communication between the phone and ESP32 (miropython) via bluetooth. I have all my software compiled in frozen code on micropython firmware. I plan to implement updating files on esp32 from the phone via BLE. The basic question is whether to update individual files or all at ...