Sergio Gasquez Arcos

I just did another test, using a freshly generated template (targetting esp32c6 and not using advanced config), I tried using your partition table and flash it with espflash and esptool:...

A small summary with some findings: - Flashing the provided elf and partition table results in the same as flashing the provided elf and a default partition table: - In...

https://github.com/bjoernQ/espsegs might help us debug this issue

Do you have any suggestions on how to solve this issue? The main concern that I have when cleaning the path is: How do I know that `espup` added that...

> This should be okay since espup only supports a single installed toolchain version, so there's no "race condition" when things are installed/uninstalled out of order. `espup` supports several installed...

I will try to gather some information about the status of LLD support, if we are close to using it, we can leave this issue as unresolved as in the...

> Any updates on the S3 runner? It would be really nice to check at least one Xtensa target in HIL. Our lab manager is not available this week as...

I just rebased the changes, and filter the `test_gpio_interrupt` for Xtensa devices (due to https://github.com/esp-rs/esp-hal/issues/1413). Tests are working fine locally: ESP32-S3 output ``` esp-hal/xtask on  feat/s3-hil [$!⇕] is 📦...

This should now be ready for review! I've updated the original post with the latest HIL run and the local results.

> If we are removing espup from the riscv targets. A few notes regarding this. Using `espup` for RISC-V targets it's not that bad. It won't install the Xtensa Rust,...