[Note: The original post, which was a 6532 question, as well as the title, were overwritten with spam, which has been deleted. The rest of the topic so far remains uncorrupted.]

ahem-- it's Western Design Center-- different company altogether.

Since the 6532 was probably never made in anything faster than a couple of MHz, you could probably emulate it with a fast microcontroller. One member here keeps pushing the SX ones that do 75MIPS IIRC and has an instruction set similar to PICs' but slightly better. It would have to do a lot of instructions for every 6502 half clock cycle to do the whole job, so an actual PIC would not be anywhere near fast enough.

Being new at this, didn't think there was a difference. Sorry WDC or WD or both!

IMHO Microcontrollers are still too slow to handle that, even at high speeds. They need to monitor the address/data busses and catch the transferred data in a few ns, don't think you can get that with less than say 100MHz (which makes a 10ns cycle time, where each microcontroller opcode can possibly take multiple cycles, and then it still has to be optimal like detect Phi2 transition, read opcode, decode/execute it then read data from the databus within the 6502 cycle time; it would only get a bit better if you latch the data externally, but that would mean more hardware cost)

So I think an FPGA would be the way to go in this case. I have been programming the 6532 and emulating the 6532 in the VICE emulator, there are some tricks with the timer indeed.
But it should be doable with an FPGA. I was thinking about getting into FPGAs, but not before next year or even later...

André

Hummm. Guess you are like me, booked up for the forseeable future. Also, guess I will put this design away for a while anyhow. I would think that with 6832s going for $5-$7 a pop that this would make comercial sense to somebody with way too much time on their hands! Maybe in another couple of years when they go above $10.

This is probably a stupid question and I should finish reading the data sheet for the 6532 but ...

Isn't the 6532 functionally (in terms of features) very similar to the 6522? In terms of features all I see in the 6532 that isn't in the 6522 is 128 bytes of static RAM.

In the case of jknight6's question I imagine pin compatibility and actually controlling it will be issues but in general am I missing something?

Found this in a sourceforge project. Has RAM, ports and Timer:
http://fpga2600.cvs.sourceforge.net/fpga2600/src/riot/riot.vhdl?view=markup
I haven't synthesised it to see how many logic units it needs but its quite a small bit of code so it might squeeze into a 5V CPLD like the one Daryl was playing with for Video or an Altera MAX 7000.

You could build a small PCB to house the PLCC CPLD chip with DIP40 pins to plug into the main board.

_________________
Andrew Jacobs
6502 & PIC Stuff - http://www.obelisk.me.uk/
Cross-Platform 6502/65C02/65816 Macro Assembler - http://www.obelisk.me.uk/dev65/
Open Source Projects - https://github.com/andrew-jacobs

Don't know how to post directly to LOST's question about the 6522 compatability to the 6532. He is correct that there is no RAM in the 6522; However, not having address bits A0 to A6 also keeps the 6522 from providing the count down Timer or "T" in RIOT. The 6522, without the RAM or "R" and without the Timer or "T" instead of being a RIOT is mor of an IO.

My 2c anyway!

Response to BitWise.

This actually looks very promising. Also the need to convert it to a 40 pin DIP to be pin-for-pin compatablility to the original 6532, although nice, isn't required for my specific application as I can layout the PCB for any footprint.

In the general sense, yes, the 6522 has similar functionality (minus the RAM). However, the original post states that it must be software compatible as they do not have access to the source code to modify the access to the chips functions. With that being the case, the target device be addressed exact like a 6532. However, the pinout is not an issue.

Now, if you could rewrite the firmware, then I'm sure you could use a 6522 along with external RAM to replace the 6532.

Daryl

The 6522 has not just one, but two, timers in it, one of which is a proper count-down timer.

Strictly speaking, excepting only the RAM, the 6522 is actually more powerful than the 6532, feature for feature.

I removed the RAM from the code and compiled it. It will not fit in an XC95108 but it will fit in an XC95144. The package for that is a 100 pin TQFP. The cost of those would be quite high unless you are able to buy in bulk.

Xilinx compiler stats:
Macrocells Used - 79/144 (55%)
Pterms Used - 478/720 (67%)
Registers Used - 78/144 (55%)
Pins Used - 37/81 (46%)
Function Block Inputs Used 283/288 (99%)

With some tweeking, you may get it to fit in the 95108.

It may also be possible, to just build the timer and IRQ logic into an even smaller CPLD and just use a 6522 for the 2 8 bit IO ports. I haven't checked the datasheet for compatibility on that idea though.

Daryl

For Gottlieb, it would work out nicely since I always had that problem of 6532s being a dry resource.

If you can make a drop in pin replacement, I would be a happy camper

Tony

_________________
"My biggest dream in life? Building black plywood Habitrails"