Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop MCS-51 IAP concept #2

Open
TG9541 opened this issue Jun 5, 2022 · 0 comments
Open

Develop MCS-51 IAP concept #2

TG9541 opened this issue Jun 5, 2022 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@TG9541
Copy link
Owner

TG9541 commented Jun 5, 2022

Like 8051forth, CamelForth 8051, Payne's 8051 Forth the original 8051-eForth requires a "dual mapped RAM" (i.e., addressable as XRAM or ROM). Modern MCS-51 IP cores in very-low-cost µCs and SoCs are "pure Harvard archetecture" and can't do that. Most of them lack an external bus feature. If they have it, like the CH559 it may be limited to XDATA RAM access.

Some possible approaches are:

  • limitation to non-interactive use cases
  • interactive use with a temporary dictionary in RAM (words can't use assembler code)
  • interactive use with RAM as a "construction area" and copying to Flash ROM

Discuss and document possible solutions.

@TG9541 TG9541 self-assigned this Jun 5, 2022
@TG9541 TG9541 added the documentation Improvements or additions to documentation label Jun 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: 🏗 In progress
Development

No branches or pull requests

1 participant