• Updated toolchain version to 1.62.1.0
• Added an extra step that installs cargo-generate via cargo if the binary installation failed
• Formated scripts
• Fixed an issue where elf path in scripts was not correct for projects with - on the name
• Update https://github.com/esp-rs/esp-hal/pull/134 changes
• Update xtensa-atomic-emulation-trap version

Hi, I'm trying to use cargo generate, but it throw this error:

cargo generate https://github.com/esp-rs/esp-template          
error: Found argument 'https://github.com/esp-rs/esp-template' which wasn't expected, or isn't valid in this context

USAGE:
    cargo generate [FLAGS] [OPTIONS] --git <git>

For more information try --help

when I use --git:

cargo generate --git=https://github.com/esp-rs/esp-template
 Project Name: test-esp8266
 Creating project called `test-esp8266`...
Error:  Git Error: failed to clone into: /home/samuel/Downloads/test-esp8266IXEFXF

Have I did something wrong ?

why there is no esp8266 template ?

I just used cargo generate to create a new project for ESP32C3 with allocations via the esp-alloc crate. When I build I get this warning message:

warning: function `init_heap` is never used
  --> src\main.rs:10:4
   |
10 | fn init_heap() {
   |    ^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

Should I call init_heap() first thing in main()?

• Add devcontainer support for:
  • VS Code Dev Containers
  • Gitpod
  • GitHub Codespaces
• When using dev containers:
  • Wokwi support
  • Web flasher support
  • Readme with instructions

The current template is a hollow shell. My wish is that it gets "blinking LED" code.

Benefits I see:

• The whole toolchain can be verified
• There is something that works and can be tweaked ( frequency of LED blinking )

Possible down side: The unwanted source code has to be removed. (but that is outweighted by all project starts that do need / want something that proves a working target)

I'm new to rust on embedded systems. I want to use esp-hal instead of esp-idf because idf has lots of stuff and configuration I dont understand, so being more bare metal will help me learn here.

I am attempting to use the alloc crate, it would be great if the cargo generate for this template prompted the user to ask them if they want to use alloc, and gives them a good default global allocator to use, like esp-alloc

• If any user would like to submit a PR from a fork of the repo, the CI should use his repo (and the propper branch) to generate the project to build
• Fix conditions to generate a project as schedule triggers were not generating any project,hence the CI was failing

Before applying these changes, both version 0.13 and version 0.14 was built when I created a new repo using this template. It resulted in link errors like these:

error: linking with `xtensa-esp32-elf-gcc` failed: exit status: 1
  |
  = note: "xtensa-esp32-elf-gcc" <snip>
  = note: <snip>/xtensa-esp32-elf/bin/ld: <snip>/deps/libxtensa_lx_rt-e583d49af76632b7.rlib(xtensa_lx_rt-e583d49af76632b7.xtensa_lx_rt.eb13f165-cgu.11.rcgu.o): in function `__default_exception':
          <snip>/.cargo/registry/src/github.com-1ecc6299db9ec823/xtensa-lx-rt-0.14.0/src/exception/esp32.rs:95: multiple definition of `__default_exception'; <snip>/deps/libxtensa_lx_rt-b7c97e11631cd506.rlib(xtensa_lx_rt-b7c97e11631cd506.xtensa_lx_rt.5a35a154-cgu.1.rcgu.o):<snip>/.cargo/registry/src/github.com-1ecc6299db9ec823/xtensa-lx-rt-0.13.0/src/exception/esp32.rs:95: first defined here
<snip>

• Updated some dependencies versions

Maybe we should come up with a way to notify when a new version of the dependencies is available (something like dependabot) for the template that we could integrate in the CI

We should briefly describe each prompt, its options, and why you may or may not want to use any given feature.

@SergioGasquez maybe if you had some time (this is low priority) you could look into this? If not I can do it at some point. If you're interested please just assign yourself to the issue!

• Update rust toolchain version to 1.63.0.2
• Update editor.formatOnSaveMode property as it was not formatting documents properly.
• Update esp-hal revision to include https://github.com/esp-rs/esp-hal/pull/176