mirror of
https://github.com/TomHarte/CLK.git
synced 2024-07-01 14:29:51 +00:00
110 lines
3.3 KiB
C++
110 lines
3.3 KiB
C++
//
|
||
// 68000.hpp
|
||
// Clock Signal
|
||
//
|
||
// Created by Thomas Harte on 08/03/2019.
|
||
// Copyright © 2019 Thomas Harte. All rights reserved.
|
||
//
|
||
|
||
#ifndef MC68000_h
|
||
#define MC68000_h
|
||
|
||
#include <cstdint>
|
||
#include <iostream>
|
||
#include <vector>
|
||
|
||
#include "../../ClockReceiver/ClockReceiver.hpp"
|
||
#include "../RegisterSizes.hpp"
|
||
|
||
namespace CPU {
|
||
namespace MC68000 {
|
||
|
||
/*!
|
||
A microcycle is an atomic unit of 68000 bus activity — it is a single item large enough
|
||
fully to specify a sequence of bus events that occur without any possible interruption.
|
||
|
||
Concretely, a standard read cycle breaks down into at least two microcycles:
|
||
|
||
1) a 5 half-cycle length microcycle in which the address strobe is signalled; and
|
||
2) a 3 half-cycle length microcycle in which at least one of the data strobes is
|
||
signalled, and the data bus is sampled.
|
||
|
||
That is, assuming DTack were signalled when microcycle (1) ended. If not then additional
|
||
wait state microcycles would fall between those two parts.
|
||
|
||
The 68000 data sheet defines when the address becomes valid during microcycle (1), and
|
||
when the address strobe is actually asserted. But those timings are fixed. So simply
|
||
telling you that this was a microcycle during which the address trobe was signalled is
|
||
sufficient fully to describe the bus activity.
|
||
|
||
(Aside: see the 68000 template's definition for options re: implicit DTack; if your
|
||
68000 owner can always predict exactly how long it will hold DTack following observation
|
||
of an address-strobing microcycle, it can just supply those periods for accounting and
|
||
avoid the runtime cost of actual DTack emulation. But such as the bus allows.)
|
||
*/
|
||
struct Microcycle {
|
||
/*
|
||
The operation code is a mask of all the signals that relevantly became active during
|
||
this microcycle.
|
||
*/
|
||
static const int Address = 1 << 0;
|
||
static const int UpperData = 1 << 1;
|
||
static const int LowerData = 1 << 2;
|
||
static const int ReadWrite = 1 << 3; // Set = read; unset = write.
|
||
|
||
static const int IsData = 1 << 4; // i.e. this is FC0.
|
||
static const int IsProgram = 1 << 5; // i.e. this is FC1.
|
||
|
||
int operation = 0;
|
||
HalfCycles length = HalfCycles(2);
|
||
|
||
/*!
|
||
For expediency, this provides a full 32-bit byte-resolution address — e.g.
|
||
if reading indirectly via an address register, this will indicate the full
|
||
value of the address register.
|
||
|
||
The receiver should ignore bits 0 and 24+.
|
||
*/
|
||
const uint32_t *address = nullptr;
|
||
RegisterPair16 *value = nullptr;
|
||
};
|
||
|
||
/*!
|
||
This is the prototype for a 68000 bus handler; real bus handlers can descend from this
|
||
in order to get default implementations of any changes that may occur in the expected interface.
|
||
*/
|
||
class BusHandler {
|
||
public:
|
||
/*!
|
||
Provides the bus handler with a single Microcycle to 'perform'.
|
||
|
||
FC0 and FC1 are provided inside the microcycle as the IsData and IsProgram
|
||
flags; FC2 is provided here as is_supervisor — it'll be either 0 or 1.
|
||
*/
|
||
HalfCycles perform_bus_operation(const Microcycle &cycle, int is_supervisor) {
|
||
return HalfCycles(0);
|
||
}
|
||
|
||
void flush() {}
|
||
};
|
||
|
||
#include "Implementation/68000Storage.hpp"
|
||
|
||
class ProcessorBase: public ProcessorStorage {
|
||
};
|
||
|
||
template <class T, bool dtack_is_implicit> class Processor: public ProcessorBase {
|
||
public:
|
||
void run_for(const Cycles cycles);
|
||
|
||
private:
|
||
T &bus_handler_;
|
||
};
|
||
|
||
#include "Implementation/68000Implementation.hpp"
|
||
|
||
}
|
||
}
|
||
|
||
#endif /* MC68000_h */
|