Include Detailed Guidance on Selecting and Purchasing Physical Hardware for ESP32-C3 Development #4
Comments
|
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. |
|
Dear @theembeddedrustacean , Thank you for your prompt response and for considering my feedback. I genuinely appreciate the book’s goal of enabling embedded development using Wokwi, with the need for physical hardware only in rare cases. However, my experience has not been as seamless as hoped. Yesterday, I eagerly followed the instructions in the book to run the first “Hello World” example on Wokwi (project link), but I was met with the following error message: Project Link: https://wokwi.com/projects/414857042750169089?gh=1 I tried again today and encountered the same issue. Unfortunately, this has halted my progress at the beginning of Chapter 4 in an 11-chapter book. Understandably, this has been quite frustrating, and the error messages have dampened the joy of reading and learning from your book. While assembling and debugging hardware devices can be challenging, I believe that with detailed documentation and a supportive Discord community, it wouldn’t hinder readers from continuing with the book. Adding an appendix that discusses hardware assembly and debugging would be highly beneficial, and I suggest completing it as soon as possible. I’ve already ordered the recommended hardware from your list and look forward to exploring the practical aspects of embedded Rust development. I appreciate your efforts in making this subject accessible and eagerly anticipate the upcoming updates. Thank you once again for your consideration. Best regards, Bin Wu |
|
Hello Again @wubin28, The cited issue can be resolved by modifying the build parameters requiring Wowki support. Hopefully, this can be resolved soon. An alternative avenue would be using the Wokwi VS Code extension locally but I would still have to try that out if the issue still remains. Also, relative to both Wokwi and hardware, the following issue might appear: esp-rs/std-training/issues/266 All this is mostly due to the project still being relatively dynamic. The good news is that updates typically propagate fairly quickly. |
|
Update @wubin28, The Wokwi examples are back up and running now. However, you might still encounter the esp-rs/std-training#266 issue highlighted earlier. As a workaround, until Espressif introduces a fix, add |
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.
The text was updated successfully, but these errors were encountered: