Re: 7501/8501 R/W gate in

From: Gerrit Heitsch <gerrit_at_laosinh.s.bawue.de>
Date: Sun, 30 Aug 2020 16:43:14 +0200
Message-ID: <7b85b3ff-1234-430c-29ce-370f297f0eb7_at_laosinh.s.bawue.de>
On 8/30/20 3:57 PM, Francesco Messineo wrote:
> Hi all,
> maybe this has been discussed before, but I really can't get all
> informations together.
> We all know the 7501 is a crippled 6510 (I say crippled because they
> needed to get rid of either NMI or PHI2 pins to have this gate-in
> signal fit in the 40 PIN dip package, while adding also an additional
> port bit I/O, which is fine).
> 
> Now, reading the 264 timing and documentation (it's on zimmers), it appears
> that gate_in is a latch enable for the R/W signal, meaning R/W will be
> held in its
> previous state when gate is low.

 From what I see on the scope, the Gate IN signal only allows R/W to 
change state with the rising edge of MUX.


> This gate_in input is driven by MUX output from the TED chip. Basically MUX is
> a signal for driving the DRAM address multiplexers, it's high in the /
> RAS address
> phase to the DRAMs and low in the /CAS address phase. So by gating R/W with
> MUX, they prevented it to change during the later phase of a CPU Cycle.
> Now my questions:
> 1) why on earth would R/W change halfway a CPU cycle (phi2 high), that
> can't happen as far as I know on a 6502/6510 system

Don't forget that a 264 system changes the CPU clock between normal and 
double clock unless you set the right bit in TED. With the Gate IN, the 
R/W=LOW part of a write cycle is the same length no matter what the CPU 
clock.


> 2) How can a 6510 (that doesn't have any gate_in input) work apparently fine
> as a 7501 replacement (there're people doing that, it's documented).

Probably because the circuit is a bit more robust than thought. If I 
disable GateIN, I get an aborted R/W=LOW where it shouldn't be. I can 
send the captures from the scope to whoever wants them. I used a 4 
channel scope to capture R/W, PHI0, MUX and, on one set, AEC at the same 
time.


> 3) Why on a C64 there was no need for this R/W latch? What main difference
> exist between a C64 DRAM access and a C16 DRAM access (that I don't get)?

Changing CPU clock speed probably.


> 4) Why they didn't simply latch the R/W signal externally if
> absolutely needed and just re-use a 6510 die with an additional port
> pin bonded out and just leave out only one of PHI2 or NMI)?

The goal was to save on discrete chips. Remember Bil Herd had to fight 
for a simple 555 for the reset circuit.

  Gerrit
Received on 2020-08-30 17:00:29

Archive generated by hypermail 2.3.0.