TF1260 + Mediator
Posted: 12 Aug 2020 19:41
It been a royal PITA but i have managed to get the Mediator working with the TF1260. Notes for any other hardware designers needing to figure out why your card goes nuts when a mediator is installed.
Firstly Mediator accesses long words at odd addresses.. My card wasnt happy with that originally but its legal on an 020 system but i guess not much else does it. So it might be a surprise use case.
Secondly Mediator has occasional very very short DSACK pulses. Nasty ...
Finally Mediator occasionally (not always) asserts DSACK1 and DSACK0 up to 15ns appart... just enough to fall either side of a clock edge.
This last one was a kicker... it meant the bus state machine thought it was acknowledging a byte then suddenly that cycle turned to a long ack.
I was able to find it relatively quickly with the logic analyzer.
I asked for help from Elbox about this but all i ever got told was PSU, PSU etc and then finally they stopped responding. In short i think the CPLDs on Mediator are a bit of a dirty hack. If your board stops responding in the middle of something i'd lay a bet its because of this.
Firstly Mediator accesses long words at odd addresses.. My card wasnt happy with that originally but its legal on an 020 system but i guess not much else does it. So it might be a surprise use case.
Secondly Mediator has occasional very very short DSACK pulses. Nasty ...
Finally Mediator occasionally (not always) asserts DSACK1 and DSACK0 up to 15ns appart... just enough to fall either side of a clock edge.
This last one was a kicker... it meant the bus state machine thought it was acknowledging a byte then suddenly that cycle turned to a long ack.
I was able to find it relatively quickly with the logic analyzer.
I asked for help from Elbox about this but all i ever got told was PSU, PSU etc and then finally they stopped responding. In short i think the CPLDs on Mediator are a bit of a dirty hack. If your board stops responding in the middle of something i'd lay a bet its because of this.