Sergio Gasquez Arcos
Sergio Gasquez Arcos
It shouldn't be an issue since there is a new patch release `1.16.3` but just created a PR updating the dep
Is your port listed if you use `--list-all-ports` flag?
By the way, I dont have any issues recognizing a `ESP32-S3-DevKitC-1 v1.0` connected via USB Serial JTAG port. ``` $ espflash -V espflash 3.1.0 $ espflash board-info [2024-06-25T09:58:21Z INFO ]...
Have you tried with other flashing tools like `esptool`?
> The same error occurred in my environment. I was able to compile successfully by replacing LLVM17 files with LLVM16 files in `.rustup\toolchains\esp\xtensa-esp32-elf-clang\esp-clang` directory. Out of curiosity, what happens if...
Thanks for the detailed information, at the moment I don't have a Windows environment to reproduce the error and Im not sure what we can do from the `espup` side...
@pai2shub can you try with latest version of espup (`0.15.1`)?
Why you want to install that LLVM version? `espup` now installs LLVM 19. LLVM 16 was used before Rust 1.81.0
> Perhaps it is due to some special issues with LLVM in windows Im not sure Im following your reply, Windows shouldn't be any different regarding LLVM versions
Can you try using the latest version (of the toolchain and of espup): ``` rustup update cargo install espup --locked espup install ```