Broken ini tests

[tfcollins]

For FMComms5 ini tests two capture windows are launched during test. One is done by the ini file manually, the second appears when doing calibration. However, after the calibration window launches remaining capture windows cannot be resumed. This is only fixed by running a fru_connect which requires user interaction.

To repeat run standard FMComms5_test.ini, which should fail after: https://github.com/analogdevicesinc/iio-oscilloscope/blob/9b9a4410be713a3ce2d72b5bac07f225ca33aef7/profiles/FMComms5_test.ini#L240

My guess is that other tests are broken as well since FMComms3 does similar things. This likely will require the frequency counters which are connected to over SCPI to fully check the tests.

[dNechita]

I couldn't find the issue you've mentioned. What do you mean by fail after 'calibrate = 1'? Is there an error message? Or does something get stuck or crashes? Can you provide more details about this? What is expected to work but doesn't?

[tfcollins]

From what I recall it gave a test failure. To be more specific I was using the production script https://github.com/analogdevicesinc/linux_image_ADI-scripts/blob/master/test_fmcomms5.sh running on the board itself.