Re: Falcon clock buffer patch V2 progress
Posted: 21 Feb 2022 02:54
Think improving the clock signal at the DMA CLKIN is paramount and your buffer solves this.
While a stock Falcon's timing is fairly lazy, there could be a condition where the CPU is ending TS before the DMA asserts TA.
That's going to cause errors.
Think the delay mod is shifting the TS signal timing riding on the clock. Why the delay works on some machines, and not others.
Using the CMOS logic, we are kind of tied to built in delays, so the buffer is adding ~5ns, ~10ns, etc. Surely, they fit somewhere in there, just at what point would be optimum for each Falcon, and how to adjust it on the user end.
It's just a theory after reading up on some Amiga documentation.
When you test your new boards, maybe you could look at those signals with your analyzer, that's the only way to see it.
In the Amiga docs, it deals with those 2 signals with respect to fast ram and the 040 CPU. It details how to program a GAL to actually widen the TS signal where it doesn't end before the receiving device can acknowledge transfer.
Terriblefire here would be the one to discuss this with, if he has time. From his post, sounded like he was taking a break, and out of respect didn't chime in on any of his discussions.
Noticed too, on the Sparrow, the DMA has its own internal clock independent of the COMBEL. They are near identical design of the Falcon otherwise in that area. It requires no clock patch, SCSI, floppy and SDMA work perfectly. Too bad Atari went to save a buck with the Falcon design.
While a stock Falcon's timing is fairly lazy, there could be a condition where the CPU is ending TS before the DMA asserts TA.
That's going to cause errors.
Think the delay mod is shifting the TS signal timing riding on the clock. Why the delay works on some machines, and not others.
Using the CMOS logic, we are kind of tied to built in delays, so the buffer is adding ~5ns, ~10ns, etc. Surely, they fit somewhere in there, just at what point would be optimum for each Falcon, and how to adjust it on the user end.
It's just a theory after reading up on some Amiga documentation.
When you test your new boards, maybe you could look at those signals with your analyzer, that's the only way to see it.
In the Amiga docs, it deals with those 2 signals with respect to fast ram and the 040 CPU. It details how to program a GAL to actually widen the TS signal where it doesn't end before the receiving device can acknowledge transfer.
Terriblefire here would be the one to discuss this with, if he has time. From his post, sounded like he was taking a break, and out of respect didn't chime in on any of his discussions.
Noticed too, on the Sparrow, the DMA has its own internal clock independent of the COMBEL. They are near identical design of the Falcon otherwise in that area. It requires no clock patch, SCSI, floppy and SDMA work perfectly. Too bad Atari went to save a buck with the Falcon design.