[Discuss OpenCPI] Single bit errors in output of fsk_filerw on Ettus N310

From: Munro, Robert M. <Robert.Munro_at_jhuapl.edu>
Date: Thu, 10 Oct 19 16:20:08 +0000

The performance of the fsk_filerw application running on the Ettus N310 is being examined as a functional verification of integrated software and hardware using the OpenCPI framework runtime for loading and execution. The application runs without any errors output and completes the operations with the same binary output size at all times. The expected output file has been extracted from the input file, opencpi/projects/assets/applications/FSK/idata/Os.jpeg, by removing the 242 byte header and 2 byte tail. Binary comparison of multiple runs shows that there are randomly placed single bit errors in multiple places in the output file.

The framework and application were built for the Matchstiq_Z1 using the OCPI 1.4 baseline and the output of the application matched the expected result over multiple runs.

Attached are a golden expected output and outputs with single bit errors in varying numbers, locations, and conditions generated by running the fsk_filerw application on the N310. The application was run using the command 'ocpirun app_fsk_filerw.xml'. Runs were performed in a mixture of immediately following power cycles and repeatedly to see if it affected performance. The files were generated in the following manner:

- Power N310

- Generate run7

- Generate run8

- Reboot

- Generate run9

- Reboot

- Generate run10

- Reboot

- Generate run11

- Generate run12

- Reboot

- Generate run13

Has this kind of issue been encountered before while using the framework? If so, what were the cause and resolution taken? What steps are necessary to debug the performance of this reference application?

Thanks,
Rob


Received on Thu Oct 10 2019 - 16:20:08 CDT