theembeddedrustacean
commented
3 days ago Valid point. Thank you for the feedback @wubin28. Unfortunately, the build failures can happen either due to the code version being out of sync or sometimes due to server issues. They were also more frequent than anticipated. Hopefully, with time, this would stabilize. Also, the development options chapter was actually much more extensive and was reduced through the book's review process. The goal ultimately was to direct beginners to Wokwi to avoid the intricacies and pain of dealing with and purchasing hardware, adding another layer of complexity. Readers were referred to the repo for the option of dealing with hardware.
My current thinking is to either include all that in an appendix rather than the main body to maintain the flow focused on Wokwi or extend the description in the git repo.
I'll keep this issue open until a decision has been made on addressing this in an upcoming update cycle of the book.
wubin28
Is your feature request related to a problem? Please describe. Readers following “Simplified Embedded Rust: ESP Standard Library Edition” may encounter build failures when running “Hello World” examples on the Wokwi simulator, hindering their learning experience. This issue necessitates the use of physical hardware. However, the book lacks detailed information on purchasing such hardware. While some guidance is available at the end of the ser-std GitHub repository, it does not provide clear instructions on choosing between boards like the ESP32-C3-DevKitM-1 and the ESP32-C3-DevKit-RUST-1 for Rust-based embedded development.
Describe the feature you'd like I recommend adding a dedicated section in the book that offers: • Clear instructions on selecting appropriate physical hardware for ESP32-C3 development. • A comparison of available development boards, such as the ESP32-C3-DevKitM-1 and ESP32-C3-DevKit-RUST-1, highlighting their features, benefits, and suitability for Rust-based projects. • Detailed purchasing information, including recommended retailers and considerations for international readers.
This addition would provide readers with the necessary guidance to acquire suitable hardware, ensuring a seamless learning experience.
Describe alternatives you've considered An alternative approach could involve directing readers to external resources or forums for hardware selection advice. However, incorporating this information directly into the book would offer immediate value and maintain its self-contained nature, enhancing the reader’s experience.
Additional context Including detailed hardware selection and purchasing guidance aligns with the book’s goal of simplifying embedded Rust development. This addition would empower readers to make informed decisions, facilitating a smoother transition from simulation to physical implementation.