Skip to content

The USB link from the shared emulink submodule - #25

Merged
finger563 merged 2 commits into
feat/remote-touchfrom
feat/emulink-submodule
Nov 16, 2026
Merged

finger563 merged 2 commits into
feat/remote-touchfrom
feat/emulink-submodule

Conversation

@finger563

Copy link
Copy Markdown
Contributor

Stacked on the touch PR (#24); retarget to main once it merges. The same change is in the other emulator's repo (esp-cpp/esp-box-emu).

components/devlink, main/remote_control.hpp, tools/emulink and web/ were the same in esp-box-emu and tab5-emu. They now live in one place, esp-cpp/emulink, a submodule at components/emulink.

What changes here

  • Firmware: the emulink component replaces devlink in the component list. It contains DevLink and the header-only RemoteControl, which main includes with its own cart.hpp, gui.hpp and settings.hpp.
  • Board: the board component comes from idf_build_set_property(EMULINK_BOARD_COMPONENT ...), set before project(). It defaults to box-emu; the Tab5 sets tab5-emu.
  • Symlinks: tools/emulink and web are now links into the submodule, so cd tools/emulink && python -m emulink and python3 -m http.server -d web work as before.
  • Pages workflow: it fetches only the emulink submodule and publishes components/emulink/web. It now triggers on a change to the submodule's commit.

What the shared copy merged

  • Panic details: the box's extra panic details (cache errors, the faulting address). The Xtensa-only parts are guarded, so the same file builds for the P4.
  • Settings parsing: strtol instead of std::from_chars (one file for both).
  • Comments: the touch request's comment covers both boards.

Testing

  • Both emulators build.
  • Both boards were updated over the link with these builds.
  • Status, screenshots and a touch work on both boards afterwards.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SFCMzomCZ5wRHJN4sxwkvY

finger563 and others added 2 commits November 15, 2026 18:48
components/devlink, main/remote_control.hpp, tools/emulink and web/ were
the same in esp-box-emu and tab5-emu; they are esp-cpp/emulink now, a
submodule at components/emulink (the `emulink` component: DevLink and
the header-only RemoteControl). tools/emulink and web are links into it,
so `cd tools/emulink && python -m emulink` and the local web server work
as before; the pages workflow publishes components/emulink/web. The
board component comes from EMULINK_BOARD_COMPONENT (box-emu by default).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SFCMzomCZ5wRHJN4sxwkvY
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant