- Install and use ESP-IDF 5.4 or newer. The CI pipeline builds against the
release-v5.4toolchain to ensure the project uses the NG I²C driver stack exclusively. - Run
python3 fetch_repos.pybefore building so that managed components are pulled into the workspace or refreshed to the pinned revisions.
- Set the target with
idf.py set-target esp32p4the first time you configure a new working tree. - Run
idf.py buildfromplatforms/tab5/before sending a change for review. - Format any modified C or C++ sources with
./tools/clang_tools.sh format. Run./tools/clang_tools.sh tidy(orfix) when you need clang-tidy to apply additional suggestions. - If you touch component metadata, run
idf.py lintto validate the manifest files.
ESP-IDF 5.4.2 ships the ESP32 Wi-Fi remote project in
$IDF_PATH/components/espressif__esp_hosted/slave. Build and flash it once so
the Tab5 SDIO link negotiates correctly:
cd "$IDF_PATH/components/espressif__esp_hosted/slave"
idf.py set-target esp32
idf.py build
idf.py -p <remote_port> flashThe build drops build/network_adapter.bin if you prefer flashing with
esptool.py. Future ESP32-C6 variants should publish their binaries as external
artifacts instead of committing them to the repo.