Hello all,

I've been trying to build a very simple 65C02 system as a learning project, but I must be misinterpreting or misunderstanding something.

My goal is to use a WDC 65C02 to run a program stored in a 28C256, that uses a 74HCT373 to light eight LEDs in sequence, D7 to D0 (i.e. one LED lit at a time). What I get instead is each LED lighting in sequence and staying lit.

I've attached schematics for the main portion and for the memory decode section. My apologies if they are confusing. I've omitted the LEDs, power connections, and clock as they are trivial.

Schematic notes:

1. The address bus joins the CPU to ROM via A0-A7. The upper eight lines are not used and the corresponding lines on the ROM chip are tied high, as the program is entirely contained in the highest page ($FFxx).
2. I'm cheating a bit with memory decoding by using RWB instead of A15 to determine whether the system should select ROM or the '373. My reason for doing this is because the program reads only from ROM and "writes" only to the '373.
3. CLOCK is generated by a oscillator-to-74ABT74 circuit. Frequency is 0.5 MHz.
4. RESET is controlled by a DS1813.
5. OUT_0-OUT_7 are just LEDs, each with a 470 Ω resistor.

(Btw, I'm using TTL because those were the parts I had. Further development would use 74HC logic.)

Here is the program I wrote. I used straight machine code because the code was small enough (33 bytes) to allow me to put off learning an assembler. But I've hand-assembled--accurately, I hope--the bytes into opcodes and operands:

My first thought was that the ROR was doing sign extension, but the WDC programming manual indicates that that's not the case. I feel like I've missed something obvious; would one of the experienced users have time to critique my work? Thanks in advance.

Hello, TomC. One thing jumped out at me, and that's these last two opcodes. Is this a transcription error that occurred when you wrote your post? Or do you really have $FC in there? The opcode for JMP abs is $4C, of course, just as you've used earlier in your code.

( $FC is undefined but is know to behave as a 3-byte NOP. So if the code really is as shown then these last two instructions do nothing, and the CPU will happily proceed to execute whatever follows -- FF's or zeroes or whatever other junk happens to be in your ROM above the intended program. )

Otherwise I've noticed no actual errors so far, although I or others may suggest improvements later.

cheers
Jeff

_________________
In 1988 my 65C02 got six new registers and 44 new full-speed instructions!
https://laughtonelectronics.com/Arcana/ ... mmary.html

BIT # 00 will always set the zero flag. I think what you wanted was BIT #$FF. (BIT updates the zero flag according to the result of a logical AND between A and memory. You had zero in memory, so the AND result will always be zero no matter what's in A.)

BTW, using BCS or BCC is a more direct way of determining whether the ant has marched all the way to the carry bit.

Quick 'n dirty. I like it.

BTW your schematic shows /OE of the 373 tied high but that'd yield no LEDs, so I'm guessing it's really tied low.

_________________
In 1988 my 65C02 got six new registers and 44 new full-speed instructions!
https://laughtonelectronics.com/Arcana/ ... mmary.html

Please post the entire schematic...nothing is trivial when something isn't working. Also, I suggest you replace the 74ABT74 with a 74AC74 or 74AHC74. The 74ABT series generates TTL-level outputs, but if operating the 65C02 on 5 volts, a clock signal that swings between ground and Vcc (5 volts) is required.

Mixing TTL with CMOS can cause a variety of problems due to the two logic types having different logic 0 and logic 1 thresholds.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

I just double-checked, and I do indeed have 0xFC in those two spots--thanks for catching that. I had even hooked a cheapo 8-input logic analyzer ($20 from sparkfun) and found/ignored those two opcodes. That makes me wonder why I even got the results I did!



Thanks again--I'll review those instructions and change the program. And you're correct: the schematic is incorrect wrt /OE on the 373.

Btw, is there a way to branch backwards with BNE or BEQ?



Sure, BDD. Here are the other 3 portions of the schematic. I'm not sure if the oscillator can symbol is correct but it is wired correctly on the breadboard.





I see now that I forgot to include the bypass caps for the CPU and the ROM in the schematic. They are there.

As for TTL, I bought the ABT because it has the 5ns slew rate that WDC's datasheet specifies. I know about CMOS/TTL discrepancies but it was truly just a case of the parts being on hand. I made sure to apply Garth's "Murder at a Megahertz" maxim to tell myself it was ok.

(I picked up the 74HCT373 10 years ago at a rural Radio Shack that had a treasure trove of old parts. The elderly owner told me, "I just leave 'em on the shelf until they sell." He had a large inventory of tubes/valves, phonograph needles, components in the old blue Archer packaging (and some even older), several TRS-80 model IIIs...I thought I'd walked into a museum. I drove past a year ago; the building now houses a lawn care business. Sic transit)

Oh, wait--I see now how backward branching works. Always check the reference guide...

_________________
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?

It worked! It worked it worked it worked! :happydance:

I don't understand why it didn't work the way it did...er, didn't?...before, but changing the BIT operand and correcting the JMP instructions did the trick.

Next step will be to construct/acquire a better programmer (currently using Ben Eater's Arduino-based device on a breadboard), add a 65C22, and hang the 373 off one of the ports.

Thanks Dr J and BDD!

Hurrah!

74AC hardware easily meets the 5ns slew rate, but unlike 74ABT, swings rail-to-rail. I used 74AC logic in my POC V1 series—POC V1.1 will boot at 15 MHz, so it's clear 74AC logic is sufficiently fast. POC V1.2 (currently on the drawing board) will also be 100 percent 74AC discrete logic.

Glad to read that you've got your unit working.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!