3 ms·
This is what I threw together: https://github.com/David-OConnor/esp32c3_quickstart https://github.com/David-OConnor/esp32c3_quickstart In theory, there is a qu
by the__alchemist 3y ago
This is what I threw together: https://github.com/David-OConnor/esp32c3_quickstart https://github.com/David-OConnor/esp32c3_quickstart
In theory, there is a quickstart CLI tool that should generate a project, but it is currently broken. This is the repo I set up that "just works" for C3.
- sergiogasquez 3y ago> In theory, there is a quickstart CLI tool that should generate a project, but it is currently broken. Which tool do you mean? `cargo-generate` it's working fine for both templates: - esp-idf-template(std): https://github.com/esp-rs/esp-idf-template https://github.com/esp-rs/esp-idf-template) - esp-template (no_std): https://github.com/esp-rs/esp-template https://github.com/esp-rs/esp-template
- the__alchemist 3y agoYep - that's what I'm referring to. Broken as of when I tried 2 weeks ago; can't speak to it currently.
- ukd1 3y agoYa, the tooling is improving (e.g. https://github.com/esp-rs/espup https://github.com/esp-rs/espup) - but still, the experience with Rust is always interesting; I try it every few months, then give up as it breaks, sometimes check tinygo, then realize it's still missing wifi/bt support, and go back to c. Micropython is interesting, but also the developer experience around the tooling isn't great. I was spoiled with rails imho. (if tinygo supported more than one core, and had wifi/bt support on esp32, I'd not be looking back that often)
- steveklabnik 3y agoHopefully it will continually improve given that at least one person is paid to work on it full time. It's come a long long way over the past few years.