For this activity, I explored the embedded programming workflow using Wokwi and the Arduino IDE.
My goal was to better understand how microcontroller programs can be developed, tested, and deployed
before working with physical hardware.
Tools Used
- Wokwi Online Simulator
- Arduino IDE
- Arduino Uno R3
- C/C++ Programming Language
- Workflow
The development process began in Wokwi, where circuits and code could be tested in a virtual environment.
Wokwi allowed me to simulate an Arduino Uno and observe the behavior of my program without needing physical hardware.
Once the program behaved as expected in the simulator, the same code could be used in the Arduino IDE and
uploaded to a physical microcontroller. This workflow reduced troubleshooting time by allowing code and
circuit behavior to be verified before deployment.
Comparison of Toolchains
>
Wokwi Simulation
Advantages:
- No physical hardware required.
- Immediate feedback during testing.
- Easy to modify circuits and components.
- Useful for learning and experimentation.
Limitations:
- Does not fully replicate real-world electrical issues.
- Sensor behavior may differ from actual hardware.
Arduino IDE and Physical Hardware
Advantages:
- Interacts with real electronic components.
- Provides experience with wiring and troubleshooting.
- Allows testing of actual hardware performance.
Limitations:
- Requires physical components.
- Wiring errors and hardware issues can affect testing.
- What I Learned
This exercise showed how simulation and physical hardware complement each other during embedded
development. Wokwi made it easy to learn programming concepts and test ideas quickly, while the
Arduino IDE and physical hardware provided experience working with real circuits and devices.
Using both tools together created a more efficient development workflow.