6502.org

I agree - the 6502 choice is the clever choice! It makes good sense from an implementation perspective, although sometimes people complain about the SEC and the not-borrow.

"BCC, or "branch on carry clear," means "branch if less than" if it's after a subtraction."
Thank you! Oh! So the XORing of the carry with Sub was unnecessary. Good to know! So I will simply letch the carry signal into the status register - and my code has to analyse what it means in case of subtraction or addition.

I want to enhance my current breadboard computer to become a 65C02 (I know that this could take ages or will never be successful. But I need a target. And I will learn a lot)
This is why I asked for the microcode. In my breadboard computer I used an EEPROM for the control Logic.
(see screenshot) And I wonder if this is the same in the 65C02.

I think we know from die photos that the 65C02 structure and floorplan is very like the 6502: a large regular first-stage decode (often called a PLA, sometimes called a ROM) followed by a less regular second stage decode (often called random logic)

See here for example (blog post with video within) which we discussed here:
"65C02: Tear down, A look at the CMOS version of the 6502"

But I don't believe anyone has extracted the structure of a 65c02 in the way that visual6502 has done for the 6502.

Hi! Thanks! I am just printing out the patent he's referring to.
Exactly was I was looking for!

Patents cited on die:

http://www.google.ca/patents/US4800487
http://www.google.ca/patents/US4652992
http://www.google.ca/patents/US4876639
http://www.google.ca/patents/US4652992

Good thinking!

Perhaps a typo - you missed this one:
https://www.google.com/patents/US4876639
Edit oops, meant this one:
https://www.google.com/patents/US4739475

Note that two of the four patents are for the '816.

I should have been more clear and complete. "Carry clear" means there was a borrow because the number you started with was less than the number you subtracted. You normally start the subtraction with the carry flag set. If the number you're starting with is less than the number you're subtracting, there has to be a borrow, and the borrowed bit came from the carry flag, which is now clear. It can also means the result of the subtraction is less than 0. It works the same way for compare instructions (although you don't have to set the carry flag before a compare instruction); for example, if you start with 7 in A, and do a CMP #9, 7 is less than 9, so the carry flag ends up clear, meaning there was a borrow. Here's an example for subtracting $361 from a 2-byte (ie, 16-bit) variable, and putting the result in the same variable: If you wanted to only subtract 2, you can do that to the low byte and the use BCS to branch around the decrementing of the high byte, like this: This is all described very clearly in the manual "Programming the 65816 including the 6502, 65C02, and 65802" by David Eyes and Ron Liechty. This is a .pdf file of what is definitely the best 65xx programming manual available, and a must-have for every 65xx programmer! It starts with the basics, followed by architecture, the CMOS 65c02's many improvements over the original NMOS 6502 including added instructions and addressing modes and fixing the NMOS's bugs and quirks, and then the natural progression to the 65816; a thorough tutorial, writing applications, then very detailed and diagrammed information on all 34 addressing modes, at least a page of very detailed description for each instruction, with info on every addressing mode available for that instruction, then instruction lists, tables, and groups, of all 255 active op codes (of the '816), plus more. 469 pages.

Thank you. I just print out the last pages of the 6502 manual. This information is missing in the 65C02 manual.
And I will start to print the first 40 pages of the programmers guide. Thanks for all the tipps.

Hi,

I dont have a 10pF to connect the crystal to the 65c51.
Can I take another value?

No harm in trying different values -- anything under 50 pF, say. Or it might work with no cap at all. But if you run into quirky behavior then try to get a cap that's at least close to spec. Have fun!

Thanks!
Currently I have a 100nF connected.
I get only dots ...........

I adapted a little program to write Hello to the ACIA in a loop:

========================
.alias ACIA $4080
.alias ACIA_DATA ACIA+0
.alias ACIA_STAT ACIA+1
.alias ACIA_COMM ACIA+2
.alias ACIA_CTRL ACIA+3

RESET: LDX #$FF
TXS
LDA #$00
LDX #$00
LDY #$00
STX ACIA_STAT
LDA ACIA_DATA
LDA #%00011110
STA ACIA_CTRL
LDA #%00001011
STA ACIA_COMM

START: LDY #$0

OUTPUT: LDA Hello,y
STA ACIA_DATA
CPY #5
INY
BNE OUTPUT
BEQ START

hello: .byte "HELLO", 0
========================

single stepping looks good.

I have certainly forgotten to connect some pins of the ACIA. Or the address decoding is not correct.
So I will have fun debugging!


Terminal configuration: Cool Term - 9600 8-N-1

nF? Or is that a typo?
Could be improper initialization (the software). Or maybe the crystal oscillator is off-frequency -- or not running at all. Better if we can narrow things down. Can you 'scope what the oscillator pins are doing? Or at least tell us the DC levels (as measured with a DMM, for instance)?

Hello,
I have no Oscilloscope. Do I need one?
The Voltage at pins 6,7 is 2,65 Volts

IOW about 1/2 of the supply voltage (+5). And that is as it should be. (I'm looking for signs of trouble.) So, the oscillator is probably running.

But we're not sure if it's producing the correct frequency. A 'scope would reveal that. And maybe your DMM can. Does it have a frequency range? One with sufficient range to measure the oscillator frequency?

Please answer the question about nF versus pF.