Closed zachmoshe closed 1 year ago
v923z
commented
1 year ago What happens if you remove the artifacts, and start from scratch? It seems to me that the prepocessor doesn't reach the point, where ulab would make any difference. In other words, I believe, you would get the same error, if you left out ulab completely.
hamza-712
commented
1 year ago I was having the same problem. I used esp idf v4.4.3 and I was able to build firmware.
hamza-712
commented
1 year ago @v923z I need help too. I have built firmware for ESP-WROOM-32 but my ESP32 keeps resetting indefinitely. Is there a compiled binary available with latest micropython firmware?
I looked at the troubleshooting link as well. I changed CONFIG_ESPTOOLPY_FLASHMODE but it didn't work.
https://github.com/micropython/micropython/tree/master/ports/esp32#configurationtroubleshooting Configuration Troubleshooting Continuous reboots after programming: Ensure CONFIG_ESPTOOLPY_FLASHMODE is correct for your board (e.g. ESP-WROOM-32 should be DIO). Then perform a make clean, rebuild, redeploy.
zachmoshe
commented
1 year ago OK, it's a bit weird but I can confirm it works for me..
It didn't at first, then as Zoltan suggested I tried make clean and even re-cloning micropython from scratch. After a few tries I was able to compile both the GENERIC and the GENERIC_S3 boards. I'm not sure what exactly did the trick but here are the settings that work for me:
0acc73344 (this is currently origin/master). I only added 2 files in the ports/esp32 folder called makefile_ulab and makefile_ulab_s3 with the following content:
BOARD = GENERIC # GENERIC_S3 in the s3 file.
USER_C_MODULES = <PATH TO ULAB FOLDER>/code/micropython.cmakeinclude Makefile
* I have ulab at commit `8585407` (one before the latest, don't think it will make a difference). The only change I have there is in `code/ulab.h`: -#define ULAB_MAX_DIMS 2 +#define ULAB_MAX_DIMS 4
* My ESP-IDF is `v4.4`.
From the `micropython/ports/esp32` I can successfully run `make -f makefile_ulab_s3` now (for both files).
I also uploaded the result binaries to ESP32-S3 and it seems to work (was able to import numpy form the repl, didn't check further).
@hamza-712 - Hope this helps... thanks i have successfully built firmware I use idf.py command to build firmware instead of make and it worked.
v923z
commented
1 year ago @zachmoshe @hamza-712 If either of you could reproduce these results, it would be a worthwhile addition to https://github.com/v923z/micropython-builder.
zachmoshe
commented
1 year ago @v923z - I believe this can be closed as we both were able to build the firmware and it probably wasn't a ulab problem anyway ( I guess a WONT_FIX?)
v923z
commented
1 year ago You can definitely close it, but I still feel that others could profit from an automated build. Let me know if you're interested.
zachmoshe
commented
1 year ago sure, I'll take a look and submit a PR
I'm trying to compile
ulabinto MicroPython, following this page. I have an old ESP32 and a newer ESP32-S3 which I want to try.I've created two makefiles for
BOARD=GENERICandBOARD=GENERIC_S3. The first one works as expected, but when I try the S3 one I get this:I'm a bit clueless with C compilation errors. Looks like something is declared twice but not sure why this doesn't happen for the regular board type.. Any ideas?