Actually, I don't like to use the phone for anything. I don't like the random interruptions, I don't like the always-inconvenient interrupt-driven nature of the thing. I much prefer the way email works. I send a message when I have a need to do so, and I see the reply when it's convenient to look. That way I don't have to give someone the "bum's rush" when I've got someone else here discussing something that might be affected by what he hears.
Moreover, it's MUCH more convenient to read what someone's written down, rather than listening to the hemming and hawing over something that hasn't been sufficiently thought out yet. It's bad enough wading through a disorganized, "stream-of-consciousness" written piece. Often with dreadful errors in syntax, grammar, and orthography, indicating that the fellow doing the writing doesn't see the effort as important enough to do it right.
If WDC's IP 650x core were competitive in performance, to the micrcocontroller cores already out there, it would be wonderful, but since it isn't ...
My problem with them has been their outright evasion of questions like "what do these things cost?"
I can't go to my clients, who still use 6502 applications I designed for them in the late '70's - early '80's timeframe, with the notion of upgrading their system with a software peripheral that will only run on a fast part if I can't tell them what it will cost. Estimated annual volume depends heavily on what it will cost, and I can't speculate. Moreover, I've no idea whatever what the WDC folks think their product is worth. I'd be really embarrassed if I told them it cost twice or three times what their current 4 MHz CMOS part (running at 5, BTW) when it's really 20 or 30 times that. I've asked for budgetary pricing on more than one occasion, only to get no reply at all.
As a consequence, I now have a couple of clients using current-generation 80C5x-core based products also of my design, that would have worked fine with their previous hardware and a faster 65C02. The 80C5x core does have instructions that allow for fairly fast table lookups, in fact faster than the 6502 at the same cycle rate but all bets are off if the 65C02 is running at, say, 15-20 MHz.
CPLD's and FPGA's, as well as ASIC's are large enough and fast enough that one can build a CPU into one with a substantial internal RAM or, alternatively a port to external RAM, that one should be able to run a 2.5 ns cycle given fast enough external RAM. The crux is the ALU design. A 650x core is simple enough that it can be small, and, with an efficient and efficiently used ALU doesn't have to consume a lot of logic. Since the stand-alone CPU can take as many as 8 (?) cycles to execute a single instruction, depending on core version and addressing mode as well as page boundary associations, even a very fast one takes quite some time to do the slowest things it does. It's probable that one implementing a core in hardware would modify his design to facilitate the operations that will most impact his task. That's an option you don't have with the fixed CPU design.
My own interests don't run as far as the 65816, since it's single-sourced. Complete Pentium or super-x86 board sets on PC-104 format boards are so competitive that it's hard not to use them. Software for almost anything already exists, so unless the CPU core is very fast indeed, it's likely I'd be inclined to buy a ready-made solution.
The bit with WDC has been that I'm not only P*SSED because my questions have gone unanswered and I've, as a result, lost competitive opportunities, but I'm disappointed at not being able to extend the life of my old designs when they're so inherently capable of surviving another decade, and simply because they, WDC, have been unhelpful.
Uli
|
|