4 ms·
I had an easy time getting setup with the esp32c3 with this repository (linked to in author's first post): https://github.com/ivmarkov/rust-esp32-std-demo https
by pfes 5y ago
I had an easy time getting setup with the esp32c3 with this repository (linked to in author's first post):
https://github.com/ivmarkov/rust-esp32-std-demo https://github.com/ivmarkov/rust-esp32-std-demo
Also got it working on WSL2. I could install flashing and monitoring tools as Windows binaries, which have access to Windows ports.
https://pfesenmeier.github.io/wsl2-and-embedded-development/ https://pfesenmeier.github.io/wsl2-and-embedded-development/
- dljsjr 5y agoThat's because the c3 is a RISC-V chip and so doesn't require all of the annoying tooling that parent comment is referring to. The rest of Espressif's product line, including the extremely popular original ESP32 and the older 8266, use different chip architecture (xtensa) that requires a more annoying setup.
- pfes 5y agoIt was easy because of ivmarkov's tooling (see linked repo in previous comment). The "flasher coded in python, IDF coded in C" is installable through cargo. I did not have to install "MinWin". Docker does not having access to ports, but WSL2 does have access to the computers ports (through cross-compiling build tools). Not having to install custom Rust toolchain for Xtensa chips was nice, too.
- dljsjr 5y agoI stand corrected, that's a useful template project. Thanks for linking!