add esp32c6

[seanaye]

Adds the options for the esp32 c6 dev board in the cargo generate toml

[SergioGasquez]

Hi @seanaye! Thanks for your contribution! We would also need some logic, as the new targets are not supported in some ESP-IDF versions, see https://github.com/espressif/esp-idf#esp-idf-release-and-soc-compatibility.

[sredman]

Hi @seanaye! Thanks for your contribution! We would also need some logic, as the new targets are not supported in some ESP-IDF versions, see https://github.com/espressif/esp-idf#esp-idf-release-and-soc-compatibility.

Do you have a suggestion for how you're thinking of this? I've never edited a cargo-generate template before, but from my struggles it seems that this isn't an easy thing to do.

[sredman]

Hi @seanaye! Thanks for your contribution! We would also need some logic, as the new targets are not supported in some ESP-IDF versions, see https://github.com/espressif/esp-idf#esp-idf-release-and-soc-compatibility.

Do you have a suggestion for how you're thinking of this? I've never edited a cargo-generate template before, but from my struggles it seems that this isn't an easy thing to do.

I have this, but it's not pretty, and will grow "infinitely" as more boards are released which need new SDKs.

[conditional.'defaults == false && (mcu == "esp32s6" || mcu == "esp32p4")'.placeholders.espidfver]
type = "string"
prompt = "ESP-IDF version (master = UNSTABLE)"
choices = ["master"] # Supported as of v5.1
default = "master"

[conditional.'defaults == false && (mcu == "esp32" || mcu == "esp32c3" || mcu == "esp32s2" || mcu == "esp32s3")'.placeholders.espidfver]
type = "string"
prompt = "ESP-IDF version (master = UNSTABLE)"
choices = ["v4.4", "v5.0", "master"]
default = "v4.4"

[Vollbrecht]

Also missing:
as long as the upstream support for the new c6 target is not integrated, the template should include the target manually as a file and invoke it in the build command.
riscv32imac-esp-espidf.json

{
    "arch": "riscv32",
    "cpu": "generic-rv32",
    "data-layout": "e-m:e-p:32:32-i64:64-n32-S128",
    "eh-frame-header": false,
    "emit-debug-gdb-scripts": false,
    "env": "newlib",
    "features": "+m,+a,+c",
    "is-builtin": false,
    "linker": "riscv32-esp-elf-gcc",
    "llvm-target": "riscv32",
    "max-atomic-width": 64,
    "os": "espidf",
    "panic-strategy": "abort",
    "relocation-model": "static",
    "target-family": [
      "unix"
    ],
    "target-pointer-width": "32",
    "vendor": "espressif"
  }

invoked with --target riscv32imac-esp-espidf.json or better add to the rustflags in config.toml so the user workflow dont change

[sredman]

Also missing: as long as the upstream support for the new c6 target is not integrated, the template should include the target manually as a file and invoke it in the build command. riscv32imac-esp-espidf.json

invoked with --target riscv32imac-esp-espidf.json or better add to the rustflags in config.toml so the user workflow dont change

Support for riscv32imac-esp-espidf was merged a couple of days ago: rust-lang/rust#111369

I have modified a project generated by this template locally, and I can confirm that the Hello World example works with a C6 board given you're using a nightly rust build. So now, ideally, the template should be made to work, and documentation updated.

[Vollbrecht]

Also missing: as long as the upstream support for the new c6 target is not integrated, the template should include the target manually as a file and invoke it in the build command. riscv32imac-esp-espidf.json

invoked with --target riscv32imac-esp-espidf.json or better add to the rustflags in config.toml so the user workflow dont change

Support for riscv32imac-esp-espidf was merged a couple of days ago: rust-lang/rust#111369

I have modified a project generated by this template locally, and I can confirm that the Hello World example works with a C6 board given you're using a nightly rust build. So now, ideally, the template should be made to work, and documentation updated.

🤩 nice, i missed that merge

[sredman]

This needs to be riscv32imac-esp-espidf (imAc) for esp32c6

[sredman]

See #124

[sredman]

Hi @seanaye! Thanks for your contribution! We would also need some logic, as the new targets are not supported in some ESP-IDF versions, see https://github.com/espressif/esp-idf#esp-idf-release-and-soc-compatibility.

I have put my proposal in #125