W65C265SXB vs W65C816SXB?

[barrym95838]

porcupine wrote:

Here's my complete updated listing, using 'far' addressing...

Code: Select all

    ...
    sta f:artd0
    ...

That's an amusing coincidence for an operand, in light of the issue being examined.

Mike B.

[porcupine]

Hah, I didn't see it. Thanks for lightening my day.

[Dr Jefyll]

After reading parts of WDC's '265 datasheet and tracing into the '265 Monitor ROM listing (available here) I'm now pretty sure the '265 ACIA is unlike the 'c51, and there's no reason to suppose it has the same bug. For example it appears the ROM uses an interrupt-powered queue to output characters to the PC host -- and interrupt-driven output is where the 'c51 fails. More detail later... this is just an update.

[BigDumbDinosaur]

Dr Jefyll wrote:

After reading parts of WDC's '265 datasheet and tracing into the '265 Monitor ROM listing (available here) I'm now pretty sure the '265 ACIA is unlike the 'c51, and there's no reason to suppose it has the same bug. For example it appears the ROM uses an interrupt-powered queue to output characters to the PC host -- and interrupt-driven output is where the 'c51 fails. More detail later... this is just an update.

Man, how did you read all that? The typesetting on the ROM listing is atrocious!

[porcupine]

Ok yah I was wondering if the output there was using interrupts. And also feeling foolish for using the UART there would use the same bits. I'll read the docs for the chip on the UART section and see if I can change my code.

It would be a relief. I am hoping to make a few PCBs to stack/connect to it; a RAM expander, but also a MIDI one, which will use the UARTs. Just wish WDC had published the measurements of their PCB and all the components in it. Better yet, Eagle CAD schematics + PCB layouts for the board would be amazing, for those wanting to use this chip in their own designs.