Re: [Fuego] Time sync

"Bird, Tim" <[email protected]> Wed, 27 Apr 2022 16:58:09 +0000
Newsgroups dev.linux.lists.fuego
Message-ID <BYAPR13MB2503F27C4A905513CE8D8378FDFA9@BYAPR13MB2503.namprd13.prod.outlook.com>
> -----Original Message-----
> From: Muk Anc <[email protected]>
>=20
...
> I would also like to pose another question while we are at it.
>=20
> I have an ADC on our DUT. I would like to read this ADC every second whil=
e a batch test is running. The batch test runs around 20 individual
> tests. I would like to start reading this ADC and show its readings on th=
e console (I use the FTC command to trigger the batch test) at the
> beginning of the first sub test, and stop when the batch test finishes, e=
ither successfully or due to a failure of a sub test.
>=20
> Currently, I have updated a few of the subtest's test script to additiona=
lly read the ADC and echo the output, but I can do this only for tests
> that run for a long period of time, e.g. memtest. While memtest is runnin=
g in the background, I keep reading and outputting the ADC every
> second. What would be the best way to decouple this?

I have a few questions that may help me recommend an appropriate solution.

Where would you like the stream of values of the ADC reported?  Do you want=
 to see them interleaved with
the test output for the sub-tests of the batch test, or would it be suffici=
ent to collect them into a file at the
end, and just emit the list of ADC values?  You could possibly timestamp th=
em on the target in order to
do post-processing to correlate the values with the test executions, if the=
y are somehow related.

Or, you could do both - both emit them and simultaneously put them to a fil=
e on the target.

If you want a long-running process to execute and collect data while other =
things are happening
on the target, then I might have some code that would be useful for you.  S=
ome years ago I started
work on a parallel task feature to allow for multiple tests to execute at t=
he same time on a board.
The intent was to allow for doing things like measuring power, or doing fil=
esystem benchmarks, while
executing a stress workload on the board.   I'll have to see if I can find =
this work, which I shelved, but
which might work for your requirements.

The aspect of getting the results into either the console log of the batch =
test, or into the testlogs of
the Fuego sub-tests, is a bit trickier.  Let me know if that's what you hav=
e in mind, and we can discuss
options.

 -- Tim