The machine was in a hell of a state when I bought it on ebay but simbo brought it back to life!

Moderators: Mug UK, Zorro 2, Greenious, Moderator Team
Have added this Frank... but can't make out the number, I assume a 'C' is hidden under that component -Frank B wrote:Here's one of my STEs. I don't think we have a picture of this type yet. It has the integrated blitter and square DMA chip.
The machine was in a hell of a state when I bought it on ebay but simbo brought it back to life!
Hi there ppera. (since I can't PM, this will have to go here...)ppera wrote:This may help about knowing diverse revisions:
But SofiST may make a replyinsanity wrote: Ppera left the forum years back, so I would expect any reply - Sorry!
I believe this changed between GLUE -38 and -38A. But I'm not so familiar with GLUE -20 revision. Those -20 parts are quite rare and even strange.Dio wrote:In particular, I'm interested to determine which Glue revision changed the PAL top border timing from early to late. The even earlier ST in this thread has a different Glue revision (-20) and so it might be that one, but I'm looking to rule the -38 in or out if I can.
That is not a problem. If you happen find any of the -20 chips, I would take care of them.Dio wrote:Looking at that old machine of his with the -20 and the kludge on the ras / cas lines it looks like some patches might be needed though...
It is a revision code, not exactly a consecutive number. Why they used -20, and then they sort of "jumped" to -38, I have no idea. But it doesn't suprise so much, I've seen other cases like this. It is possible that there is a process difference. But again, I can't say too much about those "-20" chips.Because all the chips turned from -20 to -38 at the same time (and it's almost impossible that they all needed the same number of design revisions) it seems unlikely that suffix is a pure revision number ...
I agree that there aren't so many versions of the chipset. I was saying something similar long ago. I think the main problem related to overscan coding was wake-ups. Not only that the different wakeups introduce more timing variations, the whole thing wasn't well understood (it was actually barely known) at the time. Main clock frequency is a minor issue. But yes, we know that some demos break on some (mostly rare ones) crystals. Not sure what you mean by "clock nudger" ?One of the things that's intriguing me most is that given the reported difficulties making border removals work on a very wide range of STs - always allegedly because Atari made lots of changes to Glue, MMU and Shifter - there seem to be very few revisions. ... My current theory is that the major differences in timing are to do with the large different master crystals and the presence or absence of the clock nudger
The clock nudger is the circuit present on STMs that tweaks the master clock based on the colour clock. I'm certain that it's purpose is to create a phase relation with the colour clock to avoid the dot crawl issue that affected the Spectrum (it used a different crystal for the colour clock and master clock, which is prohibited by the PAL / NTSC standards). I'm not exactly certain how it works, though, and I'm still investigating if it produces any detectable behaviour change in the system.ijor wrote:I agree that there aren't so many versions of the chipset. I was saying something similar long ago. I think the main problem related to overscan coding was wake-ups. Not only that the different wakeups introduce more timing variations, the whole thing wasn't well understood (it was actually barely known) at the time. Main clock frequency is a minor issue. But yes, we know that some demos break on some (mostly rare ones) crystals. Not sure what you mean by "clock nudger" ?
You sir are a gent. I'm not sure if it's more valuable for you to send them to ijor or myself though. It is probably worth multiple people having a look in order that we can cross-check our conclusions?jokker wrote:I still have those chips Dio and I can send them to you if want to check them out. I certainly have no issues contributing back to this community!
Just PM me an address and I can mail them off (and package them up safely!)
I'm not expert in this kind of circuits. But as far as I understand, this is some sort of PLL like circuit for locking HSYNC to the color clock. It will, of course, affect the master clock. But I don't think this will be very significant for our purposes.Dio wrote:The clock nudger is the circuit present on STMs that tweaks the master clock based on the colour clock...
Yeah, I forgot about that. Guess I'm getting older ...(I think you postulated in the past that the big clock frequency change explains the "MFP latency change" that the Alive overscan document suggests
Oh, now is you the one who seems to be getting olderI in turn are slightly confused by the use of the term "wake-ups" - what do you mean by those?
I don't mind at all you checking it first. But I'm not sure it is correct to abuse the generosity of jokker. I don't need (and I don't want) the motherboard, just the chipset. Do note that I won't be able to pass the chips later to you. They will be destroyed as part of the analysis process that I intend to perform.I'm also very interested in that early motherboard in order to work out what the kludge is and hence if it's required for the early chip.
Correct! If I remember correctly you even provided a program for thatijor wrote:Oh, now is you the one who seems to be getting olderI in turn are slightly confused by the use of the term "wake-ups" - what do you mean by those?Because I'm (almost) sure we talked about this, at least, once.
Wakeups refer to the different phase relationships between the GLUE video process, and the MMU DRAM process. The relationship is established at power-up time and is not affected by reset. But it could change across different power-up cycles on the very same machine. Hence the term "wake-up".
Ah, right. Yes, I remember that discussion, although I don't remember used the term for it at that point.ijor wrote:Oh, now is you the one who seems to be getting olderI in turn are slightly confused by the use of the term "wake-ups" - what do you mean by those?Because I'm (almost) sure we talked about this, at least, once.
Wakeups refer to the different phase relationships between the GLUE video process, and the MMU DRAM process. The relationship is established at power-up time and is not affected by reset. But it could change across different power-up cycles on the very same machine. Hence the term "wake-up".
Absolutely. Even offering the chips is undoubtedly a generous act.But I'm not sure it is correct to abuse the generosity of jokker.
I definitely don't plan to destroy the chips - just sub them in another board and run the logic analyser on the system and my library of chip testers on the machine to check for any differences in timing. If I was taking a belt-and-braces approach I'd like to verify the pinout hadn't changed to verify there's no danger from doing this, although I view that as unlikely. Of course, it's possible that they simply just won't function in a later motherboard.I don't need (and I don't want) the motherboard, just the chipset. Do note that I won't be able to pass the chips later to you. They will be destroyed as part of the analysis process that I intend to perform.
Err - looking again, yes. OK, so the motherboard is not relevant, if I don't bother to check the pinout.What kludge are you talking about? I suspect you are looking at the wrong motherboard.