Skip to main content

Eval Pack: ESP32 ESP-IDF VS Code Hello World

Required evidence (minimum)​

  • Repo link (preferred) or zip
  • Proof of build (idf.py build) — screenshot or pasted output
  • Proof of flash (idf.py -p COMx flash) — screenshot or pasted output
  • Proof of monitor (idf.py -p COMx monitor) — must show boot + hello logs
  • Config proof:
    • either attach sdkconfig or paste the values you changed
  • Reflection (5–10 lines): what went wrong, how you fixed it

Checkpoint questions (Coach Agent)​

1) Environment Ready​

  1. Where does the ESP-IDF extension install toolchains by default (roughly), and why do we keep paths short on Windows?
  2. How do you confirm Windows assigned the board a COM port?

2) Project + Target​

  1. What does idf.py set-target <chip> do? When do you need to run idf.py fullclean?
  2. If you build for esp32s3 but your board is esp32, what kinds of failures might you see?

3) Build / Flash / Monitor​

  1. What command builds the project? What does a successful build produce (name the main output file type)?
  2. How do you exit idf.py monitor?
  3. What are 2 common reasons flashing fails on Windows?

4) menuconfig​

  1. What file does menuconfig write to, and should you commit that file to Git?
  2. Name two settings you can change in menuconfig that often matter in real projects.

Rubric (10 points)​

  • Environment setup correctness (0–2)
  • Build/flash/monitor success (0–3)
  • menuconfig understanding + change applied (0–2)
  • Troubleshooting ability (0–2)
  • Reproducibility / cleanliness (0–1)

Pass = ≥ 7/10 AND minimum evidence complete.

Notes for the Coach Agent​

  • Don’t ask all questions at once; ask per checkpoint.
  • If learner fails, give a short remediation step and re-check.