How is this thing ever going to catch runt pulses ? or glitches ? it almost looks like they are doing software triggering ...
that the screen freezes when you are zooming on or out, ok , but not when you change trigger level ! if i slide that trigger level up or down the machine should keep capturing .. that's how you seek out glitches in the first place. play with the trigger level until it traps something that is not normal. you do not know what you are looking for in the first place. it is an abnormality. so you need to bank on repetitive , fast and reliable acquisition to fish for it. This scope is sleeping 90% of its time , and completely dead if you do anything on screen.
they have a powerful FPGA and multicore processor. why is this not handled in the hardware fabric ?
I used to joke that Tektronix in Dutch was written as Trektopnix (looks like junk). I got bitten multiple times on their TDS540 (i believe it was a 540. it was 4 channel machine with only 2 adc's). equivalent time sampling ... what a joke. And using two adc's for 4 channels. That re-trigger (for the old school scope users : so they effectively run in ALT mode, not chop mode.). So the acquisitions are desynchronized in time. ( the sweep for channel 1 and 3 is taken first , then they throw the multiplexer and sweep channel 2 and 4. you are not looking at the same point in time. if something happens on channel two immediately after you triggered on a channel 1 event you will never see it. (that's what bit me...)
The acquisition system should run independent of the visualization system. That should be easy on that Zync... i wonder how come that is not the case. Are they using this thing just as an application processor ?
Maybe, since this is a prototype, they are still working on the FPGA logic. it could be that this will be fixed in the production machine or a later fpga build. time-to-market could have been a driver. benefit of the doubt. but it doesn't smell right.