I have an old Rockwell chip with label "R6502-13" that i'd like to do the "Free Run" test. I'm guessing it's an NMOS chip?

I've read the 6502 Primer: Clock Generation but I do not have the parts yet as mentioned for the NMOS chip. What I have is this 4pin crystal. Will this work?

_________________
// tinkerBOY

Yes. Not only will that work, it's the preferred method.

And yes, I believe that is an old NMOS chip which has a minimum frequency to run (IIRC, something like 100KHz).

A modern WDC 65C02 would be better but the NMOS version can certainly be used (assuming it works).

_________________
Cat; the other white meat.

Ok thanks. So the output of the crystal goes directly to the 6502's pin 37, correct?

_________________
// tinkerBOY

So I tried it on a breadboard and connected all the necessary pins including the data bus pins to run the NOP code "ea". I' ve also connected one LED to one of the address bus. Powered it with a 5v power supply but I don't see to get any activity from the led. Anything I missed?

_________________
// tinkerBOY

connecting the LED to pin 25 (A15) may be more visible - A0 is going to be wiggling at clock/2 , so fast. However it ought to still glow somewhat. I presume you've done the usual thing of connect the LED directly to just 5v rail - just to be sure it's in the right way round and working...

And make sure the can oscillator is the right way round.

This is where an oscilloscope, even a cheap one, can be really handy just to check a few things.

There is also the possibility of a fake/broken chip - if this is something you bought off ebay. Do you have anything with a real working 6502 in it that you could use to check?

-Gordon

_________________
--
Gordon Henderson.
See my Ruby 6502 and 65816 SBC projects here: https://projects.drogon.net/ruby/

I have tested the led to be working fine. For the 6502, it’s also tested to work just fine with a clone replica of Apple I i assembled. For the crystal i have no way of testing it though. I will definitely get an Oscilloscope in the near future.

I tried several nmos 6502 chips i have laying around but but couldn’t seem to do the “free run”.

_________________
// tinkerBOY

Was Rockwell still manufacturing NMOS on the 45th week of 2011? Or am I reading something incorrectly ...

I also noticed on first glance that your reset circuit might possibly be cause for concern.

_________________
Got a kilobyte lying fallow in your 65xx's memory map? Sprinkle some VTL02C on it and see how it grows on you!

Mike B. (about me) (learning how to github)

It looks like the jumper wire for the VCC is not intact so i pressed it down and made sure there’s 5v on that pin. Sure thing, now it’s working.

Now I just need to find a way to slow down the 1mhz clock so I can clearly see what’s happening. Is it possible to slow it down to maybe the minimum 100khz clock?

_________________
// tinkerBOY

You can divide by 2 with a Flip Flop, so a single 74xx74 dual flip flip would give you options of 500khz and 250khz, chain 2 together and you'd have 125khz and 62.5khz too.

Or use a counter, something like a 74xx93 would give you the same 4 clock rate options as pair of 74s.

(I wonder about that date code too)

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

Yeah i was suspicious about the datecode too. I actually bought a few wdc 65c02s from Mouser.com a few days ago and just waiting for it to arrive.

If the chip i have is an old NMOS, is it possible to single pulse it or slow down the oscillator to about 100khz? I think it's mentioned in the 6502 Primer: Clock Generation that it's not possible.

_________________
// tinkerBOY

100kHz yes; but not single-pulsing it as in leaving it long enough in one state to poke around and look at the various lines. The NMOS 6502 apparently has registers that are similar to DRAM in that they keep their data in charges that die out quickly. WDC's 65c02 lets you stop the clock indefinitely, in either phase, without losing information or losing its place.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

Thanks.

So I built a clock on a breadboard that I can adjust and one that I can single pulse which both use a 555 timer. Both clocks work on this particular 6502 chip including the single-pulse. One thing I noticed though if I use the single-pulse clock when I leave it off for a while and single pulse it again, the outputs from the address bus do not seem to continue from where it stopped. It works fine though as long as I keep single-pulsing it and not stopping for maybe a while.

_________________
// tinkerBOY

Right. Without a clock input at a minimum rate the chip "forgets" its internal state. According to both the MOS preliminary data sheet (1976) and the MOS/CSG 1980 data sheet that maximum pluse width of either phase of Φ₀ IN is 520 ns, which means that technically you can't run it at much less than 1 MHz and expect it to work, if I'm reading this right. But I see people running 6502s at 750 KHz all the time, so perhaps the data sheet is a bit conservative?

FWIW, I do remember that the 6800 was spec'd to run down to about 160 KHz, or something like that.

If you want to single-step these CPUs, you can do it by bringing the RDY low (while continuing to give it a full-speed clock), which will stop processing either immediately or, if a write cycle is in progress, at the end of that write cycle.

_________________
Curt J. Sampson - github.com/0cjs

It's all true - but note that it's the max cycle time which is the constraint here. The general advice is to go no slower than 100kHz for reliable operation. In practice you've probably got some tens of milliseconds before charge leakage starts to flip values, maybe more: for manual experimentation this is no big deal, but reliable operation in the field is another matter. And if you're trying to debug something, you don't want an extra source of uncertainty!