I've been doing some more testing for cryptodad.
Tonight I was testing his clock generator code for the Raspberry Pi.
Initially I tried with the Hantek 'scope but knew I was pushing it as the 'scope is only rated for 100MHz and the GPIO clock is above that.
With his new test software I hooked up the Hantek and ran the test. I couldn't get a large signal but the 'scope said that it was 129.601 MHz. I didn't trust that figure though. So, I decided to bring out the Tektronix 'scope and hope that it would boot properly tonight.
After setting up I pressed the power button and after about two minutes it said that the self-test had passed. Phew!

- IMG_3734.jpeg (261.05 KiB) Viewed 958 times
Hooked up the probe, hit the "auto setting" button and...

- IMG_3733.jpeg (214.54 KiB) Viewed 958 times
Yep, a nice signal and precisely the same frequency measured as on the Hantek. So, the Hantek can be trusted.
Running the test code showed that when the Pi was accessing the PiStorm it created quite a bit of jitter on the clock, over 10%, which is rather a lot! And it's noisy too.

- IMG_3736.jpeg (218.03 KiB) Viewed 958 times
Still, I don't think that is likely to be the cause of the stability issues, but it is concerning how much possible cross talk is going on.
Testing his original code, if run without the --clock option his program thinks that it's generating a 125MHz clock but in fact it's 187MHz, way outside the range Broadcom state is permissible to work reliably. With the "--clock 80" setting the clock signal is precisely 125MHz.
Intro retro computers since before they were retro...
ZX81->Spectrum->Memotech MTX->Sinclair QL->520STM->BBC Micro->TT030->PCs & Sun Workstations.
Added code to the MiNT kernel (still there the last time I checked) + put together MiNTOS.
Collection now with added Macs, Amigas, Suns and Acorns.