we see that the chip is clocking to much. In other words we put in 64 pulses a counter says 65 or 66. If I view the signal on the oscilloscope I see a nice monotonic rising signal and with the GTL2003 I get rise times of 100ns. This doesn't work....
You're describing absolutely classic symptoms of poor impedance matching. What happens is:
- fast edge is launched by the driver into a transmission line, which could be a PCB trace, a wire, or the lead frame of an IC... or some combination of them.
- the edge arrives at the receiver, which causes the device to clock.
- because the receiver isn't correctly terminated with the characteristic impedance of the transmission line, the wave reflects off the receiver and starts travelling back up the transmission line towards the transmitter again.
- it then bounces off the transmitter, and travels back towards the receiver again. When it arrives at the receiver for the second time, depending on the relative magnitudes of the incident and reflected waves, and the 0/1 threshold at the receiver, it can cause a second clock transition.
This is a very well understood topic, and there's a set of 'rules of thumb' which will help you get the circuit working even if you don't have access to a proper high speed simulation package. You need to fully understand series and parallel termination, the concept of a characteristic impedance, and the importance of a solid, unbroken ground plane on your PCB.
Once you've researched these topics, you should have a feel for the numbers too. It's all but impossible to actually see these effects with a scope, and once you consider the effect of the scope probe's capacitance, the reason why should become obvious.