MC6809 0.7.2

MC6809 CPU emulator written in Python

MC6809 is a Open source (GPL v3 or later) emulator for the legendary 6809 CPU, used old homecomputer Dragon 32/64 and Tandy TRS-80 Color Computer (CoCo) built in the 1980s...

Tested with Python 3.8, 3.9, 3.10 and PyPy3

A example usage can be find in: MC6809/example6809.py

Getting started:

~$ git clone https://github.com/6809/MC6809.git
~$ cd MC6809
~/MC6809 $ ./cli.py --help

The output of ./cli.py --help looks like:

Usage: ./cli.py [OPTIONS] COMMAND [ARGS]...

╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
│ --help      Show this message and exit.                                                          │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ───────────────────────────────────────────────────────────────────────────────────────╮
│ benchmark            Run a MC6809 emulation benchmark                                            │
│ profile              Profile the MC6809 emulation benchmark                                      │
│ version              Print version and exit                                                      │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯

There is a simple benchmark. Run e.g.:

~/MC6809$ ./cli.py benchmark --help

The output of ./cli.py benchmark --help looks like:

Usage: ./cli.py benchmark [OPTIONS]

 Run a MC6809 emulation benchmark

╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
│ --loops       INTEGER  How many benchmark loops should be run? [default: 6]                      │
│ --multiply    INTEGER  est data multiplier [default: 15]                                         │
│ --help                 Show this message and exit.                                               │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯

profile

You can run the Python profiler against the benchmark, e.g.:

~/MC6809$ ./cli.py profile --help

The output of ./cli.py profile --help looks like:

Usage: ./cli.py profile [OPTIONS]

 Profile the MC6809 emulation benchmark

╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
│ --loops       INTEGER  How many benchmark loops should be run? [default: 6]                      │
│ --multiply    INTEGER  est data multiplier [default: 15]                                         │
│ --help                 Show this message and exit.                                               │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯

development

For development exists dev-cli, e.g.:

~/MC6809$ ./dev-cli.py --help

The output of ./dev-cli.py --help looks like:

Usage: ./dev-cli.py [OPTIONS] COMMAND [ARGS]...

╭─ Options ────────────────────────────────────────────────────────────────────────────────────────╮
│ --help      Show this message and exit.                                                          │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Commands ───────────────────────────────────────────────────────────────────────────────────────╮
│ check-code-style            Check code style by calling darker + flake8                          │
│ coverage                    Run and show coverage.                                               │
│ fix-code-style              Fix code style of all MC6809 source code files via darker            │
│ install                     Run pip-sync and install 'MC6809' via pip as editable.               │
│ mypy                        Run Mypy (configured in pyproject.toml)                              │
│ publish                     Build and upload this project to PyPi                                │
│ safety                      Run safety check against current requirements files                  │
│ test                        Run unittests                                                        │
│ tox                         Run tox                                                              │
│ update                      Update "requirements*.txt" dependencies files                        │
│ update-test-snapshot-files  Update all test snapshot files (by remove and recreate all snapshot  │
│                             files)                                                               │
│ version                     Print version and exit                                               │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯

Run tests, e.g.:

~/DragonPy$ ./dev-cli.py coverage
# or just:
~/DragonPy$ ./dev-cli.py test
# or with different Python versions:
~/DragonPy$ ./dev-cli.py tox

TODO

• Update 'cpu6809_html_debug.py'
• Use bottle for http control server part
• unimplemented OPs:
  • RESET
  • SWI / SWI2 / SWI3
  • SYNC

Make new release

We use cli-base-utilities to generate the history in this README.

To make a new release, do this:

• Increase your project version number
• Run tests to update the README
• commit the changes
• Create release

History

(Some of the points are related to DragonPy Emulator)

• v0.7.2
  • 2023-11-03 - Auto generate README history
  • 2023-11-03 - Fix code style
  • 2023-11-03 - Apply manageprojects updates + Update requirements
  • 2023-11-03 - Use verbose_check_call from cli_base
  • 2023-11-02 - Bump pip from 23.2.1 to 23.3
• v0.7.1
  • 2023-08-05 - fix publish call
  • 2023-08-05 - Split CLI by apply manageprojects update
  • 2023-08-04 - Update requirements
• v0.7.0
  • 2023-03-07 - Add "benchmark" and "profile" to CLI and remove dev-shell add DocTests
  • 2023-03-07 - Apply managedprojects update: Add DocTests via bx_py_utils helper
  • 2023-03-06 - Update README.md
  • 2023-03-06 - Migrate to https://github.com/jedie/cookiecutter_templates
  • 2022-09-04 - deactivate pypy3
  • 2022-09-04 - fix tests under windows
  • 2022-09-04 - fix code style
  • 2022-09-04 - replace Makefile with "dev-shell"
  • 2022-09-04 - update Makefile
  • 2022-09-04 - update README
  • 2022-09-04 - small code update
  • 2022-09-04 - remove travis config
  • 2022-09-04 - flynt updates
  • 2022-09-04 - fix flynt call
  • 2022-09-04 - replace Creole README with markdown
  • 2022-09-04 - fix pytest config
  • 2022-09-04 - update github CI
  • 2022-09-04 - add "make update"
  • 2022-09-04 - fix editorconfig
• v0.6.0
  • 2020-02-10 - update CLI Tests
  • 2020-02-10 - git ignore: +/publish.log
  • 2020-02-10 - update CLI and README
  • 2020-02-10 - test release v0.6.0.dev0
  • 2020-02-10 - swap autopep8 and isort
  • 2020-02-10 - update Travis CI config
  • 2020-02-10 - fix code style
  • 2020-02-10 - update .join() statements
  • 2020-02-10 - setup poetry-publish
  • 2020-02-10 - apply pyupgrade
  • 2020-02-10 - apply code formatter
  • 2020-02-10 - f-strings convert
  • 2020-02-10 - WIP

donation

• Flattr This!
• Send Bitcoins to 1823RZ5Md1Q2X5aSXRC5LRPcYdveCiVX6F