GithubHelp home page GithubHelp logo

gdevic / a-z80 Goto Github PK

View Code? Open in Web Editor NEW
132.0 132.0 32.0 46.76 MB

An implementation of the Z80 CPU for Altera, Xilinx and Lattice FPGAs

License: GNU General Public License v2.0

Verilog 6.45% Stata 2.85% SystemVerilog 28.70% Python 2.21% Coq 0.47% Batchfile 0.52% Shell 0.79% Tcl 0.27% Assembly 24.87% VHDL 0.49% C++ 0.59% HTML 30.67% C# 1.11%

a-z80's People

Contributors

gdevic 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  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  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

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

a-z80's Issues

M1 asserted during bus acknowledge cycles

It seems like the M1 signal is pulled low during bus acknowledge, which would break DMA to IO devices, since they could interpret the I/O request as an interrupt acknowledge. I have no original Z80 on hand right now, but I checked using Z80 explorer that M1 should indeed be high when BUSACK goes low.

Data pin latching

By Z-80 specification Data pins are sampled (latch-ed) in the beginning of T3 for Op-Code fetching or in the middle of T3 for Memory/IO read.
By this project implementation it ALWAYS are fetched in the middle of T2.
It's way to early! In the middle of T2 WAIT bus are sampled, and if it's LOW - extra Tw are added between T2 and T3 until WAIT go HIGH.
That's why Data pins always sampled in T3 and never in T2.
Why that? Does that is unspecified declination from specification in Z-80 chip or just error in that particular project?

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.