simbit18 commented on PR #18661: URL: https://github.com/apache/nuttx/pull/18661#issuecomment-4176584676
> I am also not able to reproduce, could you test locally? Maybe something on CI is different, still looking into it. > > **Update:** Seems this is caused by an old esptool version that is running on CI. I downgraded my own and got the same issue. Will open a PR updating the CI esptool version and that should fix the problem. Hi @fdcavalcanti, I’ve tested the CMake build on Windows Native and it works fine! I used the latest version of esptool, v5.2.0 https://github.com/espressif/esptool/releases So do we need to update the version in the NuttX Docker image? Which version did you use for your tests? Later, if I can, I’ll run a test on a Waveshare ESP32-C3-Zero board that I have. <details> <summary>Log esp32c6-devkitc:nsh</summary> ``` D:\nuttxtmp\nuttx>cmake -B build -DBOARD_CONFIG=esp32c6-devkitc:nsh -DNXTMPDIR=on -GNinja -- nuttx_add_subdirectory: Skipping cxx-oot-build -- Initializing NuttX Loaded configuration 'D:/nuttxtmp/nuttx/build/.config.compressed' Minimal configuration saved to 'D:/nuttxtmp/nuttx/build/defconfig.tmp' -- ENV{PROCESSOR_ARCHITECTURE} = AMD64 Select HOST_WINDOWS=y Select WINDOWS_NATIVE=y -- CMake: 3.31.5 -- Ninja: 1.12.1 -- Board: esp32c6-devkitc -- Config: nsh -- Appdir: D:/nuttxtmp/apps -- Building for: Ninja -- The C compiler identification is GNU 14.2.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: C:/mingw/mingw64/bin/gcc.exe - skipped -- Detecting C compile features -- Detecting C compile features - done -- NuttX Host Tools -- CMake C compiler: GNU -- CMake system name: Windows -- CMake host system processor: AMD64 TOOLS_DIR path is "D:/nuttxtmp/nuttx" HOST = WINDOWS NATIVE -- Configuring done (0.9s) -- Generating done (0.0s) -- Build files have been written to: D:/nuttxtmp/nuttx/build/bin_host -- The C compiler identification is GNU 14.2.0 -- The CXX compiler identification is GNU 14.2.0 -- The ASM compiler identification is GNU -- Found assembler: D:/nx20250410/tools/riscv-none-elf-gcc/bin/riscv-none-elf-gcc.exe -- Cloning Espressif HAL for 3rd Party Platforms -- Populating esp_hal_3rdparty -- Configuring done (0.1s) -- Generating done (0.1s) -- Build files have been written to: D:/nuttxtmp/nuttx/build/_deps/esp_hal_3rdparty-subbuild [1/9] Creating directories for 'esp_hal_3rdparty-populate' [1/9] Performing download step (git clone) for 'esp_hal_3rdparty-populate' Cloning into 'esp-hal-3rdparty'... HEAD is now at 41b8c5f1206 Add ULP lpcore support esp32p4 [2/9] Performing update step for 'esp_hal_3rdparty-populate' -- Already at requested ref: 41b8c5f12063f6cce5796ce50b5eb4bd2ceeeb12 [3/9] No patch step for 'esp_hal_3rdparty-populate' [5/9] No configure step for 'esp_hal_3rdparty-populate' [6/9] No build step for 'esp_hal_3rdparty-populate' [7/9] No install step for 'esp_hal_3rdparty-populate' [8/9] No test step for 'esp_hal_3rdparty-populate' [9/9] Completed 'esp_hal_3rdparty-populate' HEAD is now at 582ff4820 feat(drivers): ESP-HMAC opaque driver -- Copying from D:/nuttxtmp/nxtmpdir/esp-hal-3rdparty to D:/nuttxtmp/nuttx/build/arch/risc-v/src/common/espressif/esp-hal-3rdparty -- nuttx_add_subdirectory: Skipping cxx-oot-build -- Configuring done (119.1s) -- Generating done (5.0s) -- Build files have been written to: D:/nuttxtmp/nuttx/build D:\nuttxtmp\nuttx>cmake --build build [1358/1358] Running utility command for nuttx_post_build -- Generate NuttX image (esptool elf2image) esptool v5.2.0 Creating ESP32-C6 image... Image has only RAM segments visible. ROM segments are hidden and SHA256 digest is not appended. Note: Inserting 63628 bytes padding between .flash.text and .flash.rodata Merged 1 ELF section. Successfully created ESP32-C6 image. -- Generated: nuttx.bin </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
