can not build esp32p4 fireware

[kyozhou]

Describe the bug
when i build esp32p4 fireware using this comman: python3 make.py esp32 BOARD=ESP32_GENERIC_P4, it show error "fatal error: esp32/ulp.h: No such file or directory"

Expected behavior
release a fireware.bin for esp32p4

Images

If you are having a problem compiling paste the build output below. (NO SCREENSHOTS)

fireware/lvgl_micropython/lib/micropython/ports/esp32/esp32_ulp.c:32:10: fatal error: esp32/ulp.h: No such file or directory
32 | #include "esp32/ulp.h"
|          ^~~~~~~~~~~~~
compilation terminated.

If your problem is running the binding please past the code you are using below.*
I need to see ALL of the setup code exactly as it is being ran.

python3 make.py esp32 BOARD=ESP32_GENERIC_P4

**Exact make and model number of the MCU that you are compiling for or the firmware is running on. **

• Make:
• Model:
  I do not known, but the MCU revision is v1.0

For ESP32 MCU's The PSRAM and FLASH SPI type, quad SPI or octal SPI.

• PSRAM: quad 32MB
• FLASH: quad 16MB

I need to know the OS and OS version of the machine that compiled the binary. If using a VM then I need to know the OS and OS version the VM is running. (WSL == VM)

• OS: MacOS

Build Command

python3 make.py esp32 BOARD=ESP32_GENERIC_P4

[kyozhou]

micropython has released new version 1.27.0 that support esp32p4, is it possible to add the new version to lvgl_micropython to solve this problem?

[kdschlosser]

It's done. give it a test and see if it works.

[kyozhou]

It's done. give it a test and see if it works.

Thanks for your working. but it show the same error.

I find the build const CONFIG_SOC_ULP_SUPPORTED=y, but another place it is CONFIG_SOC_ULP_SUPPORTED=n (in lib/micropython/ports/esp32/boards/sdkconfig.p4). and esp32p4 isn't support ulp.
so I think it's may be some config missing or error in builder/esp32.py

[kdschlosser]

I find the build const CONFIG_SOC_ULP_SUPPORTED=y

where are you seeing this???

There are people that are currently compiling for the P4 and not having any issue. It has to be something in your system or something that you are specifically doing that is causing the issue. We just have to track down what it is that is causing the problem.