8 May
2019
8 May
'19
9:50 a.m.
Hi,
On Mon, 6 May 2019, Guennadi Liakhovetski wrote:
What I am seeing here is, that I get traces but then the logger immediately terminates instead of waiting for further data like e.g. on Up^2. Is this an intrinsic limitation on BYT?
please update your sof-logger binary to the latest one. I've made a few patches that will probably help. Specifically in trace mode (-t), if sog-logger gets an eof, it will reopen the file node.
This doesn't explain why you started seeing this on BYT, but might help nevertheless. The patches help on UP^2 as well to keep tracing going over S3 suspend/resume cycles.
Br, Kai