search

esp-rs / espup

Tool for installing and maintaining Espressif Rust ecosystem.
Apache License 2.0
224 stars 23 forks source link

`xtensa-esp32-none-elf` not installed with espup #447

Closed nbaraz closed 1 week ago

nbaraz commented 1 week ago

After runnint espup install on Windows 10, when I run rustc +esp --print target-list I only get the following xtensa targets:

xtensa-esp32-espidf
xtensa-esp32s2-espidf
xtensa-esp32s3-espidf
xtensa-esp32s3-none-elf

(xtensa-esp32-none-elf is missing)

SergioGasquez commented 1 week ago

That's very strange, as no_std version of s3 is installed. Have you tried building a no_std project for ESP32 and see if you get any error? Also, might be worth to try rustc +esp --print target-list | grep "xtensa"

nbaraz commented 1 week ago

I don't have grep installed, and find was giving me issues, but I'll install it and try once I get home. I'm fairly certain it's not in the list though.

Is there an extra verbose espup flag/patch I can apply to gather more info, and any cache I need to clean after espup uninstall?

My first installation was with -t esp32, but I uninstalled and reinstalled with -t all after I didn't see the 8266 target installed.

nbaraz commented 1 week ago

I'm really sorry, I meant xtensa-esp8266-none-elf. I must have been really tired when I opened the issue.

>rustc +esp --print target-list | find "xtensa"
xtensa-esp32-espidf
xtensa-esp32-none-elf
xtensa-esp32s2-espidf
xtensa-esp32s2-none-elf
xtensa-esp32s3-espidf
xtensa-esp32s3-none-elf
nbaraz commented 1 week ago

The issue is that cargo-pio creates a project which relies on a non-existent target, I'll open an issue there.

nbaraz commented 1 week ago

Ok, cargo-pio was ok. It seems that support for xtensa-esp8266-none-elf was dropped in 1.81. I opened an issue: https://github.com/esp-rs/rust/issues/237