Replies: 3 comments 2 replies
-
Have you tried doing a clean build, completely removing the directory "ports/esp32/build-ESP32_GENERIC_S3"? |
Beta Was this translation helpful? Give feedback.
2 replies
-
I discovered that additional frozen modules do not end up in the
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Suppose your project has these files: $ ls
logging.py manifest.py then your manifest.py should have these lines in it: $ cat manifest.py
include("$(PORT_DIR)/boards/manifest.py")
freeze("./", "logging.py") |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I am trying to freeze some bytecode into a firmware for the ESP32-S3. However, the bytecode seems not to end up in the firmware.
What I have tried:
The manifest.py looks like this:
When I flash the resulting
micropython.bin
onto the ESP, the logging library cannot be used usingimport logging
on the REPL. Also, when I search for strings used by the logging library inside the firmware binary, e.g. "CRITICAL", there are no results.The
ports/esp32/build-ESP32_GENERIC_S3/frozen_content.c
file seems to contain the logging library, and it also ends up insideports/esp32/build-ESP32_GENERIC_S3/frozen_mpy/logging.mpy
.It seems as if frozen_content.c is not part of the firmware binary.
Does anyone have an idea how to resolve the issue so that frozen bytecode gets included in the firmware binary?
My environment:
Beta Was this translation helpful? Give feedback.
All reactions