Giter Site home page Giter Site logo

visrealm / vremutms9918 Goto Github PK

View Code? Open in Web Editor NEW
40.0 3.0 8.0 3.27 MB

TMS9918A emulator library (C99)

License: MIT License

C 90.64% Makefile 0.93% Python 0.64% C++ 5.49% CMake 2.29%
tms9918 tms9929a tms9918a emulator ti-99 ti99 colecovision msx creativision c

vremutms9918's People

Contributors

fabiodl avatar jettmonstersgoboom avatar troy-petrosys avatar tschrapel avatar visrealm avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

vremutms9918's Issues

Write then read of VDP vram should return previously written value

According to this hardware deep-dive VDP hardware uses a read-ahead buffer for speed and other reasons. This results in some interesting behavior if you mix reads and writes. Most obviously:

  1. write a value to the data port (mode=0)
  2. read from the data port (mode=0)

Due to the read-ahead buffer, you will get back the written value, you will not get the value advanced by the pointer. There are other behavioral oddities here as well regarding how read and write deals with the vram pointer.

When reading:

  1. value in read-ahead buffer is returned
  2. read-ahead buffer is updated with value pointed at by current vram address
  3. vram address is incremented

When writing:

  1. vram pointed at by vram address is updated with new value
  2. read-ahead buffer is set to new value as well
  3. vram address is incremented

I have verified this with my own hardware but worth checking on yours as well. I'm using TMS9128.

VRAM address should only be set on successful register write pair

Current implementation can inadvertently erase the current vram address if you:

  1. write a legitimate vram address to the VDP so it's pointing somewhere expected
  2. write a value to register port (mode=1)
  3. read status register (mode=1)
  4. read data port (mode=0)

VDP has now overwritten lower byte of vram address. According to this hardware deep-dive, changes are only committed on successful pairs.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.