Proposal: first-class RT-Thread / Edgi-Talk host (M55, shared ESP UI stack)

Open
#577 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
c, rust, typescript
Domain
embedded-iot

Research direction

This is a design proposal, not a task to start on. The maintainers must first answer the five open questions: the host directory name, the native target policy, the docs page, the host profile path, and how to handle the esp_err and heap_caps coupling. The existing hosts/esp-idf/components sources are the code to share rather than fork. Done means a maintainer decision on those questions, not a patch.

Written by the indexing model from the issue text.

Description

Summary

Proposal to add a first-class RT-Thread / Edgi-Talk host tree to PocketJS, proven on PSoC E84 (Cortex-M55 + HyperRAM, 800×480). Product firmware still owns LCD, touch, Wi-Fi, and BT — same philosophy as hosts/esp-idf.

Full write-up (on our fork):
https://github.com/1024971823/pocketjs/blob/main/hosts/rt-thread-edgitalk/docs/upstream-proposal.md

Ready-to-paste PR body:
https://github.com/1024971823/pocketjs/blob/main/hosts/rt-thread-edgitalk/docs/upstream-pr-body.md

Working fork (merged): https://github.com/1024971823/pocketjs
Board/product overlay (out of monorepo scope): https://github.com/1024971823/PocketJS_for_Edgi-Talk

Motivation

Edgi-Talk already runs package / guest / ui_core / ui_qjs / render_rgb565 on M55 via an overlay that consumes the ESP-IDF component C sources and rebuilds Rust for thumbv8m.main-none-eabihf. Promoting the reusable host pieces into the monorepo avoids a forever private fork and gives pocket-nexus a documented third native target (or an explicit source-build-only policy).

In scope for upstream

  • hosts/rt-thread-edgitalk/ (or a generic hosts/rt-thread/) — docs, native glue, SCons include, shared-component policy
  • Tooling analogous to esp-idf-native / contracts for M55
  • Optional in-tree example app (apps/edgitalk-m55-smoke) if desired
  • Share existing hosts/esp-idf/components/{package,guest,ui_*,render_rgb565} — do not fork those C sources

Explicitly out of scope

  • BSP patches, CYW BT firmware blobs, KitProg3 / flash scripts
  • Full RT-Thread board project / Infineon-specific bring-up
  • Product Wi-Fi / BT / game / __edgi bridges

Asks for maintainers

  1. Host directory name: rt-thread-edgitalk vs generic rt-thread
  2. Native target: document thumbv8m.main-none-eabihf or mark source-build only (no Registry archives)
  3. Docs page like /docs/rt-thread/
  4. Host profile path toward pocket-rtt-host-1 / platform: "rt-thread" (today apps still borrow pocket-idf-host-1)
  5. Preference: reduce esp_err / heap_caps coupling upstream vs bless a thin host OSAL

Hardware note

We have run clean build + KitProg3 flash of the overlay firmware on Edgi-Talk hardware; PocketJS reports frames= / ui= / lcd= over serial with Wi-Fi and BT advertising. Hardware gates (frame hash, heap steady-state, present cadence @ 800×480) would be a follow-up, not a blocker for reviewing the proposal.

Happy to open a draft PR from https://github.com/1024971823/pocketjs when you want code in review, or adjust scope first.

Dominant language
TypeScript
Stars
1.6k
Forks
88
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pocket-stack/pocketjs

All issues in pocket-stack/pocketjs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.