Hi everybody:
I have just received an old source file which uses an old 65 chip: G65SC22 from California Micro Devices. I find several assembers for the source code. Neither can do successfully. From some guys help, it seems Frank A. Kingswood's assember is popular. However, it gives the following errors:

1394: lda #high timint
"mx18.src",1394 : Syntax error.
1638: adc #low inpbuf
"mx18.src",1638 : Syntax error.
1641: adc #high inpbuf
"mx18.src",1641 : Syntax error.
1715: adc #low inpbuf
"mx18.src",1715 : Syntax error.
1718: adc #high inpbuf
"mx18.src",1718 : Syntax error.
1771: adc #low outbuf
"mx18.src",1771 : Syntax error.
1774: adc #high outbuf
"mx18.src",1774 : Syntax error.
1859: adc #low outbuf
"mx18.src",1859 : Syntax error.
1862: adc #high outbuf
"mx18.src",1862 : Syntax error.
File mx18.src, Line 420 : Undefined label Ack
File mx18.src, Line 1394 : Undefined label high
File mx18.src, Line 1638 : Undefined label low
File mx18.src, Line 1650 : Undefined label Xoff
File mx18.src, Line 1694 : Undefined label Xon


Can anyone help me?
Which assember should I use?
Thanks!!

The assembler does not concern itself with what I/O chips you use. The '22 is an I/O chip, not a processor. BTW, it is still being made by Western Design Center, although in 16MHz, not 2 or 4MHz. There is no end of production in sight.

I'm not familiar with the assembler you mention, but if you're trying to do what it looks like to me, most assemblers would want something like LDA #>timint, not lda #high timint, assuming timint is a 16-bit constant and you want to load its high byte into the accumulator.

The source code does indeed look a bit strange. In fact the syntax for 6502 assembler is not 100% standardised. Your

lda #high timint

is probably what normally is written as

lda #>timint

what is the syntax I use in the assembler I have written myself

This then means that somwhere the address "timint" is defined as a 2 byte integer value and the high part of this 2 byte value shall be loaded to the ackumulator with immediate adressing.

Try to change all these "high" and "low" to ">" and "<". [/code]

Sorry, I now see that Garth wrote exactly the same already!