3 ms·
The hash map was definitely not robust enough, that’s why I ultimately switched back to the default behavior and increased the memory available on the board! A
by sodality2 3y ago
The hash map was definitely not robust enough, that’s why I ultimately switched back to the default behavior and increased the memory available on the board!
Also, I am a Rust fanatic. I do nearly everything in it! I gave a talk on it at our last hackathon! I even wear a Rust t-shirt regularly! So rest assured I will be exploring my options with Rust. I would love to get rid of my dependence on Arduino. But C++ was easiest to get off the ground with, believe it or not, just because I have experience flashing Arduino boards.
- fnordpiglet 3y agoNo that’s awesome. Experiment and enjoy. But I would check out the esp33 toolchain for rust. It’s remarkably mature. Awesome project btw.
- kramerger 3y agoIs it possible to program this device without the espresso SDK and the arduino stuff? Whether I'll use C++ or Rust for my next project depends on which one I can first get working on this board with the standard toolchain (GCC and Rustc respectively)
- fnordpiglet 3y agohttps://esp-rs.github.io/book/ https://esp-rs.github.io/book/ Yes
- kramerger 3y agohttps://esp-rs.github.io/book/installation/riscv-and-xtensa.html https://esp-rs.github.io/book/installation/riscv-and-xtensa.... "What espup Installs ... Espressif Rust fork with support for Espressif targets ... LLVM fork with support for Xtensa targets" :( ?
- fnordpiglet 3y agoYeah risc-v is in the rust supported tiers but xtensa isn’t. I haven’t dug deeply into whether the riscv esp32c3 boards still use some forked rust etc, though, but in theory shouldn’t as it’s a tier 2 architecture. That said, for my use, it’s entirely transparent this is happening under the covers. Things work as they should in your ESP32 cargo projects as don’t interfere with other targets, and I’ve not found any weird edges. I do however use the c3 boards.