-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Short (less than a frame) I2S loopback discontinuity #188
Comments
In this capture the last good sample value on channel 0 is 371643 = 0x05abbb which is:
The next sample value is 371646 = 0x05abbe, which is:
There are then zero values on all channels for remainder of IN 59675 (8 samples), and first 13 samples of IN 59683 (then correct ramp from sample value 0x05abbe) |
Analysing the lengths of packets in the complete five minute trace:
Gap between pairs of consecutive 736 len packets should be 20, so 19x704 then 1x736, ... OUT transactions had similar results in terms of packet lengths. |
Adding a conditional exception on outUnderflow being true here fired during my latest test run. |
Just to clarify, this is with Theyscon driver, correct? |
Yes |
xk_316_mc configs 2SMi8o8xxxxxx and 2SSi8o8xxxxxx have seen short discontinuities which are shorter than a frame's worth of samples. Collecting the failures over a week, this has been seen on the Windows 10 and 11 agents, but not on the Mac. It happens after about three minutes of the output stream, so isn't seen in short tests.
Seen often at 176400, and once at 88200.
Discontinuity from xsig
There are 21 zeros, which is shorter than the 22 or 23 samples per frame that we would expect at 176400.
The text was updated successfully, but these errors were encountered: