MicroPython
IDF 5.2 and ESP32C3 - build succeeds but does not successfully start micropython #14530
Replies: 3 comments 1 reply
-
|
I have manage to build esp32-c3 and run it on the "LUATOS.COM/T/ESP32C3" $ tio /dev/ttyACM0
[tio 19:05:36] tio v1.32
[tio 19:05:36] Press ctrl-t q to quit
[tio 19:05:36] Connected
>>>
>>> dir()
['bdev', 'gc', '__name__', 'vfs']
>>> import os
>>> os.listdir()
['boot.py']
>>>
>>> import sys
>>> sys.implementation
(name='micropython', version=(1, 23, 0, 'preview'), _machine='ESP32-C3 (KAKI5-NTNG) with ESP32-C3', _mpy=774, _v2=True)
You can have a look at the configuration files and the build script at: https://github.com/shariltumin/others-micropython/tree/master/esp32-c3-luatos-blueboard It will not be difficult for you to modify these files to suit your board. You will need to change the IDF_PATH in the build script, mpb_esp32_kaki5.sh, to point to your esp-idf directory. You will need to modify the contents of boards/ESP32_C3_KAKI5/manifest.py to suit your specific frozen modules. Please note that this build disables GIL (see, mpconfigport.h-KAKI5) and is not fully tested. It is not guaranteed to work. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I will be able to check it out Tuesday. This looks like it will help me understand better. |
Beta Was this translation helpful? Give feedback.
-
|
It took a while for me to get back to this. I removed the manifest completely from your board definition, and used your script replacing the IDF paths with mine. Compiling the latest (as of 20 May) got the same link error compiling with IDF 5.0.4, 5.1, and 5.2: (5.0.4 example)
I must be missing something in my configuration I think. |
Beta Was this translation helpful? Give feedback.
-
|
This is strange. I just downloaded the latest MP and compiled it with IDF-5.2.1 Did you run This is what I usually do when downloading a new esp-idf:
Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
I am working with a SEEED XIAO ESP32C3. My builds using 5.0.4 work fine using either my cuatom board config or the ESP32_GENERIC_C3. For fun I tried IDF v5.2. The build succeeds but board fails to start micropython and has a repeating error/boot sequence.
Here are my steps:
I initially was trying to get the v5.2 build to succeed when I had several external modules (ulab, display driver) but the v5.2 build failed because it was now large enough to overrun the factory partition as generically defined. I increased the factory partition size and reduced the vfs size. The build now works, but run fails as above. So I tried the reduced default config.
Am I missing something in the configuration for C3 board?
(v5.0.4 and v5.1 build okay with defaults)
Beta Was this translation helpful? Give feedback.
All reactions