Zilog Z8S180 problems - solved
Some of you may recall that about 3 weeks ago I posted the following:
------------------------------------------------------------------- I seem to be unable to access the new registers on the Zilog Z8S180 CPU, things like the Clock Multiplier register, the additional DMA register etc. When I try to write to these registers my writes seem to be ignored and when I read them back I read FF from most 00 from one. Anyone else having problems with this chip or know the secret code to make it work? :) For all the world it's behaving as if it were a Z180 rather than a S180. I have tried two different chips, one date coded 0106 and the other 0348 - same problem with both.
-------------------------------------------------------------------
The solution: It would appear there are two different mask versions of the Zilog Z8S180 currently in production - Rev K which is purely a static CMOS version of the part and otherwise identical to the Z180 and Rev N which is both a static CMOS part and has the additional features the datasheet for the Z8S180 describes. NB. The only way to tell which part is which is that the Rev K version has "SL1960" printed on the package whereas Rev N does not; although the number is not printed as a prefix or suffix to the part number but on another part of the package in the same manner as a date code.
Nowhere on Zilog's web site is this information available. (Although it might be now!) The latest datasheet for the part (off the website) makes no mention of it. In other words unless one somehow "knows" this, by telepathy perhaps, one doesn't have a bloody clue why the damn chip won't work as the datasheet says it should!
I would have hoped Zilog's tech. support would have immediately known this was a mask problem and alerted me to it - however they didn't appear to have a clue.
Interestingly even "Bill A" of Softools (who kindly responded to my original post) appears to be unawares of this issue and he's been writing tools for these parts for years.
In Zilog's defence I will say that once I alerted senior management to my problem - sparks flew and the issue was resolved in 24 hours.
Mike Harding